Secure bootloader ble with UART

RE: Secure bootloader ble with UART

Hieu — Tue, 13 Aug 2024 10:56:40 GMT

[quote user="AP1"]i have attached files if you can tell us where it went wrong at least we can proceed further [/quote]

I usually only start considering debugging projects after there have been substantial evidences showing that it is necessary. That is not the case here. You will need to tell me what you have done, and what is not working in more details.

If you need someone to help you with your project, we do have a list of Design Partners here: Design Partners - nordicsemi.com

[quote user="AP1"]1. Hi i went through the links provided but i doesn't got much info to proceed further i have attached files if you can tell us where it went wrong at least we can proceed further [/quote]

I do not believe the links I provided you does not have information. Please go over discussions carefully, visit the links that the people provided. You will find references you can use in your implementation.

If you insist that it doesn't help, please answer these questions:

Have you tried the solution?
Can you explain to me in some details why the discussion there does not help?
What steps have you taken?
What is not working?

[quote user="AP1"]3. we have added UART with wrapper function in nrf_dfu_flash.c file and changes in the nrf_dfu_utils.c file so that it can able to accept irrespective of size[/quote]

This is the only detail you have given me, and I must ask, why did you do that?

The size check is there for a very good reason: preventing new download from overwriting important data regions. If your downloaded binary does not pass the size check, that means the binary is too big.

RE: Secure bootloader ble with UART

AP1 — Fri, 09 Aug 2024 05:37:24 GMT

1. Hi i went through the links provided but i doesn't got much info to proceed further i have attached files if you can tell us where it went wrong at least we can proceed further

2. \..\..\nRF5_SDK_17.1.0_ddde560_ver_1.1\examples\dfu\secure_bootloader\pca10056_s140_ble_debug

3. we have added UART with wrapper function in nrf_dfu_flash.c file and changes in the nrf_dfu_utils.c file so that it can able to accept irrespective of size

devzone.nordicsemi.com/.../nRF5_5F00_SDK_5F00_17.1.0_5F00_ddde560_5F00_ver_5F00_1.1.zip

RE: Secure bootloader ble with UART

Hieu — Wed, 07 Aug 2024 14:57:54 GMT

My question was not what your requirements are. They were plenty clear from the diagrams.

The question was: What do you need help with?

I already provide links with details on the current solution in the nRF5 SDK.

RE: Secure bootloader ble with UART

AP1 — Mon, 05 Aug 2024 07:12:45 GMT

1. in secure bootloader/pca10056_ble_debug sdk we need to add uart

2. For to tx the bin data to the other controller device

RE: Secure bootloader ble with UART

Hieu — Mon, 29 Jul 2024 13:36:28 GMT

Unfortunately, I still don't understand what you want help with, or if there is any issue at all.

[quote user="vthieu"]

I really sorry, but I am still unclear what the problem or question is, or if there is any.

Could you please use shorter sentences and more punctuations?

[/quote]

RE: Secure bootloader ble with UART

AP1 — Wed, 24 Jul 2024 04:48:43 GMT

Hi our requirement is instead of writing the data in flash for new bin the same bin data should be tx via uart we will comment the flash writing part in bootloader_ble_debug NOTE: this one we need to achieve through he secure_booloader/ble_bootloader_debug sdk

RE: Secure bootloader ble with UART

Hieu — Mon, 15 Jul 2024 21:25:57 GMT

I really sorry, but I am still unclear what the problem or question is, or if there is any.

Could you please use shorter sentences and more punctuations?

RE: Secure bootloader ble with UART

AP1 — Sat, 13 Jul 2024 14:28:53 GMT

1. Hi thanks for your reply let me explain in simple way in booloader_ble_debug sdk after while performing dfu the new firmware is going to write in the flash instead of writing the data in flash the same should be sent in the uart

2. flash -> replace with UART transfer

3. So whenever it is required we will write in flash or we will send same data in UART only one at a time

4. we need to achieve this in booloader_ble_debug app

New_firmware_write_func

if(cond)

{

uart_tx(data)

}

else

{

rc = nrf_fstorage_write(&m_fs, dest, p_src, len, (void *)callback);

}

RE: Secure bootloader ble with UART

Hieu — Sat, 13 Jul 2024 12:44:37 GMT

Hi AP1,

You have created a new ticket for this BLE connection issue, so let's try to fix the issue over there.

Regarding the requirement you have listed here, what kind of help do you expect from the community and Nordic here? I am a little unclear.

There is one part in your requirement that says that the image is only saved to flash if the image is for the current device.

Whether this is possible or not depends on what you mean by saved to flash. The image itself is always downloaded to flash memory. It is just first downloaded to the unused spare space, and then copied over to the application region when confirmed. Refer to: nRF5 SDK v17.1.0: Dual-bank and single-bank updates (nordicsemi.com).

