about current problems of peripheral connection event in s132

[leopeng]

dear friend,

in document S132_SDS_v0.5 page 67,there is a table as followed.i have some problems:

1，what work is done in stae (A)-(I)? can i get a detailed description？

2，which peripheral device consume the current,such as Ion,Ix32k,Ix16M？and how can i get the value of each current? best regards.

[Stian Røed Hafskjold]

Hi,

1. 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.

2. 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.

[leopeng]

thank u for your help

[leopeng]

"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.

[Stian Røed Hafskjold]

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.

[leopeng]

thank u very much