I am using the latest version of the PSP (linux-v3.2_AM335xPSP_04.06.00.08) on AM3359.
I observed the following abnormalities:
-Invalid access to register PMR_PER (0x44e00c04)...the register offset is not correct. the memory is reserved.-The kernel initializes the internal SRAM at address 0x4020f000 (the am335x has the SRAM at address 0x402f0400)
Have you encountered these problems? Depend on the configuration of the kernel? Or are the problems of the version I'm using?
Are you seeing this error when booting? Which board?
If so, are you using Prebuilt binaries or have you followed the kernal defconfig procedure below?:
We've been able to build and boot AM335X-LINUX-PSP-04.06.00.08 on both AM335x EVM and beta version of the Starter Kit that is coming out soon (with the same uImage which was pretty cool!): http://processors.wiki.ti.com/index.php/AM335xStarterKitHardwareUsersGuide
Yes, the error occurs during the boot phase. but the kernel is finished booting seems without problems.
I use buildroot (buildroot-2012.08-rc1) and the kernel linux v3.2-PSP 04.06.00.08 (http://arago-project.org/git/projects/?p=linux-am33x.git;a=shortlog;h=refs/heads/AM335XPSP_04.06.00.08).
I run the linux kernel on the simulator (AM335x simulation model).
In addition to the offset (0x04) of the register PRM_PER invalid, the error most strange is the address of the SRAM!!!
I'm using the PSP from the TI EZSDK site (http://www.ti.com/tool/linuxezsdk-sitara) on HW. Attached is my boot log.
I don't see any references to 0x4xxxxxxx adresses except for valid peripheral addresses (i.e, UART, Ethernet MAC, etc.)
Can you please share your boot log where the errors you have mentioned can be seen?
Attached is my boot log. The error is not visible from the log of the boot. I observe the error by monitoring the memory accesses in simulation. The invalid access occurs in the first phase of the boot, during the first initialization of the power module.
Before using buildroot, I tried the prebuild (uImage) the following release (ti-sdk-am335x-evm-05.04.01.00-Linux-x86-Install). I noticed four memory offset invalid (note that the kernel still complete the boot). If you want I can give you more information about these errors.
Furthermore, regarding SRAM, after a static analysis of the kernel source files I have not found the correct address of the SRAM.
Could you please share more info on your simulation model and screenshots or logs of the error you are seeing.
Also, any specific reason why you are using simulation model?
I did a quick search of the source and found that the address 0x402F_0400 is used only in u-boot
and kernel uses the SRAM region from 0x4030_0000. I could not find any reference to 0x402f0400.
Also, please share the invalid memory offset errors you encountered while using the prebuilt uImage.
Correction from my previous post:
I meant "I could not find any reference to 0x4020f000 "
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.