Need guidance on code modifiaction based on SDK

RE: Need guidance on code modifiaction based on SDK

MartinBL — Mon, 28 May 2018 13:34:44 GMT

Hi,

Sorry for the late response. I have been on holiday for a while.

Did you disable the UART to see if that helps with the 500 uA base current? You can also try to disable the logger module.
How high are your peak currents? It doesn't have to be the radio. I'm thinking that a 100 Ohm series resistor between your supply and the IC might cause significant voltage drops that are possibly resetting your IC.
Is the interval exactly 250 ms?
Can you zoom in on the peaks? It might give us a clue about what is causing them.

It is the central that ultimately decides on what connection interval to use, but it will always try to use an interval between the min and max value provided by the peripheral. You can try to set both min and max value to 1800 ms if you want to force the central to use that exact interval.

Martin

RE: Need guidance on code modifiaction based on SDK

ngml73 — Wed, 16 May 2018 07:15:47 GMT

This is the current consumption of our nRF52, 100 Ohm put between supply and the IC.
No matter what interval we set, the peak current always happen at 250ms period. the standby/ sleep current always about 500uA.

Do you think this is something related to Android Apps -> nRF Toolbox -> UART restrict the interval fix to 250ms?

If we want to modify from the code of the Apps to longer interval. Can you advise us which file to modify.

Thanks!

Jimmy Ng

RE: Need guidance on code modifiaction based on SDK

ngml73 — Tue, 15 May 2018 00:41:43 GMT

Hi MartinBL,

Thanks for your guidance. My customer has futher question on (2) as below. Any chance to reduce current further to 100uA ?

min current that i get is 550uA.
Adv interval=3500ms
Min interval=20ms
Max interval=1800ms
If i increase the max interval to 2000ms, it does not function

RE: Need guidance on code modifiaction based on SDK

MartinBL — Wed, 02 May 2018 13:29:21 GMT

Hi,

By default the UART TX and RX pins are defined in the file called sdk_config.h.
The UART can be used in legacy mode or in EasyDMA mode. In legacy mode the UART will have an internal 6 byte FIFO, which need to be off-loaded by an interrupt and the UART will require a HF clock while waiting for data in RX mode. The current consumption depends on supply voltage and if you have enabled DCDC, but typically less than 1mA. In EasyDMA mode the UART will require a direct access to the RAM and the current consumption will typically be about 2mA, because more digital domains in the chip needs to be powered. There is no real time requirements to off-load data by an interrupt, since data is written to RAM directly.

By default the ble_app_uart example uses EasyDMA and that is why they are measuring ~2.5 mA. You can turn off EasyDMA in the file called sdk_config.h, but the example is still leaving the HF clock running and this draws ~470 uA. The clock is necessary to receive data. To turn it off you need to disable the UART.

To change advertising intervals you can modify APP_ADV_INTERVAL in main.c. To change the connection intervals you can modify MIN_CONN_INTERVAL and MAX_CONN_INTERVAL in main.c.
Then I would start with the proximity example and import the files ble_nus.c and ble_nus.h. Then look at the ble_app_uart example to see how to implement it it in your code.