gumstix

Hi Demetris,

> I wanted to ask if it is possible to make so that i don't have to enable the
> LCD each time manually by:
>
> pxaregs GPCR0_16 1
> pxaregs GPDR0_16 1
> pxaregs GPSR0_16 1
>
> i know that this can be done with a simple shell script for bootup but can i
> do it in another way not using a script?

You could do it in u-boot.

You'd need to figure out what the addresses and bits are for the
registers you're interested in.

I described doing some of these manipulations for the robostix:
http://www.gumstix.org/tikiwiki/tiki-index.php?page=Robostix-Uboot

This would enable the LCD before linux starts to boot.

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

Tnx for the Reply Dave, much appriciated.


Demetris Z

.
----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Thursday, June 15, 2006 11:16 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
>> I wanted to ask if it is possible to make so that i don't have to enable 
>> the
>> LCD each time manually by:
>>
>> pxaregs GPCR0_16 1
>> pxaregs GPDR0_16 1
>> pxaregs GPSR0_16 1
>>
>> i know that this can be done with a simple shell script for bootup but 
>> can i
>> do it in another way not using a script?
>
> You could do it in u-boot.
>
> You'd need to figure out what the addresses and bits are for the
> registers you're interested in.
>
> I described doing some of these manipulations for the robostix:
> http://www.gumstix.org/tikiwiki/tiki-index.php?page=Robostix-Uboot
>
> This would enable the LCD before linux starts to boot.
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
>
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

I read the part on WIKI about enabling pins on PXA but i have a bit o 
difficulty of understanding it.

I need to set GPCR0_16 to 1 , GPDR0_16 to 1 , and GPSR0_16 to 1.

i understand this is done with the "mw" command in u-boot.

But i still have dificulty of getting how to do it.

Could someone explain it to me a bit more or help me out on doing it.?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Thursday, June 15, 2006 11:16 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
>> I wanted to ask if it is possible to make so that i don't have to enable 
>> the
>> LCD each time manually by:
>>
>> pxaregs GPCR0_16 1
>> pxaregs GPDR0_16 1
>> pxaregs GPSR0_16 1
>>
>> i know that this can be done with a simple shell script for bootup but 
>> can i
>> do it in another way not using a script?
>
> You could do it in u-boot.
>
> You'd need to figure out what the addresses and bits are for the
> registers you're interested in.
>
> I described doing some of these manipulations for the robostix:
> http://www.gumstix.org/tikiwiki/tiki-index.php?page=Robostix-Uboot
>
> This would enable the LCD before linux starts to boot.
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
>
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> I read the part on WIKI about enabling pins on PXA but i have a bit o
> difficulty of understanding it.
>
> I need to set GPCR0_16 to 1 , GPDR0_16 to 1 , and GPSR0_16 to 1.
>
> i understand this is done with the "mw" command in u-boot.
>
> But i still have dificulty of getting how to do it.
>
> Could someone explain it to me a bit more or help me out on doing it.?

First of all, I'd take a look at this page:
http://www.gumstix.org/tikiwiki/tiki-index.php?page=Robostix-uboot

It describes doing exactly that for some of the GPIO lines that
control the robostix.

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

ok,

So i have these registers:

"GPDR0_16", 0x40E0000C, 16, 0x00000001, 'd', "GPIO 16 i/o direction 
(1=output)" },

"GPSR0_16", 0x40E00018, 16, 0x00000001, 'd', "GPIO 16 set" },

"GPCR0_16", 0x40E00024, 16, 0x00000001, 'd', "GPIO 16 clear" },



on the PXA255 datasheet it says :



for the GPDR0                              for GPSR0 
for GPCR0

Physical Address 0x40E0_000C       Physical Address 0x40E0_0018 
Physical Address 0x40E0_0024



so i enter in U-boot (for the GPDR0): md 0x40E0000C

i get this:

