• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 30 subscribers
  • Views 607 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.

Original question:

Compiler/LAUNCHXL2-570LC43: GEL Output: Memory Map Setup for Flash @ Address 0x0 due to System Reset

Compiler/LAUNCHXL2-570LC43: Can not erase, change the FLASH and debug the microcontroller

Turker Berke Yildirim
Prodigy 40 points
Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: UNIFLASH

Tool/software: TI C/C++ Compiler

Hello everyone, 

We are working on TMS570LC43 Hercules Launchpad (we have got two of them) and for two days we could compile Blinky example and UART Example without any problem. 

But third day, first Launchpad started to give an error message so we couldn't debug it anymore. So we plug the second Launchpad and try to debug a clean project (there is only an empty while loop inside it). But the second one also gave us an error message.

Before I write the error messages wanted to say that we have read almost every articles about out error codes in http://software-dl.ti.com/ . Also we tried to wipe out all FLASH via Uniflash, but it firstly can read the Memory only one time. After we try to erase whole flash, it gives the "MODULE CLOSED" error and doesn't do anything.

I will write the error messages;

First time we plug the microcontroller in and try to debug:

Cortex R5: GEL Output Memory Map Setup for Flash@ Adress 0x00

File Loader: Memory write failed Target failed to read 0x08000000

Cortex R5: Error -2063 @ 0x00 Unable to reset device.

After that (every time we try to debug without plug out) we take these errors randomly:

Error connecting to the target

Error -1170 0x00

Unable to access DAP.

Reset the device and retry the operation. If error persists, confirm configuration, power-cycle the board and/or try more reliable JTAG setting (e.g. Lower TCLK)

Emulation Package (9.1.0.00001)

Thanks for your helps already. 

Regards Berke.

  • 0
    TI__Guru**** 197036 points

    Hello Turker,

    Is the ERR led (LED1 close to RJ45 connector) turned on? Is there any issue to connect the target through JTAG? Can you try to erase the flash from CCS?

  • 0 in reply to QJ Wang
    Prodigy 40 points

    Hello sir again,

    Yes The ERR Led is turned on. First time we push "Reset Button" it goes and second time we push again it turns on again.

    We've write some code for erase flash but we couldn't flash it... Is there any specific way to erase the flash? 
    I am a stranger to this platform since I had experience with STM before. 
    I look forward to all your help and thank you in advance.

  • 0 in reply to Turker Berke Yildirim
    TI__Guru**** 197036 points

    Hello,

    My understanding is that you have erased the flash and programmed some code to the flash before, and the execution of the code causes ERROR, the code also causes the JTAG connection failed.

    It looks like the code you programmed is making the part enter an exception state repeatedly. This prevents the CPU from entering a debug state, resulting in the behavior you observe. You need to try to erase the part, assert and release nRST to see if the erase command is able to halt the CPU and erase the flash.

    Please try this procedure to let CPU enter a debug state:

    1. Open the target configuration window, and launch the selected the configuration
    2. Switch to debug window
    3. Press the reset (nRST) button and hold it
    4. Click “Connect Target” immediately after you release the nRST button
    5. The board should be connected after couple tries

  • 0 in reply to QJ Wang
    Prodigy 40 points

    Sir Thank you now we can access the FLASH with CSS.

    But we only can change Sector 0 part, other parts is not changeable.

    In Sector 0, everything is set "0x0000000" but in other sectors they're "0x000FFFF" or "0xFFFF0000".

  • 0 in reply to Turker Berke Yildirim
    TI__Guru**** 197036 points

    Hello,

    After the target is connected in CCS, are you able to run the flash erase:

    Can you check the which gel file is used?