about current problems of peripheral connection event in s132

RE: about current problems of peripheral connection event in s132

leopeng — Sat, 02 Dec 2017 07:56:00 GMT

thank u very much. As u mentioned here infocenter.nordicsemi.com/index.jsp, Icpu,flash is called I_IDDFLASH(DCDC). How to determine it? There are some options,such as cache enabled\disabled, DCDC\LDO. How to determine which one is used? i am using nRF5_SDK_12.3.0 and nRF PCA10040, and all configurations are set by default. In addition, where can i get the sleep current of the chip (the state followed (a) to (i) in an interval)?

RE: about current problems of peripheral connection event in s132

Stian Røed Hafskjold — Fri, 01 Dec 2017 07:31:43 GMT

Hi, it is called I_ON, an you can find it here (under electrical specification in the POWER chapter): infocenter.nordicsemi.com/.../power.html

RE: about current problems of peripheral connection event in s132

leopeng — Fri, 01 Dec 2017 03:19:13 GMT

Dear Stian, as you mentioned, I_ON is the System ON base current. What is it called in the spec. here: infocenter.nordicsemi.com/topi...

RE: about current problems of peripheral connection event in s132

leopeng — Thu, 02 Mar 2017 01:09:51 GMT

thank u very much

RE: about current problems of peripheral connection event in s132

Stian Røed Hafskjold — Wed, 01 Mar 2017 14:37:58 GMT

First of all you should download the newest Softdevice specification (v3.1). The 0.5 version was released as an alpha version in the early days of the chip.

Icpu,flash is the current consumption of the CPU when running code from flash. You can find the current spec here: infocenter.nordicsemi.com/.../cpu.html It's called I_IDDFLASH(DCDC) in the spec.

Icrypto is the AES CCM module running encrypting/decrypting packets. This is only relevant for encrypted connection. It basically means that the AES module is blocked by the softdevice during RX and TX. When and how much the AES module is used in the softdevice (and hence the current consumption) is not released as part of the spec.

RE: about current problems of peripheral connection event in s132

leopeng — Wed, 01 Mar 2017 14:03:06 GMT

"work" ,such as,state D,it means start the RF.However,state (a) and (b)'s detail are not so easily understand.and Icpu,Icrypto stand for what ? regards.

RE: about current problems of peripheral connection event in s132

leopeng — Wed, 01 Mar 2017 13:18:13 GMT

thank u for your help

RE: about current problems of peripheral connection event in s132

Stian Røed Hafskjold — Wed, 01 Mar 2017 13:06:20 GMT

Hi,

I'm not sure what you mean by "work". The different peripherals that are active is listed in the table you posted. What happens in each step is internal to the SoftDevice and we can not give a detailed description about that. All I can say is that it is configuring the radio, processing TX/RX data, starting/stopping the HF crystal etc.. All according to the BLE spec.
The different current values in the table are described in the respective peripheral chapter in the PS, under the electrical specification chapter.

I_ON is the System ON base current
I_RTC is the RTC clock that is required for the BLE event timing.
I_X32k is the 32 kHz clock that is required by the RTC
I_X16M (which should be X32M) is the HF clock that is required by the radio.
The rest is CPU and radio currents.

You can look here, devzone.nordicsemi.com/.../, to see how different BLE parameters will impact the current consumption of the different stages in the table.