• State TI Thinks Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 917 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/CC3220: error loading internal flash in CCS

CC3235SF: Load Program Error during Debugging

Jitendra Singh7
Expert 1435 points

Part Number: CC3235SF
Other Parts Discussed in Thread: UNIFLASH, CC3220SF, CC3235S, CC3230SF

Hello,

I am facing an error while debugging on our custom boards based on CC3235SF.

I am able to download the program using Uniflash and it runs perfectly.

And I am able to debug the code also after changing the SOP to 2 wire debug.

The trouble comes when I change even a single line of code and try to debug over SWD without programming the device using Uniflash.

Then if I program using Uniflash the updated code I am able to debug it again.

Below are the exact observation during debugging:

After showing some progress during program upload it ends with below error.

This problem I am observing on custom board and not on Launchpad.

The custom board has exactly the same layout and schematics as the launchpad.

Regards

  • 0
    TI__Guru 73081 points

    Have you attempted to change the program frequency in CCS?

    Regards,
    Chris  

  • 0 in reply to Chris Sterzik
    Expert 1435 points

    Hello Chris,

    I checked by changing SWD frequency down to 100khz. It did not solve the issue. 

    Then I tied to test on 2 different launchpad boards. Same error I am getting.

    Target Reset
    Cortex_M4_0: File Loader: Verification failed: Values at address 0x010107E0 do not match Please verify target memory and memory map.
    Cortex_M4_0: GEL: File: xxx\mqtt_client_CC3235SF_LAUNCHXL_tirtos_ccs\Debug\mqtt_client_CC3235SF_LAUNCHXL_tirtos_ccs.out: a data verification error occurred, file load failed.

    If I make no changes to the program that is flashed into the device then I am able to debug it without any trouble. So this observation eliminates the possibility of hardware connection with the debugger.

    But when I make any changes in the program it throws this error. And the address is always  0x010107E0.

    example commenting below print statement results in the error and when i again uncomment the error goes away

    UART_PRINT("\n sl_Stop failed\n");

    One more observation. If I change the macro #define APPLICATION_VERSION 

    from "1.1.1" to "1.1.2"

    the program loading happens successfully but on the terminal it still prints 

    MQTT client Example Ver: 1.1.1

    So, I think the debugger is not able to program the internal flash of the device.

    If so what could be the possible reasons for this?

    I am flashing the device in development mode only.

    There is one more behavior I am observing:

    if I update the same macro 

    from "1.1.1" to "1.1.22222"

    then the debugger loads the image but the program running pointer(the arrow that shows where the current program is debugger) never comes up. The play button is also disabled, only the stop button is enabled.

    Please let me know if you need and more tests to carry on.

    regards

  • 0 in reply to Jitendra Singh7
    Expert 1435 points

    Hello,

    I tested this behavior on CC3220SF. And it works as expected.

    Regards

  • 0 in reply to Jitendra Singh7
    TI__Mastermind 48511 points

    Hi Jitendra,

    Please try the following:

    1) Set the SOP pins to 001 (allows SWD)

    2) Open a new Uniflash configuration. Make sure you choose CC3235SF and not CC3235S.

    3) Set the configuration to Development mode

    4) Add only the latest service pack

    5) Program your board with Uniflash

    6) Attempt to debug an example from the SDK with the XDS110. 

    This will make sure the device is in development mode where the JTAG can be accessed, that there is no application image re-configuring GPIOs, or putting the device in a low-power mode which could prevent JTAG access.

    Also make sure that CC3235SF_SWD is selected in CC3235SF.ccxml. 

  • 0 in reply to Seong Kim
    TI__Mastermind 48511 points

    Jitendra,

    Any progress on this?

    BR,

    Seong

  • 0 in reply to Seong Kim
    Expert 1435 points

    Hi Seong,

    I tried your suggestion it did not work.

    But I feel there is some setting in my workspace that is causing this trouble.

  • 0 in reply to Jitendra Singh7
    Expert 1435 points

    Hello Seong,

    If I change the device to CC3230SF_SWD in target config ccxml file I am able to debug the code as expected on a CC3235SF board.

    Does it have something to do with the security feature of the chip?

  • 0 in reply to Jitendra Singh7
    TI__Mastermind 48511 points

    No, that has nothing to do with it.

    Which version of CCS are you using?

    BR,

    Seong