40e0000c: c182b9f8 0012aa80 0001ffff 00000000    ................
40e0001c: 00000000 00000000 00000000 00000000    ................
40e0002c: 00000000 00000000 00000000 00000000    ................
40e0003c: 00000000 00000000 00000000 00000000    ................
40e0004c: 00000000 00000000 81011000 a5254010    .............@%.
40e0005c: 69908010 aaa5a8aa aaaaaaaa 00000000    ...i............
40e0006c: 00000000 00000000 00000000 00000000    ................
40e0007c: 00000000 3e7ccf3f 0feffff7 01dec000    ....?.|>........
40e0008c: c182b9f8 0012aa80 0001ffff 00000000    ................
40e0009c: 00000000 00000000 00000000 00000000    ................
40e000ac: 00000000 00000000 00000000 00000000    ................
40e000bc: 00000000 00000000 00000000 00000000    ................
40e000cc: 00000000 00000000 81011000 a5254010    .............@%.
40e000dc: 69908010 aaa5a8aa aaaaaaaa 00000000    ...i............
40e000ec: 00000000 00000000 00000000 00000000    ................
40e000fc: 00000000 3e7ccf3f 07effff7 01dec000    ....?.|>........

then i enter for GPSR and GPCR this: md 0x40E00000

and get this:

40e00000: 3e7ccf3f 07effff7 01dec000 c182b9f8    ?.|>............
40e00010: 0012aa80 0001ffff 00000000 00000000    ................
40e00020: 00000000 00000000 00000000 00000000    ................
40e00030: 00000000 00000000 00000000 00000000    ................
40e00040: 00000000 00000000 00000000 00000000    ................
40e00050: 00000000 81011000 a5254010 69908010    .........@...
40e00060: aaa5a8aa aaaaaaaa 00000000 00000000    ................
40e00070: 00000000 00000000 00000000 00000000    ................
40e00080: 3e7ccf3f 1feffff7 01dec000 c182b9f8    ?.|>............
40e00090: 0012aa80 0001ffff 00000000 00000000    ................
40e000a0: 00000000 00000000 00000000 00000000    ................
40e000b0: 00000000 00000000 00000000 00000000    ................
40e000c0: 00000000 00000000 00000000 00000000    ................
40e000d0: 00000000 81011000 a5254010 69908010    .........@...
40e000e0: aaa5a8aa aaaaaaaa 00000000 00000000    ................
40e000f0: 00000000 00000000 00000000 00000000    ................

on the tutorial it says that in order to enable the pin i need to enter 
somethig like this " mw 40E0002C 100"

but here is that i get a bit off track

for my needs what should i enter ? and how do i find that out?




Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Saturday, June 24, 2006 9:24 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> I read the part on WIKI about enabling pins on PXA but i have a bit o
>> difficulty of understanding it.
>>
>> I need to set GPCR0_16 to 1 , GPDR0_16 to 1 , and GPSR0_16 to 1.
>>
>> i understand this is done with the "mw" command in u-boot.
>>
>> But i still have dificulty of getting how to do it.
>>
>> Could someone explain it to me a bit more or help me out on doing it.?
>
> First of all, I'd take a look at this page:
> http://www.gumstix.org/tikiwiki/tiki-index.php?page=Robostix-uboot
>
> It describes doing exactly that for some of the GPIO lines that
> control the robostix.
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

On Sun, Jun 25, 2006 at 12:15:08AM +0300, Demetris Zavorotnichenko wrote:
> for the GPDR0                              for GPSR0 
> for GPCR0
> 
> Physical Address 0x40E0_000C       Physical Address 0x40E0_0018 
> Physical Address 0x40E0_0024

So you're seeing:
	GPDR0 - 0x40e0000c	0xc182b9f8
	GPSR0 - 0x40e00018	0x00000000
	GPCR0 - 0x40e00024	0x00000000

The direction register contains a 1 bit for outputs and 0 bit for
inputs, so bits 0-3, corresponding to GPIOs 0-3 are in, in, in, out.
If you want to drive output GPIO 3, you set bit 3 in GPSR0:
	mw 40e00018 8

If you want to turn output GPIO 3 off, you set bit 3 in GPCR0:
	mw 40e00024 8

> >> I need to set GPCR0_16 to 1 , GPDR0_16 to 1 , and GPSR0_16 to 1.

So in this case, you're turning off bit 16, setting it to output and
driving it.  I think that's:
	mw 40e00024 00010000	// deassert GPIO 16 in case it's asserted
	mw 40e0000c c183b9f8	// set direction of GPIO 16 to output
	mw 40e00018 00010000	// assert GPIO 16

Note that the value written to 40e0000c is the same as you read,
but with bit 16 set.  In C, it would be something like:
	GPCR0 = 0x00010000;
	GPDR0 = GPDR0 | 0x00010000;
	GPSR0 = 0x00010000;

Note that GPCR0 and GPSR0 only act on the bits that are set in the
write operation.

I might have the syntax wrong, but it should be close.

