From: Bruno C. <bru...@gm...> - 2010-07-19 22:02:02
|
Hi, I've just got the Gumstix Overo Fire COM, and don't know nothing about it. I'm trying to read information from a barometric pressure sensor, from Sparkfun, that uses SPI interface: http://www.sparkfun.com/commerce/product_info.php?products_id=8161 I'd like to do a simple C program that reads information from this sensor, using Summit exapansion board, for example, and displays it. According to the sensor specification, it transmits 16 bit words, containing the register address in the first 6 bits, a bit that indicates read or write, a 0 bit for LSB, and finally 8 bits of data. I think pins from the sensor are conected to 40 pins' header, from expansion board. But I don't know how to access the value read from this pins. I found this sample code for PXA255 processor: http://docwiki.gumstix.org/Sample_code/C/SPI But I don't know what modifications I must do for my Overo Fire COM. How can I do that??? Please, help me. Thanks, Bruno Caetano. |
From: Dante S. <da...@ma...> - 2007-11-09 14:35:25
|
Hi, Could anyone tell me how I can connect a SPI device to my verdex+consolelcd assembly? I've seen the code for SPI in the wiki, but I don't know where I need to solder the wires...if that's possible at all with my stack. Thanks, Dante -- View this message in context: http://www.nabble.com/SPI-Interface-tf4777983.html#a13668009 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Heilpern, M. <mar...@au...> - 2007-11-09 15:56:24
|
The ConsoleLCD has 6 through-holes in an NSSP section (seen in the silkscreen). I don't have the pin assignments handy but the wiki should have them; the four signals are: VCC, GND, MISO, MOSI, FS, and CLK. Hope that's a useful pointer even though it's not complete info. -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dante Sanchez Sent: Friday, November 09, 2007 9:35 AM To: gum...@li... Subject: [Gumstix-users] SPI Interface Hi, Could anyone tell me how I can connect a SPI device to my verdex+consolelcd assembly? I've seen the code for SPI in the wiki, but I don't know where I need to solder the wires...if that's possible at all with my stack. Thanks, Dante --=20 View this message in context: http://www.nabble.com/SPI-Interface-tf4777983.html#a13668009 Sent from the Gumstix mailing list archive at Nabble.com. ------------------------------------------------------------------------ - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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: Dante S. <da...@ma...> - 2007-11-09 16:04:12
|
Heilpern, Mark wrote: > > The ConsoleLCD has 6 through-holes in an NSSP section (seen in the > silkscreen). I don't have the pin assignments handy but the wiki should > have them; the four signals are: VCC, GND, MISO, MOSI, FS, and CLK. Hope > that's a useful pointer even though it's not complete info. > Thanks Mark, I just wanted to make sure I didn't require a robostix on top of my configuration. I guess the next step is to look at the schematics and the spi sample program. Datne -- View this message in context: http://www.nabble.com/SPI-Interface-tf4777983.html#a13669917 Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dante S. <da...@ma...> - 2008-01-22 18:13:25
|
Dave Hylands wrote: > > > That code was written before the verdex existed, so it will > undoubtedly require a few tweaks. > > The data sheet is your friend... > > Thanks Dave, I've been reading up on the developer's manual for two days now...there's so much information! One thing I've noticed is this- the chart for the 60-pin connector in the Verdex only lists these SSP registers/GPIOs: GPIO(19) SSPSCLK2 GPIO(13) SSPTXD2 GPIO(14) SSPSFRM2 GPIO(11) SSPRXD2 >From what I saw in the developer's manual, there's three SSP ports available in the pxa270, and those GPIOs correspond to the 2nd port. Does that mean I can only use that port when tweaking the code? I don't care if this is a limitation, I just want to make sure I'm using the correct physical address. Thanks again, Dante -- View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15024580.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dante S. <da...@ma...> - 2008-01-23 14:52:58
|
Steve Sakoman wrote: > > > It seems that I turned off the spi module build at some point. I'll > fix that later tonight. > > To get support for more than 1 spi peripheral requires that you devote > additional gpio's for chip selects. So the answer depends on how many > free gpio's are available with the board set in your application. > > Hi Steve, I just started using OE yesterday. Did you have a chance to fix the SPI module? I've rebuilt the image with that "MACHINE FEATURES" line uncommented, but what's the next step? Am I supposed to use some sort of function listed somewhere? I don't know what's the equivalent of a open("/dev/ttyS0") command for SPI. Thank you, Dante -- View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15043380.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dante S. <da...@ma...> - 2008-01-23 16:02:13
|
Steve Sakoman wrote: > > I am far from an SPI expert. I suggest you start by reading the > documentation at: > > tmp/work/gumstix-custom-verdex-angstrom-linux-uclibcgnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21/Documentation/spi/ > > Also available online at: > > http://www.mjmwired.net/kernel/Documentation/spi/pxa2xx > Great, I'll go ahead and take a look at that. Steve Sakoman wrote: > > As Dave Hylands said, it would be very nice to have a spi-dev driver > available. I am not aware of anything like that though. > If I really knew about driver development I could work on something like that...any advice on references I can read? Thanks for the help, Dante -- View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15045216.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Heilpern, M. <mar...@au...> - 2008-01-23 18:23:45
|
Linux Device Drivers, Third Edition. Available free electronically: http://lwn.net/Kernel/LDD3/ -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dante Sanchez Sent: Wednesday, January 23, 2008 11:02 AM To: gum...@li... Subject: Re: [Gumstix-users] SPI Interface Steve Sakoman wrote: >=20 > I am far from an SPI expert. I suggest you start by reading the > documentation at: >=20 > tmp/work/gumstix-custom-verdex-angstrom-linux-uclibcgnueabi/gumstix-kern el-2.6.21-r1/linux-2.6.21/Documentation/spi/ >=20 > Also available online at: >=20 > http://www.mjmwired.net/kernel/Documentation/spi/pxa2xx >=20 Great, I'll go ahead and take a look at that. Steve Sakoman wrote: >=20 > As Dave Hylands said, it would be very nice to have a spi-dev driver > available. I am not aware of anything like that though. >=20 If I really knew about driver development I could work on something like that...any advice on references I can read? Thanks for the help, Dante --=20 View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15045216.html Sent from the Gumstix mailing list archive at Nabble.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 gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users NOTE: The information in this message is intended for the personal and conf= idential 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 notifie= d that you have received this document in error, and any review, disseminat= ion, distribution or copying of this message is strictly prohibited. If you= have received this document in error, please delete the original message a= nd notify the sender immediately. =0D =0D Thank you.=0D =0D AuthenTec, Inc. http://www.authentec.com=0D |
From: Dante S. <da...@ma...> - 2008-01-22 17:05:31
|
Heilpern, Mark wrote: > > The ConsoleLCD has 6 through-holes in an NSSP section (seen in the > silkscreen). I don't have the pin assignments handy but the wiki should > have them; the four signals are: VCC, GND, MISO, MOSI, FS, and CLK. Hope > that's a useful pointer even though it's not complete info. > I've located the signals in the board now, but I've looked at the sample code for the pxa255 in the Gumstix wiki and some of the registers listed are not in the pxa270 developer's manual. Does anyone know how I can modify that SPI sample code to be able to use it in my Verdex/ConsoleLCD stack? Thank you, Dante -- View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15023066.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Dave H. <dhy...@gm...> - 2008-01-22 17:58:50
|
Hi Dante, > Does anyone know how I can modify that SPI sample code to be able to use it > in my Verdex/ConsoleLCD stack? That code was written before the verdex existed, so it will undoubtedly require a few tweaks. The data sheet is your friend... -- Dave Hylands Vancouver, BC, Canada http://www.DaveHylands.com/ |
From: Heilpern, M. <mar...@au...> - 2008-01-22 20:53:09
|
If you're accessing SPI from a kernel module, I suggest enabling the PXA-2xx SPI support (which is not trivial to figure out how to enable, but search this mailing list for "PXA_SSP" for messages detailing it). Then you'll have a number of functions (source in arch/arm/mach-pxa/ssp.c in your linux source tree) which will remove the direct register access requirement from your code. The PXA manual you've got will still come in handy as though your code won't directly poke the registers (ssp.c will do that for you), you'll still need to know what values to put in them. If you're trying to access things from application space, ssp.c can still serve as a useful guide. -----Original Message----- From: gum...@li... [mailto:gum...@li...] On Behalf Of Dante Sanchez Sent: Tuesday, January 22, 2008 1:13 PM To: gum...@li... Subject: Re: [Gumstix-users] SPI Interface Dave Hylands wrote: >=20 >=20 > That code was written before the verdex existed, so it will > undoubtedly require a few tweaks. >=20 > The data sheet is your friend... >=20 >=20 Thanks Dave, I've been reading up on the developer's manual for two days now...there's so much information! One thing I've noticed is this- the chart for the 60-pin connector in the Verdex only lists these SSP registers/GPIOs: GPIO(19) SSPSCLK2 GPIO(13) SSPTXD2 GPIO(14) SSPSFRM2 GPIO(11) SSPRXD2 >From what I saw in the developer's manual, there's three SSP ports available in the pxa270, and those GPIOs correspond to the 2nd port. Does that mean I can only use that port when tweaking the code? I don't care if this is a limitation, I just want to make sure I'm using the correct physical address. Thanks again, Dante --=20 View this message in context: http://www.nabble.com/SPI-Interface-tp13668009p15024580.html Sent from the Gumstix mailing list archive at Nabble.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 gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users NOTE: The information in this message is intended for the personal and conf= idential 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 notifie= d that you have received this document in error, and any review, disseminat= ion, distribution or copying of this message is strictly prohibited. If you= have received this document in error, please delete the original message a= nd notify the sender immediately. =0D =0D Thank you.=0D =0D AuthenTec, Inc. http://www.authentec.com=0D |
From: Steve S. <sa...@gm...> - 2008-01-22 22:11:52
|
For those using gumstix-oe, including the spi kernel module is fairly trivial. Just edit your gumstix-custom-verdex.conf file and uncomment this line: #MACHINE_FEATURES += "spi" This will install the spi driver in your image. It will not autoload the module. I believe it is best for each developer to chose when/how to modprobe the module depending on the needs of their spi peripheral hw. Steve On Jan 22, 2008 12:53 PM, Heilpern, Mark <mar...@au...> wrote: > If you're accessing SPI from a kernel module, I suggest enabling the > PXA-2xx SPI support (which is not trivial to figure out how to enable, > but search this mailing list for "PXA_SSP" for messages detailing it). > Then you'll have a number of functions (source in > arch/arm/mach-pxa/ssp.c in your linux source tree) which will remove the > direct register access requirement from your code. The PXA manual you've > got will still come in handy as though your code won't directly poke the > registers (ssp.c will do that for you), you'll still need to know what > values to put in them. > > If you're trying to access things from application space, ssp.c can > still serve as a useful guide. > > > > -----Original Message----- > From: gum...@li... > [mailto:gum...@li...] On Behalf Of Dante > Sanchez > > Sent: Tuesday, January 22, 2008 1:13 PM > To: gum...@li... > Subject: Re: [Gumstix-users] SPI Interface > > > > Dave Hylands wrote: > > > > > > That code was written before the verdex existed, so it will > > undoubtedly require a few tweaks. > > > > The data sheet is your friend... > > > > > > Thanks Dave, I've been reading up on the developer's manual for two days > now...there's so much information! > > One thing I've noticed is this- the chart for the 60-pin connector in > the > Verdex only lists these SSP registers/GPIOs: > GPIO(19) SSPSCLK2 > GPIO(13) SSPTXD2 > GPIO(14) SSPSFRM2 > GPIO(11) SSPRXD2 > > >From what I saw in the developer's manual, there's three SSP ports > available > in the pxa270, and those GPIOs correspond to the 2nd port. Does that > mean I > can only use that port when tweaking the code? I don't care if this is a > limitation, I just want to make sure I'm using the correct physical > address. > > Thanks again, > > Dante > -- > View this message in context: > http://www.nabble.com/SPI-Interface-tp13668009p15024580.html > Sent from the Gumstix mailing list archive at Nabble.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 > 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 > > > > ------------------------------------------------------------------------- > 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 > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ryan R. <rjr...@uc...> - 2008-01-22 23:42:14
|
Steve- sorry to threadjack, but does that give you /dev/spi0 or something of the sort? How many peripherals does this support? Ryan On Tue, 2008-01-22 at 14:11 -0800, Steve Sakoman wrote: > For those using gumstix-oe, including the spi kernel module is fairly > trivial. Just edit your gumstix-custom-verdex.conf file and uncomment > this line: > > #MACHINE_FEATURES += "spi" > > This will install the spi driver in your image. It will not autoload > the module. I believe it is best for each developer to chose when/how > to modprobe the module depending on the needs of their spi peripheral > hw. > > Steve > > On Jan 22, 2008 12:53 PM, Heilpern, Mark <mar...@au...> wrote: > > If you're accessing SPI from a kernel module, I suggest enabling the > > PXA-2xx SPI support (which is not trivial to figure out how to enable, > > but search this mailing list for "PXA_SSP" for messages detailing it). > > Then you'll have a number of functions (source in > > arch/arm/mach-pxa/ssp.c in your linux source tree) which will remove the > > direct register access requirement from your code. The PXA manual you've > > got will still come in handy as though your code won't directly poke the > > registers (ssp.c will do that for you), you'll still need to know what > > values to put in them. > > > > If you're trying to access things from application space, ssp.c can > > still serve as a useful guide. > > > > > > > > -----Original Message----- > > From: gum...@li... > > [mailto:gum...@li...] On Behalf Of Dante > > Sanchez > > > > Sent: Tuesday, January 22, 2008 1:13 PM > > To: gum...@li... > > Subject: Re: [Gumstix-users] SPI Interface > > > > > > > > Dave Hylands wrote: > > > > > > > > > That code was written before the verdex existed, so it will > > > undoubtedly require a few tweaks. > > > > > > The data sheet is your friend... > > > > > > > > > > Thanks Dave, I've been reading up on the developer's manual for two days > > now...there's so much information! > > > > One thing I've noticed is this- the chart for the 60-pin connector in > > the > > Verdex only lists these SSP registers/GPIOs: > > GPIO(19) SSPSCLK2 > > GPIO(13) SSPTXD2 > > GPIO(14) SSPSFRM2 > > GPIO(11) SSPRXD2 > > > > >From what I saw in the developer's manual, there's three SSP ports > > available > > in the pxa270, and those GPIOs correspond to the 2nd port. Does that > > mean I > > can only use that port when tweaking the code? I don't care if this is a > > limitation, I just want to make sure I'm using the correct physical > > address. > > > > Thanks again, > > > > Dante > > -- > > View this message in context: > > http://www.nabble.com/SPI-Interface-tp13668009p15024580.html > > Sent from the Gumstix mailing list archive at Nabble.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 > > 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 > > > > > > > > ------------------------------------------------------------------------- > > 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 > > gum...@li... > > 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 > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Steve S. <sa...@gm...> - 2008-01-23 00:10:09
|
Ryan, > does that give you /dev/spi0 or something of the sort? When I went to check this for you I discovered that the spi module wasn't there! That will teach me not to speak too quickly :-) It seems that I turned off the spi module build at some point. I'll fix that later tonight. To get support for more than 1 spi peripheral requires that you devote additional gpio's for chip selects. So the answer depends on how many free gpio's are available with the board set in your application. Steve On Jan 22, 2008 3:42 PM, Ryan Rapetti <rjr...@uc...> wrote: > Steve- sorry to threadjack, but does that give you /dev/spi0 or > something of the sort? How many peripherals does this support? > > Ryan > > > On Tue, 2008-01-22 at 14:11 -0800, Steve Sakoman wrote: > > For those using gumstix-oe, including the spi kernel module is fairly > > trivial. Just edit your gumstix-custom-verdex.conf file and uncomment > > this line: > > > > #MACHINE_FEATURES += "spi" > > > > This will install the spi driver in your image. It will not autoload > > the module. I believe it is best for each developer to chose when/how > > to modprobe the module depending on the needs of their spi peripheral > > hw. > > > > Steve > > > > On Jan 22, 2008 12:53 PM, Heilpern, Mark <mar...@au...> wrote: > > > If you're accessing SPI from a kernel module, I suggest enabling the > > > PXA-2xx SPI support (which is not trivial to figure out how to enable, > > > but search this mailing list for "PXA_SSP" for messages detailing it). > > > Then you'll have a number of functions (source in > > > arch/arm/mach-pxa/ssp.c in your linux source tree) which will remove the > > > direct register access requirement from your code. The PXA manual you've > > > got will still come in handy as though your code won't directly poke the > > > registers (ssp.c will do that for you), you'll still need to know what > > > values to put in them. > > > > > > If you're trying to access things from application space, ssp.c can > > > still serve as a useful guide. > > > > > > > > > > > > -----Original Message----- > > > From: gum...@li... > > > [mailto:gum...@li...] On Behalf Of Dante > > > Sanchez > > > > > > Sent: Tuesday, January 22, 2008 1:13 PM > > > To: gum...@li... > > > Subject: Re: [Gumstix-users] SPI Interface > > > > > > > > > > > > Dave Hylands wrote: > > > > > > > > > > > > That code was written before the verdex existed, so it will > > > > undoubtedly require a few tweaks. > > > > > > > > The data sheet is your friend... > > > > > > > > > > > > > > Thanks Dave, I've been reading up on the developer's manual for two days > > > now...there's so much information! > > > > > > One thing I've noticed is this- the chart for the 60-pin connector in > > > the > > > Verdex only lists these SSP registers/GPIOs: > > > GPIO(19) SSPSCLK2 > > > GPIO(13) SSPTXD2 > > > GPIO(14) SSPSFRM2 > > > GPIO(11) SSPRXD2 > > > > > > >From what I saw in the developer's manual, there's three SSP ports > > > available > > > in the pxa270, and those GPIOs correspond to the 2nd port. Does that > > > mean I > > > can only use that port when tweaking the code? I don't care if this is a > > > limitation, I just want to make sure I'm using the correct physical > > > address. > > > > > > Thanks again, > > > > > > Dante > > > -- > > > View this message in context: > > > http://www.nabble.com/SPI-Interface-tp13668009p15024580.html > > > Sent from the Gumstix mailing list archive at Nabble.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 > > > 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 > > > > > > > > > > > > ------------------------------------------------------------------------- > > > 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 > > > gum...@li... > > > 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 > > gum...@li... > > 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 > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Steve S. <sa...@gm...> - 2008-01-23 15:41:52
|
On Jan 23, 2008 6:52 AM, Dante Sanchez <da...@ma...> wrote: > I just started using OE yesterday. Did you have a chance to fix the SPI > module? Yes, it is built by default starting in revision 155. > I've rebuilt the image with that "MACHINE FEATURES" line uncommented, but > what's the next step? I am far from an SPI expert. I suggest you start by reading the documentation at: tmp/work/gumstix-custom-verdex-angstrom-linux-uclibcgnueabi/gumstix-kernel-2.6.21-r1/linux-2.6.21/Documentation/spi/ Also available online at: http://www.mjmwired.net/kernel/Documentation/spi/pxa2xx I do know that the spi driver interface isn't particularly "friendly", so be prepared for some real work to use it. As Dave Hylands said, it would be very nice to have a spi-dev driver available. I am not aware of anything like that though. Steve |
From: Victhor <vic...@gm...> - 2010-07-19 22:13:22
|
If that sensor doesn't run at 1.8V there's a great chance that you may have ruined your board. Also, SPI needs some modifications to the kernel to work with other devices that's not the ADS7846 resistive touchscreen controller on the Palo35, Palo43 and Chestnut43 expansion boards, it seems. > Hi, > > I've just got the Gumstix Overo Fire COM, and don't know nothing about > it. I'm trying to read information from a barometric pressure sensor, > from Sparkfun, that uses SPI interface: > http://www.sparkfun.com/commerce/product_info.php?products_id=8161 > > I'd like to do a simple C program that reads information from this > sensor, using Summit exapansion board, for example, and displays it. > According to the sensor specification, it transmits 16 bit words, > containing the register address in the first 6 bits, a bit that > indicates read or write, a 0 bit for LSB, and finally 8 bits of data. > I think pins from the sensor are conected to 40 pins' header, from > expansion board. But I don't know how to access the value read from > this pins. > > I found this sample code for PXA255 processor: > http://docwiki.gumstix.org/Sample_code/C/SPI > > But I don't know what modifications I must do for my Overo Fire COM. > How can I do that??? > > Please, help me. > Thanks, > > Bruno Caetano. > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ gumstix-users mailing list gum...@li... https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Andrew K. (m. l. account) <ak...@mi...> - 2010-07-19 22:31:55
|
On Monday, July 19, 2010 06:13:07 pm Victhor wrote: > If that sensor doesn't run at 1.8V there's a great chance that you may > have ruined your board. Also, SPI needs some modifications to the kernel > to work with other devices that's not the ADS7846 resistive touchscreen > controller on the Palo35, Palo43 and Chestnut43 expansion boards, it > seems. What are the modifications that need to be done? I have an ethernet switch IC that I'd like to talk to over the SPI interface (I do have level translators in the circuit). Do you have links or other information about modifying the kernel for the SPI interface on the Overo? -A. |
From: Victhor <vic...@gm...> - 2010-07-19 22:42:35
|
I don't know what modifications are necessary, but they are around the mailing list IIRC. You only need a logic level converter to use SPI devices that don't run at 1.8V. > On Monday, July 19, 2010 06:13:07 pm Victhor wrote: > > If that sensor doesn't run at 1.8V there's a great chance that you may > > have ruined your board. Also, SPI needs some modifications to the kernel > > to work with other devices that's not the ADS7846 resistive touchscreen > > controller on the Palo35, Palo43 and Chestnut43 expansion boards, it > > seems. > > What are the modifications that need to be done? I have an ethernet switch IC > that I'd like to talk to over the SPI interface (I do have level translators > in the circuit). > > Do you have links or other information about modifying the kernel for the SPI > interface on the Overo? > > -A. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Mannissa C. <man...@gm...> - 2010-07-19 22:55:38
|
I'm connecting a DAC (runs at more than 1.8V) to the SPI bus and I'm using a cheap level shifter. I've posted on a recent thread related to this. (my post is shown below) You can get cheap level shifters. This is the one I'm using: http://www.datasheetcatalog.org/datasheet/motorola/MC14504BCL.pdf You can simply place it on a breadboard, and the wiring is pretty simple from there. Take a look at the link to the data sheet I provided above. FYI: I bought mine for less than a dollar. :) Good luck! Victhor wrote: > I don't know what modifications are necessary, but they are around the > mailing list IIRC. You only need a logic level converter to use SPI > devices that don't run at 1.8V. > >> On Monday, July 19, 2010 06:13:07 pm Victhor wrote: >> >>> If that sensor doesn't run at 1.8V there's a great chance that you may >>> have ruined your board. Also, SPI needs some modifications to the kernel >>> to work with other devices that's not the ADS7846 resistive touchscreen >>> controller on the Palo35, Palo43 and Chestnut43 expansion boards, it >>> seems. >>> >> What are the modifications that need to be done? I have an ethernet switch IC >> that I'd like to talk to over the SPI interface (I do have level translators >> in the circuit). >> >> Do you have links or other information about modifying the kernel for the SPI >> interface on the Overo? >> >> -A. >> >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by Sprint >> What will you do first with EVO, the first 4G phone? >> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |