Combining two applications

[mukesh]

I want to combine two applications, both of them having two services. One application resides at 0x16000 and other one resides at 0x249f0. I am using softdevice 7.3 and sdk 6. What I wanted to do is that, when I press one button it should to jump to the second application. I combined both applications using the mergehex. If I upload the combined image with nrfjprog, both applications will work fine. But if i upload the firmware using dfu, the second application will not work. Why does the second applications not getting saved properly? How can I upload the merged hex file properly with the dfu?

[bjorn-spockeli]

Hi Mukesh,

I suggest that you take a look at this question and answer.

-Bjørn

[mukesh]

Thanks for the reply. My problem is still not solved. What I wanted to do is, I want to upload the two firmwares with different offset address using the dfu. What is happening is when I upload one firmware, the second one will get erased. I think the bootloader is erasing the entire application area before it does the firmware update. How can I solve this issue?

[bjorn-spockeli]

You will have to update both applications at the time, i.e. merge the two applications to one firmware image and then perform the DFU.

[mukesh]

I tried with mergehex. If I upload the merged hex file using nrfjprog, everything will work fine. That is the application switching is working fine. I but if I do the same with dfu, it won't work. Instead of going to the second code region, it is going back to the dfu mode. I am using this function for doing the application switching

uint32_t err_code = sd_softdevice_disable();
  APP_ERROR_CHECK(err_code);

  interrupts_disable();

  err_code = sd_softdevice_vector_table_base_set(0x249f0);
  APP_ERROR_CHECK(err_code);

  bootloader_util_app_start(0x249f0);

What would be the problem?

[mukesh]

I think the bootloader_util_app_start() function is resetting the device and it is going back to the dfu mode. Is it possible to branch to different address other than 0x16000 from the bootloader.