Part Number: CC1352R
Greetings,
I am using CC1352R with SDK simplelink_cc13x2_26x2_sdk_3_20_00_68, and I want to add BLE OAD to "dmm_wsnnode_remote_display_app_CC1352R1_LAUNCHXL_tirtos_ccs" example. I followed the steps in this tutorial :
http://dev.ti.com/tirex/content/simplelink_academy_cc13x2_26x2sdk_3_20_03_00/modules/ble5stack/ble_enhanced_oad/ble_enhanced_oad.html?fbclid=IwAR2lvTcCV3XtB-lQ1jnDukH-aeKA5gJsgzoHYj-fml2NvfT83F0toTDHe24
But I noticed that the device is not functional (does not advertise). I tried to debug, but this issue happens when debugging using CCS 9:
Cortex_M4_0: Error: (Error -1170 @ 0x0) Unable to access the DAP. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.2.0.00004)
Cortex_M4_0: Trouble Halting Target CPU: (Error -2064 @ 0x0) Unable to read device status. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK). (Emulation package 8.2.0.00004)
Cortex_M4_0: Unable to determine target status after 20 attempts
Cortex_M4_0: Failed to remove the debug state from the target before disconnecting. There may still be breakpoint op-codes embedded in program memory. It is recommended that you reset the emulator before you connect and reload your program before you continue debugging
It occures when trying to execute function "ICall_registerApp()" in "RemoteDisplay_init()". After I terminate the debugging, CCS crashes and closes!
The example worked fine before OAD modifications.
1- What could cause this problem? Are there some further changes needed for OAD to run on this example?
2- Is there a tutorial/manual for adding OAD to a DMM example directly?
* James *
