From: Dirk Behme <dirk.behme@googlemail.com>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Reading OMAP3 CONTROL_RAND_KEY_0 register hangs
Date: Fri, 16 Jan 2009 17:11:22 +0100 [thread overview]
Message-ID: <4970B1AA.7090403@googlemail.com> (raw)
In-Reply-To: <13B9B4C6EF24D648824FF11BE8967162036D63FEB7@dlee02.ent.ti.com>
Woodruff, Richard wrote:
>> With OMAP3530 on BeagleBoard we like to read OMAP3's
>> CONTROL_RAND_KEY_0 (0x4800 2318) register with something like
>>
>> printf ("attempting cpu_uid read\n");
>> u32 cpu_uid = *((u32 *) 0x48002318);
>> /* u32 cpu_uid = readl(&ctrl_base->randkey_0); */
>> printf ("cpu_uid read done\n");
>
> This address is not accessible out side of secure mode along with some other qualifiers.
>
> Trying to access is futile and will result in an abort. The control register range is full of readable and aborting addresses.
Is there any hint in TRM (spruf98b.pdf) identifying/marking which
registers are readable in normal and which are only accessible in
secure mode?
Thanks
Dirk
next prev parent reply other threads:[~2009-01-16 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 16:23 Reading OMAP3 CONTROL_RAND_KEY_0 register hangs Dirk Behme
2009-01-15 19:43 ` Woodruff, Richard
2009-01-16 16:11 ` Dirk Behme [this message]
2009-01-17 0:14 ` Woodruff, Richard
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=4970B1AA.7090403@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap@vger.kernel.org \
--cc=r-woodruff2@ti.com \
/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