In our blog we regularly post about the status of the project, things we figured out while working on it and other things that might come to our mind. Please contact us if you want to share your experience with Open SoC Debug, guest posts are always welcome!
Stop the engines! This command will be understood by Open SoC Debug soon as Shivam Aggarwal (@shivmgg) adds run-control debug support to Open SoC Debug. Run-control debug, or “stop and stare debugging” is known to many when using a debugger such as GDB to set breakpoints and inspect the program state once the executed halted. Up to now, Open SoC Debug focused on tracing, leaving this other important debugging technique on the wishlist. But not any longer.
Over the last roughly two years, Open SoC Debug has grown into a reliable debugging tool for the needs of lowRISC and OpTiMSoC. A lot of effort went into fixing small bugs to improve reliability and to add some features such as the emulated UART device, UART-DEM. And it was worth the effort, as we’ve seen over the summer when we added Linux support to OpTiMSoC. Control flow traces generated by the CTM modules, as well as the UART-DEM module were major enablers for this work.
We have updated our specification and other documentation significantly!
We have migrated the OpTiMSoC debug structure to use the Open SoC Debug prototype implementation. Learn more about it and get started with the tutorial in the user guide.
We finished prototyping of the first full Open SoC Debug-based lowRISC SoC. There is a comprehensive tutorial that includes documentation details.
You can find the basic ideas and components of Open SoC Debug in an Online Overview Presentation.