Migration nRF51822 -> nRF52832

RE: Migration nRF51822 -> nRF52832

stunt_man — Mon, 31 Oct 2016 15:18:24 GMT

As stated, here is how the aforementioned issues were solved.

Configuration : Hardware : PCA10040 Software : Segger Embedded Studio IDE using SoftDevice S132 v3 (Nordic’s SDK v12)

Migration from a PCA10001 to a 10040 (hardware), from SoftDevice S110 (Nordic’s SDK v7) to SoftDevice S132 v3 (Nordic’s SDK v12)

1/ Peer Manager

The main issue were about the migration from device manger to the new peer manager. Following Segger Embedded Studio tutorial in Nordic’s blog almost worked for me (devzone.nordicsemi.com/.../).

Tutorial is made for ble_app_beacon example. This example does not require peer manager. So everything works fine.

When adding peer manager some adjustments have to be made so the project can compile and run without any problem.

First adjustement: Memory settings. With SDK v12, the accurate configuration is the following:

FLASH_START=0x1F000
FLASH_SIZE=0x61000
SRAM_START=0x20002128
SRAM_SIZE=0xDED8

Second adjustment: Section To make project compile and run without memory problem, just follow RK’s advice (devzone.nordicsemi.com/.../)

flash_placement.xml has to be changed:

<MemorySegment name="$(FLASH_NAME:FLASH)">
....
    <ProgramSection alignment="4" load="Yes" runin=".fs_data_run" name=".fs_data" />
</MemorySegment>

<MemorySegment name="$(RAM_NAME:RAM);SRAM">
....
    <ProgramSection alignment="4" load="No" name=".fs_data_run" address_symbol="__start_fs_data"  end_symbol="__stop_fs_data" />
</MemorySegment>

Same for thumb_crt0.s

ldr r2, =__tdata_end__
bl memory_copy
# ADD HERE ... 
ldr r0, =__fs_data_load_start__
ldr r1, =__fs_data_start__
ldr r2, =__fs_data_end__
bl memory_copy
# TO HERE ...

At this point, the projet compiles and runs through Segger Embedded Studio!

2/ BLE Services

Some minor changes from SDK v7 to SDK v12 were made, inspired by Glucose-meter example (ble_app_gls). I recommend to have a deep look inside this example to write new services. No big changes, everything is pretty clear.

RE: Migration nRF51822 -> nRF52832

stunt_man — Wed, 26 Oct 2016 17:53:33 GMT

I am happy to say a solution was found following RK comment [here] - unvaluable thread for SES users! There was a problem with the sections the project. peer_manager() is now working (and now nrfjprog test gives the right answer)! Oh yeah! :-D

Now, I'll focus on the ble services.

When everything is working, I'll be writing a summary of what I've done. Your help was really appreciated

RE: Migration nRF51822 -> nRF52832

FormerMember — Wed, 26 Oct 2016 14:08:03 GMT

Okay. After programming the softdevice and the firmware, there should be tag in flash, indicating where the bonding information should be stored. That tag starts with FDS_PAGE_TAG_MAGIC (0xDEADCODE). After programming the softdevice + fimware to the chip. Could you read page 0x7D000 and check if has the DEADCODE tag:

nrfjprog -f nrf52 --memrd 0x7d000

You could also double check that it works with one of the examples in the sdk, like ble_app_gls for instance.

RE: Migration nRF51822 -> nRF52832

stunt_man — Wed, 26 Oct 2016 13:48:42 GMT

Yes, for each page (FDS_VIRTUAL_PAGES is set equal to 3 in sdk_config.h), the program goes to case FDS_PAGE_UNDEFINED" --> // Do not initialize or use this page.

RE: Migration nRF51822 -> nRF52832

FormerMember — Wed, 26 Oct 2016 13:38:59 GMT

Yes, that looks correct.

