• State Verified Answer
  • Replies 3 replies
  • Subscribers 86 subscribers
  • Views 1167 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 219884
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

After upload firmware high current in Sleep Mode

ricardo vasquez rossi

Hi all

I have a custom Board, I have tested it a lot. NRF51822, programed with Mbed..

In general the Software and Board WORKS FINE, but I found some problem in my procedure of upload the firmware to the board.

1.- Conect the battery to the custom board.

2.- connect the firmware cable to board

3.- Upload the firmware.

with it procedure in the sleep mode the board consuption 1.2 mA, the board works fine,  sends the advertising, going to sleep, the button and led works fine. only fail the Consuption en Sleep mode.

I realized if I unplug the battery and connect again the current in sleep mode works fine 4uA.

.my question Is.

Is it a normal behaviour?

do you have some little program (if it is in  Keil, IAR, or other it is fine) to do resetting the chip when it start for first time and store some data in non volatile memory to know if the chip was resetting?

Thanks In Advance.

Parents
  • +1

    Hi Ricardo, 

    are you using the bootloader from a offical Nordic SDK or is the bootloader provided by Mbed? It could sound like the bootloader you're using does not disable the peripherals its using before jumping to the application. Of any peripheral using the HFCLK is used in the bootloader and not unintialized prior to the bootloader jumping to the application, then this peripheral and the HFCLK will be running in the application as well. 

    Resetting the device will reset the peripherals, so thats why you see the current consumption returning to normal. 

    No, I do not think we have such an example, but you should be able to modify one of the flash storage examples in the nRF5 SDK v12.3.0 to do this. 

    Best regards

    Bjørn

Reply
  • +1

    Hi Ricardo, 

    are you using the bootloader from a offical Nordic SDK or is the bootloader provided by Mbed? It could sound like the bootloader you're using does not disable the peripherals its using before jumping to the application. Of any peripheral using the HFCLK is used in the bootloader and not unintialized prior to the bootloader jumping to the application, then this peripheral and the HFCLK will be running in the application as well. 

    Resetting the device will reset the peripherals, so thats why you see the current consumption returning to normal. 

    No, I do not think we have such an example, but you should be able to modify one of the flash storage examples in the nRF5 SDK v12.3.0 to do this. 

    Best regards

    Bjørn

Children
Related
Terms of service