• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 244 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AWR1642BOOST: Application error when booting from flash

Sara Marina Salvador
Intellectual 410 points
Part Number: AWR1642BOOST

Hi, 

I am having this big issue ... starting from the non-os application example, I removed some parts of the code. The new code runs ok when I launch it from code composer.

When I flash it to the board everything is ok as well. BUT when I remove from the DSS code the definition of a function which is NOT USED anywhere in the code, or if I just simply remove a few lines, the application starts correctly but then the DSS gives a "frame Processing Deadline Miss Exception" . The same application (I took the same .bin file ) gives  no problem when launched in debug mode (code composer).

Any idea ? 

Sara

  • 0
    TI__Guru*** 149104 points
    Could you please double check that the flashed code is identical to the one running with CCS?

    Thank you
    Cesar
  • 0 in reply to Cesar
    Intellectual 410 points

    Yes it is. I think there are some differences in managing stack and heap memories when running from ccs or flash. With another code, correctly running in CCS, I had to move a vector accessed by EDMA from heap L1 to heap L2 or L3 to have it running correctly from flash. Is it any initialization done automatically by CCS that I am missing ? I checked the GEL file and there is nothing in there....

    Sara

  • 0 in reply to Sara Marina Salvador
    TI__Mastermind 21025 points
    There should be no difference - the executable should be able to run from flash or debugger. The difference in assigning load addresses is that the Boot loader cannot load into L1, which is why the demos create "fast code" sections that are loaded by Boot into L3, then copied by the program once it starts running. Take a look at how the SDK demos manage this.