Hi fellas,
First of all sorry for the long post but I'm stuck for quite some time now and I need your help. I guess better provide more info than less.
I am working with a custom board which is very-very similar to the evaluation kit using the nRF5340.
The image I currently have is quite hefty around 500K.
So using the MCU boot loader with dual banks is not feasible. Also we would like to use the remaining flash for other actions.
I have been reading all around the net for a possible solution.
There must be something that I am missing, mostly concerning the conf file
SDK nRF Connect 1.9.1
My starting point is the smp sample.
I have tried it with simple smaller applications using both newtmgr and mcumgr and they work perfectly fine.
I am able to list, upload, confirm and finally erase unwanted slots.
All previously described actions have been done using ACM0 (usb-serial), using the cdc-overlay.
Default overlays:
proj.conf
cdc-overlay.conf
I created an overlay (nrf5340dk_nrf5340_cpuapp.overlay)
giving 65KB to the bootloader and the rest (1MB-65KB) for the application
I also declared
inside
I know that the last one might not be elegant or approved and maybe I should've used KConfig for that
While compiling I get the following:
From what I can understand it's looking for "image-1" which he is not finding.
When I remove
it works and compiles fine. Then again I don't have enough space to use the dual slots.
It all boils up to these questions:
- Am looking at this the wrong way?
- Do I need to provide a mapping of the memory (from what I've seen around probably yes)
- Are there any configurations options that I can add inside proj.conf to solve this issue
If you need any other information which I did not include please feel free to ask for them.