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 ?

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

Re: More Probs to get Rom

quote:

---

Originally posted by Sepp
I created c:\Handspring\PalmTools\bin\Device put the debugger in this directory

---

Registered: Oct 2000
Location:
Posts: 1

Visor ROM download

For some reason, I get this:

Initializing parser...
Initializing lex...
Installing keywords...
Initializing eval...
Initializing exec...
Loading startup script...
CmdRunScript: error opening file UserStartup-PalmDebugger
============================
DebOut = false
SymbolsOn = true
StepRegs = false
ReadMemHack = false
Attached = false
............................
dot address = 00000000
last address = 00000000
last count = 00000000
============================

Can someone please explain what I can do about the error?

Chris Johns

Registered: Oct 2000
Location:
Posts: 2

Prism ROM with USB?

I've tried the posted method of downloading the
Visor ROM, but it doesn't seem to work with
my Handspring Prism.

The ROM that was downloaded was claimed invalid by
the emulator -- and when I looked at it, it looks
like mostly random memory. It is mostly (in hex)
"00 45 00 45 00 45 ..." I tried using the debugger
to find 'ROM Store' in memory, but it couldn't
find anything that looked like a ROM. [Other
ROM's I've looked at have that string.]

So is the 10C00000 ROM address different on the
Prism? Or is there some kind of memory trick going on?

Rich

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

Wow, havent been here for a while :-)

rrauenza: That seems really werid, as far as I know pretty much every palmOS device has followed that kind of memory map.

Possibly there may be some debugger changes in 3.5,

Try a seach on palmgear.com for "Disassembler v0.6.3 0.6.3", install that app and take a look around the memory. If it is at 10C00000 then it's most likely a debugger issue.

Registered: Oct 2000
Location:
Posts: 1

I have some problem about palmdebugger. My version is v3.5. this below is in my debugger. I choose connection to USB and set my visor to debug mode already. How can i solve this problem ???

Initializing parser...
Initializing lex...
Installing keywords...
Initializing eval...
Initializing exec...
Loading startup script...
CmdRunScript: error opening file UserStartup-PalmDebugger
============================
DebOut = false
SymbolsOn = true
StepRegs = false
ReadMemHack = false
Attached = false
............................
dot address = 00000000
last address = 00000000
last count = 00000000
============================
"debugger"
"debugger"
save "visor.rom" 10c00000 200000
Error: not attached to remote.

Registered: Jul 2000
Location: Southern California, USA
Posts: 41

Re: Prism ROM with USB?

(Disclaimer: I don't know Assembly, and probably never will.)

quote:

---

Originally posted by rrauenza
I've tried the posted method of downloading the
Visor ROM, but it doesn't seem to work with
my Handspring Prism.

The ROM that was downloaded was claimed invalid by
the emulator -- and when I looked at it, it looks
like mostly random memory. It is mostly (in hex)
"00 45 00 45 00 45 ..." I tried using the debugger
to find 'ROM Store' in memory, but it couldn't
find anything that looked like a ROM. [Other
ROM's I've looked at have that string.]

So is the 10C00000 ROM address different on the
Prism? Or is there some kind of memory trick going on?

---

__________________
<img src="http://www.handspring.com/products/visorprism/images/PrsmLgPct02.jpg" align="left" width="115" height="115">Brent Dax
[email protected]

Visor Prism, USB recharging cradle, Win2K
I wish I could post from AvantGo...

<B><-- Cobalt Blue is really cool!</B>

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

sompoo:
CmdRunScript: error opening file UserStartup-PalmDebugger <- this probably isnt the cause of the problem, but it is an error none the less, there should be a file called "UserStartup-Palm Debugger" in the handspring/palmtools/bin directory. From what you posted it would seem either the visor is not entering debug mode (are you sure it is, do you have the constant irritating buzz sound?), or there is some connection problem. Other than that it should "just work".

Brent:
If you really want to crawl around in there :) Change to hexdump mode and take a look for "PalmCard", the start of the rom is 16 bytes before that. You will also find that the or.b "00d0" are simply "0000000" in hex, just unused space.


Ok, now for those who are interested (anybody?). And because rrauenza just informed me that the rom is not where it should be :).
Let me just show how the Visor memory is laid out.

00000000
- (8mb of ram)
00800000
- Void of nothingness :)
10C00000
- (2mb of rom)
10E00000
- More void of nothingness
1FFFFFFF
- (8 mb of ram) this is where the ram really is, 0-008... is just a mirror of this.
20800000

Ok, so there is a lot more than that (traps, registers, etc..) but thats all we really need to know right now.

Simplest way I can think of to locate just where th prism rom "actuall is", is to just look at the locations of the databases that are stored in the rom. Like the ones Brent mentioned. So right now I would be inclined to think that it is at either 0x10100000 or simply 0x10000000.

Registered: Jul 2000
Location: Southern California, USA
Posts: 41

quote:

---

Originally posted by nashdj

Brent:
If you really want to crawl around in there :) Change to hexdump mode and take a look for "PalmCard", the start of the rom is 16 bytes before that. You will also find that the or.b "00d0" are simply "0000000" in hex, just unused space.

---

code:

0x00002A06
----------
06  4600 0008 5061 6C6D  F[][][]Palm
0E  4361 7279 6500 0000  Carye[][][]

__________________
<img src="http://www.handspring.com/products/visorprism/images/PrsmLgPct02.jpg" align="left" width="115" height="115">Brent Dax
[email protected]

Visor Prism, USB recharging cradle, Win2K
I wish I could post from AvantGo...

<B><-- Cobalt Blue is really cool!</B>

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

Bent:
What comes up at 0x10100000 and 0x10000000?

Registered: Jul 2000
Location: Southern California, USA
Posts: 41

PalmCard!

quote:

---

Originally posted by nashdj
Bent:
What comes up at 0x10100000 and 0x10000000?

---

__________________
<img src="http://www.handspring.com/products/visorprism/images/PrsmLgPct02.jpg" align="left" width="115" height="115">Brent Dax
[email protected]

Visor Prism, USB recharging cradle, Win2K
I wish I could post from AvantGo...

<B><-- Cobalt Blue is really cool!</B>