I have been using VS code with a Segger Jlink for debugging so far but am struggling to find the cause of a problem in a driver I'm writing and I think the VS Code debug setup may be lacking.
Before I spend time getting openOCD installed and following the various guides for that, with NuttX, that exist, has anyone used VS Code to more thoroughly debug NuttX (threads, memory exceptions/errors) rather than just relying on breakpoints? Thanks, TimH
