Re: [Flashforth-devel] ...transition from PIC18 FlashForth to dsPIC33E, can I buy a clue?

[craig b. <dab...@ya...>]

Mike,
Thanks again for the pointer, getting the right config file DOES make a difference (grin).
I've gotten the 33EP to program with a couple tweaks.  The flash size number didn't make sense to me so I cut the example in half on the theory that a 128 chip should use half of what was called out for a 256.  Memory size, ditto.  Since the baudrate was set down to 9600 for the console, I switched it to xon/xoff to simplify trying it out.  I also activated the CPU-Activity LED as an indicator that the processor was running.

Eventually, it proved to be a serious issue with a cheap breadboard that was causing much of my problems, but now that it appears to be running, I've hit another snag... I found the console pins with my trusty 3v-logic-FTDI cable and a systematic test of available pins and had communication with it.  Then I changed the baud-rate, re-assembled, and reprogrammed it and it stopped running entirely.  I put the code back and tried again, still nothing, not even the  CPU-blip.  I probably should have dumped the flash to a hex-file for reference, but appearently I got overconfident...  I can still read avd write it through PGEx3 pair so I'm still playing with it.  

Reloaded a fresh copy of p33e_config.exe and started tweaking from scratch.  Do these config bits look right?  All those Zeros bother me.

(attaching file)

Thanks for your patience,
craig