• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 30 subscribers
  • Views 321 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.

LAUNCHXL2-570LC43: Example Project 6.3 Bootloader Hercule MCU Verification Error, Memory and Memory Map, XDS110 and X2xx

Tomas Fernandez
Prodigy 145 points
Part Number: LAUNCHXL2-570LC43
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

I am working on trying to upload the example bootloader project found here: 6.1. Project 0 — Hercules Safety MCUs Documentation (https://software-dl.ti.com/hercules/hercules_docs/latest/hercules/Examples/Examples.html#bootloader). The development board I am using is the LAUNCHXL2-570LC43 (https://www.ti.com/tool/LAUNCHXL2-570LC43). 

The board itself only seems to have a Texas Instruments XDS110 USB Debug Probe. The example project, when I downloaded it, has a connection of Texas Instruments XDS2xx USB Debug Probe. The only change I made to the project was changing this XDS2xx connection to XDS110 so that it would connect to my board. I get the following error about a verification error and memory and memory map problem: 

  • +1
    TI__Guru 69771 points

    Hi Tomas,

    We can do ECC generation for our code in two ways:

    1. First way is using CCS or UNIFLASH, if we choose this method then the loader generates the ECC while loading the .out file into the flash.

    This can be done by the following option in CCS:

    If we select the above option, then the ECC will be calculated and loaded to the controller while loading the .out file by the loader.

    2. The other option is using linker, in this method we will modify the linker command file to generate the ECC like as shown below.

    If we do this then the ECC is also included in the object file along with the code and data.

    If we used this second method, then we should disable the Auto ECC generation in the first step. If you verify the linker command of this bootloader code there we are using this second method so you should need to disable the Auto ECC generation in the first step. Also verification during programming needs to be skipped because the data areas and ECC areas will now be programmed in separate steps.

    So, choose the CCS debug options as below:

    --
    Thanks & regards,
    Jagadish.