Re: [Flashforth-devel] ...transition from PIC18 FlashForth to dsPIC33E, can I buy a clue?
Brought to you by:
oh2aun
From: Mikael N. <mik...@fl...> - 2015-03-22 21:57:46
|
<div style="font-size:10pt;"><p style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;">The pic33e series has its own config file.</p><p style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;">P33e_config.inc</p><p style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;">That would be a good place to start;-)</p><p style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;">Mike</p><div><signature_tag><p style="margin-top:0;margin-bottom:0;">Sent from my LG Mobile</p></signature_tag></div><p id="last_enter" style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;"> </p><p style="margin-top:0;margin-bottom:0;">------ Original message------</p> <p style="margin-top:0;margin-bottom:0;"><b>From: </b>craig bair<dab...@ya...></p><p style="margin-top:0;margin-bottom:0;"><b>Date: </b>Sun, 22/03/2015 22:53</p><p style="margin-top:0;margin-bottom:0;"><b>To: </b>fla...@li...;</p><p style="margin-top:0;margin-bottom:0;"><b>Subject:</b>[Flashforth-devel] ...transition from PIC18 FlashForth to dsPIC33E, can I buy a clue?</p><p style="margin-top:0;margin-bottom:0;"> </p><pre>I dearly love the ease of development and performance on PIC18F chips, especially the xxK22 series. I've been handed a dsPIC33EP128MC202 to drive a couple of sensors so of course the first thing I think of is "Why, toss FlashForth on it. This is what it's for." It didn't take too long to hook it up to the PICkit3 after finding the default PGMCLK & PGMDAT pins (even though they're not called that), find all of the power and ground pins scattered all around it, and figure out the right config file and how to invoke it with the trusty old MPLab-IDE (8.92 still works appearently). I did some scrounging through the widely scattered Microchip Docs, I decided that the settings called out for the dsPICFJ129GP802 at the top of the p33_config.inc file should be a close enough starting point. It assembled up, programmed up with no arguement, and it just sat there. Since it's quite likely that I don't understand the pin-mapping mechanism, I started around the pins with a scope looking for the Console Output hitting the MCLR and watching for a few seconds and not seeing anything that looked like a UART. Ok, next step... Since the FOSC stuff looks like what the dsPIC33E FSM calls out for using the internal FastRC with PLL, I'm guessing that I don't need an external oscilator and I begin playing with the IDLE MODE and CPU LOAD settings to try and get the CPU LOAD LED to give me a heartbeat like I did when learning my way around the PIC18-s. No joy in Mudville, I'm not seeing any activity on any pin. As usual, when I get desperate enough to post to the mailing list I've concluded that I'm missing something basic that I probably should see, but it's sitting in my blind-spot. I'm open to suggestions as to what to try. Can anyone help me get this thing off of ground zero? (The first chip is always the hardest...(grin)). Oh, if it makes a difference, I'm using the flashforth-master.zip that I downoaded from Git-Hub on Nov 23, last year. Thanks for your attention, craig bair ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Flashforth-devel mailing list Fla...@li... https://lists.sourceforge.net/lists/listinfo/flashforth-devel </pre></div> |