H338334.mp4 May 2026

Hi all,

I'm using ST's CubeMX implementation on a F4 discovery board. I use ST's USB middlewares with FreeRTOS.

When I get a special OutputReport from PC side I have to answer nearly immediately (in 10-15 ms). Currently I cannot achieve this timing and it seems my high priority tasks can interrupt the USB callback. What do you think, is it possible? Because it's generated code I'm not sure but can I increase the priority of the USB interrupt (if there is any)?

Thank you, David

10 to 15 ms is very slow, so I'm sure its possible.

Where is the USB callback function called from? If it is an interrupt then it cannot be interrupted by high priority RTOS tasks. Any non interrupt code (whether you are using an RTOS or not) can only run if no interrupts are running.

Without knowing the control flow in your application its hard to know what to suggest. How is the OutputReport communicated to you? By an interrupt, a message from another task, or some other way?

The callback which receive the data from PC is called from the OTGFSIRQHandler (it's the part of the HALPCDIRQHandler function). I think the problem is SysTickHandler's priority is higher than OTGFSIRQHandler and it's cannot be modified, but the scheduler shouldn't interrupt the OTGFSIRQHandler with any task handled by the scheduler. Am I wrong that the scheduler can interrupt the OTGFS_IRQHandler?

Then he found the drive labeled Lot 338 . It was a heavy, old-school mechanical drive, vibrating with a low, rhythmic hum that felt slightly out of sync with the room. Inside was a single folder, and within that folder, a single file: . He double-clicked.

Elias didn't look at the door. He looked at his computer screen, hoping for one more frame, a hint, a warning. But the screen only reflected his own face, pale and waiting, as the shadows in the room began to stretch into the shape of a circle.

The circle of figures begins to hum. Elias couldn't hear it through his speakers—they were muted—but he could see the vibration in the image. The pavement around the man’s feet started to ripple like water. The man in the center finally began to turn. Slowly. Very slowly.

The digital noise begins to distort. Horizontal lines of purple and green tear across the screen. When the image stabilizes, the man is no longer alone. He is surrounded by dozens of other figures, all standing in a perfect circle around him. They weren't there a second ago. They didn't walk into the frame. They simply were .

Thank you for the answer, I think I'm a bit confused with the Cortex ISR priorities :-) What I can observe is if I use a much higher osDelay in my high priority task I can respond for the received USB message much faster. This is why I think tasks can mess up with my OTG interrupt.