RE: [U-Boot-Users] MPC8272ADS and uboot program check

Hi,
First of all, I would acknowleging that Wolfgang is probably right and you
probably have a hardware problem.
It could be. I had some problem with the Flash in the past, but there, the board didn't start at all and kept rebooting in a few miliseconds with a HRESET.
In case that is not true, my follow-up questions and observations are...
#1 question in debugging: what changed between when it last worked and now?
Nothing changed. The uboot version is exactly the same it was before.
Looking at the above, what is the software trying to do when all the
garbage is being spewed out (just before it prints "8MB"? What it is doing is likely related to the problem.
I don't really now what it was doing at this point. So this is the point where I would need your help. I have tried to guess it. Has it any relation with the CRC warning, or some other problem with SDRAM?
Did the board previously print the correct clock rate, or has it always
been wrong? Why is it wrong?
No. Previously it showed the correct clock rate (400 Mhz). I can't imagine why this is not right. Could be some problem with the integer unit ??? SDRAM ???
#1 rule in debugging: always fix the known bugs before hunting for the
unknown, known (but discounted and ignored) bugs tend to cause additional "unknown bugs" in strange and mysterious ways.
OK. I will try to follow this method.
gvb
Thanks
Alex

Hello,
in message 51DB8827D393D411BB69003048003F46FDCEF6@tvesntr.televes.com you wrote:
First of all, I would acknowleging that Wolfgang is probably right and you
probably have a hardware problem.
Please configure your mailer to quote correctly.
BOTH lines above are quotes, but only the first line is marked as such. This essentially makes your messages unreadable. please fix this!
It could be. I had some problem with the Flash in the past, but there, the board didn't start at all and kept rebooting in a few miliseconds with a HRESET.
I think all additional discussion is in vain. You have known hardware problems, so it makes no sense to continue.
Don't try to understand why the failure mode is a reset in one case or a spectacular crash in another one - when yoiur flash is failing you must assume that the CPU is executing random data. This can be anything, and fail at any time andin any way you can or cannot imagine.
Stop here, and fix or replace the hardware.
Best regards,
Wolfgang Denk

I finaly can run linux on my ppc acess point and the last thing left is to enable pci, does bootloader must initialize pci controler? I it is normal to leave that to linux?
If I do not do anything linux complains that cant alocate resource for pci, then I added bios fixup code from walnut405, now linux crashes if try to load device driver, but it can enumerate pci devices.
The questions are: What pci initialization is nesecary for integrated ppc405gp pci bridge? Which bard pci code is the best example to start? Does intergrated pci initialization depends on board design?
participants (3)
-
Bastos Fernandez Alexandre
-
Tadas
-
Wolfgang Denk