• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 1080 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.

Connecting and loading code into EVM

Jane Perera78562
Intellectual 350 points

I get the following message when trying to load code into Netra M3 via the Blackhawk USB560

CortexM3_RTOS_0: Warning: (Error -1268 @ 0x1090001) Device is locked up in Hard Fault or in NMI. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Release 5.0.333.0)

 

I have previously been able to load and run this code, although always took a few attempts.  I have tried power cycling, closing and re-opening tool, resetting CPU etc etc.   Configuration file is same as before.  Also tried swapping for a different EVM and no different.  Another person in my team had this problem and overcame by using a different version of CGTools.  I am using version 4.5.1.

 

 

  • TI__Guru**** 171094 points

    Hi,

    As shown in the error message, sometimes a unstable connection can be caused by JTAG settings. Can you try to change the TDS/TDO output timing to Falling Edge or set the JTAG clock speed to a lower value? Usually the ARM cores require Adaptive clocking, but I don't think the BH USB560m supports it - in this case a good workaround is to use a slower JTAG clock.

    For details on how to change these settings please check the short clip Changing the Target Configuration Properties of the Quick Tips page below:

    http://processors.wiki.ti.com/index.php/Quick_Tips

    Hope this helps,

    Rafael

  • in reply to desouza
    Intellectual 350 points

    In this case the problem was solved by powering down not only the EVM board but also removing power to the emulator.  Changing the clock speed was also required to initially get the emulator connected, but the loading problem was still there.  Once both the EVM and emulator are re-powered, the GEL initialization run and M3 connected  the code loads OK .