Where exactly in fds_init(..) -> pages_init(..): Where does the program "go", does it go into any of the switch cases? Is it " case FDS_PAGE_UNDEFINED" --> // Do not initialize or use this page. ?

RE: Migration nRF51822 -> nRF52832

stunt_man — Wed, 26 Oct 2016 13:10:14 GMT

1/ Thx, I'll have a look on this service

2/ I use a PCA10040 v1.1.0

Global settings for the device : Flash: START_ADDRESS 0x0 / SIZE 0x00080000 (512 kb) RAM: START_ADDRESS 0x20000000 / SIZE 0x00010000 (64 kb)

Due to the fact that SoftDevice (SDK12 / S132 v3.0) will use part of this space, settings for the project are the following Flash: START_ADDRESS 0x1F000 / SIZE 0x61000 (approximately 390 kb) RAM: START_ADDRESS 0x20002128 / SIZE 0xDED8 (approximately 55 kb)

Does it look right?

RE: Migration nRF51822 -> nRF52832

FormerMember — Wed, 26 Oct 2016 12:35:44 GMT

1) The example ble_app_uart shows how to implement a custom service.

2) Which size/length do you use for the flash and RAM settings?

RE: Migration nRF51822 -> nRF52832

stunt_man — Wed, 26 Oct 2016 11:53:30 GMT

#ifndef FDS_ENABLED #define FDS_ENABLED 1 #endif #if FDS_ENABLED // FDS_OP_QUEUE_SIZE - Size of the internal queue. #ifndef FDS_OP_QUEUE_SIZE #define FDS_OP_QUEUE_SIZE 4 #endif

// <o> FDS_CHUNK_QUEUE_SIZE - Determines how many @ref fds_record_chunk_t structures can be buffered at any time. 
#ifndef FDS_CHUNK_QUEUE_SIZE
#define FDS_CHUNK_QUEUE_SIZE 8
#endif

// <o> FDS_MAX_USERS - Maximum number of callbacks that can be registered. 
#ifndef FDS_MAX_USERS
#define FDS_MAX_USERS 8
#endif

#ifndef FDS_VIRTUAL_PAGES
#define FDS_VIRTUAL_PAGES 3
#endif

#ifndef FDS_VIRTUAL_PAGE_SIZE
#define FDS_VIRTUAL_PAGE_SIZE 1024
#endif

Preprocessor definitions I added: FDS_ENABLED FSTORAGE_ENABLED PEER_MANAGER_ENABLED

RE: Migration nRF51822 -> nRF52832

stunt_man — Wed, 26 Oct 2016 11:51:44 GMT

Hi Kristin, thank you for your reply.

1/ About service and characteristics: same result with nRF Connect / Android or iOS (iOS is indeed making a service discovery). My guess is that it has something to do with the way I implement my custom services (initialization and event management). What worked with SDK 8 seems to be obsolete with SDK12 - S132. Do you know if there is an example where I can fin custom service implementation - currently analysing ble_hrs file?

2/ Concerning peer_manager : as stated, error happens during pm_init(). To be precise, in pm_init(), a call is made to pds_init(). In pds_init(), everything is fine until fds_init(). Calling fds_init() returns a FDS_ERR_NO_PAGES error that causes the NRF_ERROR_NO_MEM. Memory configuration is the following: FLASH_START=0x1F000 SRAM_START=0x20002128 I paste my FDS settings in sdk_config.h in next comment

RE: Migration nRF51822 -> nRF52832

FormerMember — Wed, 26 Oct 2016 11:19:18 GMT

Being able to see the services and characteristics is independent of the peer manager.

I assume that the service and characteristics have been successfully added to the device? If so, could you use the sniffer to check if the iOS device is doing a service discovery? Could you try do delete all cached information on the iOS device about the nRF52? Does it work with nRF Connect (PC) or Android?

Regarding pm_init()/fds_init() failing: If you run the chip in debug mode, where exactly is the error code being returned from? Which FDS settings do you use in sdk_config.h?