Description
- Type: Bug? / Question
- Priority: Major
Bug
Target
NRF52DK
Toolchain:
GCC_ARM
Toolchain version:
mbed-os sha:
5f6572179 (tag: mbed_lib_rev157, tag: mbed-os-5.6.6, origin/mbed-os-5.6) Merge pull request #5634 from ARMmbed/release-candidate
DAPLink version:
Expected behavior
Nop
Actual behavior
mbed assertation failed: os_timer->get_tick() == svcRtxKernelGetTickCount(), file: ./mbed-os/rtos/TARGET_CORTEX/mbed_rtx_idle.c
Followed by ending up in the hardfault handler mbed_die
Steps to reproduce
Happens to me all the time as soon as I use a debugger, I would rather know if this is either a known issue or what can cause this.
My program works fine unless a debugger is attached in one case, in another it just leaves the debugger behind (ozone and JLink sotware) and doesn't break.
My use case is running the AtWinc1500 as an SPI slave.
drahnr
All 4 comments
Possibly related:
https://os.mbed.com/questions/79770/nRF52832-Assert-Lockup/
https://github.com/ARMmbed/mbed-os/pull/5595
drahnr
on 25 Jan 2018
@c1728p9 Please review
0xc0170
on 25 Jan 2018
Halting the device in a debugger for too long or being in a critical section for too long can cause this assert to occur. This is not ideal so I created #5942 to remove the assert.
c1728p9
on 25 Jan 2018
Closing this issue since #5942 has been merged.
c1728p9
on 3 Apr 2018
Related issues
DuyTrandeLion
路
3Comments
1domen1
路
3Comments
ghost
路
4Comments
bcostm
路
4Comments
pilotak
路
3Comments
Most helpful comment
Halting the device in a debugger for too long or being in a critical section for too long can cause this assert to occur. This is not ideal so I created #5942 to remove the assert.