I'm trying to evaluate the nrf5340 using the PDK.
I want to port an nrf52(832) application to it and I'm having a lot of trouble understanding how to work with west and the nrf connect sdk in general. But one of my biggest problems is I don't know how to modify the linker script. This application requires our custom bootloader and various other flash regions.
Is this something that you use the prj.conf file for?
Take a look at the Code relocation sample for guidance on how to relocate code, data or bss sections using a custom linker script
Is it possible for you to use MCUBoot instead of the custom bootloader? You may save a lot of work if you use MCUboot, especially if you're going to update the network core, which is a quite complex procedure.
If you want to stick with your DFU Protocol (how the updated image is transferred to the chip and stored in flash) you can still use MCUBoot with your custom protocol. Please tell me if this is the case and I can tell you how to go about it.
If you need to continue to use the custom bootloader, I can help you with that. Could you give me some more information about the custom bootloader and the flash regions? Are you using the nRF5 SDK bootloader? What flash regions are you talking about? A colleague made a sample that might be helpful, where he used the Partition Manager to add the mbr from the nRF5 SDK as a static partition before MCUBoot
Check out the sample here: 6811.peripheral_uart.7z
This case might be helpful as well: https://devzone.nordicsemi.com/f/nordic-q-a/65819/updating-start-address-to-nrf52840-dk-via-code/269330#269330
Best regards,
Simon
Take a look at the Code relocation sample for guidance on how to relocate code, data or bss sections using a custom linker script
Is it possible for you to use MCUBoot instead of the custom bootloader? You may save a lot of work if you use MCUboot, especially if you're going to update the network core, which is a quite complex procedure.
If you want to stick with your DFU Protocol (how the updated image is transferred to the chip and stored in flash) you can still use MCUBoot with your custom protocol. Please tell me if this is the case and I can tell you how to go about it.
If you need to continue to use the custom bootloader, I can help you with that. Could you give me some more information about the custom bootloader and the flash regions? Are you using the nRF5 SDK bootloader? What flash regions are you talking about? A colleague made a sample that might be helpful, where he used the Partition Manager to add the mbr from the nRF5 SDK as a static partition before MCUBoot
Check out the sample here: 6811.peripheral_uart.7z
This case might be helpful as well: https://devzone.nordicsemi.com/f/nordic-q-a/65819/updating-start-address-to-nrf52840-dk-via-code/269330#269330
Best regards,
Simon
