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.

Compiler/TMS570LS3137: arm_15.12.3.LTS

Part Number: TMS570LS3137

Tool/software: TI C/C++ Compiler

Hi ,

While flashing the code in to target board, using USB560 JTAG Emulator. I am getting error dialog box attached below.

So request you please suggest how to get resolve this issue.

With Regards

Shankar

  • Error Log is:
    CortexR4: GEL Output: OnHalt called
    CortexR4: GEL Output: PC - 0x00000010
    CortexR4: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR4: Error initializing flash programming: Target failed to read 0xFFFFFFF0
    CortexR4: Loader: One or more sections of your program falls into a memory region that is not writable. These regions will not actually be written to the target. Check your linker configuration and/or memory map.
    CortexR4: File Loader: Verification failed: Values at address 0x00000002 do not match Please verify target memory and memory map.
    CortexR4: GEL: File: D:\MPOS\SOUCRE_CODE\Functional_Safety_Automotive_POC_10Apr2017\Source_code\ESCL\Debug\ESCL.out: a data verification error occurred, file load failed.
    IcePick: Power Failure on Target CPU
    Dap: Power Failure on Target CPU: (Error -180 @ 0x0) The controller has detected a target power loss. The user must turn-on or connect the power supply for the target. (Emulation package 6.0.407.3)
  • Hello Shankar,

    This is very similar to another post with similar error conditions. We are looking into this issue and will get back with you soon with an explanation.

    Also, please note that this isn't a compiler issue since it seems to be an issue with programming and the memory map used by CCS which would be more related to the USB560 emulator probe probe instead.
  • Shankar,

    I see that this issue with the same reported error has been resolved in this thread e2e.ti.com/.../2177517.

    Please have a look to insure your debug configuration is correct for the emulator and device you are using.