CPU dont go to sleep

RE: CPU dont go to sleep

Susheel Nuguru — Fri, 19 Jul 2024 07:54:16 GMT

[quote user="Novo"]

If I give it to the working correctly devices, the current is 200micro

If I give them to the faulty devices, the current is 6mA

[/quote]

How many faulty devices do you have? Is it like 1 in 100 or like 1 in 10.

It also depends if you have a custom device or working on the nRF53 DK?

Can you test your application hex file in the nrf53DK if you have not done that already?

What I am trying here is to exclude few things to see if we need to focus on the hardware issue or the software issue.

RE: CPU dont go to sleep

Novo — Fri, 19 Jul 2024 06:46:20 GMT

Hi, thanks for the quick response!

I given the ble_app_hrs_freertos.hex file to the faulty devices, and they seems to work properly, with current of 200micro.

Now say that I have a file: myApp.hex

If I give it to the working correctly devices, the current is 200micro

If I give them to the faulty devices, the current is 6mA

I will check about the SystemView maybe it will be helpful, thanks!

Yes I understand that I didnt gave you enough info about myApp, I will try to summarize it in more proper and informative way, and will send it.

Anyway, if you have more ideas in mind to how to debug it, or what the cause might be, I would be happy to hear!

RE: CPU dont go to sleep

Susheel Nuguru — Fri, 19 Jul 2024 06:11:05 GMT

Hi,

[quote user=""]

I tried the following with the devices that always do has the problem:

Write the example hex of ble_app_hrs_freertos.hex, and the current was 200micro, so it seems that the micro controller is fine.

[/quote]

Not sure if I understand this first point correct. If you have the hex file that is giving proper power consumption in the devices working correctly and used this hex file in the faulty devices and if that is also working fine, then it seems that the app binary and the chips are fine.

Have you tried to compare the two hexes which causes correct and faulty behavior?

Also you can use SystemView to understand of there are any contexts or times where the chip is waking up unnecessarily.

From the description you gave, it is hard for me to narrow down the problem to anything as I do not know anything about your application or the custom boards.