Two applications in parallel, freertos

RE: Two applications in parallel, freertos

Susheel Nuguru — Fri, 23 Aug 2019 12:27:33 GMT

I do not understand the conflicts that could arise with this integration. Sent you a note in your private ticket

RE: Two applications in parallel, freertos

twittich — Thu, 22 Aug 2019 10:35:03 GMT

[quote userid="6207" url="~/f/nordic-q-a/51031/two-applications-in-parallel-freertos/205531"]dfu device is visible in the device manager[/quote]

If you test the openbootlaoder example and start the dfu mode by pressing button or reset or setting the GPREGRET register in the device manager of windows is coming a new serial port named "nRF52 SDFU USB". This is what i integrated in the blinky freertos example. Because the main plan is that i have this device visible and that i can start anytime a dfu update, but this should not affect the other task until the dfu process starts, then it has to be terminated.

RE: Two applications in parallel, freertos

Susheel Nuguru — Thu, 22 Aug 2019 10:24:04 GMT

[quote user="twittich"]The good thing the dfu device is visible in the device manager of windows but the dfu update is not working.[/quote]

Not sure what is visible in the device manager? What does windows device manager have to do with your problem?

[quote user="twittich"]Something in there kills the task or timer of the blink task ?[/quote]

Nothing kills any tasks unless explicitly done in the application. The other likely thing is that the other tasks probably have higher priority and are not yielding the CPU.

RE: Two applications in parallel, freertos

twittich — Thu, 22 Aug 2019 06:23:55 GMT

There is enough space even to make update over dfu, i'm testing with the blinky freertos. I moved the settingspage to a higher address and compiling works without any errors.

Now the problem is if i call "nrf_bootloader_init(dfu_observer)" or start a task with this function the other task is not working anymore. The good thing the dfu device is visible in the device manager of windows but the dfu update is not working.

Something in there kills the task or timer of the blink task ?

RE: Two applications in parallel, freertos

Susheel Nuguru — Tue, 20 Aug 2019 12:49:56 GMT

Does it mean that you do not have enough space in the chip to put them together? If that is the case, it would not work to put them apart either.

RE: Two applications in parallel, freertos

twittich — Mon, 19 Aug 2019 13:22:01 GMT

[quote userid="80700" url="~/f/nordic-q-a/51031/two-applications-in-parallel-freertos/204693"] unplaced section is overflowed by 8192 byte [/quote]

