This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

0xDEADBEEF, 722, src \ ll_adv.c

Hi all,

I use nRF51822, sdk_v5_0_0_34603 and s110_nrf51822_6.0.0-5.beta. In a different periods of time appears error "0xDEADBEEF, 722, src \ ll_adv.c". Error appears only with battery powered device (tested with different batteries). What may be the reason for this error.

Best regards, Peter

  • Hi Peter

    We are not aware of anyting that can cause the assert you see.

    Can you provide us with a simplified application example and description on how we can recreate your observation? Have you tried to use a power supply to control the supply voltage to see at what level the error may occur? If you are using nRFgo Motherboard you can set the supply voltage from nRFgo Studio, a devkit module must be present on the motherboard.

    Best regards, Kenneth

  • Also, is the J-Link Lite connected while testing? You should know that the J-Link Lite can only support 3.3V, so any target voltage for instance below ~3.0V can trigger the internal protection diodes of the nRF51822, this is out of specifications.

  • Hi Kenneth,

    Thank you for reply.

    My tests: Test with my board and different voltages from external regulated power supply. 2.54V - error 0xDEADBEEF, 722, "src\ll_adv.c". 2.79V - error 0xDEADBEEF, 722, "src\ll_adv.c". 2.9V - no error in 5 min. Tested were 2 of my boards. Tests with dev.kit. There was the same error with dev.kit. - 0xDEADBEEF, 722, "src\ll_adv.c". used: -nRF6310_rev1.4 -pca10004_rev1.0 -sdk_v5_0_0_34603 -s110_nrf51822_6.0.0-5.beta. power: battery CR2032/3V connection: NO connection to iPhone. led indication:

    • restart - a couple of flashes
    • error - led ON for 5 seconds and resume with flashes until power-off With j-link connected there were no errors.

    Best regards, Peter

    ble_app_hrs.rar

    nRF51822_ver6.pdf

  • Hi, Peter!

    Are you starting and stopping advertising and also doing flash writes at the same time?

    We are aware of one issue with the s110 6.0.0 that might be related to what you see:

    Stopping advertising (either by calling sd_ble_gap_adv_stop() or by a timeout) after a flash operation is started and then starting advertising again before the flash operation is complete may lead to undefined behaviour (DRGN-3785). Workarounds are:

    Either wait 50 ms or more from stopping advertising until starting advertising again.
    
    Or wait until the flash operation end event (NRF_EVT_FLASH_OPERATION_SUCCESS or NRF_EVT_FLASH_OPERATION_ERROR) has been received before starting advertising again
    

    Please try one of these workarounds (the one that is most relevant for you), and report your findings.

    Asbjørn

  • Hi Asbjørn,

    I do not use flash write. But you mention about 'advertising'. Ahter advertising timeout or disconnect I am changing advertising parameters and start advertising again without stop command. May be this is the problem. Will check and report. In my previous post is source code.

    Best regards, Peter

Related