Combined BT and serial Bootloader for S132

[Uwe]

The existing Development Environment:
- nRF52832
- SDK 11
- Softdevic S132
- Eclipse

Project Status:
- Nearly finished with working OTA - bootloader

Existing Bootloader:
- Based on SDK11: ../examples/dfu/bootloader/pca10040/dual-bank_ble

Goal:
- Combined serial and OTA - bootloder

Questions:
1. Does there exists a solution for a combined bootloader?
2. Is it in principle possible to integrate a combined boot booader into the limited Boot Flash area?
3. Which existing serial bootloaders from which SDK are recommented for finding a fast and save solution.

   

[Uwe]

Hi Hung,
many thanks for your answer, which had unfortunately not the content I hoped to hear.
Anyway.  The SDK15 .../examples/dfu - folder contains a lot of examples.
And because that it is difficult with the experiences of SDK11 to make a decision.
1. Exists there a general description of all examples 
2. What is the principle difference of projects without and and with the extension "_debug"
3. Which versions are suitable for nordic tools for serial DFU

Frank

[Hung Bui]

Hi Frank, 

 

I found an error in my last reply. 

2. You can always expand the bootloader by moving the start address the bootloader down in the flash. And increase the max size of it. 

Regarding your new questions:

1. "Exists there a general description of all examples " I don't understand this. Are you asking for the documentation ?  

2. The project with "_debug" will skip the version checking, and log printing is enabled. 

3. We have the tools to do DFU for any version. Is there any particular reason you want to use SDK v11 ? If you are using NRF52 chip , we would suggest you to start with SDK v15. 

I have a small guide about DFU here that you may want to try. 

[Uwe]

../../../../../components/libraries/bootloader/dfu/nrf_dfu_validation.c:91:1: error: missing braces

static nrf_crypto_hash_context_t m_hash_context = {{{0}}};

instead of

static nrf_crypto_hash_context_t m_hash_context = {0};

seams to help for removing the warning produced by a gcc-bug?

[Uwe]

I'm able to compile both SDK15 pca10040_uart - projects.

Thats why I like to ask a serious question now:

Issue:
The nordic - chip hardware is embedded in a further hardware shell with an additional µC.
Because that, the file tranfer via UART from external devices is only possible through
the second µC.
In other words: There is no need to secure and complicate the UART-connection between NORDIC µC.
and µC of the second shell.

Question:
Exists there a simple possibilty to switch off the need of authentication or key - exchange respectively
for the SDK15 uart - dfu - examples?

[Hung Bui]

Yes, you can try this :http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v15.0.0/ble_sdk_app_open_bootloader.html?cp=4_0_0_4_3_2

It's for USB DFU but it should be possible to change the transportation layer. 

[Uwe]

Is it possible to check the function of the open bootloader with nrfutil or nRFGoStudio before the work on customer serial transfer program will be started? 

[Nabil]

Hello, 

@Uwe Have you found a solution?

Thank you !

[Uwe]

Sorry for the delayed answer. I stopped the work on this topic since the priority of this partly project was changed.