Post Reply 
The HP-71 and the Ubiquitous Binary File
08-15-2020, 06:58 PM (This post was last modified: 08-15-2020 07:24 PM by Dave Frederickson.)
Post: #4
RE: The HP-71 and the Ubiquitous Binary File
(08-15-2020 04:19 PM)J-F Garnier Wrote:  So (from my point of view), the presence [or] not of the IRAM identifier (the first 8 nibbles) is not a good criteria to identify a ROM image.

That contradicts the IDS.

3.6.2 Stand Alone Module ID
The Stand Alone Module ID field is used to distinguish an Independent RAM from other forms of memory modules. For Independent RAMs, this field has the hex value B3DDDDDE. For ROMs and all other forms of memory modules, this field may have any value except the IRAM value.

So the IDS explicitly states that a ROM may not have the Stand Alone Module ID although I suspect that is only for checksum purposes.

Regarding ROMCOPY, this program is intended for creating ROM images from an IRAM. When the image is created ROMCOPY generates the checksums and places them in the image as specified in the ROMCOPY doc. For IRAM and EPROM images the CMT TOOLS include a variation of ROMCOPY called EPRMCPY. The difference is EPRMCPY doesn't remove the Stand Alone Module ID nor add checksums when creating an image.

If you consider images with the Stand Alone Module ID to be ROM images then those images will FAIL TitanChk and the Service Module ROM test. Rather, following the IDS breaks nothing.

Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: The HP-71 and the Ubiquitous Binary File - Dave Frederickson - 08-15-2020 06:58 PM

User(s) browsing this thread: 1 Guest(s)