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.

illegal_isr() with "example _28035_Flash" program

Other Parts Discussed in Thread: CONTROLSUITE

Hello,

Here is my configuration : XDS100v2, CCS v5.3.0.00090, TMS320F28035 on a custom board.

I have a problem, when I run "Example_28035_Flash" program who come with ControlSUITE, my program always jump into the illegal_isr() trap.

I specify that I didn't touch the code.

I join a screenshot of the last instruction before the jump into the trap

Thank you

  • Nicolas,

    You've got something setup wrong or are doing something incorrectly.  I just tested the same example from ControlSuite, and it runs fine.  I can also see in the screen capture you show that the diassembly is wrong for the InitFlash() function.  The opcode values are wrong.  It should look like this:

      

    Even the address for your InitFlash is different than mine.  Yours shows 0x802E, whereas mine is 0x8032.  The address mismatch is likely explainable from your using a different version of the example project (mine is from the v1.27 folder in ControlSuite: C:\TI\controlSUITE\device_support\f2803x\v127\DSP2803x_examples_ccsv5\flash_f28035), or more likely a different version of the compiler (mine is compiler v6.1.2).  But the opcode mismatch is not from a version difference.  My first instruction in InitFlash is opcode 0x7622, which is correctly the EALLOW.  Your first instruction is 0x910A, which is an ANDB and is incorrect.

    Did you slowly go through main(), in particular can you reset the device and run to start of main()?  After that, can you see the flash-to-RAM copy happening just before you get to InitFlash?

    You can also try the code in appnote SPRA958.  Use the F28035_nonBIOS_flash example.  You say you are running on your own board, so be sure to read the relevant portion of the appnote to understand what the code does so as not to get any signal contention on your board (the code outputs on GPIO0/PWM1A pin, and also toggles GPIO34).

    http://www.ti.com/mcu/docs/litabsmultiplefilelist.tsp?sectionId=96&tabId=1502&literatureNumber=spra958l&docCategoryId=1&familyId=1414

     

    Regards,

    David

     

  • Hello David, Thank you for your quick answers.

    I'm using the v1.26 of the project, and my compiler version is the v6.1.3 (latest)

    I think the problem come from the version 1.26 of the project because I tested the v1.25 and it works.....

    Thanks again for your help

    Nicolas