From: Patrick <kpa_info@yahoo.fr>
To: barebox@lists.infradead.org
Subject: Re: GPIO commands on OMAP4
Date: Thu, 05 Apr 2012 16:58:37 +0200 [thread overview]
Message-ID: <4F7DB31D.6030800@yahoo.fr> (raw)
In-Reply-To: <4F7DAE7B.2050607@yahoo.fr>
On 04/05/2012 04:38 PM, Patrick wrote:
> On 04/05/2012 03:49 PM, Sascha Hauer wrote:
>> On Thu, Apr 05, 2012 at 11:40:49AM +0200, Patrick wrote:
>>> Dear mailing-list,
>>>
>>> I am using a pcm049 phyCORE omap4430 module from Phytec with BareBox
>>> 2011.09.0 patched with BSP from Phytec.
>>>
>>> I would like to use the GPIO command to read a switch at startup.
>>> This chip is connected on ABE_MCBSP1_DX (gpio_116). I have edited
>>> the boards/pcm049/mux.c files to change the configuration of this
>>> GPIO as follow: {ABE_MCBSP1_DX, (DIS | IEN | M3)} instead of
>>> {ABE_MCBSP1_DX, (SAFE_MODE)}.
>>>
>>> I then use the "gpio_get_value 116" command followed by "echo $?" to
>>> read the value. I always read a 0. On Linux I could read the right
>>> value depending of the position of the switch, so it's not an
>>> hardware problems.
>>>
>>> I have tried with one of the two LEDs on the module (gpio_152) and I
>>> could change the LED state and read it back with gpio_get_value.
>>>
>>> I do not understand what I am doing wrong. Any help will be appreciated.
>>
>> What you tried should work. The only thing I can imagine is that you
>> need a gpio_direction_input before reading the value.
>>
>> Sascha
>>
> I have found the the problem come from the mux configuration.
>
> I have added a call to set_muxconf_regs() from the gpio_get_value()
> (this is only to try) and then it works. I have checked my configuration
> and the lowlevel init is enabled:
>
> CONFIG_MACH_HAS_LOWLEVEL_INIT=y
> CONFIG_MACH_DO_LOWLEVEL_INIT=y
>
> I am runnig my development version of barebox from the stable barebox
> flashed on NAND. I do the following:
>
> tftp barebox.bin /dev/ram0
> go /dev/ram0
>
> Could this be a problem ?
>
> Thanks for your help
>
> Patrick
>
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
Ok things start to become clearer; As I say before I start my dev
version of BareBox from a stable flashed version.
My dev version is then executed from adress 0x80000000. On the
board_init_lowlevel() function there is the following test:
if (get_pc() > 0x80000000)
return;
As my version is started from 0x80000000 this test is true and then the
set_muxconf_regs(); is never called !
Now the question is why there is this test ?
Is the right place to call set_muxconf_regs(); from this location ?
Thanks for your help
Patrick
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-04-05 14:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-05 9:40 Patrick
2012-04-05 12:45 ` Patrick
2012-04-05 13:49 ` Sascha Hauer
2012-04-05 14:38 ` Patrick
2012-04-05 14:58 ` Patrick [this message]
2012-04-05 16:19 ` Sascha Hauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F7DB31D.6030800@yahoo.fr \
--to=kpa_info@yahoo.fr \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox