5.19 ROM, 24-Jul-12

To answer my own question,

“By the way, it gives an ‘MD5sum’ for, it seems, any file! I just tried it on a text file that I created and it gave a checksum for it. Is my Beagle behaving normally, or is this deviant behaviour?”,

before anyone else does, the software just calculates an md5sum for any file. Sorry, the answer is obvious. My excuse: It was late at night.

I reckon the ever-increasing size of various builds and number of builds are the reasons why the transmit from autobuild server to web server takes longer and longer, meaning I’ll occasionally have to make these adjustments (or make the system smarter and act of a “finished transfer” flag rather than a fixed-time cron job).

At work we have a number of items with indeterminate finish times and some that are loop process outputs that then need a transfer. The solution seems to be to have a flag file that gets a touch from the end of the source process.
The transfer process then checks for a timestamp newer than the last it recorded and sleeps then loops at intervals.

I am trying to update my BeagleBoard with the latest ROM and disc image and even recent ones have failed.

For one thing, when I click on the SD card icon, I get the error the the disc drive is empty, but it can’t be. I notice that the pair of green LEDs near the SD card are not lit (they are at power on).
What’s going on?

What’s going on?

Chances are there’s a bug in the ROM somewhere. I’m not sure where though, since I don’t think the SD drivers have changed much recently.

When I get a chance I’ll try the latest ROM on my BB and see what happens. Maybe tonight, but I said the same thing yesterday about checking the screen setup plugin…

The other alternative I can think of is that your SD card might not be seated correctly. RISC OS uses the card detect pin, but I’m not sure whether u-boot would bother doing the same. So it might be that the power & data pins are seated correctly but the card detect isn’t.

The latest ROM seems fine for me on my rev C2 BB. It’s normal for the two lights next to the SD slot to be off under RISC OS; RISC OS uses them as SD activity lights. One light flashing = reads, two lights = writes. When you insert a card one of the lights should flash (or at least it did for me).

@Jeffrey Lee
Thanks for checking and the information. I can now read the contents of the SD card. It may be I need to wait a little longer before clicking on the SD card icon to give time for the SD card to be ready (initialised? mounted?) after power on.