Registered: Jan 2000
Location: Brisbane, Australia
Posts: 22

Ok following kevinsk's post (page 4, post 3) I think this needs to be as clean and simple as possible. The following process is for the Visor, Visor Dx, and Visor Platinum, if you have a prism please see the section below in common problems.

HotSync first. Probably also a good idea to disable any hacks you have running.

Download and install the Handspring SDK. Make sure that in the directory where you find "palm-debugger.exe" usually "Handspring\PalmTools\bin\" possibly now "Handspring\prc-tools\bin\" that a subdirectory called "device" also exists. This is where the rom will be placed by the debugger.

Launch PalmDebugger "Handspring\PalmTools\bin\palm-debugger.exe". In the Connections menu select USB. Exit and restart the debugger.

Sit the visor in the cradle.

Turn the visor on and write Shortcut - dot - dot - 1
(In other words the shortcut symbol not the slash the squiggly one (cursive lowercase L), two dots to make a period, and a 1). You should hear an annoying buzz sound, and at the top left of the screen there should be a flashing square.

In the debugger window you should see something similar to the following appear
======================================================
Welcome to the PalmOS Debugger!
Built: Dec 18 1998, 15:50:23, Target 6, Rev 3
======================================================
or
======================================================
===== Welcome to the Palm OS BigROM Debugger!! =====
========= Built: Mar 6 2000, 16:40:24 (HAL) =========
======================================================
This may be different depending on the type of visor you have, or when its revision was released. Dont worry that it might say Exception ID xxx, this is just the debuggers way of telling you that the visor wanted to connect to the debugger.

This puts the visor into debug mode, through which it can communicate with the debugger. Inside the debugger window you should see something like "Welcome to the PalmOS Debugger!", a compilation date, and an exception message. If that didnt happen, something is not right, chech that you did select USB and that your connections are all ok.

Now, in Palm-Debugger's "Debugger" window type the following.
save "visor.rom" 10c00000 200000 (enter)

A percentage counter should appear - when this reaches 100% it should print the following. #2097152 bytes saved from address $10C00000 to file "visor.rom"

If you get this far you have now saved the visors rom to a file on your computer. Look for it in the "Device" subdirectory of the directory from which you ran palm-debugger.

Type reset in the debugger window, or perform a soft reset on the device to leave debug mode.

Launch POSE (make sure to slect the nice visor skin) and begin to develop some cool visor apps.




Common Problems:

Problem:
"CmdRunScript: error opening file ..\Libraries\Net\Scripts\NetDebug" seen in the debugger window on load.

Solution:
Ignore this, it is only an error loading debugger routines, none of which need be used in transferring the rom.


Problem:
"Shortcut - dot - dot - 1" fails to achieve the flashing cursor or buzzing sound.

Solution:
Check that you dont have any hacks installed that might have rewritten the shortcut commands, things like jot. In a post by frasej his solution was to perform a hard reset on the device. Check that the shortcut you are drawing is the cursive lowercase L, and not the standard slash.


Problem:
CmdSaveFile: error creating file visor.rom
###Error saving memory to file, exiting

Solution:
Make sure that in the directory where palm-debugger.exe resides, there is also a directory called "device", if not then the debugger cant work out where to save the rom image.


Problem:
Error: not attached to remote.

Solution:
The device has not entered debug mode, check that you have selected USB as the connection method, that all your cables are in place, and that you are correctly entering the command to enter debug mode on the visor.


Problem:
"$73617665 #1935767141 #1935767141 'save'", or similar displayed after typing the save command.

Solution:
I used to have single quotes around the save command, DO NOT TYPE THE SINGLE QUOTES


Problem:
The above method does not work using a Prism.... I'm not entirely convinced of this, can someone try both methods and get back to me?

Solution:
Strangely the memory map of a prism is different. The rom is located at memory address 10000000. Due to this you must use the following save command
save "visor.rom" 10000000 200000 (enter)


Problem:
Downloaded rom does not work with the emulator.

Solution:
Download the latest version of teh emulator from handsprings website.


Problem:
Cannot find The handspring SDK.

Solution:
From kevinsk (page 4, post 3).
NOTE: You may need to register as a developer with Handspring to access the following links.

First go to http://www.handspring.com/developers/sw_dev.jhtml
and download the Handspring PalmOS GNU Tools consisting of three components:
1. Cygwin
2. PalmOSGnuTools
3. Tools Patch

Also download HandspringHeaders35Win.exe.

Install the three components in the order listed accepting the default install dirs for Cygwin and PalmOSGnuTools. Once the Tools_Patch zip is extracted copy the new headers to the appropriate directories as instructed in the readme. Now run HandspringHeaders35Win.exe to update the headers in the Handspring directory.

-- note from nashdj, Cygwin is not required for the rom transfer, nor is it *really* required in order to build applications, if anyone is interested in a very simple howto for building palm apps the *easiest possible way* let me know


Problem:
Cannot find the Emulator, or the downloaded rom will not work with the emulator.

Solution
From kevinsk (page 4, post 3).
http://www.handspring.com/developers/tech_pose.jhtml
Here you will find a links for the handspring version of POSE (the emulator). Get the file POSE_307a7H1.zip and extract it anywhere you like. Optionally get POSE_307a7H1_Src.zip for the source if interested.


Problem:
Running Linux? Ok so this is a good thing, not a problem.

