Katrin39-56.rar Instant

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?

If you have encountered this file, do not extract or run its contents.

The malware employs sophisticated anti-analysis and anti-debugging tricks to detect if it is running in a virtual machine or a sandbox environment, remaining dormant to avoid detection by security researchers. Security Recommendations

Delete the file immediately and run a full system scan using an updated antivirus solution.

Based on available technical data, is a compressed archive file that has been identified by multiple security researchers and antivirus engines as a malicious downloader or a delivery vehicle for malware , specifically associated with the Guloader (also known as CloudEyE) family. Technical Overview File Type: WinRAR Archive (.rar). Primary Threat Category: Trojan / Downloader. Common Detection Names: Trojan.Downloader.Guloader Malware.Heuristic Win32:Dropper-gen Behavior and Payload

If this was received via email, flag the sender as "Phishing" and notify your IT or security department.

Once a user extracts and runs the executable file hidden inside the RAR archive, it initiates a multi-stage infection process.

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.