DFU gcc linker setting

RE: DFU gcc linker setting

Sigurd — Thu, 18 Mar 2021 14:20:40 GMT

[quote user="tai2020"]But when I tryed to program the package via DFU, the connection stoped and the package did not upload.[/quote]

Maybe you could use the debug variant of the bootloader, it's the bootloader project with the _debug prefix, and take a look at the nrf_log output from the bootloader to see if you get any errors in the bootloader when DFU is performed?

[quote user="tai2020"]My problem is that everything seems ok with keil. But I can not use gcc complier[/quote]

Check if RAM and FLASH start address is the same in Keil and in the GCC linker script. Maybe there is a difference there.

RE: DFU gcc linker setting

Tai — Thu, 18 Mar 2021 13:46:30 GMT

I do not get any errors. The code compiled and the package is created without any waring or errors:

make: Entering directory `.../nRF5_SDK_17.0.2_d674dde/examples/ble_peripheral/ble_hrs/pca10040/s132/armgcc'
Linking target: _build/nrf52832_xxaa.out
   text    data     bss     dec     hex filename
  93004     188    4880   98072   17f18 _build/nrf52832_xxaa.out
Preparing: _build/nrf52832_xxaa.hex
Preparing: _build/nrf52832_xxaa.bin
DONE nrf52832_xxaa
make: Leaving directory `.../nRF5_SDK_17.0.2_d674dde/examples/ble_peripheral/ble_hrs/pca10040/s132/armgcc'

C:\...>nrfutil pkg generate --hw-version 52 --application-version 0 --application ...\nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_hrs\pca10040\s132\armgcc\_build\nrf52832_xxaa.hex --sd-req 0x0101 --key-file keys/private.key app_001001-B.zip
Zip created at app.zip

I had already added NRF_DFU_TRANSPORT_BLE=1 and NRF_DFU_SVCI_ENABLED to keil and makefile. But I have not this flag even in keil: BL_SETTINGS_ACCESS_ONLY

My problem is that everything seems ok with keil. But I can not use gcc complier.

RE: DFU gcc linker setting

Sigurd — Tue, 16 Mar 2021 13:02:22 GMT

[quote user="tai2020"]But I can not use the package created by gcc.[/quote]

Do you get any errors, warnings? Do you have any log output?

You might need to add e.g. these C and Assembler flags to the makefile:

NRF_DFU_TRANSPORT_BLE=1
NRF_DFU_SVCI_ENABLED
BL_SETTINGS_ACCESS_ONLY

RE: DFU gcc linker setting

Tai — Thu, 11 Mar 2021 21:52:24 GMT

It is 17.0.2 version.

I am using hrs example and I added ble_dfu_buttonless_async_svci_init() and other dfu codes to the example. When I use .hex created by keil it seems to be ok. But I can not use the package created by gcc.

it is DFU package creator that I use:

nrfutil pkg generate --hw-version 52 --application-version 0 --application ~\nRF5_SDK_17.0.2_d674dde\examples\ble_peripheral\ble_habil_up\pca10040\s132\armgcc\_build\nrf52832_xxaa.hex --sd-req 0x0101 --key-file keys/private.key app_%1.zip

RE: DFU gcc linker setting

Sigurd — Thu, 11 Mar 2021 20:13:49 GMT

[quote user="tai2020"]But when I tryed to program the package via DFU, the connection stoped and the package did not upload[/quote]

What SDK version are you using?

Are you using the bootloader in examples\dfu\secure_bootloader\pca10040_s132_ble ?

Can you post the command you used to create the DFU package?

RE: DFU gcc linker setting

Tai — Wed, 10 Mar 2021 14:48:26 GMT

I tryed to change the flash and ram size to

MEMORY
{
  FLASH (rx) : ORIGIN = 0x26000, LENGTH = 0x52000
  RAM (rwx) :  ORIGIN = 0x20002bf0, LENGTH = 0xd410
  uicr_bootloader_start_address (r) : ORIGIN = 0x10001014, LENGTH = 0x4
}

SECTIONS
{
  . = ALIGN(4);
  .uicr_bootloader_start_address :
  {
    PROVIDE(__start_uicr_bootloader_start_address = .);
    KEEP(*(SORT(.uicr_bootloader_start_address*)))
    PROVIDE(__stop_uicr_bootloader_start_address = .);
  } > uicr_bootloader_start_address
}

I could compile and link and creat the package. But when I tryed to program the package via DFU, the connection stoped and the package did not upload.

RE: DFU gcc linker setting

Tai — Wed, 10 Mar 2021 14:40:07 GMT

I am going to try it.

But know I have another question. I used hrs example and then I added ble_dfu_buttonless_async_svci_init() to it in Keil. DFU seems to work correctly. I wonder if there I correctly configured everything. For example Flash length is different in gcc linker file.

RE: DFU gcc linker setting

Sigurd — Wed, 10 Mar 2021 14:15:30 GMT

[quote user="tai2020"]so if I replace the linker file by ble_app_buttonless_dfu_gcc_nrf52.ld and modify FLASH (rx) and RAM (rwx) it should work?[/quote]

Yes, I think that should be enough. If you are using the bottonless DFU service, then you might need to call ble_dfu_buttonless_async_svci_init() in your main function as well.

RE: DFU gcc linker setting

Tai — Wed, 10 Mar 2021 13:57:31 GMT

thanks for your reply.

so if I replace the linker file by ble_app_buttonless_dfu_gcc_nrf52.ld and modify FLASH (rx) and RAM (rwx) it should work?

RE: DFU gcc linker setting

Sigurd — Wed, 10 Mar 2021 13:49:30 GMT

Hi,

[quote user=""]I know that I should define the location where bootloader start address is stored in this file. But I have not found any example.[/quote]

Take a look at the gcc linker setting in SDK_folder\examples\ble_peripheral\ble_app_buttonless_dfu\pca10040\s132\armgcc\ble_app_buttonless_dfu_gcc_nrf52.ld

[quote user=""]My second question is that how I can find this address in my bootloader file?[/quote]

The bootloader linker script will write the bootloader start address to the UICR register. This value will be written in the bootloader HEX file and thus written to UICR when the bootloader is flashed into the chip. See the file nrf_bootloader_info.c