VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Visor Rom with USB - HOWTO (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=4884)

Victorious getting the Treo 270 rom...

I feel like Tom Hanks in Castaway when he made fire... I downloaded the Treo 270 rom from my handheld!

The Treo 270 rom is 4096K. I used a utility called SyncWizard to succesfully download the ROM from my handheld, and now it works perfectly in POSE. I am a happy camper!

I'm not sure what the new offsets are for using the Debugger method described in this thread, though. It's much easier to just use SyncWizard to get the rom anyway...

Sync Wizard worked for me too on Neo

I used it to grab the ROM of my Neo...but the ROM image using POSE 3.5 under Metrowerks 3.1 bombs though.

Trying to use the setup to develop an application for the barcode scanning module by Symbol, the CSM150.

Visor Rom with USB - HOWTO

Initializing parser...
Initializing lex...
Installing keywords...
Initializing eval...
Initializing exec...
Loading startup script...
============================
DebOut = false
SymbolsOn = true
StepRegs = false
ReadMemHack = false
Attached = false
............................
dot address = 00000000
last address = 00000000
last count = 00000000
............................
MemMode: normal
acc: indirect (call device if possible)
============================
Serial line error.
Serial line error.
Serial line error.
Serial line error.
Serial line error.
Serial line error.

I receive this error while trying to download the visor Deluxe Rom.
This error appears also when HotSync is running besides the debugger. If I turn the debug mode on in my visor and put it in the USB craddle then the error won't stop until I took it out of it. A reset is then the only possibility to make my visor run again.
Any Idea?

I have tried everything

1. Download the files (didnt find Tools Patch although I search all the Handspring site)
2. Install the files cygwin and GNUTools
3. Start the debugger
4. Put the Handheld in the craddle
5. Type the shorcut thing.
6. It worked! The annoying sound and the flashing sqare came out.
7. Trouble starts. Dont see the Welcome to the PalmOS Debugger! etc, etc, text in the debugger
8. I dont give up and type:
save "visor.rom" 10c00000 200000
and even
save "visor.rom" 10c00000 800000
Both lines returned: Error: not attached to remote
9. I still dont give up and change the USB cable and try in the other 3 USB ports and do all again from scratch.
10. Success? NO, I still dont get the caonnection

So my question:
Is that Tools_Patch really necesary to make this thing work out?
I downloaded the files today so maybe the Tools_Patch is not available because the other 2 files are updated with the Tools_Patch in it.
If you think Im wrong and that I really need this Tools_Patch, can you please let me know its exact location? I really cant find it.

In other case, isnt there a ROM file available anywhere in the Internet? Why dont they (Handspring) simply publish the ROM files and make people live their lives easier.

Im trying all this on a Win2000 Server machine and the ROM file Im desperately trying to get is from my handheld which is a Visor Deluxe with 8MB

Thanks in advance for your help

I forgot to mention in my last post that the Hotsync tool woks great in every USB port I tried.

Thanks again in advance

I can't have the ROM

When I open the Debugger, when I make the dot-dot-1, whan I make the "save "visor.rom" 10c00000 200000 ", nothing happened=> my cradle is ok, I disable all my ackmaster...

Why I don't have any response except "Error: not attached to remote."

Thank you


Zizou

It seems that Microsoft ActiveSync wants to grap a possible device's attention before the debugger does.
I was receiving the "not attached" situation myself with the Treo.

I deactivated all connection types in Microsoft ActiveSync (so that it has a small "x" overlay), and then using the debugger worked!

Might help out...

(oddly, just closing Microsoft ActiveSync doesn't do the trick.)

bump

__________________
<IMG WIDTH="200" HEIGHT="50" SRC=http://www.visorcentral.com/images/visorcentral.gif> VisorCentral Discussion Moderator
Do files get embarrassed when they get unzipped?

bump (ouch!)

__________________

God bless America, my home sweet home...

rom tansfer linux usb

i tried
pi-getrom /dev/pilot visor.rom

grab the image and i get a fatal error
what is that, would it be connection speed related?

i found that i can put palm debugger to any folder but you should have "device" folder under it to make it working

Ok under WinXP I get the following:

Initializing parser...
Initializing lex...
Installing keywords...
Initializing eval...
Initializing exec...
Loading startup script...
============================
DebOut = false
SymbolsOn = true
StepRegs = false
ReadMemHack = false
Attached = false
............................
dot address = 00000000
last address = 00000000
last count = 00000000
............................
MemMode: normal
acc: indirect (call device if possible)
============================
Serial line error.
Serial line error.
Serial line error.
Serial line error.
Serial line error.
Serial line error.
Serial line error.


I remember in Win98 I extracted the ROm fine, but now I don't have 98 anymore and I need to extract my ROM for development.

Did anyone fix the Win2K/WinXP issue as discussed in this thread?

I own a visor edge.

I first could not get the rom by following previous explanation.

Then I tried the palm_debugger_treo90 which worked BUT then the rom would not work with POSE (handspring version). I just had the verbose error message "dying like a dog"...

Then I download again the stuff from handpsring and this time the usual debugger worked but POSE keep continuing on dying like a dog nightmare..

Finally I download evaluation version of
SyncWizard. And it worked !!!!!
It's very easy to do it.
When I looked at the rom file, the size is 4MB not 2MB ! So It might work with palm_debugger if you enter 400000 instead of 200000.

Hope it will help someone.
Thanks for everything.

precision

Hi Guys,
Thanks for this how-to. I just wanted to mention that the steps described only work if Palm Desktop 4.1 is installed. I think that this should be aded to the how-to since Hanspring doesnt install the USBPort.dll which is absolutely necessary for the this to work.
Guy

I was getting the "Serial line error." message from the debugger on my WinXP system also, but SyncWizard did it with no problems.