Solution:
Use the pilot-link tools, avaliable almost everywhere, or try http://pilot-link.sourceforge.net/ there is a pi-getrom tool, I wont go into detail so check the docs. For those with debian, apt-get install pilot-link couldn't be easier. You will also need to setup the USB connection, for more information on this check http://milosch.net/visor/.


Yes everyone, I was bored this morning

[Edited by nashdj on 01-21-2001 at 07:00 PM]

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

This seems to work fine. I tested this from the emulator itself which the debugger also supports as a "connection".

The above instructions are for a 2mb standard model Visor. If you have a Deluxe with 8mb - you need to change the save command to the following:

save "visor.rom" 10c00000 800000

------------------
MarkEagle - Ice is nice!


[This message has been edited by MarkEagle (edited 04-23-2000).]

Registered: Jan 2000
Location: Brisbane, Australia
Posts: 22

Actually the above is for *any* visor. It downloads the rom (not ram), which itself is 2mb.

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

Hmmm... I must be losing it. You're right about the ROM vs RAM issue. I think I'll go play in traffic now.

------------------
MarkEagle - Ice is nice!

Registered: Dec 1999
Location:
Posts: 103

Do you know if this works under Win2K?

------------------
Jay

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

quote:

---

Originally posted by frasej:
Do you know if this works under Win2K?

---

Registered: Dec 1999
Location:
Posts: 103

Under Win2K nothing happens. Under Win98 I get a "Device not connected" error. When I start up Palm-Debugger this is what is in the debugger window:
Initializing parser...
Initializing lex...
Installing keywords...
Initializing eval...
Initializing exec...
Loading startup script...
CmdRunScript: error opening file ..\Libraries\Net\Scripts\NetDebug
There were errors.
============================
DebOut = false
SymbolsOn = true
StepRegs = false
ReadMemHack = false
Attached = false
............................
dot address = 00000000
last address = 00000000
last count = 00000000
============================

Notice the error. Could this be my problem and if so, where do I find this file?

------------------
Jay

Registered: Jan 2000
Location: Brisbane, Australia
Posts: 22

Well that error shouldnt be the cause - my reasons being that I get it too and it still works fine.

As for win2k I'm not sure, but its probably likely that there is some incompatability.

When you enter debug mode on the visor, you do hear a tone and then see a flashing cursor at the top left?

Registered: Dec 1999
Location:
Posts: 103

No, I don't get any of that. I'm doing the shortcut symbol, dot dot and 1. Every thing that gets written on the screen from that entry is removed, but nothing else happens.

------------------
Jay

Registered: Dec 1999
Location:
Posts: 103

Follow up to my last post. A hard reset restored my shortcuts. I had a program which removed all of the built-in shortcuts. That's why I didn't get the flashing dot and really annoying buzz. Still doesn't work under Win2K, so I'll check at home tonight with Win98. Thanks for the help.

------------------
Jay

Registered: Aug 2000
Location: Reading, MA
Posts: 28

For those who don't bother to read the
debugger manual, you may need to do a
"att" command to connect the debugger to
the visor. Took me a while to figure that out.

Thanks for the info.

Registered: Aug 2000
Location:
Posts: 2

What is the shortcut command? I tried a lowercase "L", but that did not work. What am I missing? What are the graffiti steps for the shortcut command?

Registered: Jul 2000
Location:
Posts: 3034

quote:

---

Originally posted by MountainDew:
What is the shortcut command? I tried a lowercase "L", but that did not work. What am I missing? What are the graffiti steps for the shortcut command?

---

Registered: Aug 2000
Location:
Posts: 2

I tried to connect with my Visor deluxe using the shortcut ang got following in Palmdebug.exe

Welcome to the PalmOS Debugger!
Built: Dec 18 1998, 15:50:23, Target 6, Rev 3
===============================================================
EXCEPTION ID = $F4

CAn anyone help me ?
'PrvHandleEvent'
+$062C 1000F2F2 *MOVEQ.L #$01,D0

Registered: Aug 2000
Location:
Posts: 2

I had the same results. I'm not sure what to do to fix it...

Registered: Jun 2000
Location: Seattle, WA, USA
Posts: 22

Short answer:

Create this exact path on your PC

c:\Handspring\PalmTools\bin\Device

Put the emulator in the "bin" directory. Then try it again.

Registered: Aug 2000
Location:
Posts: 1

Good job figuring this piece of junk out adenoid.

To clarify from what Adenoid said. Put the debugger (latest version from Handspring) in the c:\Handspring\PalmTools\bin directory and make sure c:\Handspring\PalmTools\bin\Device is a valid directory.

I did this and the download worked.

[email protected]

Registered: Jul 2000
Location: Ireland
Posts: 1

Hi,
I was able to use the pilot-link tools to get the rom over the usb link. I used the rom file with the latest pose under linux and it goes fine. The pose did not seem to pick up the visor skins :-(, even with the POSER_DIR set?

Registered: Nov 1999
Location: West Lafayette
Posts: 4

Skins

If you want POSE to use visor's skin, just download it from handsprings site, unzip and place in a directory whose name begins in Skins. The skins directory should be in the same directory that POSE is in. Detailed instructions are in one of the docs included with POSE.

Registered: Aug 2000
Location:
Posts: 2

More Probs to get Rom

I created c:\Handspring\PalmTools\bin\Device put the debugger in this directory and tried fooling command:
save "visor.rom" 10c00000 800000

Result was:
CmdSaveFile: error creating file visor.rom

###Error saving memory to file, exiting

Who can help me please ?