VisorCentral.com - Visor Rom with USB

Pages (5): « 1 [2] 3 4 5 »
Show 20 posts from this thread on one page

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)

Posted by adenoid on 08-30-2000 06:11 PM:

Re: More Probs to get Rom

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

Make sure the debugger is in the "bin" directory. The "Device" subdirectory should be empty (but it has to exist for the file to be created).

Posted by hoborocks on 10-20-2000 12:29 AM:

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

Posted by rrauenza on 10-20-2000 07:05 PM:

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

Posted by nashdj on 10-25-2000 10:15 AM:

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.

Posted by sompoo on 10-25-2000 08:11 PM:

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.

Posted by Brent Dax on 10-26-2000 01:09 AM:

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?

Looking around in my Prism with Disassembler v0.6.2.1B, I've found some interesting-looking databases:

HsExtensions 3.5 (there are 2 of them!)
HsExtUIRsc
Hal (Hardware Abstraction Layer, perhaps?)
SmallROMSys
Update 3.5.2H
SmallHAL
Palm OS Data
UIAppShell

Could one (or more) of these be related to the ROM you guys are looking for?

BTW, looking around in SmallROMSys, I found a couple of interesting SysTraps: a ton of "SysTrap Hwr(Disable/Enable)DataWrite" and an odd-looking "SysTrap #953". I also noticed a lot of "or.b #$00,d0" repeating for screens at a time. Also, this SysTrap came up: "SysAppStartup". After that line, I started seeing some familiar-looking Palm API call names like "DmDatabaseInfo" and "PrefGetPreference".

SmallROMSys had only one record: "#0 @ 0x10106318, 8406 bytes".

[Edited by Brent Dax on 10-25-2000 at 08:11 PM]

__________________
<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>

Posted by nashdj on 10-26-2000 02:30 AM:

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.

Posted by Brent Dax on 10-26-2000 03:59 AM:

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.

I found the phrase "PalmCarye" (who knows?):

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

where []=an unprintable character. BTW, I am seeing large regions of nothingness, as predicted. I'm too lazy to go back and find the first one :^) but the second one starts at 0x0000458A or so. 10C00000 is in an area that shows up as a bunch of bullets in Hexdump, or **** Unreadable in Disassembly.

Also, Prism users take note: instead of a blinking cursor, the Prism's screen inverts when you enter debug mode.

[Edited by Brent Dax on 10-25-2000 at 11:04 PM]

Posted by nashdj on 10-26-2000 05:59 AM:

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

Posted by Brent Dax on 10-26-2000 06:31 AM:

PalmCard!

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

