Re: Reading OMAP3 CONTROL_RAND_KEY_0 register hangs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux