[beagleboard] BBB Debian Wheezy config bootargs

I'm trying to pass console info of ttyO2 to match my jumper settings/baud 9600 on a RS232 cape, but my kernel says: dmesg | grep tty [0.00] Kernel command line: console=ttyO0,115200n8 fixrtc root=/dev/mmcblk1p2 ... As I understand in Angstrom, I would pass my boot args for console as

Re: [beagleboard] BBB Debian Wheezy config bootargs

On Mon, Nov 25, 2013 at 4:07 PM, Brian Mundell wrote: > I'm trying to pass console info of ttyO2 to match my jumper settings/baud > 9600 on a RS232 cape, but my kernel says: > > dmesg | grep tty > [0.00] Kernel command line: console=ttyO0,115200n8 fixrtc > root=/dev/mmcblk1p2 ... > > As I

Re: [beagleboard] BBB Debian Wheezy config bootargs

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? On Monday, November 25, 2013 3:10:06 PM UTC-8, RobertCNelson wrote: > > On Mon, Nov 25, 2013 at 4:07 PM, Brian Mundell > > > wrote: > > I'm tryi

Re: [beagleboard] BBB Debian Wheezy config bootargs

On Tue, Nov 26, 2013 at 12:39 PM, Brian Mundell 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

Re: [beagleboard] BBB Debian Wheezy config bootargs

The file (uEnv.txt) was created and the contents of it say just this: console=ttyO2,9600n8 There is nothing else in that file. After I rebooted with this file in place it is still not passing traffic through minicom to a Junpier NS5GT and back. On Tuesday, November 26, 2013 10:39:07 AM UTC-8,

Re: [beagleboard] BBB Debian Wheezy config bootargs

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 > > > wrote: > > I looked to see if i

Re: [beagleboard] BBB Debian Wheezy config bootargs

Ok, I flashed eMMC with the 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

Re: [beagleboard] BBB Debian Wheezy config bootargs

On Wed, Nov 27, 2013 at 1:28 PM, Brian Mundell wrote: > Ok, I flashed eMMC with the > 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

Re: [beagleboard] BBB Debian Wheezy config bootargs

console=ttyO0,9600n8 The above works for a fact, at least on my own BBB. I have to use this BAUD rate since I use an MSP430 Launchpad as a serial debug interface( and max BAUD rate is 9600 bps ) As for the rest, I couldn't say. On Wed, Nov 27, 2013 at 1:06 PM, Robert Nelson wrote: > On Wed, No

Re: [beagleboard] BBB Debian Wheezy config bootargs

I changed the baud rate, so it looks like: console=ttyO2,9600n8 and now it won't boot with the cape on. If I pull the cape off and then try to boot, I get to the penguin icon on my hdmi display, and it sits there for probably 5 minutes (presumably timing out while waiting for console?) and I c

Re: [beagleboard] BBB Debian Wheezy config bootargs

I woud recommend that you get a 3v3 ttl serial debug cable if you do not have one already, and debug over the serial debug device ttyO0. I know you're trying to get serial on a cape working but this is the only real way you'll know what is going on at boot time. So until you get one of these adapt

Re: [beagleboard] BBB Debian Wheezy config bootargs

I suppose I could debug using the header, but really the question is how BBB used ttyO0 vs. ttyO2, i.e. does it think ttyO0 is a default console used as a virtual "display" in the absence of hdmi out? Otherwise, why would changing baud make boot fail? I am tempted to re-flash the eMMC yet again

Re: [beagleboard] BBB Debian Wheezy config bootargs

Brian, it really is not that hard. Personally I use an MSP430 Launchpad v1.15 to get the serial console from the Serial debug header. I can not read / see output from uboot as I believe it is hard coded to 115200bps ( msp430 LP's max baud is 9600 ), but i get the Linux boot terminal just fine. That

Re: [beagleboard] BBB Debian Wheezy config bootargs

But whether or not I get serial debug information on those headers, the real question is if I'm really in the right place for configuring the cape, or whether I'm just passing bootargs that configure how the armhf (and assorted other system chips) talks to the rest of the system and/or the debu