-allen

This is done in prder to enable the LCD so by entering:

mw 40e00024 00010000 // deassert GPIO 16 in case it's asserted
mw 40e0000c c183b9f8 // set direction of GPIO 16 to output
mw 40e00018 00010000 // assert GPIO 16

i should enabled the lcd

but i don't see anything happening, shouldn't i set this in the bootargs or 
semething like that so whenever i boot i enable the LCD automaticly?

How do i do that?


Demetris Z.


----- Original Message ----- 
From: "Allen Briggs" <briggs@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 12:27 AM
Subject: Re: [Gumstix-users] PXAREGS


> On Sun, Jun 25, 2006 at 12:15:08AM +0300, Demetris Zavorotnichenko wrote:
>> for the GPDR0                              for GPSR0
>> for GPCR0
>>
>> Physical Address 0x40E0_000C       Physical Address 0x40E0_0018
>> Physical Address 0x40E0_0024
>
> So you're seeing:
> GPDR0 - 0x40e0000c 0xc182b9f8
> GPSR0 - 0x40e00018 0x00000000
> GPCR0 - 0x40e00024 0x00000000
>
> The direction register contains a 1 bit for outputs and 0 bit for
> inputs, so bits 0-3, corresponding to GPIOs 0-3 are in, in, in, out.
> If you want to drive output GPIO 3, you set bit 3 in GPSR0:
> mw 40e00018 8
>
> If you want to turn output GPIO 3 off, you set bit 3 in GPCR0:
> mw 40e00024 8
>
>> >> I need to set GPCR0_16 to 1 , GPDR0_16 to 1 , and GPSR0_16 to 1.
>
> So in this case, you're turning off bit 16, setting it to output and
> driving it.  I think that's:
> mw 40e00024 00010000 // deassert GPIO 16 in case it's asserted
> mw 40e0000c c183b9f8 // set direction of GPIO 16 to output
> mw 40e00018 00010000 // assert GPIO 16
>
> Note that the value written to 40e0000c is the same as you read,
> but with bit 16 set.  In C, it would be something like:
> GPCR0 = 0x00010000;
> GPDR0 = GPDR0 | 0x00010000;
> GPSR0 = 0x00010000;
>
> Note that GPCR0 and GPSR0 only act on the bits that are set in the
> write operation.
>
> I might have the syntax wrong, but it should be close.
>
> -allen
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> This is done in prder to enable the LCD so by entering:
>
> mw 40e00024 00010000 // deassert GPIO 16 in case it's asserted
> mw 40e0000c c183b9f8 // set direction of GPIO 16 to output
> mw 40e00018 00010000 // assert GPIO 16
>
> i should enabled the lcd
>
> but i don't see anything happening, shouldn't i set this in the bootargs or
> semething like that so whenever i boot i enable the LCD automaticly?

If you enter these commands at the GUM> prompt and it's not doing the
right things, then you need to figure that part out first.

bootargs is what's passed to the kernel on the command line.

bootcmd is what's executed when u-boot starts up. What I like to do is
to create a new variable to put the mw commands in like this:

setenv enable_lcd "mw 40e00024 00010000; mw 40e0000c c183b9f8; mw
40e00018 00010000"

and then use the run command to execute the contents of the variable.

When you issue the mw commands you should see the voltage change on
GPIO16. If you don't then figure out what's wrong.

So the voltage should be around 0v after setting the direction to
output, and should be around 3.3v after setting it to 1.


-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

ok, TNX for the help ALLOT Allen and Dave, i have another question though.

I saved the variable enable_lcd and run it, it works fine now.

but how do i make it start each time with u-Boot? so i don't have to run it 
each time?

also i noticed this before.

when enabling the modules "snd-pxa2xx-ac97, ucb1x00-ts, evdev" the LCd goes 
blank so i have to reenable it.

in my case when i enable the LCD from the u_boot i see the lcd go on and 
then when the Modules are enabled the LCD goes off again.

