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?
Rachel realized the potential consequences and decided against using the crack file. Instead, she proposed an alternative solution to her team: reaching out to Optitex directly to inquire about any available discounts or payment plans for small businesses.
One evening, as the team was working late to meet an impending deadline, their lead designer, Rachel, mentioned a rumor she had heard about a "crack file" for Optitex 11. The file supposedly allowed users to bypass the software's licensing requirements, enabling them to use it for free.
The team was divided. Some were intrigued by the possibility of accessing such a powerful tool without the hefty price tag, while others were concerned about the legality and ethics of using cracked software. Rachel, being the curious and ambitious person she was, decided to look into it further.
The team learned a valuable lesson about the importance of adhering to legal and ethical standards, even when faced with financial constraints. They discovered that with a little creativity and integrity, solutions could be found that benefited everyone.
She navigated through various online forums and shadowy corners of the internet where such files were often discussed. After several hours of searching, she finally found a link to download what was claimed to be an Optitex 11 crack file.
To their surprise, Optitex responded positively to their inquiry, offering a discounted rate for their subscription. It was a win-win situation; Elegance Reborn could now afford to use the software legally, and Optitex gained a satisfied customer.
In a bustling city known for its vibrant fashion scene, there was a small design house named "Elegance Reborn." The company was renowned for its exquisite clothing lines, but behind the scenes, it faced a significant challenge. The designers relied heavily on Optitex 11, a sophisticated software for textile design and pattern making, but the high cost of the software was straining their resources.
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.