In order to determine the root cause for the issue in this other thread
I started to setup the debug environment on the Linux Gateway connected onboard to a CC2530 module that the CCDebugger is connected to.
For the moment the gateway is stopped to avoid any resets.
I have taken a ZStack3.0.2 setup, and I compiled the CC2530-Debug version.
In order to keep the same NV Memory state, I have disabled "Erase Flash" and selected "Retain Unchanged Pages".
Unfortunately, this does not allow me to debug. I am under the impression that the "CC2530-Debug" target does not cope with the presence of the SBL.
Here is what IAR says:
Tue Oct 13, 2020 22:09:45: IAR Embedded Workbench 10.30.1 (C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.1\8051\bin\8051proc.dll) Tue Oct 13, 2020 22:09:45: Using license: Startup license - IAR Embedded Workbench for 8051 10.30 Tue Oct 13, 2020 22:09:46: Warning: Flash page Tue Oct 13, 2020 22:09:47: Warning: Flash page is locked and was not written to. Tue Oct 13, 2020 22:09:47: Warning: Flash page is locked and was not written to. Tue Oct 13, 2020 22:09:47: Warning: Flash page is locked and was not written to. Tue Oct 13, 2020 22:10:11: Warning: Skipped verification on page 0 due to lock bits. Tue Oct 13, 2020 22:10:11: Warning: Skipped verification on page 1 due to lock bits. Tue Oct 13, 2020 22:10:11: Warning: Skipped verification on page 2 due to lock bits. Tue Oct 13, 2020 22:10:11: Warning: Skipped verification on page 3 due to lock bits. Tue Oct 13, 2020 22:10:11: Download completed and verification successful. Tue Oct 13, 2020 22:10:11: Loaded debugee: D:\...\Projects\zstack\ZNP\CC253x\CC2530-Debug\Exe\CC2530.d51 Tue Oct 13, 2020 22:10:11: Target reset Tue Oct 13, 2020 22:10:11: There were 4 warnings during the initialization of the debugging session.
What can I do to debug the ZNP while maintaing the already loaded NV memory state (with SBL present)?
Mario
