Hello All,
Following is my setup:
ChibiOS 18.2.0: os-less
Board: Nucleo144-STM32L496ZG
SYSCLOCK: 80MHz, HSE is enabled, 16MHz Crystal.
Osal tick frequency:
#define OSAL_ST_FREQUENCY 1000
On creating an os-less project, I am unable to get SysTick interrupts. I checked the core peripheral registers value after bootup and halInit() they seem to be correct for 1msec tick.
Attached is the dmp file
Kind request if someone can help to look in the correct direction to reolve why SysTick ISR is not getting fired. The breakpoint never hits. virtual timers created do not get updated.
Thanks
SysTick ISR not firing Topic is solved
Moderators: RoccoMarco, barthess
-
- Posts: 9
- Joined: Sat Jan 27, 2018 1:33 am
- Has thanked: 4 times
- Been thanked: 5 times
- Giovanni
- Site Admin
- Posts: 14457
- Joined: Wed May 27, 2009 8:48 am
- Location: Salerno, Italy
- Has thanked: 1076 times
- Been thanked: 922 times
- Contact:
Re: SysTick ISR not firing Topic is solved
Hi,
Make sure to enable interrupts after halInit().
Giovanni
Make sure to enable interrupts after halInit().
Giovanni
-
- Posts: 9
- Joined: Sat Jan 27, 2018 1:33 am
- Has thanked: 4 times
- Been thanked: 5 times
Re: SysTick ISR not firing
Thank you, that worked for me.
chSysInit() is the case when RT is built, calls chSysEnable() which will then enable interrupts globally.
For os-less, since chSysInit() is out of the picture, osalSysEnable() was needed to be called after halInit() which enables the global interrupts.
chSysInit() is the case when RT is built, calls chSysEnable() which will then enable interrupts globally.
For os-less, since chSysInit() is out of the picture, osalSysEnable() was needed to be called after halInit() which enables the global interrupts.
Who is online
Users browsing this forum: No registered users and 43 guests