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.

CCS/CC1310: Cortex_M3_0: File Loader: Verification failed: Values at address 0x0001FFA8 do not match Please verify target memory and memory map.

Part Number: CC1310


Tool/software: Code Composer Studio

Hi,

I have custom board designed using CC1310F128RGZ.

On one of the boards I'm getting following error while program is being loaded in the flash.  I'm using CCS 7 and built non RTOS Tx application from the examples.

I have ensured the Target configuration set to CC1310F128. Request please help.   

Cortex_M3_0: 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.
Cortex_M3_0: File Loader: Verification failed: Values at address 0x0001FFA8 do not match Please verify target memory and memory map.
Cortex_M3_0: GEL: File: C:\AAA Technical\Wireless\Simple Link Projects\rfEasyLinkTx_CC1310_LAUNCHXL_nortos_ccs\Debug\rfEasyLinkTx_CC1310_LAUNCHXL_nortos_ccs.out: a data verification error occurred, file load failed.

  • To confirm: Are you using the exact code on several board but only get this error when you try to program one of the boards?

    Why are you using CCS7 and not CCS8 and which SDK are you using?
  • Thanks for quick reply. So far I have developed two boards and getting this error only one of the boards for the same code. I have older version of CCS yet to be updated. SDK version that I'm using is 2.20.
    Regards,
    Pandurang
  • If you look in C:/ti/simplelink_cc13x0_sdk_2_20_00_38/release_notes_simplelink_cc13x0_sdk_2_20_00_38.html

    you will see the dependencies for this release are newer versions of the tools than you are using. First, try to update to the newest CCS version etc so you are compliant with the versions stated in the release notes.
  • Thanks Ter. Will update my CCS and confirm this.
    Regards,
    Pandurang
  • Hi Ter,
    I found one problem my controller is F64 though I had ordered for F128. Changing the target configuration to F64 the above error has disappeared but still there seems to be something left.
    I'm getting the following error though the application seems to be running. Yet to be tested thoroughly.

    Cortex_M3_0: 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.
    Cortex_M3_0: Symbol Manager: the object file contains invalid call frame information at .debug_frame 0x2fc7; the rest of call frame information will be skipped. Callstack may not be unwound properly.

    Any clue? I have reverted to Simplelink 1.40 to get rid of CCS7 version conflict.

    Regards,
    Pandurang

  • When you switched to F64 as target, did you remove the linker file that is used for F128? If my memory serves me right, changing to F64 will add the F64 linker file but will not remove the old F128 file.

  • Will try this. Thanks Ter.
  • Did it work?
  • I need to switch over to CC8 as facing some issues with two simple link versions. 

    Will update you on Saturday.

    Regards,

    Pandurang

  • Configuration:
    Fresh installation of CCS 8.3 and simpleLink 2.20 with F64.
    Still facing the following issue.

    Cortex_M3_0: 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.
  • You wrote initially that you only saw this issue on one board. But how is that possible if you initially compiled this code for a F128 target but only have F64 devices? Do you have more than 2 boards?
  • Very correct with the earlier setup. But this time I have newly installed CC8 and SimpleLink 2.20 and compiled it very first time for F64 .  So there is no question of F128 compilation.  Still the problem continues.

    Appreciate if you could help here.

  • Meaning that you see this on all boards you are using? Could you verify that you are actually using the correct linker file?
  • I have tested this on F64 board only.  I will test it on F128 and let you know

    Please find the link files and please let me know which one to eliminate, Not sure which is a specific file for F64.

    ${COM_TI_SIMPLELINK_CC13X0_SDK_LIBRARIES}
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/source/ti/display/lib/display.aem3
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/source/ti/grlib/lib/ccs/m3/grlib.a
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/source/ti/drivers/rf/lib/rf_multiMode_cc13x0.aem3
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/source/ti/drivers/lib/drivers_cc13x0.aem3
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/kernel/nortos/lib/nortos_cc13x0.aem3
    ${COM_TI_SIMPLELINK_CC13X0_SDK_INSTALL_DIR}/source/ti/devices/cc13x0/driverlib/bin/ccs/driverlib.lib

    libc.a

    Regards,

    Pandurang

  • I was thinking about the .cmd file in your project. Check the size of the generated hex file to see if this is 64 k or 128 k.
  • Hi Ter,
    The size of the .out file is 656KB . Not sure why this is the size of the application for 64KB flash configuration.
    Also this works very well for F128. This too is surprising. I have set release configuration.

    Where is it going wrong?
    Regards,
    Pandurang
  • Hi Ter,

    The issue is resolved. The linker cmd file shipped with the simplelink has flash size 128K.  This size needs to be changed to 64K for F64 chip.

    Regards,

    Pandurang