LaoShaw Posted June 9, 2022 Report Share Posted June 9, 2022 I can use gdb to debug general systemc code. I can also use the gdbserver-stub built into my ISS to step through the target code(running inside the model, e.g. a small code outputs to UART). now when my code got stuck in the target code that is running inside the model(e.g. UART never output the character), the gdbserver-stub can not proceed to next line of code, attach gdb directly to the systemc model itself does give me a backtrace, which is nice, but it's still difficult to figure out what is wrong in the systemc/TLM's code(e.g. UART implementation in systemc) what's a better approach to debug scenarios like this? i.e. when the code running inside the model that exercises the peripherals from the systemc model is not working, how to find out what's wrong. Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.