Thread+BLE,DFU through ble

RE: Thread+BLE,DFU through ble

Vidar Berg — Fri, 20 Dec 2019 14:02:56 GMT

Hello,

I think Keil is allocating it at runtime. The OT section is not specified in the linker settings, at least. Have you tried, and if so, did you run into any problems?

RE: Thread+BLE,DFU through ble

Snail Feng — Thu, 19 Dec 2019 08:26:03 GMT

Hello, how should keil5 be configured?

RE: Thread+BLE,DFU through ble

Vidar Berg — Fri, 29 Nov 2019 15:09:09 GMT

Hi,

The table is showing the start address for the release build (project config without *_debug in the name). So the non-debug variant starts at address 0xf8000. You can see this from the project settings in SES.

RE: Thread+BLE,DFU through ble

NOA-BEN — Fri, 29 Nov 2019 09:18:54 GMT

Hi Vidar:

Thank you very much.DFU is ok after I change OT flash address to 0xed000. Could you tell me how to know the bootloader start address is 0xf1000, not 0xf8000?

RE: Thread+BLE,DFU through ble

Vidar Berg — Fri, 29 Nov 2019 08:23:52 GMT

Sorry, I just realized the 0xf000 address I suggested for ot_flash_data isn't going to work. The section is 4 pages long so it would end at 0xf0000 + 0x4000 well inside the bootloader which is currently starting at 0xf1000.

This should make it work (<bootloader start address> - 0x4000):

  <MemorySegment name="ot_flash_data" start="0xed000" size="0x4000">
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".ot_flash_data" address_symbol="__start_ot_flash_data" end_symbol="__stop_ot_flash_data" start = "0xed000" size="0x4000" />
  </MemorySegment>
</Root>

RE: Thread+BLE,DFU through ble

NOA-BEN — Fri, 29 Nov 2019 03:06:00 GMT

Hi Vidar:

Is there any progress on your side? My client is very anxious and explicitly requires the capabilities of BLE OTA

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 11:03:36 GMT

Hi Vidar:

I used Ses to Debug. When I select SES Debug->GO, the apple can run. But I think this result is because the board will be flashed program again after I select SES Debug->GO.

RE: Thread+BLE,DFU through ble

Vidar Berg — Thu, 28 Nov 2019 10:53:40 GMT

Are you only using logging for debugging? Do you use SES or one of the other supported IDEs so you can place breakpoints, etc.?

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 10:50:53 GMT

Hi Vidar:

Sorry, I do not know how to debug the app. Because the app can not run after dfu.

RE: Thread+BLE,DFU through ble

Vidar Berg — Thu, 28 Nov 2019 10:26:47 GMT

Hi,

Yes, that's the same as I got. The program is stuck in the Application's hardfault handler at address 0x26362. Probably before the app has had time to start logging. Are you able to debug the app after DFU?

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 10:23:22 GMT

Hi Vidar:

I don't know what happened, the print serial port doesn't print the data anymore。

nrfjprog --readregs
R0:   0x00000068
R1:   0x0002503C
R2:   0x00026000
R3:   0x00026363
R4:   0x200001B4
R5:   0x00000001
R6:   0x000C5C10
R7:   0x00000000
R8:   0x2003FE98
R9:   0x00000000
R10:  0x00000000
R11:  0x00000000
R12:  0xFFFFFFFF
SP:   0x2003FE08
LR:   0xFFFFFFF1
PC:   0x00026362
xPSR: 0x21000003
MSP:  0x2003FE08
PSP:  0x00000000

RE: Thread+BLE,DFU through ble

Vidar Berg — Thu, 28 Nov 2019 10:09:12 GMT

[quote userid="73760" url="~/f/nordic-q-a/54860/thread-ble-dfu-through-ble/222568"] And after DFU is completed, the bootloader program is stuck in this place. settings_backup_valid always false.[/quote]

That didn't happen when I tried the hex files you uploaded earlier. Is it stuck, or is it going in a bootloop? If stuck, try to call "nrfjprog --readregs" and post the result here.

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 10:04:20 GMT

Hi, Vidar:

Yes, I also feel that the OT flash and the partition boot table overlap. And after DFU is completed, the bootloader program is stuck in this place. settings_backup_valid always false.

And I found that the address space used by the boot sector program is 0x000-0x100000. And I tried to change the start address of the OT flash to 0xf0000. Problem still

RE: Thread+BLE,DFU through ble

Vidar Berg — Thu, 28 Nov 2019 08:24:46 GMT

Hi,

The DFU part seems to be working, but there is a hardfault in the main app after it's complete. Have you tried to debug the application after it's uploaded? The first step could be to check if it even reaches main().

Edit: I think it has to be to ot_flash_data section, it seems to be placed at a fixed address, unlike the FDS pages that are placed dynamically depending on the bootloader start address. So I suspect the app is 'hardfaulting' when it tries to access the page because it's overlapping with the bootlaoder. Can you try to move it to address 0xf0000?

  <MemorySegment name="ot_flash_data" start="0xf0000" size="0x4000">
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".ot_flash_data" address_symbol="__start_ot_flash_data" end_symbol="__stop_ot_flash_data" start = "0xf0000" size="0x4000" />
  </MemorySegment>
</Root>

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 08:14:15 GMT

Hi, Vidar:

sorry, I forget to add bootloader. I will add now.devzone.nordicsemi.com/.../secure_5F00_bootloader_5F00_ble_5F00_s140_5F00_pca10056_5F00_debug.hex

