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?
The series also explores the concept of identity and self-discovery. Many characters struggle with their past, their sins, and their sense of purpose. As they navigate the world and confront their enemies, they are forced to confront their own demons and re-evaluate their values and goals.
Nanatsu no Taizai, also known as The Seven Deadly Sins, is a popular Japanese manga and anime series created by Nakaba Suzuki. The series takes place in a medieval-inspired world where a group of knights, known as the Seven Deadly Sins, are framed for treason and forced to disband. Years later, the kingdom is in peril, and the knights must reunite to save the day. In this article, we’ll delve into the world of Nanatsu no Taizai, exploring its complex characters, themes, and storylines.
One of the primary themes of Nanatsu no Taizai is the nature of justice and morality. The series explores the gray areas between right and wrong, often blurring the lines between heroism and villainy. The characters are multidimensional, with complex motivations and backstories that make it difficult to categorize them as purely good or evil.
The action scenes are often fast-paced and thrilling, with a focus on strategy and teamwork. The Seven Deadly Sins work together to take down their enemies, using their individual strengths and weaknesses to overcome their opponents.
Another significant theme is the power of friendship and camaraderie. The Seven Deadly Sins, despite their differences and personal struggles, form a strong bond that helps them overcome the challenges they face. Their relationships are built on trust, loyalty, and a deep understanding of one another.
The Unjust Knights: Unpacking the Themes and Story of Nanatsu no Taizai**
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.