• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 32 subscribers
  • Views 1264 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.

Error when loading TMS570LS20216 development board (Error -1003 @ 0x2BC5)

Jeremy Henderson
Intellectual 740 points

Other Parts Discussed in Thread: TMS570LS20216, UNIFLASH

I am unable to load my TMS570LS20216 dev board (Keil MCBTMS570). It was working great before today. I now get the following error:

CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0

CortexR4: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.

CortexR4: GEL: File: <name of out file here>.out: Load failed.

CortexR4: Unable to terminate memory download: (Error -1003 @ 0x2BC5) Internal error: Invalid parameter passed to function. Restart the application. If error persists, please report the error. (Emulation package 5.0.872.0)

  • 0
    Intellectual 740 points

    Using UniFlash I get the following error when I try to erase all flash:

    [13:47:30] CortexR4: Erasing Flash memory...

    [13:47:52] ERROR >> CortexR4: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.

    [13:47:53] ERROR >> CortexR4: Flash Programmer: Error initializing device.

    [13:47:53] Flash operation Erase failed on core Texas Instruments XDS100v2 USB Emulator/CortexR4 .

  • 0 in reply to Jeremy Henderson
    Intellectual 740 points

    No one has any ideas?

    I am able to connect to the board with CCS using XDS100v2 and I can read flash but I cannot get anything to load. Currently there is a program in the flash that runs on startup. I have tried resetting the board while UniFlash tries to connect in order to prevent the flashed program from running before the UniFlash connection, but I get the same result. Is it possible the flash could be locked?

  • 0 in reply to Jeremy Henderson
    TI__Genius 9015 points

    Hello Jeremy,

    You stated everything was working ok up to the day before this issue began.  Did you program some new code into the device the day before this issue started to occur?

    Try connecting in a debug session with CCS without downloading any code.  Make sure the device is in a halt state.  Then try doing an erase operation from the Flash tools menu.

  • 0 in reply to John Hall
    TI__Intellectual 1235 points

    Hello Jeremy,

        I have met the same problem as yours.

        And it turned out to be the crystal problem in my case. 

        I would suggest changing the crystal frequency to 10MHz first in Uniflash and try again.

        If this works, I would assume it is the crystal problem. (10MHz is the internal LPO frequency)

        Please examine your crystal circuit as well as the power to PLL circuit.

  • 0 in reply to Renton Ma
    Intellectual 740 points

    John,

    The board stopped working while a coworker was using it. New code was loaded. I have tried your suggestion, but I get the same error. The flash erase algorigthm seems to time out.

     

    Renton,

    I tried switching to 10MHz in Uniflash and CCS, but I get the same error.

  • 0 in reply to Jeremy Henderson
    TI__Genius 9015 points

    Jeremy,

    Does the code that your coworker programmed have either the MPU set or Watchdog enabled?

    Basically, CCS/UniFlash (they use the same backend) downloads object code to RAM that performs the erase/program operations.  Based on your description, it sounds like the code programmed into the device is either protecting the RAM area that is downloaded, preventing the code from executing properly to completion or something else similar in nature. 

    Something I left out from previous suggestion is to try issuing a system or cpu reset before attempting to erase after in the halt state.

  • 0 in reply to John Hall
    Intellectual 740 points

    John,

     

    I do not believe that the MPU or Watchdog is set. The MMUGCR register is not modified in the code and the MPMODE field of SYSESR indicates that the MPU is disabled.

    I tried connecting to the board via the Target Configurations view and connecting to each core individually (Icepick, DAP, then Cortex R4). I am able to view RAM at 0x08000000 and I am able to modify it via the Memory Browser. I can also see some RAM values change when I try a flash erase. I am assuming this is the algorithm being loaded in to RAM. I get the following error on an attempt to erase flash after a cpu and system reset:

    CortexR4: Flash operation timed out waiting for the algorithm to complete. Operation cancelled.

    CortexR4: Flash Programmer: Error initializing device.

     

    It does look like RAM does not get loaded properly as only a small address range is modified: 0x080000A8 - 0x0800017C