Ok, I flashed eMMC with the https://rcn-ee.net/deb/rootfs/wheezy/debian-7.2-console-armhf-2013-11-15.tar.xz <https://rcn-ee.net/deb/rootfs/wheezy/debian-7.2-console-armhf-2013-11-15.tar.xz> image (from a live image running on a microSD) successfully and rebooted into the eMMC.
Now I see /boot/uboot/uEnv.txt like I expect. But when I changed the console=ttyO0,115200n8 to console=ttyO2,9600n8 (to connect to the serial cape connected to my serial-managed firewall box) the BBB wouldn't boot. After I reflashed the eMMC to the same image as above, it booted again. I'm wondering if the ttyO0 is reserved for some pins in case I need a "serial monitor" if my hdmi out breaks, and whether I can add a second ttyOx of ttyO2 (which matches my UART2 tx/rx jumper settings on the cape) somehow with setserial (or whatever), since my dmesg shows: root@arm:/boot/uboot# dmesg | grep tty [ 0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc ip= [ 0.524587] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88) is a OMAP UART0 [ 1.267931] console [ttyO0] enabled [ 1.805555] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 90) is a OMAP UART2 which seems to say that it sees ttyO2 at UART2, but that ttyO2 isn't enabled, no? could I add a second console directive in uEnv.txt or should I do something else? On Tuesday, November 26, 2013 11:08:55 AM UTC-8, Brian Mundell wrote: > > Ok so I am going to re-flash this eMMC and see if I can get it set up. > Thank you very much Robert for the help. Post my results later. > > On Tuesday, November 26, 2013 10:47:32 AM UTC-8, RobertCNelson wrote: >> >> On Tue, Nov 26, 2013 at 12:39 PM, Brian Mundell <[email protected]> >> wrote: >> > I looked to see if i could find that file for numerous hours.......... >> It >> > was not there. Should it be created, then edited to have what I need in >> it? >> > >> >> Okay so obviously, your running that other image. Well that user >> doesn't post here, so go ask the question on his site.. >> >> Otherwise run the images hosted here: >> http://elinux.org/BeagleBoardDebian#Demo_Image<http://www.google.com/url?q=http%3A%2F%2Felinux.org%2FBeagleBoardDebian%23Demo_Image&sa=D&sntz=1&usg=AFQjCNGd94hmy35EdJLHJFR46IXYbx2qtw> >> >> >> or >> http://elinux.org/BeagleBoardDebian#eMMC:_BeagleBone_Black<http://www.google.com/url?q=http%3A%2F%2Felinux.org%2FBeagleBoardDebian%23eMMC%3A_BeagleBone_Black&sa=D&sntz=1&usg=AFQjCNFsIme7mNfwIF-JePn9STxIJa1k2Q> >> >> >> Which happen to be made for developers to actually change things... >> >> Regards, >> >> -- >> Robert Nelson >> http://www.rcn-ee.com/<http://www.google.com/url?q=http%3A%2F%2Fwww.rcn-ee.com%2F&sa=D&sntz=1&usg=AFQjCNGOHCXJQaZwU-JxxDUh5l2sPHvC9w> >> >> > -- 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/groups/opt_out.
