• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 380 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:

CCS/RM57L843: Impossible to load a program into LaunchPad RM57L843

CCS/RM57L843: Impossible to load a program into LaunchPad RM57L843

Rahul Savariya
Prodigy 10 points
Part Number: RM57L843
Other Parts Discussed in Thread: HALCOGEN

Tool/software: Code Composer Studio

Hello,

It’s impossible to launch a program into a Load development board.

The error is the following:

CortexR5: File Loader: Memory write failed: Flash verification failed


CortexR5: GEL: File: C:\Users\mohan_000\workspace_v8\Build-LAUNCHXL2-RM57x\Debug\Build-LAUNCHXL2-RM57x.out: Load failed.

CortexR5: GEL Output: Memory Map Setup for Flash @ Address 0x0 due to System Reset

I am new user of this software. so i request to give answer with reason why the error come. thanks for the help!

  • 0
    TI__Guru**** 171034 points
    Hi,

    The error itself is covered in the Data Verification Errors article below:
    software-dl.ti.com/.../troubleshooting-data_verification_errors.html

    In summary, it may be caused by several root causes:
    - Your code is incorrectly configured and thus trying to write to invalid memory regions. If you can, try to flash an example code from HalCoGen or a pre-built binary that you know it works well. That will help isolate the issue to the code or the device.
    - If the above does not work, the Flash is not operating correctly or is not being erased successfully. The debugging options shown in the original thread are very useful to diagnose and try to recover the Flash memory.
    - If that does not work, there is a strong chance the device itself is not properly working. I would then try with a different development board to try to isolate the issue to a specific development board.

    Hope this helps,
    Rafael