Migrating from Keil to SES - Error with DFU INIT service

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Mon, 04 May 2020 08:54:18 GMT

Hmm, I didnt think that the placement of the line in the flash_placement.xml should have anything to say as the sections is absolutely placed. However, it could be that absolutely placed sections should be placed at the end of the Flash Memory Segment or in a separate memory segment.

Best regards

Bjørn

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Thu, 30 Apr 2020 12:20:24 GMT

One quick question Bjorn.

Does placement of the line

in the flash placement file has any significane?

Because when i place that statement at line 13 below the .data, it is not compiling, giving me the syntax error but when placing the same statement at line 15 below the .fs data run, it compiled fine and everything worked.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Thu, 30 Apr 2020 08:28:18 GMT

Great! Happy to hear that the application is now working as it should 🙂

-Bjørn

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Thu, 30 Apr 2020 08:20:29 GMT

Hi Bjorn,

Instead of creating new memory segment for bootloader settings, i have copied this statement

into existing flash memory segment and removing the other bootloader settings in the flash segment as you suggested above worked.

Now i am able to flash the program successfully.

Attaching the modified flash placement for your reference.

Thanks for your continued support in resolving this issue. Really appreciate your time and effort.

devzone.nordicsemi.com/.../4571.flash_5F00_placement.xml

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Thu, 30 Apr 2020 07:50:18 GMT

I have already tried that Bjorn. But it gives me the same error as the above.

Removing that doesn't make any difference.

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Thu, 30 Apr 2020 06:41:36 GMT

You have two .bootloader sections one in the first memory segment and one in the last. Can you try to remove the

in the first memory segment, i.e.

<Root name="Flash Section Placement">
  <MemorySegment name="$(FLASH_NAME:FLASH)">
    <ProgramSection alignment="0x100" load="Yes" name=".vectors" start="$(FLASH_START:)" />
    <ProgramSection alignment="4" load="Yes" name=".init" />
    <ProgramSection alignment="4" load="Yes" name=".init_rodata" />
    <ProgramSection alignment="4" load="Yes" name=".text" />
    <ProgramSection alignment="4" load="Yes" name=".dtors" />
    <ProgramSection alignment="4" load="Yes" name=".ctors" />
    <ProgramSection alignment="4" load="Yes" name=".rodata" />
    <ProgramSection alignment="4" load="Yes" name=".ARM.exidx" address_symbol="__exidx_start" end_symbol="__exidx_end" />
    <ProgramSection alignment="4" load="Yes" runin=".fast_run" name=".fast" /> 
    <ProgramSection alignment="4" load="Yes" runin=".data_run" name=".data" />
    <ProgramSection alignment="4" load="Yes" runin=".tdata_run" name=".tdata" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" runin=".fs_data_run" name=".fs_data" />
  </MemorySegment>
  <MemorySegment name="$(RAM_NAME:RAM);SRAM">
    <ProgramSection alignment="0x100" load="No" name=".vectors_ram" start="$(RAM_START:$(SRAM_START:))" />
    <ProgramSection alignment="4" load="No" name=".fast_run" />
    <ProgramSection alignment="4" load="No" name=".data_run" />
    <ProgramSection alignment="4" load="No" name=".tdata_run" />
    <ProgramSection alignment="4" load="No" keep="Yes" name=".fs_data_run" address_symbol="__start_fs_data" end_symbol="__stop_fs_data" />
    <ProgramSection alignment="4" load="No" name=".bss" />
    <ProgramSection alignment="4" load="No" name=".tbss" />
    <ProgramSection alignment="4" load="No" name=".non_init" />
    <ProgramSection alignment="4" size="__HEAPSIZE__" load="No" name=".heap" />
    <ProgramSection alignment="8" size="__STACKSIZE__" load="No" place_from_segment_end="Yes" name=".stack" />
    <ProgramSection alignment="8" size="__STACKSIZE_PROCESS__" load="No" name=".stack_process" />
  </MemorySegment>
  <MemorySegment name="$(FLASH2_NAME:FLASH2)">
    <ProgramSection alignment="4" load="Yes" name=".text2" />
    <ProgramSection alignment="4" load="Yes" name=".rodata2" />
    <ProgramSection alignment="4" load="Yes" runin=".data2_run" name=".data2" />
  </MemorySegment>
  <MemorySegment name="$(RAM2_NAME:RAM2)">
    <ProgramSection alignment="4" load="No" name=".data2_run" />
    <ProgramSection alignment="4" load="No" name=".bss2" />
  </MemorySegment>
  <MemorySegment name="bootloaderSettings" start="0x0003FC00" size="0x400">
    <ProgramSection alignment="4" keep="Yes" load="No" name=".bootloaderSettings" address_symbol="__start_bootloader_settings" end_symbol="__stop_bootloader_settings" start = "0x0003FC00" size="0x400" />
  </MemorySegment>
