NORA-B126 flash overflow

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Thu, 12 Sep 2024 12:16:39 GMT

Could you upload your project and instructions on how to build it so I can try and reproduce the issue?

If you do not want to do it here, please create a new public ticket and refer to this ticket.

RE: NORA-B126 flash overflow

sfemat — Wed, 11 Sep 2024 10:24:29 GMT

No, I'm letting it handle the partitioning dynamically

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Wed, 11 Sep 2024 08:49:32 GMT

Just to confirm: Do you use pm_static.yml or not?

RE: NORA-B126 flash overflow

sfemat — Tue, 10 Sep 2024 15:58:33 GMT

Nope, it's stuck at 15020 bytes even if I increase CONFIG_PM_PARTITION_SIZE_PROVISION to 0x300

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Fri, 06 Sep 2024 11:39:15 GMT

Hmm maybe that is not the configuration after all.

Try to use CONFIG_PM_PARTITION_SIZE_PROVISION instead. Does that impact the overflow size at all?

RE: NORA-B126 flash overflow

sfemat — Thu, 05 Sep 2024 15:27:29 GMT

The overflow gets worse

zephyr\zephyr_pre0.elf section `text' will not fit in region `FLASH'

zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 27308 bytes

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Thu, 05 Sep 2024 15:15:11 GMT

What happens if you try 0x10D80?

RE: NORA-B126 flash overflow

sfemat — Wed, 04 Sep 2024 12:27:22 GMT

It adds 0x0280 to whatever b0n_size I set, so I ended up setting 0xDD80 that is the minimum for rodata to not overflow. But now text is back at overflowing and again removing from my code doesn't change it by a bit.

