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.

CC2340R5: Proper Download and debugging of the CC2340R5 OAD (i.e. Basic BLE On Chip OAD images)

Part Number: CC2340R5
Other Parts Discussed in Thread: SYSCONFIG, , UNIFLASH

Let me know if i am missing something fundamental, but I am amazed that there is not an existing setup using CSS 12.5 that allows for the compile, download, and debug of the Basic BLE OAD on Chip project where the MCU-BOOT partition is preserved, or used to vector into the target application at its proper entry point. The only recommended process we have stumbled upon is loading the image via the DEBUG button, accepting the downloading error that occurs, then manually launching the target configuration, connecting to the target, and then using the memory browser and register views to manually correct the PC, SP, and vector table base address before punching run.

Seriously? Someone give me a hint to the real script, sysconfig settings, or GEL file that handles this for a one click download that results in a proper halt at main() so that the debugging cycle is reasonable and automated.

For this processor, we have spent more time upgrading tools, SDKs, and refactoring code than in any other CC26xx project, (and throwing away hardware - REV A) and still ending up tangled in some sticky goo.

Anyone got some fresh ideas or plans on when this will be fixed? Anyone chime in if IAR's support for the CC2340R5 has already addressed this?

It's getting to the point where we might as well just use UNIFLASH to program the image and see if it works.... forget about breakpoints, watch windows, register checks, etc.  

Guidance or links are appreciated.

Thanks.

  • Hello Stuart, 

    Thank you for reaching out.
    I agree the debugging experience for OAD projects has to be improved. 

    In the short term, you could consider enabling Flash erase protection on the part of the Flash containing MCUboot and the persistent_app (if used). This way, you can flash only the application without using Uniflash. 
    Flash erase protection should be enabled on the MCUboot project using SysConfig. 

    We are also looking at using GEL scripts or similar to directly set the core registers. Please let me follow up when I have more details. 

    Best regards,