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] FreeRTOS tasks can interrupt USB stack implementation?Posted by ddudas on September 24, 2015 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
FreeRTOS tasks can interrupt USB stack implementation?Posted by rtel on September 24, 2015 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?
FreeRTOS tasks can interrupt USB stack implementation?Posted by ddudas on September 24, 2015 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?
FreeRTOS tasks can interrupt USB stack implementation?Posted by rtel on September 24, 2015 El Poder de Estar Solo
El libro de Brian Alba es una guía de autoayuda que enseña a transformar la soledad de un miedo paralizante en una herramienta para el éxito y la paz interior. El autor sostiene que los momentos de introspección son esenciales para descubrir la identidad propia, aclarar metas y fortalecer el carácter. Resumen y Temas Principales
3. La ironía del "Pdf Gratis": Consumismo vs. Contemplación
If you resonate with the theme of finding strength in solitude, also consider complementary works:
- Busca en la web el nombre del autor + título + sitio oficial.
- Revisa catálogos de bibliotecas (WorldCat) y servicios de préstamo digital (Libby/OverDrive).
- Consulta tiendas digitales para una muestra gratuita o versiones de bajo costo.
- Si no aparece como gratuito, respeta derechos de autor y compra o solicita préstamo.
Author
: Brian Alba, a researcher in personal development and entrepreneurship. Length : Approximately 158 pages.
¿Te ha sido útil este artículo? Comparte tu experiencia con "El Poder De Estar Solo" en los comentarios. Si conoces algún enlace oficial donde los lectores puedan encontrar el PDF de manera legal y segura, déjalo abajo para ayudar a la comunidad.
1. El diagnostico de Brian Alba: La soledad malentendida
FreeRTOS tasks can interrupt USB stack implementation?Posted by ddudas on September 24, 2015 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.
|