Closed EricB-ADI closed 5 months ago
Here is the bad condition
(gdb) p *tmr
$8 = {
cnt = 0,
cmp = 0,
pwm = 0,
intfl = 0,
ctrl0 = 0,
nolcmp = 0,
ctrl1 = 0,
wkfl = 0
}
(gdb) p tmr_id
$9 = 2
This is the dump when it is good
(gdb) p/x *tmr
$5 = {
cnt = 0x7,
cmp = 0xefffffff,
pwm = 0x0,
intfl = 0x1000100,
ctrl0 = 0x4060,
nolcmp = 0x0,
ctrl1 = 0x80000008,
wkfl = 0x0
}
It appears the timer is not being enabled? May be a race condition in PalTimer for the BLE stack.
There is a spurious GPIO interrupt, during the initialization before the timer is enabled.
I keep running into an issue on the ME18 with the timer upon startup. It gets stuck waiting for an interrupt flag. This only happens upon first run after flash. A reset seems to fix it, and it can be repeatedly seen using the Bluetooth examples. Here is the backtrace
I am gonna try to find the root cause, but I figured I would leave this here if anyone has seen it.