Hello @JJhin.1
When you encounter a difference in behavior between different versions of a real-time operating system component, such as FreeRTOS CMSIS V1 versus V2, it can be due to various reasons, including changes in the API, differences in initialization code, or changes in how the middleware interacts with the underlying RTOS.
Here are some steps to troubleshoot the issue:
- Check the Middleware Initialization Code: Ensure that the middleware initialization code is compatible with CMSIS-RTOS V2. There might be changes in the initialization sequence or configuration structures that need to be addressed when upgrading from V1 to V2.
- Review the USB Host Configuration: Verify that the USB host configuration is correctly set up for CMSIS-RTOS V2. This includes checking the USB host task priorities, stack sizes, and any other relevant parameters.
- Compare API Differences: Look for any differences in the USB middleware API between the two versions. CMSIS-RTOS V2 might have introduced changes that affect how the USB middleware should be used.
- Inspect the State Machine: Review the code responsible for managing the Appli_state. It's possible that the conditions for transitioning to APPLICATION_READY are not being met due to timing issues or changes in the way the USB middleware reports its status.
- Analyze the USB Interrupts and Callbacks: Check if there are any differences in how interrupts and callbacks are handled between the two versions. Ensure that the USB interrupt priorities are compatible with FreeRTOS and that the callbacks are being set and used correctly.
- Look for RTOS Kernel Changes: Since CMSIS-RTOS V2 may introduce changes to the RTOS kernel behavior, ensure that these changes are not affecting the USB middleware. This can include task scheduling, interrupt handling, or inter-task communication mechanisms.
- Debug the Application: Use a debugger to step through the code and observe where the state machine is getting stuck. Pay special attention to any conditional statements that lead to the APPLICATION_READY state.
By systematically going through these steps, you should be able to identify and resolve the issue causing the Appli_state to remain in APPLICATION_START when using FreeRTOS CMSIS V2. If the problem persists, please provide more details on your setting project if possible, attach your .ioc file/configuration.
