You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As strange as it sounds I'm currently trying to build a good baremetal Go debug environment. The main reason is porting TamaGo to more targets. The most common way to access these targets is via JTAG which traditionally is more used with GDB in combination but I'd rather use delve if feasible. Could this be facilitated by just smartly setting some flags in either tool (probe-rs for the JTAG access and delve for the actual debugging) or would there be more needed to get this working well within delve?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
As strange as it sounds I'm currently trying to build a good baremetal Go debug environment. The main reason is porting TamaGo to more targets. The most common way to access these targets is via JTAG which traditionally is more used with GDB in combination but I'd rather use delve if feasible. Could this be facilitated by just smartly setting some flags in either tool (probe-rs for the JTAG access and delve for the actual debugging) or would there be more needed to get this working well within delve?
Beta Was this translation helpful? Give feedback.
All reactions