dnfuss Community Member

Hi guys- I appreciate you're likely busy with other things, but would like to check that I'm not missing anything obvious with this- I assume the embOS and ThreadX examples allow a complete backtrace of the call stack when the SP register is set to the…

Hi I've got as far as restoring the saved registers (r3-r11 and lr) and setting the aRegs SP and PC indexes to that of the stack frame at the top of the stack when the thread was suspended. Although this does result in the stack changing to that of the…

Thanks Nino That's good to know- My plugin was derived from the embOS plugin but the MQX kernel structure is very different, so I'll need to find where R0 - R15 and PSR are stored within an MQX task. You mentioned callstack- is that separate operation…

Hi! I'm using an RTOS aware plug-in that I've developed for MQX, and I'm wondering if there's any way of having the call stack window reflect the context of the task selected in the displayed table (as in image below)? At present, it appears only to…

Hi Nino Understood, and thanks again for your helpful explanations and prompt responses Kind regards David

Hi Nino That sounds like an elegant solution, thank you. May I enquire as to whether that will make it into the next J-Link DLL release? If so, I might hold off applying the workaround to our various jlink scripts... Kind regards David

Hi Nino Ah- Perhaps the issue is explained by the fact that I'm using the Trace Buffer (as distinct from Trace Pins), which appears to also enable Trace Pins -Is there a way of enabling/disabling Trace Pins independent of Trace Buffer? Regards David

Hi Nino Thank you for looking into this so quickly and for your explanation. I'm still a little puzzled as to why this trace pin configuration is happening at all, since I haven't explicitly enabled trace pins (assuming that this would be done via …

Hi 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.…

Hi 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…

Excellent, thank you Nino