|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
|
|
24-pin verdex connector and GPIO problemHello all,
I am using the 24-pin connector on my verdex board for GPIO. I only need to set a few lines high or low to activate/deactivate some fiber optic switches. After my verdex boots up (OE build), and I run my application, I send a command to the GPIO to set the switches low: I write to /proc/gpio/GPIO88 and send "GPIO out clear". The problem arises the first time the app tries to set the line high ("GPIO out set") - the output flickers, or quickly toggles, and my fiber optic switches don't like that. I hooked up the serial port ttyS0 on the verdex to hyperterminal on another laptop, and it get's the following messages while the GPIO line is flickering: usb 1-1: device descriptor read/64, error -62 usb 1-1: device descriptor read/64, error -62 usb 1-1: new low speed USB device using pxa27x-ohci and address 4 usb 1-1: device descriptor read/64, error -62 usb 1-1: device descriptor read/64, error -62 usb 1-1: new low speed USB device using pxa27x-ohci and address 5 usb 1-1: device not accepting address 5, error -62 usb 1-1: new low speed USB device using pxa27x-ohci and address 6 usb 1-1: device not accepting address 6, error -62 After this initial reaction, the GPIO line can be set and cleared without any further trouble. The GPIO line I am using is GPIO88, which is incidentally the USBH_PWR1 signal on the 24-pin connector. Is there anyway to disable the verdex from wanting to look for a usb device on the 24-pin connector? I am using the other USB connector for a keypad matrix, so I don't want to disable USB altogether, just for the 24-pin connector. Any ideas? ALSO... (maybe this should be another topic) I am using all three serial ports available on my consoleLCD-vx board to communicate with three fiber optic attenuators. The attenuator connected to ttyS0 is always being sent useless information (such as the above usb messages), and bootup and reboot messages. Is there a way to stop the messages from being sent over ttyS0? I think the verdex thinks a terminal window or console is hooked up to ttyS0, but it's not the case. I have the Samsung LCS hooked up, so there is no need to have the ttyS0 connected to anything other than my attenuators. Any ideas? Thanks for your suggestions in advance, Lance Naval Surface Warfare Center Corona Division ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
|
|
|
Re: FW: 24-pin verdex connector and GPIO problemNo ideas on the first topic, but it is possible to pass a silent option
to the kernel, and I think you can fiddle with uboot to shut it up too. Then you'd have to play with all the startup scripts to quiet them down too. The basic idea, iirc, is to tell Linux that you want to use /dev/null as the terminal. Try searching the message archives, I know it's come up in the past. Doddridge, Lance S CIV NSWC Corona, MS32 wrote: > BUMPED FROM LAST WEEK, ON FRIDAY... > > > Hello all, > > I am using the 24-pin connector on my verdex board for GPIO. I only > need to set a few lines high or low to activate/deactivate some fiber > optic switches. After my verdex boots up (OE build), and I run my > application, I send a command to the GPIO to set the switches low: I > write to /proc/gpio/GPIO88 and send "GPIO out clear". The problem > arises the first time the app tries to set the line high ("GPIO out > set") - the output flickers, or quickly toggles, and my fiber optic > switches don't like that. I hooked up the serial port ttyS0 on the > verdex to hyperterminal on another laptop, and it get's the following > messages while the GPIO line is flickering: > > > usb 1-1: device descriptor read/64, error -62 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 4 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 5 > usb 1-1: device not accepting address 5, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 6 > usb 1-1: device not accepting address 6, error -62 > > > After this initial reaction, the GPIO line can be set and cleared > without any further trouble. The GPIO line I am using is GPIO88, which > is incidentally the USBH_PWR1 signal on the 24-pin connector. Is there > anyway to disable the verdex from wanting to look for a usb device on > the 24-pin connector? I am using the other USB connector for a keypad > matrix, so I don't want to disable USB altogether, just for the 24-pin > connector. Any ideas? > > > ALSO... (maybe this should be another topic) > I am using all three serial ports available on my consoleLCD-vx board to > communicate with three fiber optic attenuators. The attenuator > connected to ttyS0 is always being sent useless information (such as the > above usb messages), and bootup and reboot messages. Is there a way to > stop the messages from being sent over ttyS0? I think the verdex thinks > a terminal window or console is hooked up to ttyS0, but it's not the > case. I have the Samsung LCS hooked up, so there is no need to have the > ttyS0 connected to anything other than my attenuators. Any ideas? > > Thanks for your suggestions in advance, > Lance > Naval Surface Warfare Center Corona Division > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > gumstix-users mailing list > gumstix-users@... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
|
|
Re: FW: 24-pin verdex connector and GPIO problemHi Lance,
> I am using the 24-pin connector on my verdex board for GPIO. I only > need to set a few lines high or low to activate/deactivate some fiber > optic switches. After my verdex boots up (OE build), and I run my > application, I send a command to the GPIO to set the switches low: I > write to /proc/gpio/GPIO88 and send "GPIO out clear". The problem > arises the first time the app tries to set the line high ("GPIO out > set") - the output flickers, or quickly toggles, and my fiber optic > switches don't like that. I hooked up the serial port ttyS0 on the > verdex to hyperterminal on another laptop, and it get's the following > messages while the GPIO line is flickering: > > > usb 1-1: device descriptor read/64, error -62 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 4 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: device descriptor read/64, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 5 > usb 1-1: device not accepting address 5, error -62 > usb 1-1: new low speed USB device using pxa27x-ohci and address 6 > usb 1-1: device not accepting address 6, error -62 > > > After this initial reaction, the GPIO line can be set and cleared > without any further trouble. The GPIO line I am using is GPIO88, which > is incidentally the USBH_PWR1 signal on the 24-pin connector. Is there > anyway to disable the verdex from wanting to look for a usb device on > the 24-pin connector? I am using the other USB connector for a keypad > matrix, so I don't want to disable USB altogether, just for the 24-pin > connector. Any ideas? I think that you can tweak the gumstix_ohci_init function in the arch/arm/mach-pxa/gumstix.c file. By default it seems to enable port 2. -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ gumstix-users mailing list gumstix-users@... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
| Free Forum Powered by Nabble | Forum Help |