Hello all!
I am trying to get the reporter_fh demo program to work, but I am experiencing som weird crasches. I use the smart development kit expert and Keil µVision 5.
I have undefined the sleep modes so I can start and run the program with keils debugger active. The program runns fine at first and I can find the chip on my phone and on the proximity monitor application. But after a few minutes the debugger show that the program reachs the NMI_HandlerC (it looks like some kind of watchdog timeout interrupt), and the device is no longer detectable.
What is even weirder is that every time I try to restart the debugger, Keil crasches, and it does that even if I reset the dev board by unplugging its USB cable. If I however restart Keil directly after the dev board times out, I can enter debug mode and reprogram the dev board without any problem.
I have also experienced different stability problems on different power sources. Running from the alkaline battery is even more unstable and sometimes I can not even detect the board trough the Jlink settings. I get the most stable results (the ones I have written about above) buy using the power from the USB chip (J13 in middle position).
I have also tried to launch the program, exit the debugger and dissconnect everything from the board except for the USB cable. But the behaviour persists; it runs fine for a cupple of minutes before crashing.
I have also tested different daughterboards but they all display the same behavior.
Anyone got any ideas?
Update: I undefined the watchdog and tried to run it. But once again it displays the same behavior; runns fine for a coupple of minutes and then dissaperes from the bluetooth monitor, altough without the watchdog keil doesnt notice when it crasches.
Also, if I try to restart the processor I get the message: "***JLink Error: Could not start CPU core. (ErrorCode: -1)"
更新2:车祸seams to happen if nothing connects to the unit. If I connect to the unit with serial monitor, the reporter_fh never dies. However, if I dont connect to it it still crasches after about 2 minutes.
Hello Josa,
we have experienced some challenges with the Keil v5.1x which we've asked Keil to investigate. Most of these tend to have been centred around the JLINK debugger settings ...
I've asked our local FAE to give you a call : he should be in contact with you shortly to work through these.
BR JE_Dialog
Hello
When I switched over to Keil 4.74 the IDE worked much more stable. And as I said in my second post, the code work fine if I connect to the unit with another device. However, if i leave the reporter_fh in advertising mode (nothing connects to it) it still crasches within five minutes.
Hi Joakim,
In the proximity application (reporter_fh) a timer has been enabled which, after 3 minutes of advertising (without connection) will put the DA14580 in deep sleep mode and can only be woken up and start advertising again by pressing one of the buttons (connected to P1_1).
See also the document UM-B-010 @ page 4.
Best regards,
Dialog Bluetooth Support Team.
Hi,
How do I change\cancel the advertising timeout?
I tried changing the value of gap_timeout_table.GAP_TMR_LIM_ADV_TIMEOUT_VAR in gapm.c from 0x4650 (18000 * 10ms) to 0x0BB8 (3000 * 10ms), but it doesn't affect anything.
--- Solved ---
The timeout is configured in app_proxr_proj.c :
#if USE_PUSH_BUTTON
app_timer_set(APP_ADV_TIMER, TASK_APP, 18000); //180000 ms -> 3 mins
#endif
I don't understand the meaning of gap_timeout_table.