gumstix

Ok. I got the schematic printed out and in front of me and I think I've
figured out why the colors don't come out right with your consoleLCD-vx.
Here is the relevant excerpt from pxa-regs.h:

#define GPIO58_LDD_0		58	/* LCD data pin 0 */
#define GPIO59_LDD_1		59	/* LCD data pin 1 */
#define GPIO60_LDD_2		60	/* LCD data pin 2 */
#define GPIO61_LDD_3		61	/* LCD data pin 3 */
#define GPIO62_LDD_4		62	/* LCD data pin 4 */
#define GPIO63_LDD_5		63	/* LCD data pin 5 */
#define GPIO64_LDD_6		64	/* LCD data pin 6 */
#define GPIO65_LDD_7		65	/* LCD data pin 7 */
#define GPIO66_LDD_8		66	/* LCD data pin 8 */
#define GPIO66_MBREQ		66	/* alternate bus master req */
#define GPIO67_LDD_9		67	/* LCD data pin 9 */
#define GPIO67_MMCCS0		67	/* MMC Chip Select 0 */
#define GPIO68_LDD_10		68	/* LCD data pin 10 */
#define GPIO68_MMCCS1		68	/* MMC Chip Select 1 */
#define GPIO69_LDD_11		69	/* LCD data pin 11 */
#define GPIO69_MMCCLK		69	/* MMC_CLK */
#define GPIO70_LDD_12		70	/* LCD data pin 12 */
#define GPIO70_RTCCLK		70	/* Real Time clock (1 Hz) */
#define GPIO71_LDD_13		71	/* LCD data pin 13 */
#define GPIO71_3_6MHz		71	/* 3.6 MHz Oscillator clock */
#define GPIO72_LDD_14		72	/* LCD data pin 14 */
#define GPIO72_32kHz		72	/* 32 kHz clock */
#define GPIO73_LDD_15		73	/* LCD data pin 15 */

Notice there is no definition for LDD_16 and LDD_17 (which you *do* have
routed from the LCD). If I'm not mistaken, these are also the 2 most
significant red bits? In the pxafb.c source in the linux-2.6.21gum, the
framebuffer is set up in 5-6-5 format (not 666). This throws the entire
palette off as you might imagine. I have found patches for my pxafb.c,
pxafb.h, and pxa-regs.h, but I thought you might want to have a look at
this.

Let me know what you decide here.. I'm not sure what to do about adding
LDD_16 & LDD_17 to pxa-regs.h.

thanks,
Erick
-- 
View this message in context: http://www.nabble.com/ConsoleLCDvx-problems---LDD_16---LDD_17-gone-tf4693350.html#a13415052
Sent from the Gumstix mailing list archive at Nabble.com.

Does anyone know how to include the ZD1211RW drivers in the build.  I
know that it is available I just can't see it on any of the menuconfig's

I have spent the last few days trying to get the RT73 Ralink drivers
working with this card.

At this moment the card is recognized on the gumstix, however it doesn't
allow me to scan, for that matter list is frequencies.

Any help is greatly appreciated, and that you for every one that has
already helped.

Vincent Costagliola

Thought I'd bring your attention to the new verdex-based gum packs. They are available in our on-line store:

http://www.gumstix.com/spexBundles.html




Don


====================================================================

Don Anderson		http://www.gumstix.com

====================================================================
--

Hello,

I've had this problem for awhile, and I can't seem to fix it ... any
help or direction would be greatly appreciated.

I need to set the baud rate of /dev/ttyS2 to 28800

stty -F /dev/ttyS2 28800 does not work because it is not on the list
of approved baud rates.

setserial also does not work for /dev/ttyS2

# setserial /dev/ttyS2 spd_cust divisor 32
Cannot set serial info: Invalid argument

more info:

# setserial -a /dev/ttyS2
/dev/ttyS2, Line 2, UART: undefined, Port: 0x0000, IRQ: 13
        Baud_base: 921600, close_delay: 50, divisor: 0
        closing_wait: 3000
        Flags: spd_normal

# more /proc/tty/driver/PXA\ serial
serinfo:1.0 driver revision:
0: uart:FFUART mmio:0x40100000 irq:15 tx:836 rx:0 RTS|CTS|DTR|DSR|CD|RI
1: uart:BTUART mmio:0x40200000 irq:14 tx:0 rx:1 brk:1 CTS
2: uart:STUART mmio:0x40700000 irq:13 tx:0 rx:0
3: uart:HWUART mmio:0x41600000 irq:0 tx:0 rx:0

# cat /proc/gpio/GPIO4[6789]
46      AF2     in      set
47      AF1     out     set
48      AF2     out     set
49      AF2     out     set


Please any help would be greatly appreciated!!!

Thank you!
Eric

Ong Si Hong,

