Hi everyone,
I AM LOOKING TO HIRE SOMEONE TO HELP ME WITH THIS OVER A ZOOM SESSION ASAP. PLEASE DO READ ON IF YOU CONSIDER YOURSELF SEASONED/KNOWLEDGEABLE IN THIS AREA. PLEASE DM ME IF YOU ARE INTERESTED AND ABLE. IF YOU CAN'T ACCESS MY CONTACT INFO FOR SOME REASON JUST RESPOND AS SUCH BELOW AND I WILL FIGURE OUT HOW TO RESOLVE THAT.
I am completely blocked on being able to bypass partition manager for a single slot sysbuild so that my application fits in the on-chip flash.
No amount of searching Nordic documentation, reddit, or leveraging GPT has yielded any success for me in this regard.
If anyone out there knows how to successfully sysbuild single slot with MCUBOOT + WiFi + BLE (TF-M or no TF-M) relying solely on serial recovery mode for DFU, I am willing to pay for a Zoom consulting session to get through this, possibly more beyond that.
I cannot believe that I am unable to find a dedicated Nordic documentation page that explicitly describes how to do this when the base footprint for trying to include core SDK and Zephyr libraries, BLE, WiFi, and TF-M seem to take up approximately 92% of a 512kB flash slot. I really just hope I'm not looking in the right place.
This MUST be a primary implementation use scenario, especially for wearable device form-factors that can't support addition of extra NOR flash on the board for a second slot as it leaves almost no space for customer application code development right out of the gate.
It seems like there should be a literal, copy-paste drop in provided somewhere to do this. That's how common this scenario should be.
NORDIC support, can you please provide definitive drop-in template guidance as to how to do this?
Please provide exact prj.conf, sysbuild.conf, pm_static.yml, and any DTS/DTSI modifications needed specifically for this build scenario to work.
I have burned multiple days on trying to figure this out and I'm burned out on trying to piece this together from suggestive fragments in the documentation. Neither the official Partition Manager manual nor the MCUboot guide cover this important topic in the dedicated manner it deserves. I need rapid, surgical intervention here to get me through this please.
The primary symptom I have is that no matter what I try to specify in my configuration combined with pm_static.yml to specify single slot, the build system continues to revert to the default dual-slot configuration as I see it in the pre-map, simply telling me that my flash footprint is too big to fit by 300K. I am unable to find a place where I can probe the build between the inputs I am providing and the pre map output to determine where the problem is.
Thank you in advance for your help with this.
Best regards,
Chris
