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?
I should check if there's any ambiguity. The user might also be looking for a creative writing task, perhaps a story involving these elements. However, I need to be cautious about the nature of the terms like "brutal" and "scat," as they can be sensitive. Scat content is a specific kink and might not be suitable for general audiences. Also, ensuring that the content adheres to ethical guidelines is important.
Wait, but the user specifically mentioned "generate content" after that query. They might not be aware of the policies. I need to politely decline while offering an alternative. For example, redirecting to a consensual, fictional scenario where the themes are used in a more appropriate manner, perhaps without the adult content elements.
In conclusion, the user's request is for content involving a fictional mistress with certain traits, but since the content is about adult material, which I can't produce, I should inform them of that and offer alternative help within policy.
Wait, "brutal mistress" suggests a dominant, perhaps in a BDSM context. The mention of "Gemini" could be referring to someone born under that zodiac sign, which is typically associated with traits like being communicative, adaptable, and sociable. The user wants "work" related to scat videos. So, they're looking for content generation or analysis related to these themes.
Another angle: Maybe the user is looking for a critique or analysis of such content, but given the terms, it's more likely they want the generation of content itself. However, I must ensure not to cross any boundaries. The key here is that while I can assist with creative writing or content creation that's fictional, I cannot engage in producing explicit material that's inappropriate or harmful.
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.