For those that still need to use ttyO0 for their purpose and not as login
console (I won't ask you why, in my case I simply need 5 uarts) the only
thing I had to do on my setup (beagle bone black, with
debian-9.5-iot-armhf-2018-08-30) to enable ttyO0 is disable the
serial-getty@ttyO0.service
Interesting subject,
in my case I need the Pins used by UART 0 for something else.
In the file
https://github.com/jadonk/cape-firmware/blob/master/arch/arm/boot/dts/am335x-bone-common.dtsi
There is a reference to UART 0 :
uart0 { pinctrl-names = default; pinctrl-0 = uart0_pins; status =
Some reason you can't just use one of the other UARTs? It's very handy to
have a serial console for debugging.
On Thursday, September 11, 2014 10:29:48 AM UTC-7, jgold wrote:
I've got a RS232 micro cape
http://www.logicsupply.com/components/beaglebone/capes/cbb-ttl-232/ that
I need to use
ttyo0 has to be disabled in uEnv.txt, and also the board device tree file I
believe ( could be wrong on the last part ). Also, systemd may have a
service profile for it. I have not looked, and currently am not running
systemd. Maybe I'll check later once I get this rootfs working good, and
backed
The micro cape I purchased can be either UART0 or UART4 but to change it
you have to solder some bridges across some little bitty pads. It looked
too delicate for my fat fingers so with this setup, I'm kinda stuck with
UART0.
On Thursday, September 11, 2014 3:02:34 PM UTC-7, Lee Crocker
I found the answer here;
http://stackoverflow.com/questions/21596384/cannot-disable-systemd-serial-getty-service
My port is at ttyO0. so in my case I entered systemctl mask
serial-getty@ttyO0.service. I was able to confirm the device name by
typing systemctl --full. My device was in the
