I apologize if this seems like a really bone-headed comment, but I ran into something similar when using a USB JTAG emulator (XDS100V2) and a USB<->FTDI cable for the console. Quite simply the USB serial device # changed when I had both cables plugged into my host machine.
I was used to using minicom -D /dev/ttyUSB0 on my host computer to display the BeagleBoard's console, but when i plugged in the JTAG USB emulator cable, the JTAG USB always got ttyUSB0 and the USB<->FTDI cable got ttyUSB1, so I had to type minicom -D /dev/ttyUSB1.. On Tuesday, September 19, 2017 at 8:10:09 PM UTC-5, [email protected] wrote: > > Running into an issue where we were able to see console output on the > serial console when no JTAG or CCS was connected. After connecting CCS to > JTAG and updating the DDR3 gel file we were able to see the output over the > CCS serial console. After disconnecting the JTAG and CCS and doing a board > reset, we can no longer see anything over the original serial console. > Disconnected the serial console, did hardware reset, unplugged the BBB from > the power supply and still the BBB simply appears hung or redirecting > output or simply not responding CPU hung after power is applied. > > What is causing this condition. It is fine when JTAG is connected and > using CCS. But board appears hung with no CCCs or otherwise on reboot when > JTAG and CCS is not connected. What is taking place? > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/6dc56f0b-c6c8-41f0-8f1d-71707fe49b8f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
