Other Parts Discussed in Thread: CONTROLSUITE
I experience same problem that below post by "Mitch Hanks"
http://e2e.ti.com/support/microcontrollers/c2000/f/171/t/286817.aspx
-------------------------------------------------------------------------------------------------------------------------------------------------------
Posted by Mitch Hanks on Nov 11 2013 12:29 PM
If I reprogram the C28's flash memory with the Flash version of adc_soc_c28 and run out of flash, the jump to boot code does not happen. Also, when I go back and load the Ram version of adc_soc_c28 and run it, no jump. When I load my code again and run it, the problem starts happening again. Something is apparently getting programmed in non-volatile memory that creates this situation and then continues to affect whatever code is running (at least it affects my code, and the controlSuite adc_soc_c28 code) until it is overwritten.
I am apparently using 'experimental' parts. Not sure why that is what I am getting when I purchase an F28M35 ControlCard but that is what I got both times.
----------------------------------------------------------------------------------------------------------------------------------------------------
Posted by Mitch Hanks on Nov 11 2013 18:12 PM
The adc_soc_c28 example code is v201.
I don't have a consistent cause and effect relationship tracked down, but did see the following:
When I am seeing the problem regularly (a few seconds into runtime), I can put a while(1) statement a few lines past the start point of my code. When it is after an InitAdc1() call, I see the jump to boot rom. When I put the statement before that call, I don't see the problem. That is why I chose to run the controlSuite example code adc_soc_c28 and verified that I would see the problem with that code running. This is all with code running out of RAM. When I load adc_soc_c28 into flash and run it, the problem goes away (no jump to boot rom). When I switch back to RAM with adc_soc_c28, I still don't see the problem (as if writing to Flash memory got rid of whatever my code did). When I run my code again (out of RAM), it soon starts exhibiting the problem again.
Thanks for your help,