RE: Thread+BLE,DFU through ble

Vidar Berg — Thu, 28 Nov 2019 08:10:15 GMT

Hi,

I would like to test this here, but it looks like the bootloader hex is missing?

RE: Thread+BLE,DFU through ble

NOA-BEN — Thu, 28 Nov 2019 07:40:02 GMT

Hi Vidar:

I compiled this project and generated a application hex file . File Directory is:examples\multiprotocol\ble_thread\ble_thread_dyn_mtd_coap_cli.

And i program softdevice and bootloader hex to board.

From the printed data, DFU is complete, but it cannot jump to the application.devzone.nordicsemi.com/.../ble_5F00_thread_5F00_dyn_5F00_mtd_5F00_coap_5F00_cli_5F00_pca10056_5F00_s140.hex devzone.nordicsemi.com/.../8103.s140_5F00_nrf52_5F00_6.1.1_5F00_softdevice.hex devzone.nordicsemi.com/.../syc_5F00_app3.zip

 0> <debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FE000, len=1 pages), queue usage: 3
 0> <debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FE000, src=0x2000A698, len=896 bytes), queue usage: 4
 0> <debug> nrf_dfu_req_handler: Request handling complete. Result: 0x1
 0> <debug> app: timer_stop (0x20005944)
 0> <debug> app: timer_activate (0x20005944)
 0> <debug> nrf_dfu_flash: Flash erase success: addr=0x000FF000, pending 4
 0> <debug> nrf_dfu_flash: Flash write success: addr=0x000FF000, pending 3
 0> <debug> nrf_dfu_flash: Flash erase success: addr=0x000FE000, pending 2
 0> <debug> nrf_dfu_flash: Flash write success: addr=0x000FE000, pending 1
 0> <debug> nrf_dfu_req_handler: All flash operations have completed. DFU completed.
 0> <debug> app: Shutting down transports (found: 1)
 0> <debug> nrf_dfu_ble: Shutting down BLE transport.
 0> <debug> nrf_dfu_ble: Disconnecting.
 0> <debug> nrf_dfu_ble: BLE transport shut down.
 0> <debug> app: Resetting bootloader.
 0> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
 0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 0> <info> app: Inside main
 0> <debug> app: In nrf_bootloader_init
 0> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
 0> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
 0> <debug> nrf_dfu_settings: Using settings page.
 0> <debug> nrf_dfu_settings: Copying forbidden parts from backup page.
 0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 0> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
 0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 0> <debug> app: Enter nrf_bootloader_fw_activate
 0> <debug> app: Valid App
 0> <debug> app: Enter nrf_dfu_app_continue
 0> <debug> app: No copy needed
 0> <debug> app: Setting app as valid
 0> <debug> nrf_dfu_settings: Writing settings...
 0> <debug> nrf_dfu_settings: Erasing old settings at: 0x000FF000
 0> <debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FF000, len=1 pages), queue usage: 0
 0> <debug> nrf_dfu_flash: Flash erase success: addr=0x000FF000, pending 0
 0> <debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FF000, src=0x2000A318, len=896 bytes), queue usage: 1
 0> <debug> nrf_dfu_flash: Flash write success: addr=0x000FF000, pending 0
 0> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
 0> <debug> nrf_dfu_settings: Writing settings...
 0> <debug> nrf_dfu_settings: Erasing old settings at: 0x000FE000
 0> <debug> nrf_dfu_flash: nrf_fstorage_erase(addr=0x0x000FE000, len=1 pages), queue usage: 1
 0> <debug> nrf_dfu_flash: Flash erase success: addr=0x000FE000, pending 0
 0> <debug> nrf_dfu_flash: nrf_fstorage_write(addr=0x000FE000, src=0x2000A698, len=896 bytes), queue usage: 1
 0> <debug> nrf_dfu_flash: Flash write success: addr=0x000FE000, pending 0
 0> <debug> app: Resetting bootloader.
 0> <info> nrf_dfu_settings: Backing up settings page to address 0xFE000.
 0> <debug> nrf_dfu_settings: Destination settings are identical to source, write not needed. Skipping.
 0> <info> app: Inside main
 0> <debug> app: In nrf_bootloader_init
 0> <debug> nrf_dfu_settings: Calling nrf_dfu_settings_init()...
 0> <debug> nrf_dfu_flash: Initializing nrf_fstorage_nvmc backend.
 0> <debug> nrf_dfu_settings: Using settings page.
 0> <debug> nrf_dfu_set

RE: Thread+BLE,DFU through ble

NOA-BEN — Wed, 27 Nov 2019 10:34:28 GMT

Hi Vidar:

Thank you for so fast reply. I will try to test BLE DFU again.

RE: Thread+BLE,DFU through ble

Vidar Berg — Wed, 27 Nov 2019 07:13:06 GMT

Hi,

I don't see any problems with using the BLE bootloader on the same device as a BLE+Thread app. I would suggest that you try to debug the bootloader after DFU to find out why it falls back to DFU mode instead of booting the app. First step can be to place breakpoints in nrf_bootloader.c::dfu_enter_check() and see if it returns true.

The memory layout should be ok, but make sure that NRF_DFU_APP_DATA_AREA_SIZE in the bootloader project corresponds with the number of flash pages used by your application (OT Data + FDS pages if you use FDS in your app).