Hello
i have beaglebone black Rev A5C that works correctly with the Serial debug header
yesterday i have bought a new beaglebone black Rev A6A (new BBB) , but when i connect the serial FTDI debugger it didn’t work at all
there is nothing displayed on the host terminal when the new BBB boot up
i have tried to connect TX with RX from the debug header of the new BBB and used minicom on the new BBB using with the following settings :
ttyO0
115200N1
no hardware flow control
and try to write some chars , but nothing received , i think that the FTDI debug header is not connected with the ttyO0 , i think that there is a hardware bug from the BBB factory .
if what i think is true so , i have to redirect the u-boot console output to another tty like ttyO4 , but i don’t know how to do that .
Hello
i have beaglebone black Rev A5C that works correctly with the Serial debug
header
yesterday i have bought a new beaglebone black Rev A6A (new BBB) , but when
i connect the serial FTDI debugger it didn't work at all
there is nothing displayed on the host terminal when the new BBB boot up
i have tried to connect TX with RX from the debug header of the new BBB and
used minicom on the new BBB using with the following settings :
ttyO0
115200N1
no hardware flow control
and try to write some chars , but nothing received , i think that the FTDI
debug header is not connected with the ttyO0 , i think that there is a
hardware bug from the BBB factory .
Are you certain you've got the hardware still setup properly (cable
plugged in right direction, terminal software configured the same,
etc)?
If you have access to a scope, I suggest monitoring the line.
Do you see the LEDs blink? Have you tried booting off of uSD?
if what i think is true so , i have to redirect the u-boot console output to
another tty like ttyO4 , but i don't know how to do that .
It might work to specify ttyO4 in the uenv.txt console= command line
argument and add the config enablement to the device tree. If you are
serious about this, I can break down a few of those steps for you. Of
course, that would just move the kernel output, not the u-boot output.
Much of the relevant config info is in:
(It is a bit of an odd legacy that the config is in am335x_evm, but it
was to make the code common with several other boards.)
i am sure the the cable is pluged in in the right way , cause when i connect my old BBB (Rev A5C) with the same cable and same settings it works properly .
so the problem is with my new BBB it self .
if there is a way to change the u-boot console output to ttyO4 this will be great , cause sending back my new BBB will cost me more than buying a new one .
The A6A is an old revision board. We have not made that one for a while. If you just got it, that causes me some concern. Where did you get this board?
i am sure the the cable is pluged in in the right way , cause when i connect
my old BBB (Rev A5C) with the same cable and same settings it works properly
.
so the problem is with my new BBB it self .
if there is a way to change the u-boot console output to ttyO4 this will be
great , cause sending back my new BBB will cost me more than buying a new
one .
You can successfully boot and log in, yes? LEDs blinking and all?
If you are having boot problems, simply start you work from a
known-good image and then work your way into something custom, rather
than starting from an unknown point.
as a first step i try to enable the UART4 from the uEnv.txt and change the console to ttyO4 :
this is my full uEnv.txt :
optargs=quiet drm.debug=7 capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN capemgr.enable_partno=BB-UART4 console=ttyO4,115200n8 mmcargs=setenv bootargs console=${console}
run mmcargs;
there is nothing appear in the terminal .
when the BBB has finished from booting operation , i make ssh connection with it , and check the loaded overlays
cat /sys/devices/bone_capemgr.8/slots
the result is UART4 overlay is loaded correctly , so i don’t know why there is nothing appear in my terminal from the kernel console output
Hello
i have beaglebone black Rev A5C that works correctly with the Serial debug header
yesterday i have bought a new beaglebone black Rev A6A (new BBB) , but when i connect the serial FTDI debugger it didn’t work at all
there is nothing displayed on the host terminal when the new BBB boot up
i have tried to connect TX with RX from the debug header of the new BBB and used minicom on the new BBB using with the following settings :
ttyO0
115200N1
no hardware flow control
and try to write some chars , but nothing received , i think that the FTDI debug header is not connected with the ttyO0 , i think that there is a hardware bug from the BBB factory .
if what i think is true so , i have to redirect the u-boot console output to another tty like ttyO4 , but i don’t know how to do that .
I am having the same problem. Is it solved or the A6A is flawed for serial ftdi by default and requires further to do something?