Using emulator 3.0a5 and CW 6.0 with latest PalmOS 3.5 SDK, using the
release Palm VII,OS 3.2,non-debug,non-ez,english ROM
I want to do some low level poking around to see how things work, and have run into
some random strangeness when viewing memory.
Pick any old project and get into debug mode and open a view memory window.
Set the address to 0x0
Why are the first 16 bytes blank? There should be _something_ there.
In particular, what's the reset vector?
Set the address to 0xFFFA00 or 0xFFFFFA00. I expect one of these
to hold the contents of the LSSA register, but all I see is FFFFFFFF.
I _know_ this is wrong. This used to work on older emulators (I think).
How do I look at the dragonball register contents? (Spare me the "you
shouldn't do that" lecture, I'm interested in a greater understanding of
what's going on, not proper software engineering technique).
Set the address to 0x10C00000. I expect to see the contents of the flash
ram here. However, what I see here differs from what I see when I open
the .ROM file in a binary editor. In particular, the first 16 bytes are all
00 in CW. Also, starting at 0x10C00100 I see a whole bunch of FF
Set the address to 0x10C10000. Surprise! we see the start of the flash
again. Still, the first 16 bytes are wrong, but at least we're not all FF after
0x10C10100. I didn't expect this at all. I expected to see the second
64K bytes of flash here, not the first 64K repeated.
Set the address to 0x10D70000. Why are the 16 bytes here all 00 ?
In the ROM file they contain valid text.
What's going on here?
--
Adam Wozniak
Senior Software Design Engineer
Surveyor Corporation
4501 Orcutt Rd.
San Luis Obispo, CA 93401
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
