Hi,
FYI - We have found out that our reboot BOOTP problem rather is a reset problem. (PPC 405GPr)
Our external watchdog (CPLD) asserted SysReset too short time. After correcting that it worked much better, but not perfectly. We often got *Illegal instruction* *Bus error* etc. Measureing it we noticed that it asserted SysReset for "too long"... (We had it clocked from PerClk - but it changes frequency during the reset - down to 5.5MHz)
Using SysClk as clock and asserting SysReset for 8192 cycles works. Don't ask us why - it could be interferance from another pheriperal, but why then doesn't it work to reset a longer time?
/RogerL
On Monday 25 October 2004 14.00, Larsson Roger wrote:
(resent - I can't find it on archieve)
Hi,
I see a similar problem to the one described in "Re: U-Boot DHCP request does not time out." with U-Boot 1.1.1.1 But I have not seen any patch from Pantelis.
The only related message is "[PATCH] fix dhcp command retry" from Roger Blofeld Does that patch fix the problem?
In my case I think the counter restarts at 1 but the reboot BOOTP does not work. If I interrupt (CTRL-C) and issue a 'reset' the BOOTP broad cast after reset works.
How to reproduce:
- Power on -> BOOTP boot into Linux
- In Linux issue 'reboot' command
- But this did not finish before the watchdog kicked in...
- Warm booted U-BOOT runs into this problem.
- U-BOOT CTRL-C and 'reset' -> BOOTP boot into Linux
/RogerL