RE: [U-Boot-Users] PPC8xx chip select configuration at startup

Vladimir,
I've solved my problem thanks to your request for the values of CS0 at power-up.
Here's how my board comes up at hard reset:
BR0 0400_0801 OR0 0000_0FF4 (the defaults)
And this makes sense to me... the board boots at address 0, with FLASH repeating at 0400_0000, 0800_0000, etc., and OR0 allows access to all instances of the aliasing, with max wait states, relaxed timing, burst inhibit, etc.
So guess what. I got U-boot to run without the 'boot value' modification to CS0 I had discussed. I think my problem was related to my debugging tool, the visionCLICK ICE... I had it configured to set values into the target at reset. So of course the values of BR0/OR0 were overridden with whatever I had in there... which were not the same as what the board booted up with. I hadn't occurred to me to look for and turn off this option until you asked for the values.
So I can thankfully say this is a non-issue for me, and I don't have to do anything to U-Boot, which pleases me greatly.
Thanks much for the help!
Steve
-----Original Message----- From: u-boot-users-admin@lists.sourceforge.net [mailto:u-boot-users-admin@lists.sourceforge.net] On Behalf Of Vladimir Gurevich Sent: Friday, February 17, 2006 10:35 AM To: u-boot-users@lists.sourceforge.net Subject: Re: [U-Boot-Users] PPC8xx chip select configuration at startup
Hi Steve,
Steve Strublic wrote:
I understand that 0400_0000 is my choice; it's what we use in the current product implementation (an eCos-based solution). It wouldn't
be
a bad idea to bump it.
So, you are trying to use U-boot to boot some existing code that you can't modify, correct?
And I agree that the hard reset word may be other than what U-Boot's startup sequence requires, but I'm stuck. I cannot spin the board to alter its contents.
That's a pain.
Why don't you send us the values of BR0/OR0 just after power-on reset and what you'd like them to be so that we can take a look and see more clearly what the problem is if it is there.
Happy hacking, Vladimir
------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&da... _______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users

In message 482F3C06ECF00C44AEC226520C6FCB1A51ED01@EXCHANGEVS.HYPERCOM.COM you wrote:
So guess what. I got U-boot to run without the 'boot value' modification to CS0 I had discussed. I think my problem was related to my debugging tool, the visionCLICK ICE... I had it configured to set
WHile I have nothing against a little Vision*-bashing, you should stay honest here: The tool is probably not to blame...
values into the target at reset. So of course the values of BR0/OR0
... this was a pilot error.
were overridden with whatever I had in there... which were not the same as what the board booted up with. I hadn't occurred to me to look for and turn off this option until you asked for the values.
I always recommend to use a *minimal* init file in your debug tool, just doing what is unavoidable (i. e. disable the watchdog). You should never mess with the memory controller configuration when trying to debug U-Boot.
Best regards,
Wolfgang Denk
participants (2)
-
Steve Strublic
-
Wolfgang Denk