if you are building for CPU, that’s correct, there’s no need to flash the weights as with this build, the inference runs on the MCU, we recently cleaned the output for this build.
If I am building for the ST STM32N6 CPU target (which does not need the network_weights.hex file), then why does the auto-generated flash.sh file contain a command to program the network_data.hex file when this file is not going to be created?
Should I manually edit the flash.sh file (if so how), or run individual commands to program the dev-kit when the network_data.hex file is missing (not generated nor required).
Thanks for the update. I re-read the STM32N6 instructions and successfully flashed the board with just the FW file late last night, but the system still fails to detect any objects. Not even the briefest flash of a bounding box.
Got to think my project is fundamentally broken somewhere, (bad data?), but what’s most perplexing is that I ran this same tools-flow with the same STM32N6 dev-kit back in July, and it all worked 1st time!
This is the result of the model running in the browser before being ported to the STM32N6 hardware.
i checked your project, first I would remove the unknown label and the sample associated with it.
But even after that, seems the model is not performing well on device. I tested it with other devices and I can’t get any object detected I’ll keep checking; I’m testing pointing the camera to my monitor with one of the sample.
I get the right detection on static inference, so you can try by removing the unknown label, retrain and check on real object, let me know!
regards,
fv
PS: FOMO is not available on N6, buyt you can try running Yolo Pro model.