I am able to program the DA14682 chip and have things work, but the chip seems to stop responding after 3 seconds.
What could cause something like this? I am using this 16mhz crystal:https://www.digikey.com/product-detail/en/abracon-llc/ABM8-16.000MHZ-7-1...
The app seems to freeze insidewatchdog_cb. Here is the relevant comment where this happens:
/* * latency for all tasks expired and some of them still did not notify sys_watchdog * we'll let watchdog reset the system * * note that hw_watchdog_handle_int() never returns */ hw_watchdog_handle_int(exception_args);What should I investigate to figure this out?
Device:
Hi ddustin,
Did you define the sysclk_XTAL16M in system_init() function? I provided you more information in this forum thread:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/no-16khz
Could you please clarify how did you check that the code is not responding after 3sec? Did you run in debug mode and the WDOG fired up? In the first 3 sec, the device starts advertising correctly?
Thanks, PM_Dialog
Yes in the first 3 seconds it advertises correctly and even can connect and respond to BLE requests.
I ran it attached to the debugger and found that it crashed inside unhandled exception. The int cb I pasted in the last comment seemed the most relevant thing from the backtrace.
I believe this was before I switched the LP from 32khz to RTX (internal). After making that switch the debugger gives the error “SIGINT” with no backtrace at all.
How do I go about diagnosing this?
Hi ddustin,
Could you please let me know if this ticket is related with the forum ticket below?
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/chip-seemingly
Do you have the same configurations in both tickets? This means that the WDOG hit, so I would strongly recommend you to read section 5 Reboot Analysis – WDOG of theDebugging Techniques Tutorialdocument in order to find where the WDOG hits.
Thanks, PM_Dialog
Yeah the ticket is related but the delay on these forum posts is so long I posted two for different parts of the problem.
I disabled the watchdog and the problem still happens. Does that mean it is not the watchdog?
The backtrace when it crashes is not inside the watchdog routine. It's an 'unhandled exception' from a SIGINT.
How do we go about diagnosing this issue? It is clearly not related to the watchdog because *this code works perfectly on the DA14683 daughter dev board*. It only fails on my own chip.
What could cause this to work on one circuit but fail on another circuit? How do we diagnose that?
Hi ddustin,
Please check my answer in your second forum post:
https://support.dialog-semiconductor.com/forums/post/dialog-smartbond-bluetooth-low-energy-%E2%80%93-hardware-device-reference-designs/no-16khz
If the same firmware is running as expected in Pro-DK and not in your own board, this means that there is a hardware issues in your board. First step would be to review it according to hardware design guidelines from AN-B-061 document. Please check the power rails, the grounding and the soldering of your board.
Thanks, PM_Dialog