From: Daniel F. <cyb...@cy...> - 2007-09-15 12:48:15
|
Hi folks. I have use the lcd gpio connectors on breakout-vx for IO operations. Unfortunately the default setup of the GPIO lines during bootup is causing my "relay" to cycle switch very fast until the system is fully booted and I have setup the lines correct. Is there a way to set the default mode of lines at build level, not in the u-boot setup. The lines in question are: GPIO58 : Mode OUT GPIO59 : Mode IN GPIO60 : Mode IN Please not that the board is already assembled without console access, so u-boot setup procedure is not an option. Thanks for your time. /Daniel Frederiksen |
From: Tim R. <gu...@ec...> - 2007-09-15 15:04:49
|
Hello I wonder if anyone can tell me what I'm doing wrong or if this is impossible: I'm trying to run a program that uses ttyS0 to communicate with a device (a mobile phone). So I am trying to disable the console on ttyS0 and load my program through a script in /etc/init.d In order to free ttyS0 I am using environment variables for u-boot: thusly bootargs=console=nulldev root=1f01 rootfstype=jffs2 reboot=cold,hard (to stop uboot sending junk to the phone) bootcmd=icache on; setenv stderr nulldev; setenv stdin nulldev; setenv stdout nulldev; katload 100000 && bootm; fi; fi; (to boot without using ttyS0) This seems to work: I am booting up and seeing no loading messages from linux or uboot and my program is sucessfully loading (I am debugging via audio). I can use my pc to debug the serial output, I can see the serial commands I want to send to the phone on my console. However, my program doesn't seem to be able to receive commands from ttyS0. I have tried typing the responses that the phone should send back, but my program doesn't respond. Is this completely mad? Is there some other step that needs to be taken to allow a program to receive data from ttyS0, is it being captured by a default login program? Thanks Tim Redfern |
From: Dave H. <dhy...@gm...> - 2007-09-15 23:22:07
|
Hi Tim, On 9/15/07, Tim Redfern <gu...@ec...> wrote: > Hello I wonder if anyone can tell me what I'm doing wrong or if this is > impossible: > > I'm trying to run a program that uses ttyS0 to communicate with a device > (a mobile phone). So I am trying to disable the console on ttyS0 and > load my program through a script in /etc/init.d > > In order to free ttyS0 I am using environment variables for u-boot: thusly > > bootargs=console=nulldev root=1f01 rootfstype=jffs2 reboot=cold,hard > (to stop uboot sending junk to the phone) > bootcmd=icache on; setenv stderr nulldev; setenv stdin nulldev; setenv > stdout nulldev; katload 100000 && bootm; fi; fi; > (to boot without using ttyS0) > > This seems to work: I am booting up and seeing no loading messages from > linux or uboot and my program is sucessfully loading (I am debugging via > audio). > > I can use my pc to debug the serial output, I can see the serial > commands I want to send to the phone on my console. However, my program > doesn't seem to be able to receive commands from ttyS0. I have tried > typing the responses that the phone should send back, but my program > doesn't respond. > > Is this completely mad? Is there some other step that needs to be taken > to allow a program to receive data from ttyS0, is it being captured by a > default login program? Did you comment out the call to getty on ttyS0 in the /etc/inittab file? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Black, M. <Michael.Black@EssexCorp.com> - 2007-09-16 12:42:57
|
I think you need to disable the getty in /etc/inittab Just comment out the ttyS0 line. # Put a getty on the serial port and vc1 null::respawn:/sbin/getty -L ttyS0 115200 vt100 null::respawn:/sbin/getty -L tty0 38400 linux ___________________ Michael D. Black Essex bl...@es... -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Tim Redfern Sent: Saturday, September 15, 2007 10:05 AM To: General mailing list for gumstix users. Subject: [Gumstix-users] using ttyS0 Hello I wonder if anyone can tell me what I'm doing wrong or if this is=20 impossible: I'm trying to run a program that uses ttyS0 to communicate with a device (a mobile phone). So I am trying to disable the console on ttyS0 and=20 load my program through a script in /etc/init.d In order to free ttyS0 I am using environment variables for u-boot: thusly bootargs=3Dconsole=3Dnulldev root=3D1f01 rootfstype=3Djffs2 = reboot=3Dcold,hard (to stop uboot sending junk to the phone) bootcmd=3Dicache on; setenv stderr nulldev; setenv stdin nulldev; setenv = stdout nulldev; katload 100000 && bootm; fi; fi; (to boot without using ttyS0) This seems to work: I am booting up and seeing no loading messages from=20 linux or uboot and my program is sucessfully loading (I am debugging via audio). I can use my pc to debug the serial output, I can see the serial=20 commands I want to send to the phone on my console. However, my program=20 doesn't seem to be able to receive commands from ttyS0. I have tried=20 typing the responses that the phone should send back, but my program=20 doesn't respond. Is this completely mad? Is there some other step that needs to be taken=20 to allow a program to receive data from ttyS0, is it being captured by a default login program? Thanks Tim Redfern ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users =20 =20 =20 =20 =20 =20 =20 This electronic message and any files transmitted with it contain = information which may be privileged and/or proprietary. The information = is intended for use solely by the intended recipient(s). If you are not = the intended recipient, be aware that any disclosure, copying, = distribution or use of this information is prohibited. If you have = received this electronic message in error, please advise the sender by = reply email or by telephone (301-939-7000) and delete the message. |
From: Tim R. <gu...@ec...> - 2007-09-16 13:31:24
|
Yup, I tried that, no joy. I think the problem stems from the fact that I used 'libserial' and had to cross compile it and install it manually, it must not be correctly installed. It is partly working though- it sends data but doesn't receive it- -which made me think it was a problem with access to ttyS0. Unfortunately I don't have time to wire up a 2nd serial port connector to test it. Has anyone ported libserial to gumstix? I used the commands from the example page thus: CC=arm-linux-gcc ./configure --host=arm-linux --build=x86-64-linux --prefix=/home/tim/libserial/build make install (my cross compiler toolchain is in my path) and then copied libserial.a, libserial.la and libserial.so.0.0.0 to /lib on the gumstix, remaking the softlinks to libserial.so and libserial.so.0 manually. libserial isn't giving any errors. hmm, I think I will compile a program that uses the serial ports more basically to test. Thanks, Tim > I think you need to disable the getty in /etc/inittab > Just comment out the ttyS0 line. > > # Put a getty on the serial port and vc1 > null::respawn:/sbin/getty -L ttyS0 115200 vt100 > null::respawn:/sbin/getty -L tty0 38400 linux > > ___________________ > Michael D. Black > Essex > bl...@es... > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Tim > Redfern > Sent: Saturday, September 15, 2007 10:05 AM > To: General mailing list for gumstix users. > Subject: [Gumstix-users] using ttyS0 > > Hello I wonder if anyone can tell me what I'm doing wrong or if this is > impossible: > > I'm trying to run a program that uses ttyS0 to communicate with a device > > (a mobile phone). So I am trying to disable the console on ttyS0 and > load my program through a script in /etc/init.d > > In order to free ttyS0 I am using environment variables for u-boot: > thusly > > bootargs=console=nulldev root=1f01 rootfstype=jffs2 reboot=cold,hard > (to stop uboot sending junk to the phone) > bootcmd=icache on; setenv stderr nulldev; setenv stdin nulldev; setenv > stdout nulldev; katload 100000 && bootm; fi; fi; > (to boot without using ttyS0) > > This seems to work: I am booting up and seeing no loading messages from > linux or uboot and my program is sucessfully loading (I am debugging via > > audio). > > I can use my pc to debug the serial output, I can see the serial > commands I want to send to the phone on my console. However, my program > doesn't seem to be able to receive commands from ttyS0. I have tried > typing the responses that the phone should send back, but my program > doesn't respond. > > Is this completely mad? Is there some other step that needs to be taken > to allow a program to receive data from ttyS0, is it being captured by a > > default login program? > > Thanks > > Tim Redfern > > |
From: Heilpern, M. <mar...@au...> - 2007-09-15 17:48:12
|
If I understand you correctly, you want the state of these pins to be to your needs on power-up, and you want a hardware change to cause this rather than software? You would have to convince Marvell to change the way their processor works to get that. There isn't a hardware build option to cause GPIOs to be configured one way or another; making a change in U-Boot is the best you will be able to do if you want to continue to use those specific GPIOs. To address your issue without replacing U-Boot, I would suggest moving your GPIOs. Find some pins that do not have an initial state of being output functions. Unless you can do that, you will have to replace U-Boot with a configuration that changes the pin programming to meet your needs; there still may be some chatter on the lines but at least you could keep it to a minimum. -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Daniel Frederiksen Sent: Saturday, September 15, 2007 8:48 AM To: gum...@li... Subject: [Gumstix-users] Default pxaregs? Hi folks. I have use the lcd gpio connectors on breakout-vx for IO operations.=20 Unfortunately the default setup of the GPIO lines during bootup is=20 causing my "relay" to cycle switch very fast until the system is fully=20 booted and I have setup the lines correct. Is there a way to set the=20 default mode of lines at build level, not in the u-boot setup. The lines in question are: GPIO58 : Mode OUT GPIO59 : Mode IN GPIO60 : Mode IN Please not that the board is already assembled without console access,=20 so u-boot setup procedure is not an option. Thanks for your time. /Daniel Frederiksen ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users NOTE: The information in this message is intended for the personal and = confidential use of the designated recipient(s) named above. To the extent the = recipient(s) is/are bound by a non-disclosure agreement, or other agreement that contains an = obligation of confidentiality, with AuthenTec, then this message and/or any = attachments shall be considered confidential information and subject to the confidentiality = terms of that agreement. If the reader of this message is not the intended recipient = named above, you are notified that you have received this document in error, and any = review, dissemination, distribution or copying of this message is strictly prohibited. If you = have received this document in error, please delete the original message and notify the = sender immediately. Thank you. AuthenTec, Inc. http://www.authentec.com |
From: Daniel F. <cyb...@cy...> - 2007-09-16 11:52:29
|
Hi Mark.. No I'm not requiring a hardware change, but perhaps there is a way to change the GPIO state like you do when interfacing a lcd. I would think a kernel parameter or environment setup in u-boot could setup up the lines. I'm looking for a way to reduce the "flicker" time on the relay. If I'm not mistaking you can replace u-boot without console access, I have done this before, so this is of course an option. But I I'm not familiar with the procedure of changing u-boot the environment during the build. Do you know where and how I change the lines in the u-boot configuration?. /Daniel Frederiksen Heilpern, Mark skrev: > If I understand you correctly, you want the state of these pins to be to > your needs on power-up, and you want a hardware change to cause this > rather than software? You would have to convince Marvell to change the > way their processor works to get that. There isn't a hardware build > option to cause GPIOs to be configured one way or another; making a > change in U-Boot is the best you will be able to do if you want to > continue to use those specific GPIOs. > > To address your issue without replacing U-Boot, I would suggest moving > your GPIOs. Find some pins that do not have an initial state of being > output functions. Unless you can do that, you will have to replace > U-Boot with a configuration that changes the pin programming to meet > your needs; there still may be some chatter on the lines but at least > you could keep it to a minimum. > > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Daniel > Frederiksen > Sent: Saturday, September 15, 2007 8:48 AM > To: gum...@li... > Subject: [Gumstix-users] Default pxaregs? > > Hi folks. > > I have use the lcd gpio connectors on breakout-vx for IO operations. > Unfortunately the default setup of the GPIO lines during bootup is > causing my "relay" to cycle switch very fast until the system is fully > booted and I have setup the lines correct. Is there a way to set the > default mode of lines at build level, not in the u-boot setup. > > The lines in question are: > GPIO58 : Mode OUT > GPIO59 : Mode IN > GPIO60 : Mode IN > > Please not that the board is already assembled without console access, > so u-boot setup procedure is not an option. > Thanks for your time. > > /Daniel Frederiksen > > ------------------------------------------------------------------------ > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > NOTE: The information in this message is intended for the personal and confidential use > of the designated recipient(s) named above. To the extent the recipient(s) is/are bound > by a non-disclosure agreement, or other agreement that contains an obligation of > confidentiality, with AuthenTec, then this message and/or any attachments shall be > considered confidential information and subject to the confidentiality terms of that > agreement. If the reader of this message is not the intended recipient named above, you > are notified that you have received this document in error, and any review, dissemination, > distribution or copying of this message is strictly prohibited. If you have received this > document in error, please delete the original message and notify the sender immediately. > Thank you. > > AuthenTec, Inc. http://www.authentec.com > > > |
From: DJ D. <dj...@de...> - 2007-09-16 16:22:24
|
If you can figure out how to change the uboot *environment* (not uboot itself) without a console, the magic settings you need are like this (these are from my furnace, which has to reset the sub-cpus asap): setenv reset_r8c "mw 40e00060 02a5a8aa;mw 40e00064 aaaaa800;mw 40e00010 3c12aa80;mw 40e00014 0001ffff;mw 40e0002c 0000001f;mw 40e0001c 20000000;mw 40e00020 0000001f" setenv linux "icache on; setenv stdout serial;setenv stderr serial;fsload && bootm" setenv bootcmd "run reset_r8c; run linux" Here's my cheat sheet for the various ports, you'll have to look up your specific needs: mw 40e00060 02a5a8aa # GPIO mode mw 40e00064 aaaaa800 # GPIO mode mw 40e00010 3c12aa80 # mode,mux addr = output mw 40e00014 0001ffff # resets = output mw 40e0002c 0000001f # resets = 0 mw 40e0001c 20000000 # mode = 1 mw 40e00020 0000001f # resets = 1 |
From: Dave H. <dhy...@gm...> - 2007-09-16 15:44:31
|
Hi Tim, > I think the problem stems from the fact that I used 'libserial' and had > to cross compile it and install it manually, it must not be correctly > installed. You can try sertest to see if that works. <http://docswiki.gumstix.com/Sample_code/C/Serial> If sertest works properly and your program with libserial doesn't, then that could indicate a problem with libserial. Did you disable flow control when you opened the serial port? -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Tim R. <gu...@ec...> - 2007-09-16 17:00:19
|
Hi Again ;-) > Hi Tim, > > >> I think the problem stems from the fact that I used 'libserial' and had >> to cross compile it and install it manually, it must not be correctly >> installed. >> > > You can try sertest to see if that works. > <http://docswiki.gumstix.com/Sample_code/C/Serial> > I have built an example from http://www.comptechdoc.org/os/linux/programming/c/linux_pgcserial.html and gotten it working, I conclude that the prob lem does lie with libserial. > If sertest works properly and your program with libserial doesn't, > then that could indicate a problem with libserial. > > Did you disable flow control when you opened the serial port? > No, but my old code works on linux on my laptop, I couldn't see any reason it would work differently on gumstix unless the library hadn't transated. Now <hurriedly> trying to convert my program to old-school termios stuff. Thanks again! Tim |