Manual - Brj-502

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?

The Brj-502 Manual was more than just a guide; it was a chronicle of human ingenuity, a beacon of hope for a brighter future. As Dr. Vex closed the manual, she knew that their work was just beginning. The real challenge lay not in creating the technology, but in ensuring that it was used for the betterment of all.

But the manual also spoke of the challenges they faced. The containment issues, the fluctuations in energy output, and the ethical considerations of creating a device that could potentially end humanity's dependency on fossil fuels overnight.

Deep within the heart of the Brj-502 research facility, hidden beneath layers of secrecy and protected by state-of-the-art security systems, a team of brilliant scientists had been working on a project that promised to change the course of human history. The project, codenamed "Elysium," aimed to harness the power of the sun itself, converting it into a form of sustainable, limitless energy.

And so, the story of Brj-502 became a legend, whispered among those who believed in a better tomorrow. A reminder that even in the darkest of times, there are always those working tirelessly towards a world where technology and dreams converge.

The Brj-502 Manual detailed every component of the Elysium device, from the Hyperion reactor at its core, which was capable of withstanding temperatures and pressures that would vaporize any known material, to the Aurora module, a sophisticated system for energy conversion and storage.

One entry, dated March 15, 2023, stood out:

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.