CC2340R5: Error Messages when trying to debug

Part Number: CC2340R5


I have managed to build and run the BLE DataStream example using the LP-EM-CC2340R5. This works perfectly in debug or release build. However, when starting 'debug' I get the following errrors:

Cortex_M0P: Trouble Setting Breakpoint with the Action "Terminate GEL_Go()" at 0xf0023f1: (Error -1066 @ 0xF0023F0) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.8.0.00235) 
Cortex_M0P: GEL: Error while executing OnTargetConnect(): An earlier error prevented the target from running
     at GEL_Go(entryPoint) [cc23xx_xds.gel:58]
     at OnTargetConnect()
Cortex_M0P: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x29088: (Error -1066 @ 0x29088) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 9.8.0.00235) 

The project is 'out-of-the-box' without my making any changes. The programmer / debugger tool is the TI Launchpad XDS110 with energy trace.

Am I doing something wrong?

 

  • Hi John,

    I am not able to replicate the behavior you are reporting.  Can you please share with me your SimpleLink F3 SDK, TI ARM Clang Compiler, and CCS versions?  Outside of a debug session, does the demo work as described in the README?  At what location are you trying to set a breakpoint?  Please be aware of common breakpoint issues, such as the line of code has been optimized out by the compiler.

    Regards,
    Ryan


  • Hello Ryan

    Many thanks for your prompt reply - greatly appreciated.

    The compiler is Ti CLang V2.2.0.LTS
    SDK 9.12.0.19
    CCC Version 12.8.1.00005

    The program builds, runs and works as expected running after the breakpoint (not set by me) on the __asm__ __volatile__(" ldr r0, =resetVectors\n" ;
    line.

    I have copied the dissassembler log below. Does this assist?

    John

    void resetISR(void)
    {
    /*
    * Set stack pointer based on the stack value stored in the vector table.
    * This is necessary to ensure that the application is using the correct
    * stack when using a debugger since a reset within the debugger will
    * load the stack pointer from the bootloader's vector table at address '0'.
    */
    __asm__ __volatile__(" ldr r0, =resetVectors\n"
    " ldr r0, [r0]\n"
    " mov sp, r0\n"
    " bl localProgramStart");
    }


    00028020: ???? Invalid target memory access
    00028022: ???? Invalid target memory access
    130 __asm__ __volatile__(" ldr r0, =resetVectors\n"
    resetISR():
    00028024: 4802 ldr r0, [pc, #8]
    00028026: 6800 ldr r0, [r0]
    00028028: 4685 mov r13, r0
    0002802a: F7FDFBDB bl localProgramStart
    134 }
    0002802e: 4770 bx r14
    00028030: ???? Invalid target memory access
    00028032: ???? Invalid target memory access
    00028034: ???? Invalid target memory access
    00028036: ???? Invalid target memory access
    00028038: ???? Invalid target memory access

  • Thanks for this information.  Please be aware of the following SimpleLink F3 SDK v9.12 dependencies from the SDK Release Notes:

    As you are using the default example I assume your issue could be related to an unexpected/untested compiler version, maybe CCS as well.  Are you trying to set breakpoints or is the application having difficulty breaking at "main" in the debugger?

    Regards,
    Ryan

  • Thank you Ryan, that's very helpful.  Quick question - does this means that the Eclipse based version of Code Composer are now redundant ?

  • CCS v12.8 (Eclipse-based) and earlier is being phased out of mainline usage in the SimpleLink F3 SDK in favor of CCS v20 (VSC-based) and later.

    Regards,
    Ryan