problem - migration to S130 from S110

[air]

 Hello,

 

I am using Nrf51822.

I am using sd_110/application/bootloader, etc. in SDK_10.0 without problem.

Recently, migration to SDK_12.3 / sd_130 is in progress to add ble central function.

In SDK_12.3 / sd_130 environment, it operates as a softdevice and an application without bootloader.

When the bootloader is merged, it doesn’t operate after DFU.

Bootloader refers to single_bank_serial_s110 / single_bank_serial_s130 of nRF51_SDK_10.0.0_dc26b5e, and nothing has changed except for reference files in the existing S110.

I don't know why it doesn't work because there are no changes such as address map.

The question is broad, but what should I check?

 

Thanks.

[Vidar Berg]

Hello,

Have you re-compiled the SDK 10 bootloader against the new s130 v2.0.0 API headers (located in \nRF5_SDK_12.3.0_d7731ad\components\softdevice\s130\headers)? It may require some porting to get the legacy bootloader to work with this s130 v.2.0.

Best regards,

Vidar

[air]

 In addition to explaining the current environment

 

Application migration(done)

 - SDK12.3 / s130_nrf51_2.0.1_softdevice.hex

 - It operates well.

Bootloader migration(test)

- SDK10.0 / s130_nrf51_1.0.1_softdevice.hex

Merge all

 - s130_nrf51_2.0.1_softdevice.hex / application(above) / bootloader(above)

 - It doesn’t operate.

 

Question

1. As in the above case, does it work normally even if the SDK and SD versions of the application and bootloader are different?
2. If it works, can I add the BLE central function using SDK12.3 / s130_nrf51_2.0.1_softdevice.hex?

 

Considering the FW update of existing products, I am considering this structure to keep the bootloader as close as possible to the existing one.

More questions asked.

 

 Thanks.

[Vidar Berg]

I think the first step should be to make the SDK10.0 bootloader works with s130_nrf51_2.0.1_softdevice.hex, then you can try to merge everytrhing with the new app based on SDK 12.3.0. The s130 v2 download includes a migration document that can help you with this process.

s130 download page: https://www.nordicsemi.com/Software-and-tools/Software/S130/Download#infotabs

[air]

 Regarding the existing question,

I am trying to solve it with DFU by configuring a new application.

The part that I have checked is :

1. Application migration -> success

 - SDK12.3 / s130_nrf51_2.0.1_softdevice.hex

 - It operates well.

2. Bootloader migration -> success

 - SDK12.3 / s130_nrf51_2.0.1_softdevice.hex

3. Merge all -> success

 - s130_nrf51_2.0.1_softdevice.hex / application(above) / bootloader(above)

 - It operates well including DFU.

Question

1. I am trying to DFU the new application package above using the bootloader created based on the existing

SDK10.0 / s110_nrf51_8.0.0_softdevice.hex.

In other words, I want to upload any FW  package through DFU on the intermediate bootloader.

I am curious about which part of the existing bootloader should be modified.

Several attempts are being made, including the corrections below function.

 - uint32_t dfu_init_prevalidate(uint8_t * p_init_data, uint32_t init_data_len)

 Thanks,

[Vidar Berg]

Have you been able to make the bootloader from SDK 10.0.0 work with s130 v2.0.1? You generally cannot update from the legacy bootlaoder in SDK 10 to the new secure bootloader in SDK 12.3.0 because by default they have differerent start addresses in flash.

[air]

It seems that SDK 10.0 only supports s130 v1.0.0.

I wonder if it is possible to create a bootloader using s130 v2.0.1 in SDK 10.0.

If it is impossible, can't products developed in the existing SDK 10.0 be updated with the FW migrated

to SDK 12.3 using DFU?

It's a very important issue for me.

[Vidar Berg]

Actaully, you can try to use the legacy bootloader from nRF5 SDK 11 instead of porting the one from SDK 10. It was updated to work with s130 v2. You will not be able to use the Secure bootloader from SDK 12.3.0 as I have mentioned earlier.