Thank you, Tristan! You are absolutely right! I can run a terminal session and gdb at the same time. I made wrong assumptions when my flash uploads failed when I had the terminal session up. I concluded that only one thing can use the USB device at a time. But indeed terminal and debug sessions seem to be fine sharing the same physical USB connection. I'm using MacOS and only one serial device shows up for me when I plug the board in. I don't know enough about USB to check and see the virtual ports, but it seems to be working just as you described. You've saved me a lot of time and frustration. Thank you again!
Cheers, Martin On Tue, Jan 6, 2026 at 7:04 AM <[email protected]> wrote: > Hello Martin, > > UNO R4 openOCD plus simultaneous serial connection? > > I don't have the hardware to check but would expect [1] two virtual COM > ports to be provided over the one physical USB-C connection; a debug > port you can use with openOCD etc. and a serial port you can use > simultaneously with minicom etc. or amforth-shell.py > > Best wishes, > Tristan > > [1] from previous comments I'm guessing you have the UNO R4 Wifi and not > the UNO R4 minima > > > On 2026-01-06 02:58, Martin Kobetic wrote: > > That's a great write up, Tristan. I need to figure out a way to debug > > scenarios requiring user input. I'm currently using the same USB > > connection > > for connecting OpenOCD to the board, so I can't run serial I/O while > > I'm > > debugging. I'm guessing there isn't any simple solution that won't > > require > > a separate debug connection, I just haven't figured out how to do that > > yet. > > The best workaround I could think of is to simulate input by preloading > > the > > TIB with the content I'd type in, although that's fairly cumbersome. > > Currently I just code up the scenario I want to debug in the turnkey > > word > > and throw an XT_HALT word in there somewhere (halt just invokes > > wait-for-interrupt instruction which isn't quite a halt instruction but > > does the job while I'm not really using interrupts for anything), and > > then > > reset the board under debugger. > > > > > _______________________________________________ > Amforth-devel mailing list for http://amforth.sf.net/ > [email protected] > https://lists.sourceforge.net/lists/listinfo/amforth-devel > _______________________________________________ Amforth-devel mailing list for http://amforth.sf.net/ [email protected] https://lists.sourceforge.net/lists/listinfo/amforth-devel
