Many of us work remotely. We had to work out licensing to properly tunnel to the tap. That all works but makes it a bit harder to manage.
I added a printf to some u-boot code, then tried to use fwupd. Now the target is locked up.
The tap has never allowed me to examine memory or registers.
In a past life I would attach a probe, click on "connect", then "step" or "halt", and look at memory. This one seems to need configure, configure, configure. Right now I'm looking thru docs for "Debug Configuratins" and "Build Configurations"
The help screen does not match with my tool for the topic of "Target Connection Configuration", specifically the information regarding Windows-Preferences-.
After I look thru some docs, I'll submit a ticket. If you have a suggestion, I'd be grateful.
In Target Connections panel, you could click the icon "Inspect(attach to running target)" to connect your target board, then ream memory dump and register values.
For u-boot debugging, you could refer to this document.