Skip to main content
Visitor II
July 7, 2026
Question

Need guidance for running YOLO-FastestV2 INT8 on STM32N6570-DK – Incorrect bounding boxes and false detections

  • July 7, 2026
  • 1 reply
  • 40 views

Hi ST Community,

 

I am trying to deploy a YOLO-FastestV2 INT8 object detection model on the STM32N6570-DK. The model is successfully converted and runs on the board, but I am facing issues with the detection results.

Model Information

  • Model: YOLO-FastestV2 (INT8)
  • Number of classes: 6
  • Parameters: 235,120

Model Input

Input_0_out_0
uint8 [1,1,320,320]

Model Outputs

Quantize_297_out_0
int8 [1,12,20,20]

Quantize_313_out_0
int8 [1,3,20,20]

Quantize_311_out_0
int8 [1,6,20,20]

Quantize_330_out_0
int8 [1,12,10,10]

Quantize_346_out_0
int8 [1,3,10,10]

Quantize_344_out_0
int8 [1,6,10,10]

Issues I am Facing

  1. The bounding boxes are not displayed at the correct positions on the camera image.
  2. The detected bounding boxes appear to be shifted or incorrectly scaled.
  3. Even when the camera is not viewing any object (or the camera feed is unclear), random bounding boxes continue to be displayed.
  4. These false detection remain on the screen even though there should be no valid detection.

Verification Performed

I also tested the quantized ONNX model on my PC using the same model.

The ONNX model produces correct detection results:

  • Bounding boxes are in the correct positions.
  • No false detection are observed when no object is present.

This suggests that the model itself is working correctly, and the issue is likely related to the STM32 deployment, post-processing, or output decoding.

Request for Guidance

I would appreciate guidance on the following:

  1. Is there an example of running a custom YOLO-FastestV2 model on STM32N6570-DK?
  2. Is there a reference implementation for decoding YOLO-FastestV2 outputs on STM32?
  3. Are there any requirements regarding:
    • output tensor ordering,
    • parameters,
    • anchor configuration,
    • confidence threshold,
    • NMS implementation,
    • or coordinate scaling?
  4. Could incorrect post-processing cause the bounding boxes to appear at incorrect positions and generate false detections?
  5. Are there any debugging steps you would recommend to verify whether the outputs are being decoded correctly on the device?

Attachments

I am attaching:

  • Screenshot of the quantized ONNX model output on PC (correct detection).
  • Screenshot of the STM32N6570-DK display showing the incorrect bounding boxes.

Any guidance or example project for deploying YOLO-FastestV2 on STM32N6570-DK would be greatly appreciated.

Thank you!

 

 

1 reply

mƎALLEm
ST Technical Moderator
July 8, 2026

Hello ​@Rutva Patel,

Such kind of questions need to be posted in the Edge AI forum board.

I move the post then.

To give better visibility on the answered topics, please click "Best answer" on the reply which solved your issue or answered your question.