</Root>

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Wed, 29 Apr 2020 14:02:13 GMT

Awaiting your response Bjorn

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Tue, 28 Apr 2020 09:36:14 GMT

Awaiting your response Bjorn. We are having tight schedule to fix this ASAP.

I really appreciate your help in resolving this issue at the earliest.

Thanks in Advance.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Mon, 27 Apr 2020 09:24:03 GMT

Any insights Bjorn?

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Fri, 24 Apr 2020 14:14:31 GMT

Hi Bjorn,

I have added the recommended lines to the flash placement file and it is giving me the syntax error while linking .elf files.

Attaching the screenshot for your reference.

Also attaching the modified flash placement file for your reference.

devzone.nordicsemi.com/.../7485.flash_5F00_placement.xml

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Fri, 24 Apr 2020 13:39:02 GMT

Yes, looking at the .map file you sent I see that the bootloader settings are place at 0x3ef84

.bootloaderSettings
                0x000000000003ef84      0x400
                0x000000000003ef84                __bootloaderSettings_start__ = .
 *(.bootloaderSettings .bootloaderSettings.*)
 .bootloaderSettings
                0x000000000003ef84      0x400 Output/SpineFit Strack Internal/Obj/nrf_dfu_settings.o
                0x000000000003ef84                m_dfu_settings_buffer
                0x000000000003f384                __bootloaderSettings_end__ = (__bootloaderSettings_start__ + SIZEOF (.bootloaderSettings))
                0x0000000000000400                __bootloaderSettings_size__ = SIZEOF (.bootloaderSettings)
                0x000000000003f384                __bootloaderSettings_load_end__ = __bootloaderSettings_end__
                0x0000000000000001                . = ASSERT (((__bootloaderSettings_start__ == __bootloaderSettings_end__) || ((__bootloaderSettings_end__ - __FLASH_segment_start__) <= __FLASH_segment_size__)), error: .bootloaderSettings is too large to fit in FLASH memory segment)
                0x000000000003f384                __data_load_start__ = ALIGN (__bootloaderSettings_end__, 0x4)

The m_dfu_settings_buffer is placed in a section called .bootloaderSettings.

uint8_t m_dfu_settings_buffer[CODE_PAGE_SIZE] __attribute__ ((section(".bootloaderSettings")))
                                              __attribute__((used));

I cant see any bootloaderSettings in your flash_placement.xml file you attached to your question, so need to add this snippet to your projects flash_placement.xml file

<MemorySegment name="bootloaderSettings" start="0x0003FC00" size="0x400">
    <ProgramSection alignment="4" keep="Yes" load="No" name=".bootloaderSettings" address_symbol="__start_bootloader_settings" end_symbol="__stop_bootloader_settings" start = "0x0003FC00" size="0x400" />
</MemorySegment>

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Fri, 24 Apr 2020 09:49:38 GMT

Thanks for the quick reply Bjorn.

I don't think the pointer is at 0x0003FC00. Attaching the screenshot of the debug trace for your reference.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Fri, 24 Apr 2020 07:56:39 GMT

