From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] write to mcBsp address space
Date: Tue, 15 Feb 2011 11:35:35 +0100 [thread overview]
Message-ID: <4D5A56F7.4080302@free.fr> (raw)
In-Reply-To: <loom.20110215T091722-802@post.gmane.org>
Le 15/02/2011 09:21, Ran a ?crit :
> Albert ARIBAUD<albert.aribaud<at> free.fr> writes:
>
>>
>> Hi Ran,
>>
>> Le 15/02/2011 07:35, Ran Shalit a ?crit :
>>> Hello,
>>>
>>> I'm working on OMAPL138 EVM board, with the U-BOOT.
>>> I'm trying to access and write into the register (which have write bits),
>>> but I always read 0 in all the map space of the mcBSP0 and mcBSP1.
>>> (0x01d10000 - 0x1d10800, 0x01d11000 - 0x1d11800).
>>> I wonder what I missed here. any ideas are welcomed.
>>
>> Many SoCs have "base address registers" that allow remapping internal or
>> peripheral registers anywhere in the address space, which means the
>> actual address you're trying to get at might not be the right one. Did
>> you check the BAR(s) and make sure the mcBsp address you're targetting
>> is the right one for your board?
>>
>>> Thank you very much,
>>>
>>> Ran
>>
>> Amicalement,
>
> Hello Albert,
>
> Thank you very much for your reply.
> I've checked the datasheet but I see no reference to base address registers
> for the mcBSP.
>
> mcBSP: http://www.ti.com/litv/pdf/sprugj6c
> OMAPL138: http://www.ti.com/lit/gpn/omap-l138
Evidently the mcBsp specs won't tell you how the device is mapped within
a given SoC. As for the OMAPL138 SoC, it looks more like an overview.
You would need to refer to a detailed spec, one with register level
description of the module.
> thanks again,
>
> Ran
Amicalement,
--
Albert.
next prev parent reply other threads:[~2011-02-15 10:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 6:35 [U-Boot] write to mcBsp address space Ran Shalit
2011-02-15 6:48 ` Albert ARIBAUD
2011-02-15 8:21 ` Ran
2011-02-15 10:35 ` Albert ARIBAUD [this message]
2011-02-15 11:50 ` Ran
2011-02-15 12:35 ` Albert ARIBAUD
2011-02-16 7:04 ` Aneesh V
2011-02-15 14:49 ` Bedia, Vaibhav
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=4D5A56F7.4080302@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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