Bfdi Assets Faces And Limbs Download | Easy & Proven

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?

Four, horrified, tried to close the window. But the assets had already spread. His desktop icons morphed: the trash bin became Match’s frowning mouth. His browser turned into Eraser’s stretchy arm, bookmarking random websites. Even his mouse cursor—now Firey’s flaming foot—scorched the desk.

When Four unzipped it onto his desktop, a folder appeared labeled Inside weren’t just PNGs. They were living sprites. Tiny, disembodied eyes blinked from the thumbnails. A single, confused arm waved from its preview window.

“What… am I?” it asked.

Four, a competitive but fair-minded contestant from Battle for Dream Island , was browsing a fan asset forum late one night. He needed a specific frame of Golf Ball’s angry eyebrow for an animation. Instead, he found a link titled: BFDI_COMPLETE_FACES_LIMBS_FINAL(real).zip

“Hello?” said a high-pitched voice. Four spun around. His computer screen was now a mirror. And looking back at him wasn’t his own reflection—but a collage of mismatched parts: Leafy’s warm smile, Pin’s sharp tip, and Blocky’s mischievous left leg.

“We’ve been waiting for you,” the collage said. “You animators keep downloading us, using us once, and deleting us. We exist in folders, forgotten. No faces to make. No limbs to wave. Just… storage.”

“You want faces and limbs?” Four shouted, grabbing a flash drive. “I’ll give you a new body.”

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.