HI Krish,

Ok, so then it has to be the nrf_dfu_settings_write() call at the end to nrf_dfu_settings_init(), which is called at the end of ble_dfu_init() that is the cause. As the error code implies, the address passed to nrf_dfu_flash_erase is not aligned to a page boundary.

/**@brief Function for erasing data from flash (with or without the SoftDevice enabled).
 *
 * @param[in]  p_dest    The address of the first byte to be deleted.
 * @param[in]  num_pages The number of flash pages to be deleted.
 * @param[in]  callback  Pointer to the callback function.
 *
 * @retval  FS_SUCCESS              If the operation was successful.
 * @retval  FS_ERR_UNALIGNED_ADDR   If @p p_dest is not aligned to a page boundary.
 * @retval  FS_ERR_INVALID_ADDR     If @p p_dest does not point to the start of a flash page or the operation would
 *                                  go beyond the flash memory boundary.
 * @retval  FS_ERR_NOT_INITIALIZED  If the fstorage module is not initialized.
 * @retval  FS_ERR_INVALID_CFG      If the initialization of the fstorage module is invalid.
 * @retval  FS_ERR_NULL_ARG         If @p p_dest is NULL.
 * @retval  FS_ERR_INVALID_ARG      If @p num_pages is zero.
 * @retval  FS_ERR_QUEUE_FULL       If the internal operation queue of the fstorage module is full.
 */
fs_ret_t nrf_dfu_flash_erase(uint32_t const * p_dest, uint32_t num_pages, dfu_flash_callback_t callback);

Can you set a breakpoint at nrf_dfu_flash_erase in nrf_dfu_settings_write() in nrf_dfu_settings.c? What is the pointer to to the m_dfu_settings_buffer? It should be 0x0003FC00.

Best regards

Bjørn

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Fri, 24 Apr 2020 07:43:15 GMT

Thanks for the reply Bjorn.

I am trying to debug and find the return value of the function ble_dfu_init() function. But unfortunately, the function is not returning. it is returning FS_ERR_UNALIGNED_ADDR error for fs_erase function.

No, fds_init() function is now returning success response.

I have checked my code and dfu_init function is only called after ble_stack_init() and peer_manager_init() functions. So i dont see any issues with it.

Best,
Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Thu, 23 Apr 2020 14:30:46 GMT

Thanks! Ok, now I think that i understand more. If you are using the bootloader from SDK v12.2.0, then the FLASH Origion + the FLASH length == Bootloader start address

In the default bootloader from SDK v12.2.0 starts at 0x7A000, so the length of the flash for the application should be set to 0x3AC00- 0x1B000 = 0x1FC00

So the issue is that the ble_dfu_init function return a non-zero error code? If yes, which error code is it?

