Low power problem with GPIO, I2C and SPI in nrf52

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Mon, 18 Dec 2017 10:08:30 GMT

I suppose that now that your other case is solved, then this case solved too?

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Wed, 13 Dec 2017 09:09:59 GMT

Yes, I'm using the same SDK files, reboot after programming and I have the latest JLink drivers installed

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Tue, 12 Dec 2017 14:21:04 GMT

BTW: does it help to power cycle the devices after programming? And can you make sure to upgrade to the latest JLink drivers? Some old drivers used to keep the device in debug mode after programming, which effectively left the CPU running.

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Tue, 12 Dec 2017 13:22:37 GMT

Are you also using the exact same SDK files? I once spent hours trying to recreate a customer's problem on my system, but everything seemed to work fine. It turned out that he had made changes to the drivers in his local SDK files and then forgotten about it. So when he then sent me his project files and I used them with my own SDK files, everything worked fine.

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Mon, 11 Dec 2017 10:53:02 GMT

any idea Martin? What could be the problem when changing computers?

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Thu, 07 Dec 2017 14:22:23 GMT

ARM Compiler V5.06
Impossible, the software was unistalled from the old PC because it belongs to a former employee
Yes, and everything is ok

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Tue, 05 Dec 2017 11:59:32 GMT

Which compilers do you use?
Can you double check that the compiler settings and all the defines and settings in the SDK (like logging enabled, etc. ) are the same?
If everything seems ok, can you compare the original hex file with the one compiled on your new system?

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Tue, 05 Dec 2017 11:11:44 GMT

I compile with a different compiler, but the same version of sdk and softdevice

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Tue, 05 Dec 2017 11:02:50 GMT

Do you flash the exact same hex file with both PCs? Or do you compile the application with a different compiler and different compile settings on the new PC?

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Tue, 05 Dec 2017 08:56:44 GMT

Right, but the problem is that we had ~2mA of consumption (acceptable value at the moment), but we had to change the PC which we flash, and the same project, same development board and same custom board, give us 4,2mA and we need 2mA again. What could be the problem when we changed the PC?

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Mon, 04 Dec 2017 14:43:33 GMT

I just mean that with the peripheral drivers in the SDK the interrupts should be cleared without any action required from you. In other words, you shouldn't have to worry about this at all.

If you write your own peripheral drivers from scratch however, you will most likely have to explicitly clear the interrupt in your interrupt routine yourself.

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Mon, 04 Dec 2017 09:23:56 GMT

Hi Martin, thanks for your answer. I’ll take a look to what you say, by the way, what do you mean with “this can happen if you don’t use our drivers”.

RE: Low power problem with GPIO, I2C and SPI in nrf52

adrisecmotic — Mon, 04 Dec 2017 08:57:45 GMT

Hi Alex, thanks for your answer. No, we can’t measure the consumption of the components separately, and yes, we use interrupts, and the I2C and SPI are switched off in sleep mode when they are not in use

RE: Low power problem with GPIO, I2C and SPI in nrf52

MartinBL — Mon, 04 Dec 2017 08:21:59 GMT

Typically currents of ~4mA means that the CPU is running and your application is not able to put your system to sleep (CPU current values). It could also be that you have unprocessed interrupts pending. This can happen if you don't use our drivers and forget to clear interrupts within their corresponding interrupt routines.

Shooting from the hip: Are you using floating point variables? It could be related to this erratum: CPU: Unexpected wake from System ON Idle when using FPU.

RE: Low power problem with GPIO, I2C and SPI in nrf52

AlexB — Sun, 03 Dec 2017 23:45:19 GMT

Are you able to measure the power consumption of the various components separately? Do you have interrupts for UART, I2C and SPi switched off in Sleep?