0x10100000 is the middle of an assembly command ("move.w $0006(a2),-(a7)"), and 0x10000000 is a null word--but 0x10000010 is PalmCard! :^) Thanks for the pointer (if that's what you were intending)!

BTW, it's Brent, not Bent. :^)

Posted by nashdj on 10-26-2000 09:37 AM:

Re: PalmCard!

quote:
Originally posted by Brent Dax
0x10000010 is PalmCard! :^) Thanks for the pointer (if that's what you were intending)!

BTW, it's Brent, not Bent. :^) [/B]

Great, well thats definately the rom at 0x10000000 then, so if anyone wants to give downloading it with the debugger a go.

Lol. Sorry about the name, must be my dodgy keyboard

Posted by Brent Dax on 11-02-2000 05:58 AM:

So close...

I feel like I'm really close to solving this one...I've got my Prism to this point:

code:
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
============================




======================================================
===== Welcome to the Palm OS  BigROM  Debugger!! ===== 
========= Built: Mar  6 2000, 16:40:24 (HAL) ========= 
======================================================
EXCEPTION ID = $A0
 
          1000D5C8  *MOVEQ.L   #$01,D0                                   | 7001

At that point, my Visor stops buzzing and I have to soft-reset. I'm using a USB cradle. Thoughts?

Posted by nashdj on 11-02-2000 06:14 AM:

What happens when you issue commands to the debugger after that?

Because that seems to be what should happen

Posted by Brent Dax on 11-02-2000 06:20 AM:

quote:
Originally posted by nashdj
What happens when you issue commands to the debugger after that?

Because that seems to be what should happen

Duh...My brain wasn't working right, I think. :^)

Posted by Deslock on 11-15-2000 10:00 PM:

Re: Prism ROM with USB?

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.

Do you have the newest version (3.0a7H) of the Handspring emulator? I use it with the Platinum ROM. Get it at:

http://www.handspring.com/developer...OSE_307a7H1.zip

The Handspring Developers page is:

http://www.handspring.com/developers/tech_pose.jhtml

Version 3.0a7 from http://www.palmos.com/dev/tech/tools/emulator/ would not work with the Platinum ROM (So, I assume it will not work with the Prism ROM either).

Posted by rimblas on 11-21-2000 06:08 AM:

Re: PalmCard!

quote:
Originally posted by nashdj

Great, well thats definately the rom at 0x10000000 then, so if anyone wants to give downloading it with the debugger a go.

nashdj you rock! I got my Prism ROM out.
used:
save "prism.rom" 10000000 200000

And with the new POSE (good point Deslock) it work just fine. (Nice skin)

Thank you all.

Posted by Steven Hollis on 11-27-2000 04:46 AM:

POSE works but how do I hotsync

Thanks for the info on getting POSE running on my laptop.
I have a new Visor Platinum and I got POSE running by downloading the ROM using the USB port. It works great, but
I don't exactly know how to sync my files now that it is running. I have set the preferences to usb/serial but when
I try to run hotsync on the emulator it fails to connect.
Any ideas here?

Thanks

Steve

Posted by Deslock on 11-27-2000 01:59 PM:

Re: POSE works but how do I hotsync

quote:
Originally posted by Steven Hollis
I don't exactly know how to sync my files now that it is running. I have set the preferences to usb/serial but when
I try to run hotsync on the emulator it fails to connect.

I'm not sure how to Hotsync (I've never bothered trying it). However, to install files on the emulator, simply drag them onto it in Windows. Or, right click on the Emulator and choose "Install Application/Database".

[Edited by Deslock on 11-27-2000 at 09:04 AM]

Posted by dfinberg on 11-28-2000 12:57 AM:

Hotsync'ing is pretty easy, but a bit convoluted to set up.

If you have a serial cable and two free serial ports, you can run the cable from one to the other and do a (serial) sync that way. Otherwise you do a network sync.

Make sure the hotsync conduit is running with network enabled, and that the user you want to hotsync has your pc set up as its primary pc.

under setting,properties in POSE click the redirect to
tcp/ip button. Open the hotsync app. set modem is set to network, lansync to lansync, fill in the info on primary pc name (use 127.0.0.1 if you don't have an ip). Finally you
need to configure a connection. Just enter 00 for the
phone number.

That's it, modem sync should work.

Posted by jimboh on 12-04-2000 09:10 AM:

Hi folks,
I am not having success downloading the ROM from my Visor. It has 2MB of memory and has Palm OS v.3.1H2 running. I am following NASHDJ's outlined procedure. The shortcut to get the unit into debug mode works fine with the buzzing and blinking square up in the corner. I am running the debugger on the pc from C:\Handspring\prc-tools\bin\Palm-Debugger.exe and have the empty '...bin\Device' directory ready and waiting! The connection setting has been set for USB. I also tried disabling the Hotsync program on the Win98 explorer toolbar in case it might interfere with the debugger program but it doesn't seem to make a difference. Here's a screen dump of my results from starting the debugger and issuing the 'save' command.

//Debugger
******************************
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
============================
'save "visor.rom" 10c00000 200000'
$73617665 #1935767141 #1935767141 'save'

I'm not seeing the percentage counter come up at all. Also, when I try the "reset" command to return Visor from debug mode there is no response so I'm having to do the soft reset with the ol' paperclip. It seems like I'm not getting a connection over the USB but I have no problems Hotsync'ing with the USB port I'm using. Any clues as to how I may be screwing this up? I just downloaded the Falch.net IDE and am psyched to start learning to use it but I need to get over this hurdle first. TIA, ~Jim

All times are GMT. The time now is 08:08 PM.

Pages (5): « 1 [2] 3 4 5 »
Show 20 posts from this thread on one page