dnfuss Community Member
- Member since Sep 23rd 2020
- Last Activity
- , Reading thread IRQ input configuration lost following debugger halt
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
dnfuss -
Replied to the thread IRQ input configuration lost following debugger halt.
PostHi Fabian Thanks for your prompt response It's the Port Control and Interrupt (PORT) registers that are being affected The attached image indicates my particular use-case. Initially, execution is halted and PortA[10] is set to the required value.… -
dnfuss -
Posted the thread IRQ input configuration lost following debugger halt.
ThreadHi My application runs on a K60, and I'm able to debug using the excellent Ozone tool. However, I'm experiencing something unexpected when I halt a debugging session; My application configures certain inputs from their default state to act as IRQ… -
dnfuss -
Replied to the thread [SOLVED] Expected behaviour from 'Threads.setSortByNumber'....
PostExcellent, thank you Nino -
dnfuss -
Posted the thread [SOLVED] Expected behaviour from 'Threads.setSortByNumber'....
ThreadHi In my implementation of an MQX RTOS plug-in for Ozone, I'm wanting to order a table by the values in a 'Priority' column. UM08025 suggests that this is achievable using Threads.setSortByNumber(), but I'm unable to get it to function as I'd… -
dnfuss -
Replied to the thread Correct use of Debug.Evaluate when writing RTOS-aware plug-in.
PostHi Nino Release 3.22 does resolve a couple of issues I was seeing, however the cause of this particular issue remains and appears to relate to the casting of the address The structure 'kernel_data_struct' has a typedef of KERNEL_DATA_STRUCT_PTR, if I…