You will find how to compile the video4linux drivers into the linux kernel
at this page from the mailing list:
http://article.gmane.org/gmane.linux.distributions.gumstix.general/26310/match=video

Neil Johnson


If I need to use a webcam, do I need to install video4linux or will it be
installed when I install gspca? Where can I download video4linux from?
-- 
View this message in context: http://www.nabble.com/Re%3A-Buildroot-tf3790019.html#a13412769
Sent from the Gumstix mailing list archive at Nabble.com.

Does anyone know how to change the default speed of the Gumstix I2C bus 
from 400KHz down to 100KHz.  i.e down form its normal fast mode to the 
slower standard mode?

 From the I2C spec. It implies that all devices will work at the lower 
speed.  However IF the master is running at 400KHz and you have a slow 
100KHZ slave on the bus (that isnt capable of 400KHz) then you can't 
communicate with it.

I have one such device and need to change the speed of the Master 
(Gumstix) to 100KHz.

I have checked over the wiki and the only info I can get is:


      I2C

    * The I2C unit supports a fast mode operation of 400 Kbits/sec and a
      standard mode of 100 Kbits/sec. Refer to I2C bus specification
      <http://www.semiconductors.philips.com/acrobat/literature/9398/39340011.pdf>
      for details.

Note the I2C on the Gumstix 
<http://docwiki.gumstix.org/I2C_on_the_Gumstix> page.

Not much help!  Any one come across how to do this?

Neil




--  
This message (and any attachments) is for the recipient only.  NERC is subject
to the Freedom of Information Act 2000 and the contents of this email and any
reply you make may be disclosed by NERC unless it is exempt from release under
the Act.  Any material supplied to NERC may be stored in an electronic
records management system.

Should this break ssh connectivity from a host?

On 10/23/07, Rasmus Kjeldsen <rasmus.kjeldsen@...> wrote:
> Hi Richard
>
> I dont know if my sftp-patches has been included in the buildroot yet, but
> otherwise you can get buildroot packages for dropbear and openssh from:
> http://razzle.dk/gumstix/package/
> Read the readme.txt for a short explanation.
> Openssh needs to be compiled to provide the needed sftp-server binary.
>
> Cheers
> Rasmus
>
> 2007/10/23, Richard Boyd < rlboyd@...>:
> >
> > Does anyone know if sftp should be functional in buildroot with
> > dropbear? I saw a few threads about it but it was not clear if the
> > changes ever got incorporated?
> >
> > If they did can someone drop a line or two on what needs to be added
> > to the build to make this work? Does openSSH need to be included?
> >
> > Regards,
> >
> > Richard
> >
> >
> -------------------------------------------------------------------------
> > 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
> > gumstix-users@...
> >
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> >
>
>
> -------------------------------------------------------------------------
> 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
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>

> I'm running into the same problem when issuing the mount command for an 
> NFS volume (bad file descriptor).   I've tried playing with options for 
> tcp, udp, and block size without success.  I know my server and kernel 
> are configured properly because I can boot the system with the root file 
> system on NFS.  I can even successfully mount a Windows CIFS drive. The 
> limited debug I've done leads me to think that the NFS mount problem is 
> in a call to uclibc.  If you have nfs mounts working, please post the 
> version of uclibc you are using.
>
> regards,
> frank
>
>> Craig Hughes wrote:
>> Try using NFS over TCP instead of UDP.
>> 
>> C
>> 
>> On Sep 2, 2007, at 11:56 PM, Petr Palacký wrote:
>> 
>>> Hi Craig,
>>>
>>> yes, I'm able to ping NFS server, I can connect via SSH to the NFS  
>>> server and
>>> I'm able to mount SMB shares on the same server.
>>> I tried compile NFS support into kernel and next as a modul, but  
>>> nothing
>>> happens. If is NFS compiled as a modul, loaded modules are nfs and  
>>> nfs_acl (I
>>> tried without nfs_acl too).
>>>
>>> Petr P.
>>>
>>> Dne pátek 31 srpen 2007 20:02 Craig Hughes napsal(a):
>>>> Can you ping the NFS server from the gumstix?
>>>> Is NFS compiled in to the kernel?
>>>> If not, is the NFS module loaded?

I believe I have found the problem and a potential solution.  The problem is in
the RPC code of uClibc, specifically the routine xdr_enum().  When gcc is
configured to use "short enums", the size of an enum can be between 1 and 4
bytes.  xdr_enum() doesn't handle the case of enum equal to 1.  I tried to fix
the problem by addding code for the case of a 1 byte enum to the xdr_enum(), but
it didn't work. I then followed the advice in a thread in one of the avr forums
to disable short enums in the gcc compiler.  After disabling short enums in fcc,
recompiling gcc, uClibc and all of the target code, I was able to successfully
mount using NFS.  The specific change is in file
"toolchain_build_arm_nofpu/gcc-4.1.1/gcc/config/arm/arm.c".  I changed "#define
TARGET_DEFAULT_SHORT_ENUMS arm_default_short_enums" to "#define
TARGET_DEFAULT_SHORT_ENUMS hook_bool_void_false"

