Can't flash new ROM via CF - any suggestions?

[mroz]

Hi,

This problem's driving me nuts. I've been playing with my new SL5500 for a couple of weeks now. Tried to reflash the ROM tonight, but have had no success.

I'm trying to replace the original Sharp ROM with tkrom 2.0alpha3.

I only have a single compact flash card - a Dane-Elec 128MB unit - & the Zaurus is my only means to read/write to it.

I use Qtopia Desktop from WindowsXP to copy the two files across to the Zaurus's internal memory, then use the terminal on the Zaurus to move these into the root of the compact flash card.

Then I switch the unit off, ensure the device has mains power, flip the rear switch to replace & remove the battery cover. I hold c & d on the key pad, press & release the hard reset button & then release c & d.

Neither of the power/email leds light.

To get the Zaurus up again, I have to press the hard reset button again, at which point the powed led briefly lights. I put the battery cover back & flip the switch back to normal. Powering up brings the Zaurus back to life, as though I'd just done a hard reset & nothing else. IOW the old ROM is still there.

I've tried this many times. From the terminal, dosfsck -v /dev/hda1 shows me that the card is formatted to FAT 16. I've tried multiple reformats, both via mkdosfs & mkfs.vfat (both with the default of FAT16 & by explicitly requesting it with -F 16). I also ensure there are no other files on the compact flash card.

Whatever I do, I get the same results.

I've also checked transferring the files to the card didn't corrupt them by comparing md5sums.

Can anyone help?

Am I screwing something up? Will I have to buy & try a card reader to format &/or write the files to the card. Do I have to try a different card? If so, does it matter if it's the same spec, or should I try to find a different brand &/or size? Are there any best options or other things I can try?

[lardman]

Some people have reported having troubles with particular cards, then trying a different one and it working. I don't know.

You say you checked the md5sums, good, what about the file extensions (simple I know, but you'd be amazed at the number of people who forget - me included ;-))

As a last ditch attempt, you could always try removing the partition (fdisk) and then re-creating it and then formatting it. Instructions in the HowTos page.


Si

[dhns]

Some people have reported having troubles with particular cards, then trying a different one and it working. I don't know.

The reason could be that the flash boot loader is not as sophisticated in recognizing non-standard cards as the Linux driver which has a database for PCMCIA card types and configurations and tries several different formats.

So a normally usable card is no guarantee that it can be used for flashing.

[bredroll]

im having the same problems, except that i have a broken openzaurus install instead of sharprom,

each card i have has turned out to be a toshiba card.

even my newest, a viking 128mb card wont let me flash, out of 4 cf cards i've tried i still cant flash it,

can anyone reccomend (or even lend me) a card that is known to work for flashing.?

Ian

[mroz]

Some people have reported having troubles with particular cards, then trying a different one and it working. I don't know.

...What about the file extensions

As a last ditch attempt, you could always try removing the partition (fdisk) and then re-creating it and then formatting it.

Particular cards:

That's the impression I get from searching on the subject :/

File extensions:

No, not that. I'm used to systems which don't use them & as far as I'm concerned, they're just part of the filename, so unless something clips them & I don't notice, they don't usually cause me problems

fdisk:

Thanks, I will give that a shot.

[mroz]

The reason could be that the flash boot loader is not as sophisticated in recognizing non-standard cards as the Linux driver which has a database for PCMCIA card types and configurations and tries several different formats.

That's what I reckoned, hence the reason I (think) I asked if it would be enough to merely try another card, or if it's more important to make sure I try another brand &/or size (& which of these two is more likely to make a difference).

Likewise, might it make a difference if the file is written via another device, rather than the Zaurus (seems unlikely, but you never know - well, I never know, anyway  ?

As bredroll said, can anyone recommend a particular card that's known to work?

Unfortunately the only local shop that has stock keeps only Dane-Elec, so unless the key factor is card size, I'll have to try something mail order which means more delays.

[Zaurus_Eric]

I was going to install a new Sharp ROM, but noticed the whenever I copied the OSPACK file to the CF card it was written as ospack (lowercase).

As a result, I have not tried installing the new ROM yet, and was wondering if this might be causing your problem as well.

[Zaurus_Eric]

I have successfully flashed a new Sharp ROM using a Dane-Elec CF card, so they can be used without any problems.

[mroz]

I have successfully flashed a new Sharp ROM using a Dane-Elec CF card, so they can be used without any problems.

What size?

I picked up a 64MB Impact CF card the other day from <spit /> PC World, as that was the last local place to try. Never heard of the brand. It worked

As the Dane Elec 128MB card is fine in other respects, it seems unlikely the problem was with the individual unit, so I'm left wondering if size or size/brand is the issue.

Thanks for the reply

[bredroll]

well, ive put my Z up on ebay with an explination of what i tried,

ive got another one on the way, i will try to flash with the same cards that i have here, and see how i go,

then i can rule out the card size and manufacturer for these ones.

I also know that this one on its way has been flashed before using the sharp update method, me previous one was not,

wish me luck , and keep me away from /lib

:-)

[Zaurus_Eric]

As requested, the Dane-Elec CF card that I used was a 128 MB card.

[lardman]

I was going to install a new Sharp ROM, but noticed the whenever I copied the OSPACK file to the CF card it was written as ospack (lowercase).

My understanding was that FAT16 is not case sensitive and therefore it makes no odds.

The worst that will happen is that the flash won't work so just give it a go.


Si

[tumnus]

The reason could be that the flash boot loader is not as sophisticated in recognizing non-standard cards as the Linux driver which has a database for PCMCIA card types and configurations and tries several different formats.

A memory card is a memory card, regardless of the make. There are no special drivers required, unlike with WiFi and Bluetooth etc. So I doubt the make of the card is the problem.

Make sure your files are not getting corrupt and that the partition type really is FAT16, not vFAT, not FAT32, and not FAT12.

[mroz]

Been away from email a couple of days. Thanks for the response Zaurus_Eric.

A memory card is a memory card, regardless of the make. There are no special drivers required, unlike with WiFi and Bluetooth etc. So I doubt the make of the card is the problem.

Make sure your files are not getting corrupt and that the partition type really is FAT16, not vFAT, not FAT32, and not FAT12.

That certainly wasn't the issue in my case. I did try vFAT as well, but FAT16 was used & didn't work. Likewise, the files weren't corrupt as I checked md5sum. With the alternative card it worked first time.

Something odd is happening & I'd imagine it does involve the fact that different code will be being used to access the card during a reflash than during normal running.