Need Help: Combining TinyML Inference with BLE DFU on nRF7002DK – Crashing at Runtime

RE: Need Help: Combining TinyML Inference with BLE DFU on nRF7002DK – Crashing at Runtime

Sigurd Hellesvik — Tue, 29 Apr 2025 06:54:17 GMT

[quote user="Gowtham Raj"]For TF-M, I’ll try building the project without it, so everything just runs in the non-secure domain. Hopefully that will help with the crash during model setup. I’ll test it and let you know if the unaligned memory issue still shows up.[/quote]

Without TF-M, everything will run in the Secure domain! This does not mean it is more secure, as it is the Separation that makes it secure. See Security by separation if you want to learn more.

[quote user="Gowtham Raj"]t would be great if you could try testing them on your side as well.[/quote]

Perhaps later on. First I will try and help you solve this yourself.

From the logs:
In the fault message, it says (unknown). If you set CONFIG_THREAD_NAME, you can get this to instead tell you the thread name where it fails. This can sometimes be useful.

Also, perhaps try to debug og add more prints after the "Initializing TinyML model...", so we can see exactly which function is called when the fault happens.

Oh and one more idea:
You say that the sample crashes when you add BLE DFU. => Is it the BLE or the DFU?
Try to add only MCUboot to the project and not BLE. Does that cause the fault?
Try to add only BLE to the project and not DFU. Does that cause the fault?

RE: Need Help: Combining TinyML Inference with BLE DFU on nRF7002DK – Crashing at Runtime

Gowtham Raj — Mon, 28 Apr 2025 21:29:19 GMT

Hi Sigurd,

Thanks a lot for getting back to me.

Based on what you suggested, here’s what I’m planning to do and a few things I wanted to check with you:

For TF-M, I’ll try building the project without it, so everything just runs in the non-secure domain. Hopefully that will help with the crash during model setup. I’ll test it and let you know if the unaligned memory issue still shows up.

About the flash and RAM layout, thanks for explaining that MCUboot and the app don’t share RAM. That makes sense now. I’ll also try tweaking the MCUboot partition size using CONFIG_PM_PARTITION_SIZE_MCUBOOT like you said, and see if adjusting things helps avoid any memory conflicts.

Regarding the logs, yeah, I realize the screenshot wasn’t super clear. I uploaded

it as a .txt file so it’s easier to go through.

Also, if it helps, I’ve included the links above where you can download both the BLE DFU sample and my TinyML CIFAR-10 project. It would be great if you could try testing them on your side as well. One suggestion, before building the TinyML CIFAR-10 application, please run the command "west config manifest.project-filter -- +tflite-micro" in the nRF Terminal to make sure the TensorFlow Lite Micro modules are properly pulled in. I found this step necessary to avoid module issues while building.

Thanks again for helping me out with this, I’ll try the changes you mentioned and post back with updates soon.

Best,
Gowtham Raj

devzone.nordicsemi.com/.../fatal_5F00_error.txt

RE: Need Help: Combining TinyML Inference with BLE DFU on nRF7002DK – Crashing at Runtime

Sigurd Hellesvik — Mon, 28 Apr 2025 10:57:04 GMT

Hi,

[quote user=""]

Potential issues I’m considering include:

Flash/RAM layout conflicts
SPI/QSPI usage overlap
Memory section misconfigurations
Conflicts with TF-M or secure/non-secure regions

[/quote]

I think your ideas on what could be the issues sound reasonable. Let me suggest some things for each:

[quote user=""]Conflicts with TF-M or secure/non-secure regions[/quote]

Can you try to just not use TF-M?

[quote user=""]Flash/RAM layout conflicts[/quote]

MCUboot and the application does not share RAM. TF-M is another story, but see above.

Also, perhaps try to change the size of MCUboot using CONFIG_PM_PARTITION_SIZE_MUCBOOT to see if that somehow aligns things by chance.

[quote user=""]Happy to share logs or a zipped version of the project if needed.[/quote]

The image is kinda low quality. Can you insert the logs as a .txt file?

Regards,
Sigurd Hellesvik