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?
: Use a tool like WinRAR or 7-Zip to extract the contents of your vag k can commander 14.rar file.
Connect the remaining USB end directly into the computer.
Compatible, but requires manual driver enforcement. You must launch the primary executable using administrative privileges and utilize standard Windows compatibility modes. Critical Safety Warnings
Open the destination folder. Confirm the presence of the main executable file ( Tester.exe or VagCommander.exe ), configuration initializers ( .ini files), and a dedicated Drivers folder containing FTDI USB serial interface files.
: Find the entry under "Ports (COM & LPT)" or "Other devices" (often labeled "USB Serial Converter" with a yellow question mark). Update Driver Right-click the device and select Update Driver Software "Browse my computer for driver software"
Choose . Click Browse , navigate to the Drivers folder inside your extracted directory, and select it. Click Next to install. Map the COM Port Allocation In Device Manager, expand the Ports (COM & LPT) category. Right-click USB Serial Port and choose Properties .
VAG K+CAN Commander 1.4 is a diagnostic software tool designed for Volkswagen, Audi, Seat, and Skoda vehicles. It allows users to perform advanced functions that standard OBD2 scanners cannot execute. These functions include diagnostic trouble code reading, odometer correction, key programming, and EEPROM flashing.
04 00 01 (Unlock ECU). 03 00 (Request Seed). 01 0F (Send Key).
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.