Boot Not Run with V5.19 on a BB

A multimeter test on the output of the two switched mode power supply units (Maplin codes L11BQ and L45BL) I am using for my BB, gives 5.24V for one and 5.66V for the other. According to the multimeter instructions leaflet, the accuracy is +-0.5% or +-0.025V. According to the BeagleBoard System Reference Manual, the input voltage for the BB should be between 4.8V and 5.2V (p24). The multimeter I am using is a bit of a cheapo from Maplin. So, is the multimeter less accurate than it claims to be or is the high voltaqe upsetting the BB? In fact it is the 5.24V one that seems to be more problematic (Maplin code L11BQ and has several voltage settings).

Hmm, that’s interesting the L11BQ that used to power my BB-xM died earlier this year. Replaced it with a unbranded (looks like it’s made by Voltraft though) psu capable of 5A@5V. At first it didn’t work until I discovered the BB draws too little power to be detected by the slightly beefier psu resulting in the red overvoltage light coming on. Increasing power demand fixed that.

BB continues to fail to read the USB stick containing the !Boot. Only twice has it booted correctly, on both occasions with the same combination of power pack, USB hub etc.. I can tell whether it is reading the USB stick by how the light on the stick flashes. It has always booted correctly when the USB stick is stuck dirctly into the BB; but with only one USB socket this means no keyboard or mouse. :-((

Folk with the BB-xM may not be experiencing these problems if they have their USB stick in one of the two USB sockets.
I wonder whether anyone with a BB-xM would try booting with their USB stick stuck in a hub to see whether they get the ‘no boot run’ problem?

I’ve now uploaded a ROM image here which has some logging code enabled. If you can do the following then it should hopefully give me some indication of where things are going wrong:

1. Using the above ROM, start the machine from cold so that it will fail to boot.
2. Open up a taskwindow and save the output of *dadprint
3. Reboot so that the machine will boot properly
4. Open up a taskwindow again and save the output of *dadprint
5. Email me the two log files