How do i fix this?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 12:50 AM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> This is done in prder to enable the LCD so by entering:
>>
>> mw 40e00024 00010000 // deassert GPIO 16 in case it's asserted
>> mw 40e0000c c183b9f8 // set direction of GPIO 16 to output
>> mw 40e00018 00010000 // assert GPIO 16
>>
>> i should enabled the lcd
>>
>> but i don't see anything happening, shouldn't i set this in the bootargs 
>> or
>> semething like that so whenever i boot i enable the LCD automaticly?
>
> If you enter these commands at the GUM> prompt and it's not doing the
> right things, then you need to figure that part out first.
>
> bootargs is what's passed to the kernel on the command line.
>
> bootcmd is what's executed when u-boot starts up. What I like to do is
> to create a new variable to put the mw commands in like this:
>
> setenv enable_lcd "mw 40e00024 00010000; mw 40e0000c c183b9f8; mw
> 40e00018 00010000"
>
> and then use the run command to execute the contents of the variable.
>
> When you issue the mw commands you should see the voltage change on
> GPIO16. If you don't then figure out what's wrong.
>
> So the voltage should be around 0v after setting the direction to
> output, and should be around 3.3v after setting it to 1.
>
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> ok, TNX for the help ALLOT Allen and Dave, i have another question though.
>
> I saved the variable enable_lcd and run it, it works fine now.
>
> but how do i make it start each time with u-Boot? so i don't have to run it
> each time?

You need to invoke it from bootcmd.

So that's why I do this:

setenv linux "$bootcmd"

This makes a variable called linux which contains the original
contents of the bootcmd variable.

Then I'd set bootcmd to something like this:

setenv bootcmd "run enable_lcd; run linux"

> when enabling the modules "snd-pxa2xx-ac97, ucb1x00-ts, evdev" the LCd goes
> blank so i have to reenable it.
>
> in my case when i enable the LCD from the u_boot i see the lcd go on and
> then when the Modules are enabled the LCD goes off again.
>
> How do i fix this?

Hmmm. I see that the snd-pxa2xx-ac97 driver uses GPIOs 28, 29, 30, and 31.

I don't see anything obvious which messes with GPIO16. Can you
pinpoint which module causes the problem?

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

by running the commands you have suggested i messed up mu u-Boot,

now linux doesn't boot atall

just says ERROR : memory not allocated

so what to do now?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 2:31 AM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> ok, TNX for the help ALLOT Allen and Dave, i have another question 
>> though.
>>
>> I saved the variable enable_lcd and run it, it works fine now.
>>
>> but how do i make it start each time with u-Boot? so i don't have to run 
>> it
>> each time?
>
> You need to invoke it from bootcmd.
>
> So that's why I do this:
>
> setenv linux "$bootcmd"
>
> This makes a variable called linux which contains the original
> contents of the bootcmd variable.
>
> Then I'd set bootcmd to something like this:
>
> setenv bootcmd "run enable_lcd; run linux"
>
>> when enabling the modules "snd-pxa2xx-ac97, ucb1x00-ts, evdev" the LCd 
>> goes
>> blank so i have to reenable it.
>>
>> in my case when i enable the LCD from the u_boot i see the lcd go on and
>> then when the Modules are enabled the LCD goes off again.
>>
>> How do i fix this?
>
> Hmmm. I see that the snd-pxa2xx-ac97 driver uses GPIOs 28, 29, 30, and 31.
>
> I don't see anything obvious which messes with GPIO16. Can you
> pinpoint which module causes the problem?
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Never mind that, i have redone it and it works fine now,

The module that seems to disable the LCD as soon as i enter "modprobe" is : 
UCB1x00-ts


Demetris Z.


----- Original Message ----- 
From: "Demetris Zavorotnichenko" <fgcity4652@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 12:36 PM
Subject: Re: [Gumstix-users] PXAREGS