As for transferring the image to another device over UART, you will want to take a look at the experimental NRF_DFU_SUPPORTS_EXTERNAL_APP feature.
It is discussed in this DevZone case: OTA from application layer .

I do not think you will want to enable UART as a DFU transport if you are doing this. If I understand correctly, the DFU libraries and bootloader just trigger a user implemented callback to start sending the image and does not itself take part in the sending. You will only need to enable UART functionality like you do in a regular app. I am not 100% certain about this last part, please go over the resources mentioned in the linked DevZone case.

RE: Secure bootloader ble with UART

AP1 — Thu, 11 Jul 2024 07:17:11 GMT

1. Hi currently i am using nrf52840 sdk ver 17.1.0 s140 sd we have added UART in the secure bootloader/ Bootloader_ble_debug

2. we can able to send multiple bytes once ie 53 46 30 04 02 01 00 FF 00 00 45 46 on reset of device

3. we have sending through the func ret_code_t ret = nrf_drv_uart_tx(&m_uart, data, sizeof(data));

4. while we tried to connect from mobile app but we are unable to connect to dfuTarg

Logs

<info> app: Inside main
<debug> app: In nrf_bootloader_init
<debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
<debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
<debug> nrf_dfu_settings: Using settings page.
<debug> nrf_dfu_settings: Copying forbidden parts from backup page.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
<debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
<debug> app: Enter nrf_bootloader_fw_activate
<info> app: No firmware to activate.
<info> app: Boot validation failed. No valid app to boot.
<debug> app: DFU mode because app is not valid.
<info> nrf_bootloader_wdt: WDT is not enabled
<debug> app: in weak nrf_dfu_init_user
<debug> app: timer_stop (0x200059BC)
<debug> app: timer_activate (0x200059BC)
<info> app: Entering DFU mode.
<debug> app: Initializing transports (found: 2)
<debug> nrf_dfu_ble: Initializing BLE DFU transport
<debug> nrf_dfu_ble: Setting up vector table: 0x000E8000
<debug> nrf_dfu_ble: Enabling SoftDevice.
<debug> nrf_dfu_ble: Configuring BLE stack.
<debug> nrf_dfu_ble: Enabling the BLE stack.
<debug> nrf_dfu_ble: No advertising name found
<debug> nrf_dfu_ble: Using default advertising name
<debug> nrf_dfu_ble: Advertising...
<debug> nrf_dfu_ble: BLE DFU transport initialized.
<debug> nrf_dfu_serial_uart: serial_dfu_transport_init()
<debug> nrf_dfu_serial_uart: serial_dfu_transport_init() completed
<info> nrf_dfu_serial_uart: Sending initial byte 0x24
<debug> nrf_dfu_flash: Initializing nrf_fstorage_sd backend.
<debug> app: Enter main loop

our settings as follows

RE: Secure bootloader ble with UART

AP1 — Wed, 10 Jul 2024 04:40:43 GMT

Hi i have updated the requirement can please go through it

RE: Secure bootloader ble with UART

AP1 — Tue, 09 Jul 2024 05:06:44 GMT

Hi edvin i have provided the feature requirement anything on this one

RE: Secure bootloader ble with UART

AP1 — Sun, 07 Jul 2024 06:05:27 GMT

Hi thanks for the reply our setup

1. Ble bootloader without any modification in this we need to achieve accept non ble bins and TX the non ble bins in uart irrespective of size

2. so we already able to perform non ble bins DFU OTA for any length thats working fine but we need an UART in the ble boorloader code so that we can tranfer the bin data over UART

requirement

1. it can able to accept non ble bins irrespective of the length

2. we wiill add uart to the ble bootloader for only to transmit ,RX is not required for us

Description :

1. In UART bootloader sdk it will not advertise but it has only UART RX but we need both TX and ble bootloader advertise

Note : so we need a sdk where it will advertise in dfu mode whenever required and able to perform dfu ota through mobile app for both ble bins and non ble bins and also should TX the non ble bins which is received through ble bootloader via UART TX PIN and write the nordic ble bins to the flash area as it is with dfu process

RE: Secure bootloader ble with UART

Edvin — Sat, 06 Jul 2024 21:40:09 GMT

Hello,

The length (and the signature of the image) is checked after the init packet is sent.

From what I understand you have this setup:

[Mobile device (or other BLE device)] <--- BLE ---> [nRF device running a modified BLE bootloader] <--- UART ---> [nRF running a UART bootloader]

right?

So where do you want to check the length? On the device in the middle, or on the nRF running the UART bootloader?

