Download | Amtemu V093 Patch Patched

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?

Amir’s attempts to replicate the patch on other machines were inconsistent. Some systems accepted it and hummed, producing strange, beautiful errors; one laptop died with a polite puff of smoke; another produced only a fugue of audio notes that, when played backward, sounded like children laughing. The patch chose its hosts the way lightning chooses trees.

From every doorway the patch had painted, one lesson remained: tools that listen can teach people to hear. And sometimes the only right way to patch the world is to hand the needle to the next person waiting to learn how.

Fear and fascination are twins. A small company that made protective software offered Amir and the forum a contract. For weeks his inbox filled with legalese, assurances, and veiled threats. The world beyond the forums sniffed like a conditioned animal; it wanted to know if the patch could be weaponized. It could, Amir thought. Fixing a single stubborn flaw in a render engine seemed harmless; giving a machine the power to invent intent felt dangerous.

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.