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.