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/LAUNCHXL-CC1310: debug misticaly hung at some code of TI ROM, and breakpoints are not functional

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

Hallow!

i try to work with launchpad on CCSv7 hosting on Win8, emulator tool detected as XDS110

running COntikiOS examples.- rime-tsch. or any other example.

i use debug configuration that CCS make by default. that use ..\..\emulation\gel\cc26x0.gel , and i change probe settings cJTAG mode - to cJTAG 4-pin, JTAG TCLK - to fixed 1MHz

debuger hungs at printing net-stack configuration on main start. when i stops cpu - debuger shows that it goes at 0x100035fc. after a few  cpu steps (in disassembrer view) , programs found at format_str_v, or dbg_send_bytes or cc26xx_uart_busy.

most deep stoped -  at ti_lib_prcm_power_domain_status

when i try set an HW breakpoint - it setups ok, but debuger not stops on them, when i continue.

Also, if i try to attach to running application (load only symbols, and disable target reset) - loading symbols fails with report that it endianes are different from target one.

i have disabled LPM deep sleep use. at startup messages printing also use debug version of putchar - it not use lpm sleep. 

What i do wrong? How to achieve reliable breakpoints?

how to avoid endianes mismatch failure?