Russ Butler
Russ Butler
> If no real RTOS is present, and threading is enabled, use a bare-metal provider that gives us two Main and Process threads. One concern I have with this approach...
Thanks for the detailed response @kjbracey-arm. Since GDB support for unwinding through ISRs and pyOCD writing to the non-active thread both aren't currently supported, there is no reason to limit...
**Showing the context in which a hardfault occurred rather than the hardfault ISR** I like the idea of this, but I don't like the fact that what the debugger is...
Before GCC support can be added RTX needs to be updated. The version of RTX used by DAPLink doesn't have support for GCC, but newer versions do.
I don't think the USB stack has strong ties to any toolchain, so it should be fairly straight forward to update to use GCC.
Hi @OwenBrotherwood, yep that is the right RTX. Since it's open source anyone who is interested could start the porting process.
@mmahadevan108 can you make these updates since you are maintaining the lpc4322?
If you run the DAPLink test suite on linux then this failure will occur.
This issue should already be fixed by #175. Can you confirm?
@flit, looking at this more thoroughly, it might need to be applied on top of #175. Why does the last read of the UUID cause a stickyerr? Also, why is...