Are you still seeing the FDS_ERR_NO_PAGES being returned by fds_init when initializing the Peer Manager module?( call tree peer_manager_init() -> pm_init() ->pds_init()-fds_init()?

In the SDK v12.2.0 buttonless dfu example peer_manager_init() is called before the services are initialized. So please make sure that you call your dfu_init() function after ble_stack_init() and peer_manager_init().

Best regards

Bjørn

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Wed, 22 Apr 2020 10:17:04 GMT

Thanks for the reply Bjorn.

please find the code snippet of dfu init function below

/**@brief Function for initializing the DFU Service.
*/
static void dfu_init(void)
{
uint32_t err_code;
ble_dfu_init_t dfus_init;

// Initialize the Device Firmware Update Service.
memset(&dfus_init, 0, sizeof(dfus_init));

dfus_init.evt_handler = ble_dfu_evt_handler;
dfus_init.ctrl_point_security_req_write_perm = SEC_SIGNED;
dfus_init.ctrl_point_security_req_cccd_write_perm = SEC_SIGNED;

err_code = ble_dfu_init(&m_dfus, &dfus_init);
APP_ERROR_CHECK(err_code);
}

I am using the bootloader from SDK v12.2. i have merged dfu init functions into the application. During production, i have merged bootloader.hex, softdevice.hex and application. hex together.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Wed, 22 Apr 2020 09:43:11 GMT

Can you post a snippet of the DFU Init function?

I see in the .map file that the FLASH origin is 0x1B000 and that the length is 0x25000, which means that the entire flash region above the SoftDevice is used for the application. Are you not using the bootloader from SKD v12? Or have you merged it into the application?

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Wed, 22 Apr 2020 09:22:02 GMT

Hello Bjorn,

Any luck with the memory map file?

I have been trying myself to resolve and found one scenario. On disabling the dfu_init() function, i am able to flash the code to the device and everything works fine.

So, something with dfu service is causing this error. We can not ignore this service as our device has to support DFU OTA update.

Waiting for your reply.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Tue, 21 Apr 2020 10:48:07 GMT

Hello Bjorn,

Any insight from the memory map file?

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Mon, 20 Apr 2020 09:24:11 GMT

Thanks for the reply Bjorn.

Please find the attached map file of my project.

devzone.nordicsemi.com/.../my_5F00_file.map

The section placement macros are

FLASH_START=0x1B000
RAM_START=0x20001FF8

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Mon, 20 Apr 2020 08:53:54 GMT

[quote user="krishna2203"][/quote]

Ok, i got it. It it is the case, then what will be the solution, my application uses bootloader to support DFU. please suggest what i can do to resolve this?

But does compiling the application in SES adds to the storage?

That depends on the compiler settings used. Can you upload the .map file for your application as well as post the Code > Linker > Section Placement Macros you are using in your project?

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Sat, 18 Apr 2020 14:15:18 GMT

Ok, i got it. It it is the case, then what will be the solution, my application uses bootloader to support DFU. please suggest what i can do to resolve this?

But does compiling the application in SES adds to the storage?

because the same code is working fine on my board when compiled in keil and flashed on to the device.

Thanks in advance.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Fri, 17 Apr 2020 14:30:30 GMT

/**@brief   Function for initializing the module.
 *
 * This function initializes the module and installs the file system (unless it is installed
 * already).
 *
 * This function is asynchronous. Completion is reported through an event. Make sure to call
 * @ref fds_register before calling @ref fds_init so that you receive the completion event.
 *
 * @retval  FDS_SUCCESS         If the operation was queued successfully.
 * @retval  FDS_ERR_NO_PAGES    If there is no space available in flash memory to install the
 *                              file system.
 */
ret_code_t fds_init(void);

See function brief above: FDS_ERR_NO_PAGES - If there is no space available in flash memory to install the file system.

How large is your application? There needs to be atleast two empty flash pages at the end of flash (if no bootloader is used) or two empty flash pages below the bootloader if a bootloader is present.

RE: Migrating from Keil to SES - Error with DFU INIT service

KrishNa — Fri, 17 Apr 2020 13:18:29 GMT

Thanks for the quick reply Bjorn.

I made all the changes you have mentioned and debugged. This time it is giving FDS_ERR_NO_PAGES in the pages_init function.

i am attaching the screenshot of the debug trace for your reference.

Waiting for your quick reply.

Best,

Krish

RE: Migrating from Keil to SES - Error with DFU INIT service

bjorn-spockeli — Fri, 17 Apr 2020 11:31:52 GMT

Thanks for the screenshots.

In the disassembly I can see that the FS_SECTION_VARS_START_ADDR, which is loaded into r3 is 0x20005010 ( __fs_data_run_start__) and that FS_SECTION_VARS_END_ADDR is 0x20005430 ( __fs_data_run_load_end__). The config variable is 0x0001b0c0, which is flash and not RAM.

The fs_dfu_config variable of type fs_config_t should be a static and should be placed in RAM, not flash.

You need change

under FLASH MemorySegment to the following to ensure that in runs in RAM

I also see that you have two sections with name fs_data_run in the RAM memory Segments

Can you try to remove the first one?

-Bjørn