[Flashforth-devel] status of Pic18FxxK42 FF-port?
Brought to you by:
oh2aun
From: craig b. <dab...@ya...> - 2019-01-16 16:21:58
|
Hello fellow forth-fanatics! It's been a while since I've made a nuisance of myself here in the mailing list, but I grabbed one of the Xpress PIC18F46K42 boards from Microchip on year-end clearance and found myself wondering how far the port Jordan was working on got. I'm supporting some lab-tool boards that run FlashForth on 18F46K22 chips and its looking like the K22-s are getting pushed back into "Relic" status in favor of the K40-s and K42-s. I expect to have to migrate at some point, so I should probably get started... My experience with Git-Hub is limited to bringing the url up in my browser and doing a html download of the current flashforth-master.zip file then unpacking it to a subdirectory on my hard drive. There, I frob with MPLab-X until things assemble and program up a chip to see if I did it right. (I seriously miss the old MPLab... It worked so well with MPAsm for its last decade.) Can I beg a few clues about what to look for in that Git-Hub Rat's Nest to locate anything relevant to the new PIC18-s? There doesn't appear to be a config for any of them in the master archive (ok, I'm half-blind but nothing greps up). I notice in a quick scan of the chip-specs that the 18FxxK40-s appear to be less of a change from our old standbys than the 18FxxK42-s are. Perhaps they’d make a good interim migration step. Either that or do a K42 first and have an easy step back to handle the K40... Just random thoughts... I’m wandering badly so just let me say that any pointers or suggestions will be greatly appreciated and a big “Thank You!” in advance. craig bair –- binary behaviorism for non-deterministic processors –- --foreword into the past-- |