Hi,
I am using DA14531 devkit pro and SDK6. I had an issue where device would brick after the connection. After debugging I found out that I was going into ASSERT_ERROR(0) in app_task.c line 287 in the gapc_cmp_evt_handler. I checked error status and it 67 = GAP_ERR_COMMAND_DISALLOWED. I can notice disconnect happening before so I assume it is correct that action is invalid in this state. However I wonder if I can somehow check what is the source of this erroneous message and if bricking device is actually correct behaviour . I assume I am running in some kind of debug mode that which I will disable ASSERT_ERROR won't cause device brick ? What changes I have to do to make my code run "production" mode?
Best regards,Michal
Hi Michal,Thank you for posting your question online.Could you please clarify which SDK version you are working with?Would it be possible to share more information regarding the bricked device? Which example had you loaded into the device? SRAM or SPI Flash?
MichalB said: I assume I am running in some kind of debug mode that which I will disable ASSERT_ERROR won't cause device brick ?
It is not recommend modifying the SDK folders.
MichalB said:What changes I have to do to make my code run "production" mode?
On da1458x_config_basic.h file:
/****************************************************************************************************************/ /* Enables development/debug mode. For production mode builds it must be disabled. */ /* When enabled the following debugging features are enabled */ /* - Allows the emulation of the OTP mirroring to System RAM. No actual writing to RAM is done, but the */ /* exact same amount of time is spend as if the mirroring would take place. This is to mimic the */ /* behavior as if the System Code is already in OTP, and the mirroring takes place after waking up, */ /* but the (development) code still resides in an external source. */ /* - Validation of GPIO reservations. */ /* - Enables Debug module and sets code execution in breakpoint in Hardfault and NMI (Watchdog) handlers.*/ /* It allows developer to hot attach debugger and get debug information */ /****************************************************************************************************************/ #define CFG_DEVELOPMENT_DEBUG
I don't want to modify code. I would assume that under "production" configuration implementation of ASSERT_ERROR will be empty. Is that correct assumption? I tried commenting out CFG_DEVELOPMENT_DEBUG , but it didn't help.
It is SDK_6.0.16.1144.
Hi Michal,Thank you for the reply.
MichalB said: I would assume that under "production" configuration implementation of ASSERT_ERROR will be empty. Is that correct assumption?
Yes, your assumption is correct.
MichalB said:I am using DA14531 devkit pro and SDK6. I had an issue where device would brick after the connection. After debugging I found out that I was going into ASSERT_ERROR(0) in app_task.c line 287 in the gapc_cmp_evt_handler.
If you want you can share more information regarding this issue.Best Regards,OV_Renesas