<!DOCTYPE Linker_Placement_File>
<Root name="Flash Section Placement">
  <MemorySegment name="FLASH" start="$(FLASH_PH_START)" size="$(FLASH_PH_SIZE)">
    <ProgramSection load="no" name=".reserved_flash" start="$(FLASH_PH_START)" size="$(FLASH_START)-$(FLASH_PH_START)" />
    <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" keep="Yes" load="Yes" name=".crypto_data" inputsections="*(SORT(.crypto_data*))" address_symbol="__start_crypto_data" end_symbol="__stop_crypto_data" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".nrf_queue" inputsections="*(.nrf_queue*)" address_symbol="__start_nrf_queue" end_symbol="__stop_nrf_queue" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".dfu_trans" inputsections="*(SORT(.dfu_trans*))" address_symbol="__start_dfu_trans" end_symbol="__stop_dfu_trans" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".log_const_data" inputsections="*(SORT(.log_const_data*))" address_symbol="__start_log_const_data" end_symbol="__stop_log_const_data" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".nrf_balloc" inputsections="*(.nrf_balloc*)" address_symbol="__start_nrf_balloc" end_symbol="__stop_nrf_balloc" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".log_backends" inputsections="*(SORT(.log_backends*))" address_symbol="__start_log_backends" end_symbol="__stop_log_backends" />
    <ProgramSection alignment="4" keep="Yes" load="No" name=".nrf_sections" address_symbol="__start_nrf_sections" />
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".fs_data"  inputsections="*(.fs_data*)" runin=".fs_data_run"/>
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".log_dynamic_data"  inputsections="*(SORT(.log_dynamic_data*))" runin=".log_dynamic_data_run"/>
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".log_filter_data"  inputsections="*(SORT(.log_filter_data*))" runin=".log_filter_data_run"/>
    <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" />
  </MemorySegment>
  <MemorySegment name="RAM" start="$(RAM_PH_START)" size="$(RAM_PH_SIZE)">
    <ProgramSection load="no" name=".reserved_ram" start="$(RAM_PH_START)" size="$(RAM_START)-$(RAM_PH_START)" />
    <ProgramSection alignment="0x100" load="No" name=".vectors_ram" start="$(RAM_START)" address_symbol="__app_ram_start__"/>
    <ProgramSection alignment="4" keep="Yes" load="No" name=".nrf_sections_run" address_symbol="__start_nrf_sections_run" />
    <ProgramSection alignment="4" keep="Yes" load="No" name=".fs_data_run" address_symbol="__start_fs_data" end_symbol="__stop_fs_data" />
    <ProgramSection alignment="4" keep="Yes" load="No" name=".log_dynamic_data_run" address_symbol="__start_log_dynamic_data" end_symbol="__stop_log_dynamic_data" />
    <ProgramSection alignment="4" keep="Yes" load="No" name=".log_filter_data_run" address_symbol="__start_log_filter_data" end_symbol="__stop_log_filter_data" />
    <ProgramSection alignment="4" keep="Yes" load="No" name=".nrf_sections_run_end" address_symbol="__end_nrf_sections_run" />
    <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" 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"  address_symbol="__StackLimit" end_symbol="__StackTop"/>
    <ProgramSection alignment="8" size="__STACKSIZE_PROCESS__" load="No" name=".stack_process" />
  </MemorySegment>
  <MemorySegment name="bootloader_settings_page" start="0x000FF000" size="0x1000">
    <ProgramSection alignment="4" keep="Yes" load="No" name=".bootloader_settings_page" address_symbol="__start_bootloader_settings_page" end_symbol="__stop_bootloader_settings_page" start = "0x000FF000" size="0x1000" />
  </MemorySegment>
  <MemorySegment name="mbr_params_page" start="0x000FE000" size="0x1000">
    <ProgramSection alignment="4" keep="Yes" load="No" name=".mbr_params_page" address_symbol="__start_mbr_params_page" end_symbol="__stop_mbr_params_page" start = "0x000FE000" size="0x1000" />
  </MemorySegment>
  <MemorySegment name="uicr_bootloader_start_address" start="0x00000FF8" size="0x4">
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".uicr_bootloader_start_address" address_symbol="__start_uicr_bootloader_start_address" end_symbol="__stop_uicr_bootloader_start_address" start = "0x00000FF8" size="0x4" />
  </MemorySegment>
  <MemorySegment name="uicr_mbr_params_page" start="0x00000FFC" size="0x4">
    <ProgramSection alignment="4" keep="Yes" load="Yes" name=".uicr_mbr_params_page" address_symbol="__start_uicr_mbr_params_page" end_symbol="__stop_uicr_mbr_params_page" start = "0x00000FFC" size="0x4" />
  </MemorySegment>
</Root>

RE: Two applications in parallel, freertos

twittich — Mon, 19 Aug 2019 12:21:07 GMT

The double defined timer functions in apptimer2 are not used by the blinky freertos so i commented it out without any problems.

RE: Two applications in parallel, freertos

twittich — Mon, 19 Aug 2019 09:55:34 GMT

[quote userid="6207" url="~/f/nordic-q-a/51031/two-applications-in-parallel-freertos/204509"] Good luck[/quote]

Thanks 🙂

I started to integrate OpenBootloader into blinky freertos.

And there are some multiple definition problems.

one problem is with RTC1_IRQHandler in drv_rtc.c, which is comes from the openbootloader but is also defined/used by freertos. can i change it to another one and if yes how ?

Where can i change this definition APP_TIMER_V2_RTC1_ENABLED also in drv_rtc.c ?

Also multiple definitions of the app timer functions start, create, stop, init, same questions here can i change it anyhow ?

And another problem is that the bootloader settings page will not fit becuase the unplaced section is overflowed by 8192 byte ???

many thanks in advance

twittich

RE: Two applications in parallel, freertos

Susheel Nuguru — Fri, 16 Aug 2019 12:53:55 GMT

Good that you already started to implement this way.

If you have any architectural challenges, please let me know and I will try to help you. Good luck

RE: Two applications in parallel, freertos

twittich — Fri, 16 Aug 2019 11:54:45 GMT

[quote userid="6207" url="~/f/nordic-q-a/51031/two-applications-in-parallel-freertos/204474"]two applications logic into different threads[/quote]

This i'm trying already but have some problems with multiple definitions and timers etc...

I'll continue this way ...

Thanks anyway

RE: Two applications in parallel, freertos

Susheel Nuguru — Fri, 16 Aug 2019 11:16:47 GMT

The FreeRTOS kernel is compiled into the application, So it would not be possible to have two applications that have two kernels at a different location using the same resources under the hood.

You should be able to design two applications logic into different threads and have a mutual exclusion logic between them to limit CPU access to them.