zephyr\zephyr_pre0.elf section `text' will not fit in region `FLASH'
arm-zephyr-eabi/bin/ld.exe: region `FLASH' overflowed by 15020 bytes

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Wed, 04 Sep 2024 09:22:41 GMT

SoCONFIG_FPROTECT_BLOCK_SIZE should be 0x1000 I think.

Your board is to B0N_SIZE dividable by this.
Try to increase the size of B0N_SIZE by 0x880 (0x9000 - 0x8780), and see if that works.

RE: NORA-B126 flash overflow

sfemat — Tue, 03 Sep 2024 15:11:28 GMT

I have set it like this:

CONFIG_B0N_SIZE=0x8780

and in the build folder it's 0x8a00.

It's still saying static assertion failed: "PM_B0N_CONTAINER_SIZE % CONFIG_FPROTECT_BLOCK_SIZE was not 0. Check the B0_SIZE Kconfig.

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Mon, 02 Sep 2024 13:16:26 GMT

Sure, I can help with this.

Can you check what PM_B0N_CONTAINER_SIZE project? If you search for it in your build folder, I think you should be able to find it.

My gut feeling says that B0N_SIZE should be whatever you need and plus or minus 0x200

RE: NORA-B126 flash overflow

sfemat — Mon, 02 Sep 2024 13:04:02 GMT

Yes I need help, Belalshinnawey's solution caused another issue:

If I set an high enough value for B0N_SIZE it stops overflowing, but it's somehow never aligned to the fprotect block size so the build fails.

RE: NORA-B126 flash overflow

Sigurd Hellesvik — Mon, 02 Sep 2024 12:15:03 GMT

Hi all,

I work in technical support, and have "inherited" this ticket from Håkon.
It looks like you guys are talking in this ticket, so for now I will assume it is fine.

Let me know if you need help with anything still.

RE: NORA-B126 flash overflow

sfemat — Mon, 26 Aug 2024 18:34:26 GMT

Can you help with this?

RE: NORA-B126 flash overflow

Belalshinnawey — Wed, 14 Aug 2024 17:44:36 GMT

i didn't even worry about the 2k thing, just make sure you have the amount of flash that you set aside for your b0n not occupied by anything else. maybe post the full build error in a code bock and see what it says. my entire process to get this thing to work which i tested now and thankfully it does, was to just track down all the different configs in the different child images and suppress anything that is unsetting something I am using.

RE: NORA-B126 flash overflow

sfemat — Wed, 14 Aug 2024 17:35:09 GMT

Your initial configs did help solve a few dependencies errors, but the overflow (of b0n) is still there. I'm seeing very inconsistent results by changing the B0N_SIZE, often times it says error: static assertion failed: "PM_B0N_CONTAINER_SIZE % CONFIG_FPROTECT_BLOCK_SIZE was not 0. Check the B0_SIZE Kconfig." even if the set number is divisible by 2000, 2048 or 16384 (I'm not even sure which is the correct one).

RE: NORA-B126 flash overflow

Belalshinnawey — Wed, 14 Aug 2024 07:09:39 GMT

I did some digging and I found a solution, granted, I need to do more testing to verify but at least it builds.

Here is some given variables by the nrf connect sdk.

In order to do gpio LNA, you need MPSL.
in order to do MPSL you need clock functionality, so setting

CONFIG_SYS_CLOCK_EXISTS=n

is not good. Because you will get 2 errors:
/opt/nordic/ncs/v2.3.0/nrf/subsys/mpsl/init/mpsl_init.c:192:10: error: #error "Clock source is not supported or not defined

and

/opt/nordic/ncs/v2.3.0/nrf/subsys/mpsl/init/mpsl_init.c:203:34: error: 'CONFIG_CLOCK_CONTROL_NRF_ACCURACY' undeclared (first use in this function)

so anything that sets that config flag in your netcore will stop your LNA application from working.

also, if you do anything that needs rpmsg like ble or zigbee for example, you need some kernel functions like z_impl_k_sem_reset etc.
so setting:

CONFIG_MULTITHREADING=n

is also bad news.

now for the flash overflow issue, you did not provide the full build log, so IDK if you're having the same problem as I am, but I will share my experience anyway, maybe it helps you.

I was setting

CONFIG_BOOTLOADER_MCUBOOT=y

in my app core.
This has a bunch of unintended consequences. first of all, make sure that you have a child_image file with mcuboot.conf inside of it, and set the correct size for mcuboot, if the error for flash overflow in your application is related to mcuboot, this is probably the culprit, make sure to mirror all the other settings of your pm_static.yml if you have it in your project, make sure your app_core partitions are setup correctly, etc.

the second thing that happens when you enable mcuboot in your app_core, is it automatically builds the secure_boot bootloader for your net_core. The code for this is buried in nrf/samples/nrf5340/netboot application.

CONFIG_B0N_SIZE

defined in the kconfig file in that app too low. specifically, it needed to be increased 0x3000 to fit whatever things are needed (or most likely not needed) in the background.
The proj.conf file in that application was also setting multithreading to off, and it was setting sys_clock_exists to off, which is the reason for me to have the kernel functions not available in my rpmsg app, and the reason why mpsl was not able to build due to clock issues.

the way i fixed it, is i strait up edited the CONFIG_B0N_SIZE to fit the flash overflow error I was experiencing, and enabled back multithreading and sys_clock.

if your issue is not from within mcuboot, then make sure nothing else is turning off multi-threading deep in your application, and check which image is unable to build due to flash size issues.

I hope the nrf support agent is able to elaborate on why my application was trying so hard to kill itself, and if my issue does not remotely relate to yours, then I am sorry for wasting your time.

RE: NORA-B126 flash overflow

Belalshinnawey — Wed, 14 Aug 2024 03:48:30 GMT

I am having the same exact issue with the same error message, and the same unchanged number of bytes overflowing regardless of whatever changes I make with the partitions. I am using nrf5340 with a different lna. I did not have this issue until I enabled mcuboot. I had the app working with the lna and zigbee, and lte-modem. but when i added mcuboot, everything broke. If i get a solution to this i will let you know.

RE: NORA-B126 flash overflow

sfemat — Tue, 13 Aug 2024 10:59:31 GMT

devzone.nordicsemi.com/.../NORA_2D00_B1_5F00_SIM_5F00_UBX_2D00_20027617.pdf

Here is the file, I think there is an underlying issue as even trying to remove unneeded code doesn't influence that overflow number by a bit: region `FLASH' overflowed by 12540 bytes.

RE: NORA-B126 flash overflow

Elfving — Thu, 08 Aug 2024 12:09:13 GMT

Hello,

[quote user=""]trying to increase the flash sizes in the QKAA files has zero effects on the overflow reported.[/quote]

Well that is strange for a completely different reason, but lets stick to the main problem for now.

[quote user=""]

we are trying to make the NORA-B126 (specifically its onboard LNA) work with nrf sdk 2.3.0 by modifying the 5340dk dts and defconfig files as specified in the NORA-B1_SIM_UBX-20027617.pdf

[/quote]

Could you try generating a memory report and see if you need everything that you have there?

And could you try uploading that pdf again? It didn't seem to work.

Regards,

Elfving