regards,
frank

'So to ground it did you add any additional components? or did you just
route it straight to GND on Pin 8 for example.'

I just used something like a 220ohm resistor to pull it to ground (just to
be safe). Again, I am only telling you what has worked for me. I'm not sure
how USBH_PWR1 is handled in revision 1533. 

I'm quite sure that John Hylands is doing the opposite as I am (pulling
pin21 high), but I'm not sure what revision he is using either. According to
the PXA270 developers manual, the port can be configured either way, with
USBH_PWR1 being either active low or active high. 

Of course, one important step is to ensure that you have made no mistakes in
the design of the 24-pin board. One way you can do this is use the GPIO
driver on the gumstix to set the GPIO high or low, and then confirm the
expected pin changed using a DMM. 

Good luck, and don't give up. Having the usb host is worth the effort.

Sincerely,
Matthew Friesen
Hanbay Inc.
514 426 1989
http://www.hanbayinc.com 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.503 / Virus Database: 269.15.10/1091 - Release Date: 24/10/2007
2:31 PM

There doesn't seem to be a /lib/firmware directory ... any suggestions.

I have the drivers compiling ... but get a segmentation fault

-----Original Message-----
From: gumstix-users-bounces@...
[mailto:gumstix-users-bounces@...] On Behalf Of pvm
Sent: Monday, October 22, 2007 8:19 PM
To: gumstix-users@...
Subject: Re: [Gumstix-users] RT73 Wifi Drivers




Costagliola, Vincent wrote:
>=20
> I'm having difficulty in getting the RT73 drivers to compile.
>=20
> I moved the RT25 drivers out of the way, and replaced the package
> directory with RT73 .. needless to say it didn't compile.
>=20

You don't need to "move" the RT25 drivers, you should create a separate
folder for rt73 under packages.

in the Config.in file in the packages directory add a "sources" line for
the
rt73 folder you create.

copy the Config.in file and the .mk file from the RT2500 directory to
your
rt73 directory and rename the .mk file appropriately.  Edit the
Config.in
file then edit the .mk file.  you shouldn't need any patches for the
rt73
driver. The one you need to use is the one they refer to as "legacy" on
the
serial monkey website.  Also add a line in the .mk file to copy the rt73
firmware (rt73.bin) to the target file system /lib/firmware/ directory.

-Pete

P.S. sorry I don't have the files else I would just send them to you.  I
know for a fact this works though because I've done it before.
--=20
View this message in context:
http://www.nabble.com/RT73-Wifi-Drivers-tf4672386.html#a13355321
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
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

Dave,

I did "svn update" of a robostix system build that contains I2C code
(rev1545) but I cant remember how to recompile your I2C code.

Can you give me a quick over view?  It's in a seperate directory to my build
root directory.

I recollect once compiled I scp file to my gumstix local directory and run
it from there.

Thanks
Neil


Dave Hylands wrote:
> 
> Hi Neil,
> 
>> So I went ahead and added I2cReceiveBytes and I2cSendBytes functions
>> to the robostix/gumstix/Common/i2c-api.h and .c files. (svn rev 1544).
>> I verified that they compile, but I don't have any way of testing them
>> right now.
>>
>> You bascially want to call I2cReceiveBytes with a length of 2.
>>
>> I guess I'll need to add some new commands to the i2c program to
>> exercise these functions.
> 
> And svn revision 1545 has a version of i2c which has a RecvByte (short
> form vb) and SendByte (short form sb) which will call the
> I2CReceiveByte and I2cSendByte. I was able to test the SendByte as
> follows:
> 
> i2c-io 0x08 setdir g.4 out
> 
> i2c-io --debug 0x08 set g.4 0
> which turns the red LED on and outputs:
> I2cTransfer W: 0000: 03 03 06 10 00 28
> 
> i2c-io --debug 0x08 set g.4 1
> which turns the red LED off and outputs:
> I2cTransfer W: 0000: 03 03 06 10 10 58
> 
> The equivalent commands using the WriteByte command of i2c would be:
> 
> i2c 0x08 wb 0x03 0x0306100028
> i2c 0x08 wb 0x03 0x0306101058
> 
> and the equivalent commands using the SendByte command of i2c would be:
> 
> i2c 0x08 sb 0x030306100028
> i2c 0x08 sb 0x030306101058
> 
> I don't have a way of properly testing RecvByte, so I'm hoping it works.
> 
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.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
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users
> 
> 

