RE: IoT Migration to nRF52 DK

Stian Røed Hafskjold — Mon, 21 Dec 2015 14:59:06 GMT

Are you talking about Keil packs? The IoT SDK does not use Keil packs. Just use the zip-file instead. The same goes for the 0.9.x version of the nRF52 SDK. The nRF5 SDK v11.0.0 now supports nRF52 as well. You can find it here: developer.nordicsemi.com/.../. This SDK also include Keil pack installer.
The IoT SDK does not have a migration guide, but you can find a general guide on how to migrate from nRF51 to nRF52 here: infocenter.nordicsemi.com/.../preface.html

It seems to me like you are combining nRF52 SDK and the IoT SDK. For the BLE services you can migrate using the migration guide. The ADC is completely new and has a new API and therefore you should check out some of the examples in the SDK.

A lot have changed in the IoT SDK and I think the easiest way is to start out with the Coap example in the new SDK.

DTLS is included in the IoT SDK v0.9.x
CPU is used during preprocessing of the packet to be transmitted, and during radio start/turn-around to set up the radio parameters. This is for a very short time only and does not have a big impact on the power consumption.
The advertising data is given in the ipv6_medium_ble_cfg.h file. And the m_adv_params struct is set in the adv_params_set function in ipv6_medium_ble.c file

RE: IoT Migration to nRF52 DK

cucu — Thu, 10 Dec 2015 09:21:46 GMT

one more question..

what is medium module? ,
- in 0.9 iot sdk , advertising init, and start not in main.c , but medium module..
- my project, changed adv_data, and rs data when every 100ms... (ibeacon/eddy stone, and scan response -> sensor data..) how to solve this problem..