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?

Norton Ghost 12 Ghost Explorer 2013 -x32-x64-... -

**The Sea Beast: Uncovering the Mystery of the Ocean's Legendary Monster** For centuries, tales of a monstrous sea creature have captivated the imagination of people around the world. From ancient myths to modern-day sightings, the legend of "The Sea Beast" has endured, sparking both fascination and terror in those who hear its story. But what is behind this enduring myth? Is there any truth to the claims of a massive, ocean-dwelling monster, or is it simply a product of folklore and superstition? **A History of Sea Monster Sightings** The concept of a sea monster has been around for thousands of years, with ancient civilizations such as the Greeks, Norse, and Japanese all featuring massive sea creatures in their myths and legends. In many cases, these creatures were depicted as powerful, fearsome beings with the ability to control the oceans and wreak havoc on human populations. One of the most famous sea monster stories from history is that of the Kraken, a legendary sea creature said to dwell off the coasts of Norway and Greenland. According to myth, the Kraken was a massive squid or octopus-like creature, capable of dragging ships and sailors down to a watery grave. In more recent times, reports of sea monster sightings have continued to surface, with many claiming to have seen massive, serpentine creatures breaching the surface of the ocean or swimming through the waves. While many of these sightings can be explained as misidentifications of known marine animals or natural phenomena, there remain a number of unexplained reports that continue to fuel the legend of "The Sea Beast." **The Modern Search for the Sea Beast** In recent years, a number of high-profile expeditions have set out to find evidence of the existence of a massive sea monster. Using advanced sonar and camera technology, these expeditions have scoured the world's oceans, searching for signs of a creature that could potentially match the descriptions of "The Sea Beast." One of the most notable of these expeditions was the 2004 search for the Loch Ness Monster, a legendary creature said to inhabit Scotland's Loch Ness. While the expedition ultimately failed to find conclusive evidence of the monster's existence, it did capture a number of intriguing images and videos that continue to be debated by enthusiasts to this day. **The Science Behind the Sea Beast** While the idea of a massive sea monster may seem like the stuff of legend, there are a number of scientific theories that could potentially explain the existence of such a creature. One possibility is that "The Sea Beast" is a misidentified known marine animal, such as a giant squid or a whale. Giant squids, for example, are known to grow up to 20 feet in length and weigh over 100 pounds, making them one of the largest invertebrates on the planet. It's possible that a giant squid could be mistaken for a sea monster, especially if it's seen breaching the surface of the water or swimming through the waves. Another possibility is that "The Sea Beast" is a previously undiscovered species of marine animal. The oceans are still a largely unexplored environment, and it's estimated that up to 75% of all marine species remain undiscovered. It's possible that a large, unknown species could be lurking in the depths of the ocean, waiting to be discovered. **Conclusion** The legend of "The Sea Beast" continues to captivate the imagination of people around the world. While there is currently no conclusive evidence to prove the existence of such a creature, there are many intriguing reports and sightings that suggest that there may be more to the story than meets the eye. Whether or not "The Sea Beast" ultimately proves to be a real creature, its place in our collective imagination is secure. As a symbol of the power and mystery of the ocean, "The Sea Beast" will continue to inspire and fascinate us for generations to come. Some of the reported characteristics of The Sea Beast include: * Massive size, often reported to be over 50 feet in length * Serpentine or squid-like appearance * Ability to breach the surface of the water or swim through the waves * Often associated with mysterious or unexplained phenomena, such as strange lights or sounds. Some of the locations where The Sea Beast has been reportedly spotted include: * The oceans of Norway and Greenland, where the legend of the Kraken originated * Loch Ness, Scotland, where the famous Loch Ness Monster is said to reside * The coast of Maine, where a number of reported sea monster sightings have been documented * The depths of the Pacific Ocean, where a number of unexplained phenomena have been reported by sailors and fishermen. No input data

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.