Help - Search - Members - Calendar
Full Version: flashing rom on SL 5500 - get blinking lights
OESF Portables Forum > General Forums > General Discussion
loup-noir
I'm attempting to flash back the rom from 3.10 to 2.12 or 2.38, I have backed up, etc., I put the ospack image on to the root of a CF card (PQI 256Mb), put the CF card into the slot (with the machine off), then hold down C+D and push the full reset button.

The two LED's blink and the rom does not upgrade. When I check the CF card via Win98 (yeah I know, I must get it converted to linux) it says the card has a FAT filesystem and the card has never been formatted (ie has original filesystem from purchase)

Anybody got any clues as to what to try next? I've read loads of stuff and can't find anything I'm doing wrong.

Thanks - L.

PS the upgrade from 2.12 to 3.10 was via Sharp supplied PC software and went swimmingly
Greg2
I would reformat the cf-card on the Z to vfat (fat16) to be sure of a good file system. If you don't have a terminal install one, then:

# su
# umount /dev/hda1
# mkfs.vfat /dev/hda1
# mount /dev/hda1 /mnt/cf
# exit

remove card and use your windows box to place Ospack (not ospack) file on card then flash as per instructions

Greg
loup-noir
Thanks for the advice, but still no joy. I have reformated the card as per your notes, placed the Ospack file and checked under the Z console to ensure it saw the correct name -Ospack (don't trust Windoze naming). Then took the CF card back to the Win98 machine and removed the extra directories added in by the Z before following the flash instructions. Still get blinking lights.

I am getting a little frazzled now. I'm beginning to suspect the CF card although it has been reformated correctly and running the File Manager tests on it seem to work. Suggestions on a CF card that has worked to flash the OS anyone?

Thanks again
L.
DrWily
Do your C and D keys work properly? I know I had problems with getting them held down just right when I flashed the 40 Zaurii that came my way.
Greg2
QUOTE
PS the upgrade from 2.12 to 3.10 was via Sharp supplied PC software and went swimmingly

loup-noir

Last year I wanted to make an old jeode.ipk and I had problems retuning to rom v2.38 but successfully flashed v2.37 (don't know why?). Maybe this is your problem, so here is the link to myzaurus.com with instructions and link for v2.37 at the bottom of page:
http://www.myzaurus.com/ROMupdate3.asp

And be sure you are only pressing C + D on reset

Greg
loup-noir
Many thanks for the continued suggestions. Alas so far with no success.

I have downloaded the 2.37 ROM and transferred the Ospack file (verifying the file name, etc) and I have made up a small piece of wood (how sad is that!) to exactly cover the C and D keys on the keyboard to ensure that those keys and no others are pressed. I am still getting the blinking lights. When I'm pressing the keys there are two distinct clicks - one for each key so I think it's ok.

Not sure if I said earlier, but I have also tried zImage and initrd.bin from OZ, but with the same results - LED's flash.

I'm still thinking that the next step is to buy a 32 or 64 MB CF card to try - a recommended mfgr would be helpful. The reason I'm flashing back is that the Socket Ethernet card I have doesn't work under 3.10 and this is to confirm that it is a driver issue with the OS.

Thanks again
L.
Greg2
You are using the AC adapter throughout the flash, aren't you?

I've used Lexar, Sandisk and Kodak CF-cards without problems. There is a more complete list of tested cards but I can't find it now, just do a search on the ZUG for CF-cards.

Greg
loup-noir
Yes I am using the AC adapter throughout. Something else I might try is using ROMIMAGE or OSPACK for the name. There seems to be some reference to using these filenames way back in the mists of time. That will give me something to do today. Monday I'll try for a 64 Mb card of one of the above types

L.
loup-noir
There is no joy in Mudville . . .

I have now got a Lexar 64Mb CF card and for each of 2.12, 2.37, and 2.38 ROM's done the following:

1. Plug in Z to mains adapter not on the cradle.
2. Copy the Ospack file to the Lexar card via a card reader.
3. Put the CF card in the Z and check that the file name is Ospack
4. Put the card back in the card reader and remove all files/dirs except Ospack
5. fully extend the keyboard
6. take the cover off the battery
8. put in the CF card
9. using the special gadget (see post above), hold down the c and d keys (so only c and d are being held down)
10. press the full reset button once using the stylus
11. Admire the blinking LED's before pressing the full reset again and starting on the next ROM.

If anyone can see any mistakes in the above please let me know.

Thanks L.
Greg2
OK....you have already tried the initrd.bin and zImage method. So you might try to clear the memory by a full reset of 5 to 10 seconds and removing the battery for about 2 hours. Have your Ospack file ready on your CF-card before the reset so you are ready to flash.

There were some threads about this on the Dev/Net but you can't do a search for them on the mirror. This may be of some help:
http://www.zaurususergroup.com/modules.php...ing%20The%20ROM

Good luck

Greg
loup-noir
Once more them blinking lights. The procedure was . . .

1. Plug in Z to mains adapter not on the cradle.
2. Copy the Ospack file to the Lexar card via a card reader (for Sharp ROM 2.12).
3. Put the CF card in the Z and check that the file name is Ospack
4. Put the card back in the card reader and remove all files/dirs except Ospack
5. Open the battery compartment on the Z (no cards in it)
6. disconnect from extl power
7. push down the full reset for 10 secs and remove battery at the end of this with reset button still pressed down
8. leave Z for 24 hours
9. connect to AC power (battery light started blinking which was different)
10. put in CF card
11. put in battery
12. press C and D and full reset
13. lights blink on mail and battery
14. do another full reset and it comes up 3.10

Taking a sideways look at this, there is an update ROM button on the settings panel, but I can't find any documentation about how this is to be used with the 5500. Ive tried to go forward with it, but it can't find an image to flash to and I don't know where it's looking. Is this a possibility? Has anyone tried this on a 5500?

Thanks
L.
loup-noir
PS going to be away for 2 weeks (with a Z with no network card) - L.
Greg2
I think that your step #4 might be a problem, you don't have to do that.

QUOTE
Taking a sideways look at this, there is  an update ROM button on the settings panel, but I can't find any documentation about how this is to be used with the 5500.  Ive tried to go forward with it, but it can't find an image to flash to and I don't know where it's looking.   Is this a possibility?  Has anyone tried this on a 5500?


I've never done it that way but here is the file you need with instructions:
https://www.oesf.org/commu...html?group_id=5

Greg
Greg2
That file should be highlighted but if not it's version 3.13 and you can upgrade with your update button.

Good luck again

Greg
loup-noir
Have just spoken to a very nice man on the Sharp tel support line who has said the the ROM will not update to a previous release and that the instructions given on the web-site to flash back usually don't work!

Can people confirm that he's right or alternatively say that he's wrong (as in you have done this yourself?)

Thanks v. much L.
tecknobabble
QUOTE
Have just spoken to a very nice man on the Sharp tel support line who has said the  the ROM will not update to a previous release and that the instructions given on the web-site to flash back usually don't work!

Can people confirm that he's right or alternatively say that he's wrong (as in you have done this yourself?)

But even if that's right you should be able to flash the latest version available... but I think he's confused and searching for an explanation for why it doesn't work.... otherwise how can people flash OZ, tkcROM, etc...

Is the CF card being written from Windows or Linux....? I can't remember for sure but I think I had problems sometimes when I used mine under windows.

Do you have anyway to confirm the md5sum of the files you've written to the CF card match those on the PC before the transfer? That would at least factor out the card reader as part of the problem.

zImage and initrd is preferrable to the OSPACK - won't overwrite the routine in the ROM that does the loading.... which isn't a problem unless something goes wrong writing that portion of the ROM.
Greg2
QUOTE
Can people confirm that he's right or alternatively say that he's wrong (as in you have done this yourself?)

loup-noir

As I said before I could only return to v2.37 and that was done to make a jeode.ipk that would work with whatever rom I was using. I don't remember if it was an oz version or sharp-based rom but it can be done. Although I didn't flash back to v2.37 from a standard sharp rom version.

You said you couldn't flash the initrd.bin and zImage of OZ before, have you tried that or any other custom rom image?

Greg
Greg2
Just a thought...why don't you go ahead and upgrade to v3.13 then try your ethernet card?

Here's a list of the ones that work (it's not up to date) if it's not there you might be able to make it work anyhow. Someone here will help.

Ethernet Card Support:
http://www.zaurususergroup.com/modules.php...rnetCardSupport

Greg
markw
It alsways blinks for me when i flash the ROM, however i just try it again a few times and it usually workes. you might want to try redownloading the ROM update (unless you got it off a CD), and trying flashing the roma few more times.
derekp
One other thing that I've seen people do:
If you are writing the files out to the CF card from a windows host, and then remove the card without clicking on the Windows "eject" icon, then you WILL have filesystem corruption on the card, which will result in a bad flash. If this is the case, then:
1. chkdsk /f drive: (where drive is e:, f:, or whatever your CF card is mounted as)
2. copy files over to the card again, and make sure you hit the eject (or media removal) icon in the windows taskbar

Hope this helps.
Joshp
I know on my laptop that was running windows 2000. I had to make sure that I ejected the cf card before I removed it form the pcmcia slot. If I did not the files that I had just copyed would not work right. Is there any way for you to conferm that files are ok after you remove the cf card form the card reader? And also I have never used the Ospack. Because form what I'v heard if something gos worng, wall lets just say the Z would make a nice paper wight, dont you think? If you have access to a linux box, try exctering initrd.bin and zimage form the ospack puting them on your cf card and flashing with them.

JP
loup-noir
Finally recovered from the holiday.

I was hoping someone could say definitedly yes they have flashed backwards from one Sharp ROM to a previous or no they could not.

I've also heard from Socket (who are prepared to commit to email) but they are saying that the card works with the ROM /ROM emulator provided by Sharp and so it is a Sharp issue - Socket say they are going to raise it with Sharp.

My next step will probably by to go to 3.13 to give it a whirl (just in case) and then to try to flash to another ROM with a view to flashing back to a previous Sharp version (or not if the other ROM suffices)

One question - is there a way to do md5checksums under windoze? (and for that matter under UNIX/Z? And I don't recall seeing the md5checksums on the Sharp site - are they listed there or is there another source?

Thanks
L
khafra
This probably won't help, but I have the exact same blinking light problem, trying to upgrade from 2.38 to OZ. Sharp 3.10 does the same thing when I try it. I've repartitioned and reformatted the CF card, checked for bad blocks, tried over and over again--nothing seems to make it do anything but blink indefinitely, then restart with the same old 2.38 rom.
Xaser
Well, Im not so sure if that could help but I had found this points when I had similar trouble....
1) Check that your CF is NOT READ ONLY set (In my case with TKCrom 1 if I USE the applet to UNMOUNT the CF or SD, the rom without asking nothing, simply set the card to READ ONLY mode and with this I had troubles with reflashing...)
2) Use the Zinergy ROM v1 that is based in 2.xx rom as a dummy flash ( when I need to do some tests with 2.38 I first reflash with this old Zinergy rom and then reflash with the original sharp rom 2.38 without troubles, but I was unable to do this using directly the original sharp 2.38...) I didnt know why this work for me but anyway, if you need a 2.xx sharp rom based the zimergy v1 is very nice option...
khafra
Well, I got my problem with those same symptoms fixed (sort of). Despite all diagnostics saying the CF card was fine, I went out and got another, just a cheap li'l used 16 meg one, and tried to flash the OZ rom. It worked.
When I say "worked," I mean I get the OpenZaurus splash screen now when I turn it on. Unfortunately, I get nothing beyond that. But at least I have something.
Qman
I just flashed back from 3.10 to 2.38 using the CF method just yesterday (05/04/04) without any problems then flashed to 3.13 after that using the same method!




HTH
Qman....
Qman
QUOTE
I'm attempting to flash back the rom from 3.10 to 2.12 or 2.38, I have backed up, etc., I put the ospack image on to the root of a CF card (PQI 256Mb), put the CF card into the slot (with the machine off), then hold down C+D and push the full reset button.


I'm not sure if it makes any difference but I had put my CF card in the device with it on.



HTH
Qman...
zbones
QUOTE
I'm not sure if it makes any difference but I had put my CF card in the device with it on.


That shouldn't matter, I always insert my card with the device off so those iritating directories don't get auto created.

I always do a fresh format in my PC using a card reader and have (touch wood) never had an issue with flashing a rom yet.

The cf card does make a big difference, some cards that work ok in the z cannot be used to flash the device, don't know why. Also never try to flash from a microdrive. I have read several posts from people who have bricked their unit like that. Again I don't know why, it just is that way.

Peter
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2019 Invision Power Services, Inc.