> by running the commands you have suggested i messed up mu u-Boot,
>
> now linux doesn't boot atall
>
> just says ERROR : memory not allocated
>
> so what to do now?
>
>
> Demetris Z.
>
>
> ----- Original Message ----- 
> From: "Dave Hylands" <dhylands@...>
> To: "General mailing list for gumstix users."
> <gumstix-users@...>
> Sent: Sunday, June 25, 2006 2:31 AM
> Subject: Re: [Gumstix-users] PXAREGS
>
>
>> Hi Demetris,
>>
>> On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>>> ok, TNX for the help ALLOT Allen and Dave, i have another question
>>> though.
>>>
>>> I saved the variable enable_lcd and run it, it works fine now.
>>>
>>> but how do i make it start each time with u-Boot? so i don't have to run
>>> it
>>> each time?
>>
>> You need to invoke it from bootcmd.
>>
>> So that's why I do this:
>>
>> setenv linux "$bootcmd"
>>
>> This makes a variable called linux which contains the original
>> contents of the bootcmd variable.
>>
>> Then I'd set bootcmd to something like this:
>>
>> setenv bootcmd "run enable_lcd; run linux"
>>
>>> when enabling the modules "snd-pxa2xx-ac97, ucb1x00-ts, evdev" the LCd
>>> goes
>>> blank so i have to reenable it.
>>>
>>> in my case when i enable the LCD from the u_boot i see the lcd go on and
>>> then when the Modules are enabled the LCD goes off again.
>>>
>>> How do i fix this?
>>
>> Hmmm. I see that the snd-pxa2xx-ac97 driver uses GPIOs 28, 29, 30, and 
>> 31.
>>
>> I don't see anything obvious which messes with GPIO16. Can you
>> pinpoint which module causes the problem?
>>
>> -- 
>> Dave Hylands
>> Vancouver, BC, Canada
>> http://www.DaveHylands.com/
>>
>> Using Tomcat but need to do more? Need to support web services, security?
>> Get stuff done quickly with pre-integrated technology to make your job
>> easier
>> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
>> Geronimo
>> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>> _______________________________________________
>> gumstix-users mailing list
>> gumstix-users@...
>> https://lists.sourceforge.net/lists/listinfo/gumstix-users
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

I have managed to get the u-Boot to boot up with the settings that You have 
suggested Dave, very much appriciated.

Now about the problem with the screen going blank after a module is being 
enabled.

I pinpointed the module, it's UCB1x00-ts.

So how can this be fixed?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 2:31 AM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/24/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> ok, TNX for the help ALLOT Allen and Dave, i have another question 
>> though.
>>
>> I saved the variable enable_lcd and run it, it works fine now.
>>
>> but how do i make it start each time with u-Boot? so i don't have to run 
>> it
>> each time?
>
> You need to invoke it from bootcmd.
>
> So that's why I do this:
>
> setenv linux "$bootcmd"
>
> This makes a variable called linux which contains the original
> contents of the bootcmd variable.
>
> Then I'd set bootcmd to something like this:
>
> setenv bootcmd "run enable_lcd; run linux"
>
>> when enabling the modules "snd-pxa2xx-ac97, ucb1x00-ts, evdev" the LCd 
>> goes
>> blank so i have to reenable it.
>>
>> in my case when i enable the LCD from the u_boot i see the lcd go on and
>> then when the Modules are enabled the LCD goes off again.
>>
>> How do i fix this?
>
> Hmmm. I see that the snd-pxa2xx-ac97 driver uses GPIOs 28, 29, 30, and 31.
>
> I don't see anything obvious which messes with GPIO16. Can you
> pinpoint which module causes the problem?
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> I have managed to get the u-Boot to boot up with the settings that You have
> suggested Dave, very much appriciated.
>
> Now about the problem with the screen going blank after a module is being
> enabled.
>
> I pinpointed the module, it's UCB1x00-ts.

OK. Lets see what exactly is different about the GPIOs.

Before loading UCB1x00-ts do this:

cat /proc/gpio/* > gpio-before.txt
modprobe USB1x00-ts
cat /proc/gpio/* > gpio-after.txt

and what's the diff between the two txt files.

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

i don't have gpio in Proc :)


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 10:14 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> I have managed to get the u-Boot to boot up with the settings that You 
>> have
>> suggested Dave, very much appriciated.
>>
>> Now about the problem with the screen going blank after a module is being
>> enabled.
>>
>> I pinpointed the module, it's UCB1x00-ts.
>
> OK. Lets see what exactly is different about the GPIOs.
>
> Before loading UCB1x00-ts do this:
>
> cat /proc/gpio/* > gpio-before.txt
> modprobe USB1x00-ts
> cat /proc/gpio/* > gpio-after.txt
>
> and what's the diff between the two txt files.
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
> i don't have gpio in Proc :)

then do a

modprobe proc_gpio

first

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

it seems that if i just enable ucb1x00-ts then the LCD doesn't go off , 
nither if i enable evdev module.

This happends if i enable all 3 of them in order to get the 
/dev/input/event0


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 10:14 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> I have managed to get the u-Boot to boot up with the settings that You 
>> have
>> suggested Dave, very much appriciated.
>>
>> Now about the problem with the screen going blank after a module is being
>> enabled.
>>
>> I pinpointed the module, it's UCB1x00-ts.
>
> OK. Lets see what exactly is different about the GPIOs.
>
> Before loading UCB1x00-ts do this:
>
> cat /proc/gpio/* > gpio-before.txt
> modprobe USB1x00-ts
> cat /proc/gpio/* > gpio-after.txt
>
> and what's the diff between the two txt files.
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

how can i send files from gumstix to my Hyperterm ?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 10:34 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> i don't have gpio in Proc :)
>
> then do a
>
> modprobe proc_gpio
>
> first
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

ok

Before i enable the modules"snd-pxa2xx-ac97" and "ucb1x00-ts" the GPIO's are 
as follows

GAFR0_L: 81011000
GAFR0_U: a5254010
GAFR1_L: 69908010
GAFR1_U: aaa5a8aa
GAFR2_L: aaaaaaaa
GAFR2_U: 00000000
GPDR0: c183b9f8
GPDR1: fc12a880
GPDR2: 0001ffff
0       GPIO    in      set
1       GPIO    in      set
10      GPIO    in      set
11      GPIO    out     set
12      AF1     out     set
13      GPIO    out     clear
14      GPIO    in      set
15      AF2     out     set
16      GPIO    out     set
17      GPIO    out     clear
18      AF1     in      set
19      GPIO    in      set
2       GPIO    in      set
20      GPIO    in      set
21      GPIO    in      set
22      GPIO    in      set
23      AF1     out     clear
24      AF1     out     clear
25      AF1     in      set
26      AF2     in      set
27      GPIO    in      set
28      AF1     in      set
29      AF1     in      set
3       GPIO    out     set
30      AF2     out     clear
31      AF2     out     clear
32      GPIO    in      set
33      GPIO    in      set
34      AF1     in      set
35      GPIO    in      clear
36      GPIO    in      set
37      GPIO    in      set
38      GPIO    in      set
39      AF2     out     set
4       GPIO    out     set
40      GPIO    in      set
41      GPIO    in      set
42      AF1     in      set
43      AF2     out     set
44      AF1     in      set
45      AF2     out     set
46      AF2     in      set
47      AF1     out     set
48      AF2     in      set
49      AF2     out     set
5       GPIO    out     set
50      AF2     in      set
51      AF2     in      set
52      GPIO    out     clear
53      AF2     in      set
54      AF2     in      set
55      AF2     in      set
56      AF1     in      set
57      AF1     in      set
58      AF2     out     clear
59      AF2     out     clear
6       AF1     out     clear
60      AF2     out     clear
61      AF2     out     clear
62      AF2     out     clear
63      AF2     out     clear
64      AF2     out     clear
65      AF2     out     clear
66      AF2     out     clear
67      AF2     out     clear
68      AF2     out     clear
69      AF2     out     clear
7       GPIO    out     clear
70      AF2     out     clear
71      AF2     out     clear
72      AF2     out     clear
73      AF2     out     clear
74      AF2     out     clear
75      AF2     out     clear
76      AF2     out     set
r
77      AF2     out     clear
78      AF2     out     set
79      AF2     out     set
8       AF1     out     set
80      GPIO    out     clear
81      GPIO    in      set
82      GPIO    in      set
83      GPIO    in      set
84      GPIO    in      set
9       GPIO    in      set
GPLR0: 3e7dcf3f
GPLR1: 03effff7
GPLR2: 01dec000


and after :

GAFR0_L: 81011000
GAFR0_U: a5254010
GAFR1_L: 69908010
GAFR1_U: aaa5a8aa
GAFR2_L: aaaaaaaa
GAFR2_U: 00000000
GPDR0: c1809140
GPDR1: fc02a880
GPDR2: 0000ffff
0       GPIO    in      set
1       GPIO    in      set
10      GPIO    in      set
11      GPIO    in      set
12      AF1     out     set
13      GPIO    in      set
14      GPIO    in      set
15      AF2     out     set
16      GPIO    in      clear
17      GPIO    in      set
18      AF1     in      set
19      GPIO    in      set
2       GPIO    in      set
20      GPIO    in      set
21      GPIO    in      set
22      GPIO    in      set
23      AF1     out     clear
24      AF1     out     clear
25      AF1     in      set
26      AF2     in      set
27      GPIO    in      set
28      AF1     in      clear
29      AF1     in      clear
3       GPIO    in      set
30      AF2     out     clear
31      AF2     out     clear
32      GPIO    in      set
33      GPIO    in      set
34      AF1     in      set
35      GPIO    in      clear
36      GPIO    in      set
37      GPIO    in      set
38      GPIO    in      set
39      AF2     out     set
4       GPIO    in      set
40      GPIO    in      set
41      GPIO    in      set
42      AF1     in      set
43      AF2     out     set
44      AF1     in      set
45      AF2     out     set
46      AF2     in      set
47      AF1     out     set
48      AF2     in      set
49      AF2     out     set
5       GPIO    in      set
50      AF2     in      set
51      AF2     in      set
52      GPIO    in      set
53      AF2     in      set
54      AF2     in      set
55      AF2     in      set
56      AF1     in      set
57      AF1     in      set
58      AF2     out     clear
59      AF2     out     clear
6       AF1     out     clear
60      AF2     out     clear
61      AF2     out     clear
62      AF2     out     clear
63      AF2     out     clear
64      AF2     out     clear
65      AF2     out     clear
66      AF2     out     clear
67      AF2     out     clear
68      AF2     out     clear
69      AF2     out     clear
7       GPIO    in      set
70      AF2     out     clear
71      AF2     out     clear
72      AF2     out     clear
73      AF2     out     clear
74      AF2     out     clear
75      AF2     out     clear
76      AF2     out     set
77      AF2     out     clear
78      AF2     out     set
79      AF2     out     set
8       AF1     out     set
80      GPIO    in      set
81      GPIO    in      set
82      GPIO    in      set
83      GPIO    in      set
84      GPIO    in      set
9       GPIO    in      set
GPLR0: 1e7effbf
GPLR1: 03fffff7
GPLR2: 02dfc000



You can clearly see that GPIO 16 goes from OUT - SET to IN - CLEAR

so how can i make this NOT happen ? i mean this is what causing the LCD go 
out.



Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Sunday, June 25, 2006 10:34 PM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
> On 6/25/06, Demetris Zavorotnichenko <fgcity4652@...> wrote:
>> i don't have gpio in Proc :)
>
> then do a
>
> modprobe proc_gpio
>
> first
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

Hi Demetris,

> You can clearly see that GPIO 16 goes from OUT - SET to IN - CLEAR
>
> so how can i make this NOT happen ? i mean this is what causing the LCD go
> out.

So there are actually quite a few differences:

3, 4, 5, 7, 11, 13, 16, 17, 52, 80 were changed from out to in.

I'd be inclined to start by adding a printk to the
linux-2.6.17gum/arch/arm/mach-pxa/generic.c in the pxa_gpio_mode
function.

I'd add something like this:

if ( gpio == 16 )
{
    if (gpio_mode & GPIO_MD_MASK_DIR)
        printk( "GPIO16 set to output\n" );
    else
        printk( "GPIO16 set to input\n" );
}

and see if the print fires. If it does, then I'd add a counter and
trigger a memory access failure on the nth attempt (where n matches
whatever is appropriate for your situation). This will cause an oops
which will show you who is calling pxa_gpio_mode

-- 
Dave Hylands
Vancouver, BC, Canada
http://www.DaveHylands.com/

I'll try that Dave, but i am using linux 2.6.15.

You suggest i change it to the newer one?


Demetris Z.


----- Original Message ----- 
From: "Dave Hylands" <dhylands@...>
To: "General mailing list for gumstix users." 
<gumstix-users@...>
Sent: Monday, June 26, 2006 3:44 AM
Subject: Re: [Gumstix-users] PXAREGS


> Hi Demetris,
>
>> You can clearly see that GPIO 16 goes from OUT - SET to IN - CLEAR
>>
>> so how can i make this NOT happen ? i mean this is what causing the LCD 
>> go
>> out.
>
> So there are actually quite a few differences:
>
> 3, 4, 5, 7, 11, 13, 16, 17, 52, 80 were changed from out to in.
>
> I'd be inclined to start by adding a printk to the
> linux-2.6.17gum/arch/arm/mach-pxa/generic.c in the pxa_gpio_mode
> function.
>
> I'd add something like this:
>
> if ( gpio == 16 )
> {
>    if (gpio_mode & GPIO_MD_MASK_DIR)
>        printk( "GPIO16 set to output\n" );
>    else
>        printk( "GPIO16 set to input\n" );
> }
>
> and see if the print fires. If it does, then I'd add a counter and
> trigger a memory access failure on the nth attempt (where n matches
> whatever is appropriate for your situation). This will cause an oops
> which will show you who is calling pxa_gpio_mode
>
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job 
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users