-
Notifications
You must be signed in to change notification settings - Fork 5
Clean ROM images
Until this specific hardware existed for reading Newton "N2" platform ROMs, images of ROMs were obtained by using Hammer to read the ROM-backed memory space. These images are not correct representations of what is stored in the ROM chips though. Hammer reads memory through the MMU, so virtual memory addresses are used, not physical.
In the N2 platform, there is a 4K page of memory at Virt 0x1000
that is mapped to Phys 0x40DE000
. This is the parameter block and is actually backed by RAM. In particular, this block contains bits that control debugging features of the ROM, some of which are set by Hammer when it connects to the system. Therefore, ROM images created in this method may have debugging bits "baked in" to the data.
Though Einstein clears this data when it loads a ROM image, it means that ROM images made in this manner are unsuitable for compiling a list of known good ROM images and their hashes.
This list is intended to be a definitive list of Clean ROM images: images created by reading the ROM board directly.
Device | Model | Language | Major/Minor | Revision | Size | SHA1 |
---|---|---|---|---|---|---|
MessagePad 2000 | DVT | |||||
MessagePad 2000 | EVT | |||||
MessagePad 2x00 | production | DE | 2.1 | 747129 | 8388608 | d2b8371a11cc94252d7e64052bcd11d78ba0a6ac |
MessagePad 2100 | production | EN | 2.1 | 717006 | 8388608 | ? |
eMate 300 | production | EN | 2.2 | 737041 | 8388608 | c89279bfb241d91dc6eaaa5fd43e9a60279f8543 |
Watson | production | FR | 2.2 | 8388608 |
Model is to indicate whether the ROM board came from a prototype, DVT, EVT, or production model.
Size is in bytes