FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [September 2015 Threads]
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?
Blue Thunder on DVD5 is a lean, mean machine—just like the helicopter itself. It lacks the bells and whistles of a special edition, but the film’s raw power and timely paranoia shine through. If you want a clean transfer of a forgotten classic that flies under the radar, this disc delivers.
Anamorphic Widescreen (2.35:1). The transfer preserves the gritty, naturalistic cinematography of the early 80s. Expect some film grain and occasional softness (inherent to the source), but colors—especially the LAPD patrol blue and the desert browns—remain faithful. Black levels are strong during night flights.
Here’s a solid, concise write-up for a DVD5 release of Blue Thunder (1983), covering the film’s significance, plot, cast, and what a collector can expect from the disc. Film Overview
English SDH, Spanish, French (varies by region).
Roy Scheider stars as Frank Murphy, a veteran LAPD helicopter pilot haunted by past trauma. Paired with his reluctant observer, Richard Lymangood (Daniel Stern), Murphy is assigned to test the ultimate surveillance and weapons platform: "Blue Thunder," a heavily armed, experimental stealth helicopter designed for urban pacification. But as Murphy digs deeper into the helicopter’s true purpose—and the shadowy government forces behind it (led by a chilling Malcolm McDowell)—he realizes Blue Thunder isn’t meant to protect the public, but to control it.
Blue Thunder is a high-octane, paranoid action-thriller from director John Badham ( Saturday Night Fever , WarGames ). Released in 1983, it arrived at the peak of the Cold War and the dawn of the high-tech military-industrial complex. Part police drama, part conspiracy thriller, and part aerial war movie, the film blends visceral practical effects with a sharp, post-Vietnam cynicism.
Dolby Digital 2.0 Stereo (original theatrical mix) and optional 5.1 Surround. The 2.0 track delivers the aggressive rotor soundscape accurately, while the 5.1 adds modest rear-channel ambiance during flyovers.
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.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.