remove "console=tty0" and see what that results in. On Tue, Nov 25, 2014 at 7:16 PM, foreverska <[email protected]> wrote:
> console=tty0 console=/dev/ttyO0,115200n8 > capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN,BB-BONE-EMMC-2G > root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc quiet > init=/lib/systemd/systemd > > On Tuesday, November 25, 2014 7:12:54 PM UTC-6, William Hermans wrote: >> >> Finally I wanted to see if I could finagle it working even with the >>> terminal running on TTYO0 (login and run a program that doesn't poll the >>> resource). However, after changing uenv.txt back the terminal hasn't come >>> back after several reboots. I might have changed other stuff in trying to >>> get it to work but I can't remember what. What else controls the function >>> of TTYO0? >>> >> >> Double check to make sure the changes stuck. Also what is the pout put of >> : >> >> *$ cat /proc/cmdline* >> >> ? >> >> On Tue, Nov 25, 2014 at 6:06 PM, William Hermans <[email protected]> >> wrote: >> >>> Does the file */etc/inittab* >>> >>> Contain a line similar to this -> *T0:23:respawn:/sbin/getty -L ttyO0 >>> 115200 vt102* >>> >>> ?? >>> >>> On Tue, Nov 25, 2014 at 2:41 PM, foreverska <[email protected]> wrote: >>> >>>> Also if I sudo echo to ttyO0 it doesn't show on the terminal monitoring >>>> it on the other side. >>>> >>>> >>>> On Tuesday, November 25, 2014 3:35:18 PM UTC-6, foreverska wrote: >>>>> >>>>> Hi board, >>>>> >>>>> I'm working on a project and there are some comms traditionally done >>>>> by RS232. The "cape" already has a FTDI chip connected to J1 for >>>>> convenience. So I thought that might just be the easiest solution, tell C >>>>> to latch onto ttyO0 and call it a day. Well it worked alright but the >>>>> open >>>>> terminal on that port kinda got in the way. So I went into uEnv.txt and >>>>> moved the terminal (the splurge of info on boot isn't a big deal). >>>>> However >>>>> now TTYO0 is basically unresponsive. When I open TTYUSB1 on my PC with >>>>> screen the boot splurge happens and then after the kernel is booted there >>>>> is no more output and it won't accept input. When I run my application >>>>> screen stays unresponsive. >>>>> >>>>> Finally I wanted to see if I could finagle it working even with the >>>>> terminal running on TTYO0 (login and run a program that doesn't poll the >>>>> resource). However, after changing uenv.txt back the terminal hasn't come >>>>> back after several reboots. I might have changed other stuff in trying to >>>>> get it to work but I can't remember what. What else controls the function >>>>> of TTYO0? >>>>> >>>> -- >>>> 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]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
