Hi,
thanks, link updated, it was because the new web site. Added some more info to the articles too.
Giovanni
[INFO] ChibiOS 2.6->3.0 porting guide
- Giovanni
- Site Admin
- Posts: 14444
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1074 times
- Been thanked: 921 times
- Contact:
- russian
- Posts: 364
- Joined: Mon Oct 29, 2012 3:17 am
- Location: Jersey City, USA
- Has thanked: 16 times
- Been thanked: 14 times
Re: [INFO] ChibiOS 2.6->3.0 porting guide
What is the 3.0 replacement for CORTEX_PRIORITY_SYSTICK?
I am using 3.0 in tick mode and just realized that I have no idea what is the priority of my virtual timers which I assume are on the systick handler.
CORTEX_PRIORITY_SYSTICK is not mentioned in the code anymore and I am not sure if CORTEX_PRIORITY_SVCALL is what I need.
I am using 3.0 in tick mode and just realized that I have no idea what is the priority of my virtual timers which I assume are on the systick handler.
CORTEX_PRIORITY_SYSTICK is not mentioned in the code anymore and I am not sure if CORTEX_PRIORITY_SVCALL is what I need.
http://rusefi.com/ - electronic fuel injection
- Giovanni
- Site Admin
- Posts: 14444
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1074 times
- Been thanked: 921 times
- Contact:
Re: [INFO] ChibiOS 2.6->3.0 porting guide
Hi,
Systick is no more handled in the Cortex port layer, now there is a new "ST" (SysTick) driver in HAL, related settings are there. Note that in tickless mode the systick cortex timer is not used.
Giovanni
Systick is no more handled in the Cortex port layer, now there is a new "ST" (SysTick) driver in HAL, related settings are there. Note that in tickless mode the systick cortex timer is not used.
Giovanni
- russian
- Posts: 364
- Joined: Mon Oct 29, 2012 3:17 am
- Location: Jersey City, USA
- Has thanked: 16 times
- Been thanked: 14 times
Re: [INFO] ChibiOS 2.6->3.0 porting guide
Sounds like STM32_ST_IRQ_PRIORITY is CORTEX_PRIORITY_SYSTICK replacement
Wonder how many people are confused by "ST" abbreviation. Would it be beneficial to mention SysTick in the @brief or @details?
* @file st.c
* @brief ST Driver code.
* @file st.h
* @brief ST Driver macros and structures.
* @details This header is designed to be include-able without having to
* include other files from the HAL.
Wonder how many people are confused by "ST" abbreviation. Would it be beneficial to mention SysTick in the @brief or @details?
* @file st.c
* @brief ST Driver code.
* @file st.h
* @brief ST Driver macros and structures.
* @details This header is designed to be include-able without having to
* include other files from the HAL.
http://rusefi.com/ - electronic fuel injection
Return to “Development and Feedback”
Who is online
Users browsing this forum: No registered users and 25 guests