And how do you generate your DFU images? Using nrfutil? Or are you sending the raw binary files somehow?

If you are using nrfutil to generate the DFU image (zip file), then it contains the init packet (containing information about length and signature), and the actual DFU image, containing the new application.

The place that normally checks the init packet (and thus, the length) is the function: nrf_dfu_validation_init_cmd_execute(). But you should decide whether you need to check this on your BLE device, or if you should just forward the command that initializes this check to the UART bootloader.

Best regards,

Edvin

RE: Secure bootloader ble with UART

AP1 — Sat, 06 Jul 2024 14:50:23 GMT

Hi thanks for the reply what about this point

3. one more thing is there any checks for the size for uploading zip file via mobile app if it is there where should i check in secure bootloader/pca10056_ble sdk

Beacuse we already tried with other than nordic bin in which we observe that if the size of the bin is more than 1 MB than it was unable to perform DFU OTA but for less than 1 MB it is ok to perform DFU OTA

It is possible to perform dfu ota and transfer those bytes via UART Transport layer ?

RE: Secure bootloader ble with UART

Edvin — Fri, 05 Jul 2024 22:18:59 GMT

Oh, sorry. I misunderstood.

The init packet is sent first, and is used by the bootloader to determine whether or not to store the rest of the image. This protocol isn't very good documented. But do you want to do this test locally before forwarding the packet over UART, or do you want to check it on the device that receives the UART messages? Because the signature of the init packet and DFU image itself needs to be checked on the device that actually holds the keys for the bootloader/image.

[quote user="AP1"]4. we added uart to the secure bootloader /pca10056_ble whenever we call func app_uart_put(data[i]) in main func device unable to advertise [/quote]

So what do you observe? Do you just don't see the advertisements, or did you actually try to debug the bootloader? In cases like these, when you are modifying the bootloader, I suggest you use the pca10056_ble_debug bootloader, so that you can check the logs from the bootloader. This way it is easier to check where things don't go as planned.

When it is unable to advertise, what does the log say?

Best regards,

Edvin

RE: Secure bootloader ble with UART

AP1 — Thu, 04 Jul 2024 13:32:47 GMT

1. Hi thanks for the reply our requirements is we will use uart to transport the bin file which will receive in the dfu ota Ie through mobile instead of storing in the flash after uploading the bin from mobile

2. It should check some condition whether it should perform dfu ble for nordic or just take the bin to uart via uart we will transfer the data to other device so main thing is we should perform dfu via mobile app and the data should transfer in uart

3. one more thing is there any checks for the size for uploading zip file via mobile app if it is there where should i check in secure bootloader/pca10056_ble sdk

4. we added uart to the secure bootloader /pca10056_ble whenever we call func app_uart_put(data[i]) in main func device unable to advertise

RE: Secure bootloader ble with UART

Edvin — Thu, 04 Jul 2024 10:46:07 GMT

Oh, you may also need these in your sdk_config.h:

// <h> nrf_dfu_serial_uart - UART DFU transport

//==========================================================
// <q> NRF_DFU_SERIAL_UART_USES_HWFC  - HWFC configuration
 

#ifndef NRF_DFU_SERIAL_UART_USES_HWFC
#define NRF_DFU_SERIAL_UART_USES_HWFC 1
#endif

// <o> NRF_DFU_SERIAL_UART_RX_BUFFERS - Number of RX buffers. 
// <i> Number of buffers depends on flash access vs.
// <i> transport throughtput. If value is too low it may lead
// <i> to received packets being dropped.

#ifndef NRF_DFU_SERIAL_UART_RX_BUFFERS
#define NRF_DFU_SERIAL_UART_RX_BUFFERS 3
#endif

// </h> 
//==========================================================

// </h> 
//==========================================================

If it complains about other things that are lacking, look for it in the uart bootloader, and include it in your current bootloader.

BR,
Edvin

RE: Secure bootloader ble with UART

Edvin — Thu, 04 Jul 2024 10:44:50 GMT

Hello,

It should be possible to add uart to the BLE bootloader. But the way it is added in the bootloader is a bit strange.

If you look at nrf_dfu_serial_uart.c, line 86:

DFU_TRANSPORT_REGISTER(nrf_dfu_transport_t const uart_dfu_transport) =
{
    .init_func  = uart_dfu_transport_init,
    .close_func = uart_dfu_transport_close,
};

So simply by including this file, uart will be added as a DFU transport layer. This is then fetched by nrf_dfu_transports_init() in nrf_dfu_transport.c.

So it should be a matter of adding nrf_dfu_serial_uart.c (and including the folder that contains nrf_dfu_serial.h), and try to build. If it complains about lacking functions/files, then keep adding until it builds without warnings/errors.

Best regards,

Edvin