-- 
View this message in context: http://www.nabble.com/I2c-read-problem-tf4685334.html#a13407167
Sent from the Gumstix mailing list archive at Nabble.com.

Hi Dave,

I downloaded sum of the tarballs from internet and followed the configuation
process as guided.
However i am unable to achieve my task i.e get a complete buildroot to
compile my programs that will run on my gumstix.

Please give me the exact location / the tar file for buildroot so that i
would be able to initiate my process .

Thanks & Regards
Anil

-----Original Message-----
From: gumstix-users-bounces@...
[mailto:gumstix-users-bounces@... Behalf Of Dave
Hylands
Sent: Wednesday, October 24, 2007 7:16 PM
To: General mailing list for gumstix users.
Subject: Re: [Gumstix-users] I2c-io change


Hi Anil,

>    Indeed you cleraed up my queries quite effectively.I tried to find out
> the compiler i.e
>
>     "arm-linux-uclibcgnueabi-gcc compiler" for comiling as u suggested but
> couldnot locate the same on my gumstix

It isn't on your gumstix, but rather on your host machine

>      please tell me the reference site/linkl from where it can be
> downloaded.

You need to build it, by following the directions for building buildroot:
<http://docswiki.gumstix.com/Buildroot>

--
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.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
gumstix-users@...
https://lists.sourceforge.net/lists/listinfo/gumstix-users

go to http://svn.gumstix.com=20
username: gumstix=20
password: gumstix

Click on Buildroot, and next to trunk click on viewlog.  It will show what
change was made with each commit.  you can also navigate to a specific file
and view the log for that as well.


Sergio Fernandez-2 wrote:
>=20
> I=C2=B4m looking for a list or some place to view
> the changes between the different  Buildroot
> Revisions.
> Do you know where can I find it?
>=20

--=20
View this message in context: http://www.nabble.com/Buildroot-Revisions.-Li=
st-of-changes--tf4689157.html#a13406828
Sent from the Gumstix mailing list archive at Nabble.com.

Should I be able to access registers STDLL and STDLH using pxaregs?
Because when I: pxaregs | grep STDLL; I get nothing.  And,

/opt/gumstix-buildroot/build_arm_nofpu/linux-2.6.18gum/include/asm-arm/arch-pxa/pxa-regs.h

does show STDLL and STDLH.  Which seems to show A LOT more then the
list I get when I execute: pxaregs > file.

It seems I'm missing something?

Thank you!
Eric


On 10/23/07, Michael Kenney <mfkenney@...> wrote:
> Eric,
>
> On 10/22/07, Eric Berryman <eric.berryman@...> wrote:
> > Here is some more information (does anything look wrong?):
>
> Those GPIO settings look right to me (this is from memory as I don't
> currently have a board available to test it on).
>
> --Mike
>
> >
> > # more /proc/tty/driver/PXA\ serial
> > serinfo:1.0 driver revision:
> > 0: uart:FFUART mmio:0x40100000 irq:15 tx:836 rx:0 RTS|CTS|DTR|DSR|CD|RI
> > 1: uart:BTUART mmio:0x40200000 irq:14 tx:0 rx:0
> > 2: uart:STUART mmio:0x40700000 irq:13 tx:0 rx:0
> > 3: uart:HWUART mmio:0x41600000 irq:0 tx:0 rx:0
> >
> > # cat /proc/gpio/GPIO4[6789]
> > 46      AF2     in      set
> > 47      AF1     out     set
> > 48      AF2     out     set
> > 49      AF2     out     set
> >
> >
> > Thank you!
> > Eric Berryman
> >
> >
> > On 10/22/07, Eric Berryman <eric.berryman@...> wrote:
> > > This seems very odd.  I can use stty to set the (ttyS1, ttyS2, etc.)
> > > baud rate to "standard" rates, but not 28800.  And, setserial works
> > > for only ttyS1.  Is there an initialization I don't know about
> > > (something in /etc/init.d)?
> > >
> > > Thank you!
> > > Eric
> > >
> > > On 10/22/07, Michael Kenney <mfkenney@...> wrote:
> > > > Eric,
> > > >
> > > > On 10/22/07, Eric Berryman <eric.berryman@...> wrote:
> > > > > Sorry for the late reply, I was away for a bit.
> > > > >
> > > > > I just tried this for divisors 1 through 32 and all gave me:
> > > > >
> > > > > # ./setserial /dev/ttyS2 spd_cust divisor 8 baud_base 230400
> > > > > Cannot set serial info: Invalid argument
> > > > >
> > > > > Is there a problem with setting the register?
> > > >
> > > > There shouldn't be (assuming you are running the command as
> > > > "root"...).  You might need to poke around in the source code for the
> > > > pxa serial driver and see if ttyS2 is handled differently
> > > >
> > > > --Mike
> > > >
> > >
> >
>