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.

CC2642R-Q1: File Loader: Memory write failed: std::exception

Part Number: CC2642R-Q1
Other Parts Discussed in Thread: TIDA-020032, UNIFLASH

Hi Everyone, 

I am trying to debug the simple_peripheral project on a custom board. However i frequently run into a std::exception error "File Loader: Memory write failed: std:exception" when trying to load the application binary. 

This is the error as reported on the console:

Sometimes the next attempt to "Debug as -> Code Composer Debug Session" works without any issues. Sometimes i get this error multiple times in a row. 

The setup in use is: xds110 Firmware 3.00.00.25, CCS 12.3.0.00005 and  simplelink_cc13xx_cc26xx_sdk_6_41_00_17

FYI From time to time i had the same error on the TIDA-020032 but not as frequent. However, when testing with TIDA-020032 i was also still using older firmware 3.00.00.22 on the xds110 

Do you know what might be the issue and how to resolve or mitigate it?

Thanks a lot and Best Regards,

Max

  • Hi Max,

    Thank you for reaching out about this issue. Just to confirm, have you made any modifications to the example? And are you able to directly flash either the .out file that the project generates or the pre-compiled .hex file?

    What does your debug setup look like? Are you using a stand-alone XDS110 probe or making use of a LaunchPad's integrated debugger? Additionally, what type of JTAG connector are you using (i.e. how many pins)?

    Otherwise, I will continue to look into your issue.

    Best,
    Joe

  • Hi Joe, 

    Thank you for your reply. There are some modifications to the example. We only use the GPIOs for UART TX and RX and have them mapped to our pinout, other GPIOs are removed. Apart from that we mainly just adapted Device Name and Address.

    I tried to use uniflash to flash the *.out directly but the results are similar. Testing it with the pre-compiled .hex file also has the same results. Sometimes it works sometimes it doesn't. I have enabled verbose output in uniflash and took some screenshots, maybe it can help. 

    Here an attempt with the error: 

    Here a successful attempt: 

    Part1:

    Part2:

     

    As for the debug setup, im using a stand-alone XDS110 and the connector is a ARM Cortex 10 Pin connector.

     

    Thank you and Best Regards,

    Max

  • Hi Max,

    All sounds good from a setup point of view. I am unable to recreate your issue with the same setup, substituting a LaunchPad.

    Could you double-check that the HW implementation follows the recommendations outlined in this Design Guide (see Figure 3-1 and Section 3.4)? The LaunchPad design files are also available here for reference.

    I will continue to look into what on the software side of the debug chain could be raising the exception that you are seeing.

    Best,
    Joe

  • Hi Joe, 

    Thanks a lot for your reply. At this point i suspect there is an issue with my host machine in general, as it seems to work better after a reboot and the problem gets worse over time it feels like. I had some USB related issues on this machine in the past as well. 

    In addition a colleague of mine has no problem at all using a similar setup. 

     I think we can close this topic for now. Thanks a lot for taking the time and looking into this issue. 

    Best Regards,

    Max

  • Hi Max,

    Thank you for keeping us updated. I will go ahead and close this thread for now.

    Best,
    Joe