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 while flash process using an activated license

Other Parts Discussed in Thread: SEGGER, TMS570LC4357, OS3

Hello everybody,

i am using CCS 6.1.1.00022 and a J-LINK debug probe to flash my TMS570LC43xx. Flashing works fine when I use the "free license".

To use the debug features, i activated my license and now the flash process fails as well when i am using the "evaluation license".

The Console displays this error message:

CortexR5: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR5: Trouble Writing Memory Block at 0x7ff00 on Page 0 of Length 0x6828: Flash download failed! ...

CortexR5: File Loader: Verification failed: Target failed to write 0x0007FF00

CortexR5: GEL: File: C:\Users\....out: Load failed.

When i first flash with the free license and then try to debug it, i am able to use the dedug feature (Because the program is compared, but not flashed). When i try to flash one more time it shows the error message above.

Thank for your support.

  • Christian,
    I'm not sure if this combination is supported officially. There was experimental support from TI for JLINK in CCSv5 but I am not sure it's status in CCSv6 - I can check.
    In any case it sounds like it was working for you. But when you say 'i activated my license' which license are you referring to? A license for TI CCS or one that is attached to the JLINK.
  • Hello Anthony,
    i received a patch from Segger J-Link which was working so far. They delivered me as well a CCS project, which worked without any problems.
    The current problem with my project is that flashing just works once (free or full license).

    When I crash CCS changing <!--<partnum beginsWith="TMS570" />--> in the file FlashDLLDB.xml (which was actually the patch) it works one one more time after restarting the application.

    I thought, something with my settings would be wrong, but there are 100% equal.

    Kind regards,

    Christian
  • Christian,

    Ok, so to be clear the problem has changed, so I should forget the part about the license.

    The current problem is: 'flashing just works once' and 'it works one one more time after restarting the application.'

    Please see:
    e2e.ti.com/.../1633424
    with info on patch to fix the problem here: e2e.ti.com/.../458526

    And let me know if the problem appears to be similar or the same.

    I am not sure how much of TI's drivers Segger uses - if they use the TI Cortex R driver, then they may have the same problem.

    Anyway it would be good to know if the signature is the same.
  • This is the new error message i get when i try to change the .gel file like suggested here (e2e.ti.com/.../1633424

    CortexR5: GEL Output: Memory Map Setup for Flash @ Address 0x0CortexR5: GEL Output: OFP
    CortexR5: 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.
    CortexR5: File Loader: Verification failed: Values at address 0x000000000001FFC0 do not match Please verify target memory and memory map.
    CortexR5: GEL: File: C:\Users\q385332\Desktop\CCS Support\TMS570LC4357_V01\cc_project\Debug\OS3.out: a data verification error occurred, file load failed.

    I wonder why the basis project from segger is working without problems, and my project always fails after the first flash. (Successfull first compare,erase,flash,verify -> Successfull compare, erase, flash at 2% -> Error message shown in the first post)


    Kind regards,

    Christian
  • Hi Christian,

    It's possible the issue is related to your object code and not present in the Segger project.

    Did you check your code for issues hinted at in the error message:

    Ch Ma said:
    CortexR5: 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.


    If you need help w. this please post the .map file and your linker .cmd file.   The .map file is not created by default, but can be turned on with the ARM Linker 'Basic Options' tab, the linker should be invoked with a -m 'outfile.map' option.



    We need to know as well what your settings are in the "Debug->Flash Settings".   Are you using the linker to generate ECC data?  If so you need to make sure "Auto ECC Generation" is not checked, and that Flash Verification Settings are set to 'None' and not verify.   (Verify or Fast Verify will fail if you use linker ECC, because the verify is done on the fly but the ECC data sections are not programmed until after all the data sections are programmed.)

    There is also a 'Verbose' checkbox on the "Debug->Flash Settings" tab way at the bottom so scroll down.

    Turning on 'Verbose' usually provides much more precise information about the problem in the console output window.



  • Anthony F. Seely said:


    We need to know as well what your settings are in the "Debug->Flash Settings".   Are you using the linker to generate ECC data?  If so you need to make sure "Auto ECC Generation" is not checked, and that Flash Verification Settings are set to 'None' and not verify.   (Verify or Fast Verify will fail if you use linker ECC, because the verify is done on the fly but the ECC data sections are not programmed until after all the data sections are programmed.)

    There is also a 'Verbose' checkbox on the "Debug->Flash Settings" tab way at the bottom so scroll down.

    Thank you very much. I am acutally using the linker to generate the ECC Data.

    The change in the settings resolved the problem.