From: hypo <hyp...@gm...> - 2010-02-08 08:03:38
|
hi, is there a way to change uboot parameters from the linux console? my basic problem is described here: http://old.nabble.com/verdex-serial-spitting-out-garbage..-please-help!-tt27335409.html#a27335409 The serial communication to / from my Gumstix is hosed (looks like one bit is permanently set high), so i can't stop the bootup at the uboot prompt, nor can i type via the serial console. ssh works perfectly, however. I'm not sure if the problem is with the Verdex COM board or the LCD16-console-vx board or the particular output (i'm using the default center serial out). What would be a good way to debug this? I want to be sure that the problem is with the console-vx board before i fork out more money for a replacement board. i have tested the cable with another serial setup and it seems to work fine, so the problem must be either the particular port, the console-vx board (hope not) or the verdex COM board (yikes!). Is there a way to have the board use one of the other serial terminals (labeled HWUART or BWUART) for the serial console instead of the default center serial terminal? I understand that uboot passes the console as an argument to the linux kernel. More importantly, can i modify these settings from the linux ssh window? the ssh terminal is the only access i have right now to the board since the serial communication is broken. Any help would be most appreciated before i end up spending more money on wild-goose chases. thanks, hypo -- View this message in context: http://old.nabble.com/change-uBoot-parameters-from-linux-tp27496466p27496466.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2010-02-08 08:37:50
|
Hi Hypo, On Mon, Feb 8, 2010 at 12:03 AM, hypo <hyp...@gm...> wrote: > > is there a way to change uboot parameters from the linux console? my basic > problem is described here: > http://old.nabble.com/verdex-serial-spitting-out-garbage..-please-help!-tt27335409.html#a27335409 > > The serial communication to / from my Gumstix is hosed (looks like one bit > is permanently set high), so i can't stop the bootup at the uboot prompt, > nor can i type via the serial console. ssh works perfectly, however. > > I'm not sure if the problem is with the Verdex COM board or the > LCD16-console-vx board or the particular output (i'm using the default > center serial out). What would be a good way to debug this? I want to be > sure that the problem is with the console-vx board before i fork out more > money for a replacement board. The simplest way would be to swap in another console-vx board (or any other daughtercard) and see if the problem persists. It sounds like a bad ground, which could be caused by a cold solder joint (most likely on the connector which attaches to the console-vx board). > i have tested the cable with another serial setup and it seems to work fine, > so the problem must be either the particular port, the console-vx board > (hope not) or the verdex COM board (yikes!). > > Is there a way to have the board use one of the other serial terminals > (labeled HWUART or BWUART) for the serial console instead of the default > center serial terminal? I understand that uboot passes the console as an > argument to the linux kernel. > > More importantly, can i modify these settings from the linux ssh window? the > ssh terminal is the only access i have right now to the board since the > serial communication is broken. I seem to recall that there is a utility called fw_env that you can build (it's part of u-boot). From what II recall it's VERY important to have it match exactly with the version of of u-boot running on your board (otherwise you can hose your u-boot). Having a 2nd console-vx will at least allow you to further eliminate if it's the console-vx or the COM board. Have you tried any other type of device on your serial connection? (to eliminate a problem with your host PC). I had a pin break on one of my laptops serial ports (fortunately it was still under warranty - they had to replace the entire motherboard) and it caused intermittent problems with my serial comms. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: hypo <hyp...@gm...> - 2010-02-09 01:05:29
|
hi Dave, i came across one of your older posts that talked about fw_printenv and fw_setenv just before i hit the bed last night. i tried fw_printenv and it printed out what i have in uboot currently (i have my verdex booting off NFS and all settings printed out seemed to corroborate that), so i think it should match it (fingers crossed). is there anyother way to see if it matches the uboot version? Is there a help / documentation page for fw_printenv / fw_setenv? i didn't want to run fw_setenv without knowing what it would do with no / default / incorrect parameters. > Have you tried any other type of device on your serial connection? (to > eliminate a problem with your host PC). I had a pin break on one of my > laptops serial ports (fortunately it was still under warranty - they > had to replace the entire motherboard) and it caused intermittent > problems with my serial comms. > yes, i used another ATMEL board on the same connection which works with the same kermit settings, so i'm sure the problem is not with my Ubuntu machine or the RS232/USB dongle, or with the cable. i will probably end up getting another console-vx board. in the interim, is there a way to open a new serial terminal on one of the other ports without going via UBOOT/fw_setenv? i tried: getty -L ttyS1 115200 vt100 and getty -L ttyS2 115200 vt100 but i still don't see anything on the other ports (i took care to move the cable! :) thanks! hypo Dave Hylands wrote: > > Hi Hypo, > > On Mon, Feb 8, 2010 at 12:03 AM, hypo <hyp...@gm...> wrote: >> >> is there a way to change uboot parameters from the linux console? my >> basic >> problem is described here: >> http://old.nabble.com/verdex-serial-spitting-out-garbage..-please-help!-tt27335409.html#a27335409 >> >> The serial communication to / from my Gumstix is hosed (looks like one >> bit >> is permanently set high), so i can't stop the bootup at the uboot prompt, >> nor can i type via the serial console. ssh works perfectly, however. >> >> I'm not sure if the problem is with the Verdex COM board or the >> LCD16-console-vx board or the particular output (i'm using the default >> center serial out). What would be a good way to debug this? I want to be >> sure that the problem is with the console-vx board before i fork out more >> money for a replacement board. > > The simplest way would be to swap in another console-vx board (or any > other daughtercard) and see if the problem persists. > > It sounds like a bad ground, which could be caused by a cold solder > joint (most likely on the connector which attaches to the console-vx > board). > >> i have tested the cable with another serial setup and it seems to work >> fine, >> so the problem must be either the particular port, the console-vx board >> (hope not) or the verdex COM board (yikes!). >> >> Is there a way to have the board use one of the other serial terminals >> (labeled HWUART or BWUART) for the serial console instead of the default >> center serial terminal? I understand that uboot passes the console as an >> argument to the linux kernel. >> >> More importantly, can i modify these settings from the linux ssh window? >> the >> ssh terminal is the only access i have right now to the board since the >> serial communication is broken. > > I seem to recall that there is a utility called fw_env that you can > build (it's part of u-boot). From what II recall it's VERY important > to have it match exactly with the version of of u-boot running on your > board (otherwise you can hose your u-boot). > > Having a 2nd console-vx will at least allow you to further eliminate > if it's the console-vx or the COM board. > > Have you tried any other type of device on your serial connection? (to > eliminate a problem with your host PC). I had a pin break on one of my > laptops serial ports (fortunately it was still under warranty - they > had to replace the entire motherboard) and it caused intermittent > problems with my serial comms. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/change-uBoot-parameters-from-linux-tp27496466p27508701.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2010-02-09 02:14:26
|
Hi hypo, On Mon, Feb 8, 2010 at 4:31 PM, hypo <hyp...@gm...> wrote: > > hi Dave, > > i came across one of your older posts that talked about fw_printenv and > fw_setenv just before i hit the bed last night. i tried fw_printenv and it > printed out what i have in uboot currently (i have my verdex booting off NFS > and all settings printed out seemed to corroborate that), so i think it > should match it (fingers crossed). is there anyother way to see if it > matches the uboot version? > > Is there a help / documentation page for fw_printenv / fw_setenv? i didn't > want to run fw_setenv without knowing what it would do with no / default / > incorrect parameters. > >> Have you tried any other type of device on your serial connection? (to >> eliminate a problem with your host PC). I had a pin break on one of my >> laptops serial ports (fortunately it was still under warranty - they >> had to replace the entire motherboard) and it caused intermittent >> problems with my serial comms. >> > > yes, i used another ATMEL board on the same connection which works with the > same kermit settings, so i'm sure the problem is not with my Ubuntu machine > or the RS232/USB dongle, or with the cable. > > i will probably end up getting another console-vx board. in the interim, is > there a way to open a new serial terminal on one of the other ports without > going via UBOOT/fw_setenv? i tried: > > getty -L ttyS1 115200 vt100 > > and > > getty -L ttyS2 115200 vt100 > > but i still don't see anything on the other ports (i took care to move the > cable! :) Since your getty calls aren't working, I wouldn't risk trying mess with the u-boot environment, since you could brick your verdex. It's possible that the voltage regulator on the console-vx is dead. Does the power LED turn on? Actually, it looks like the power LED is on the input to the voltage regulator, not the output, so that doesn't tell us much. You'd need to check the VCC voltage on one of the connector spots (for example the square pad on the 6-pin STUART connector is ground, and the one beside it is VCC (3.3v) (same distance from the edge of the board as GND). If you've got no voltage - then you know the board is dead for sure. -- Dave Hylands Shuswap, BC, Canada http://www.DaveHylands.com/ |
From: hypo <hyp...@gm...> - 2010-02-13 21:30:00
|
Well, got my new console-vx board today and that's working splendidly. Still extremely puzzled as to what happened to the original board and concerned if that can happen to this one again and what i can do to prevent it. thanks for all your help Dave. cheers, hypo Dave Hylands wrote: > > Hi hypo, > > On Mon, Feb 8, 2010 at 4:31 PM, hypo <hyp...@gm...> wrote: >> >> hi Dave, >> >> i came across one of your older posts that talked about fw_printenv and >> fw_setenv just before i hit the bed last night. i tried fw_printenv and >> it >> printed out what i have in uboot currently (i have my verdex booting off >> NFS >> and all settings printed out seemed to corroborate that), so i think it >> should match it (fingers crossed). is there anyother way to see if it >> matches the uboot version? >> >> Is there a help / documentation page for fw_printenv / fw_setenv? i >> didn't >> want to run fw_setenv without knowing what it would do with no / default >> / >> incorrect parameters. >> >>> Have you tried any other type of device on your serial connection? (to >>> eliminate a problem with your host PC). I had a pin break on one of my >>> laptops serial ports (fortunately it was still under warranty - they >>> had to replace the entire motherboard) and it caused intermittent >>> problems with my serial comms. >>> >> >> yes, i used another ATMEL board on the same connection which works with >> the >> same kermit settings, so i'm sure the problem is not with my Ubuntu >> machine >> or the RS232/USB dongle, or with the cable. >> >> i will probably end up getting another console-vx board. in the interim, >> is >> there a way to open a new serial terminal on one of the other ports >> without >> going via UBOOT/fw_setenv? i tried: >> >> getty -L ttyS1 115200 vt100 >> >> and >> >> getty -L ttyS2 115200 vt100 >> >> but i still don't see anything on the other ports (i took care to move >> the >> cable! :) > > Since your getty calls aren't working, I wouldn't risk trying mess > with the u-boot environment, since you could brick your verdex. > > It's possible that the voltage regulator on the console-vx is dead. > Does the power LED turn on? > > Actually, it looks like the power LED is on the input to the voltage > regulator, not the output, so that doesn't tell us much. > > You'd need to check the VCC voltage on one of the connector spots (for > example the square pad on the 6-pin STUART connector is ground, and > the one beside it is VCC (3.3v) (same distance from the edge of the > board as GND). > > If you've got no voltage - then you know the board is dead for sure. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/change-uBoot-parameters-from-linux-tp27496466p27578876.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: hypo <hyp...@gm...> - 2010-02-09 03:07:03
|
> Since your getty calls aren't working, I wouldn't risk trying mess > with the u-boot environment, since you could brick your verdex. ok. i wasn't sure if i was using getty correctly or if i needed to load any modules or change any other variables or something in /etc or something else, before doing a getty would make sense. so ttyS1 / ttyS2 params were correct, i guess. (i took the getty command from /etc/inittab) > You'd need to check the VCC voltage on one of the connector spots (for > example the square pad on the 6-pin STUART connector is ground, and > the one beside it is VCC (3.3v) (same distance from the edge of the > board as GND). > If you've got no voltage - then you know the board is dead for sure. i'll check the voltages once i get home, but ya, the LED does light up for sure. in fact, i'm powering the Verdex via the console-vx, so at least that part is working, but i guess that doesn't tell us much. thanks, hypo Dave Hylands wrote: > > Hi hypo, > > On Mon, Feb 8, 2010 at 4:31 PM, hypo <hyp...@gm...> wrote: >> >> hi Dave, >> >> i came across one of your older posts that talked about fw_printenv and >> fw_setenv just before i hit the bed last night. i tried fw_printenv and >> it >> printed out what i have in uboot currently (i have my verdex booting off >> NFS >> and all settings printed out seemed to corroborate that), so i think it >> should match it (fingers crossed). is there anyother way to see if it >> matches the uboot version? >> >> Is there a help / documentation page for fw_printenv / fw_setenv? i >> didn't >> want to run fw_setenv without knowing what it would do with no / default >> / >> incorrect parameters. >> >>> Have you tried any other type of device on your serial connection? (to >>> eliminate a problem with your host PC). I had a pin break on one of my >>> laptops serial ports (fortunately it was still under warranty - they >>> had to replace the entire motherboard) and it caused intermittent >>> problems with my serial comms. >>> >> >> yes, i used another ATMEL board on the same connection which works with >> the >> same kermit settings, so i'm sure the problem is not with my Ubuntu >> machine >> or the RS232/USB dongle, or with the cable. >> >> i will probably end up getting another console-vx board. in the interim, >> is >> there a way to open a new serial terminal on one of the other ports >> without >> going via UBOOT/fw_setenv? i tried: >> >> getty -L ttyS1 115200 vt100 >> >> and >> >> getty -L ttyS2 115200 vt100 >> >> but i still don't see anything on the other ports (i took care to move >> the >> cable! :) > > Since your getty calls aren't working, I wouldn't risk trying mess > with the u-boot environment, since you could brick your verdex. > > It's possible that the voltage regulator on the console-vx is dead. > Does the power LED turn on? > > Actually, it looks like the power LED is on the input to the voltage > regulator, not the output, so that doesn't tell us much. > > You'd need to check the VCC voltage on one of the connector spots (for > example the square pad on the 6-pin STUART connector is ground, and > the one beside it is VCC (3.3v) (same distance from the edge of the > board as GND). > > If you've got no voltage - then you know the board is dead for sure. > > -- > Dave Hylands > Shuswap, BC, Canada > http://www.DaveHylands.com/ > > ------------------------------------------------------------------------------ > The Planet: dedicated and managed hosting, cloud storage, colocation > Stay online with enterprise data centers and the best network in the > business > Choose flexible plans and management services without long-term contracts > Personal 24x7 support from experience hosting pros just a phone call away. > http://p.sf.net/sfu/theplanet-com > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > -- View this message in context: http://old.nabble.com/change-uBoot-parameters-from-linux-tp27496466p27509860.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: hypo <hyp...@gm...> - 2010-02-11 12:09:23
|
i see the voltages and also can toggle the gpios, so i know the board isn't dead. hopefully it is a dry solder issue. anyways, i've ordered another console-vx board, so hopefully i'll find out soon. just wishing it isn't the verdex board. thanks, hypo hypo wrote: > >> Since your getty calls aren't working, I wouldn't risk trying mess >> with the u-boot environment, since you could brick your verdex. > > ok. i wasn't sure if i was using getty correctly or if i needed to load > any modules or change any other variables or something in /etc or > something else, before doing a getty would make sense. so ttyS1 / ttyS2 > params were correct, i guess. (i took the getty command from > /etc/inittab) > >> You'd need to check the VCC voltage on one of the connector spots (for >> example the square pad on the 6-pin STUART connector is ground, and >> the one beside it is VCC (3.3v) (same distance from the edge of the >> board as GND). >> If you've got no voltage - then you know the board is dead for sure. > > i'll check the voltages once i get home, but ya, the LED does light up for > sure. in fact, i'm powering the Verdex via the console-vx, so at least > that part is working, but i guess that doesn't tell us much. > > thanks, > hypo > > > Dave Hylands wrote: >> >> Hi hypo, >> >> On Mon, Feb 8, 2010 at 4:31 PM, hypo <hyp...@gm...> wrote: >>> >>> hi Dave, >>> >>> i came across one of your older posts that talked about fw_printenv and >>> fw_setenv just before i hit the bed last night. i tried fw_printenv and >>> it >>> printed out what i have in uboot currently (i have my verdex booting off >>> NFS >>> and all settings printed out seemed to corroborate that), so i think it >>> should match it (fingers crossed). is there anyother way to see if it >>> matches the uboot version? >>> >>> Is there a help / documentation page for fw_printenv / fw_setenv? i >>> didn't >>> want to run fw_setenv without knowing what it would do with no / default >>> / >>> incorrect parameters. >>> >>>> Have you tried any other type of device on your serial connection? (to >>>> eliminate a problem with your host PC). I had a pin break on one of my >>>> laptops serial ports (fortunately it was still under warranty - they >>>> had to replace the entire motherboard) and it caused intermittent >>>> problems with my serial comms. >>>> >>> >>> yes, i used another ATMEL board on the same connection which works with >>> the >>> same kermit settings, so i'm sure the problem is not with my Ubuntu >>> machine >>> or the RS232/USB dongle, or with the cable. >>> >>> i will probably end up getting another console-vx board. in the interim, >>> is >>> there a way to open a new serial terminal on one of the other ports >>> without >>> going via UBOOT/fw_setenv? i tried: >>> >>> getty -L ttyS1 115200 vt100 >>> >>> and >>> >>> getty -L ttyS2 115200 vt100 >>> >>> but i still don't see anything on the other ports (i took care to move >>> the >>> cable! :) >> >> Since your getty calls aren't working, I wouldn't risk trying mess >> with the u-boot environment, since you could brick your verdex. >> >> It's possible that the voltage regulator on the console-vx is dead. >> Does the power LED turn on? >> >> Actually, it looks like the power LED is on the input to the voltage >> regulator, not the output, so that doesn't tell us much. >> >> You'd need to check the VCC voltage on one of the connector spots (for >> example the square pad on the 6-pin STUART connector is ground, and >> the one beside it is VCC (3.3v) (same distance from the edge of the >> board as GND). >> >> If you've got no voltage - then you know the board is dead for sure. >> >> -- >> Dave Hylands >> Shuswap, BC, Canada >> http://www.DaveHylands.com/ >> >> ------------------------------------------------------------------------------ >> The Planet: dedicated and managed hosting, cloud storage, colocation >> Stay online with enterprise data centers and the best network in the >> business >> Choose flexible plans and management services without long-term contracts >> Personal 24x7 support from experience hosting pros just a phone call >> away. >> http://p.sf.net/sfu/theplanet-com >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> >> > > -- View this message in context: http://old.nabble.com/change-uBoot-parameters-from-linux-tp27496466p27544533.html Sent from the Gumstix mailing list archive at Nabble.com. |