Threaded Mode | Linear Mode

Christoph Giesselink · 03-12-2017, 09:40 PM

(03-09-2017 08:50 PM)Dave Frederickson Wrote: Here's the detailed procedure:

Code:

1. Dump the EPROM using the procedure in the Emu71/Win manual. a. Connect the PIL-Box and run ILPer. b. Enter the example dump routine for the HPIL ROM. Substitute the name of the first file in the EPROM for "HPILROM" in line 20. c. Execute DISPLAY IS :1 d. Run the program. This should produce 2048 64-nibble lines in the printer area. e. Copy and paste the dump to a text file named EPROM.txt f. Convert the text file to a binary file using DMP2ROM from the Filetool package on the PC Utilities webpage. Execute DMP2ROM EPROM.txt EPROM.bin. g. Verify the dump using TITANCHK from the Emu71/Win webpage. Execute TITANCHK EPROM.bin. 2. Convert the ROM image to an IRAM image. a. Open EPROM.bin using a hex editor. b. Overwrite the first 4 bytes of the file with the IRAM identifier "B3DDDDDE". This is also called the Stand Alone Module ID in the IDS. 3. Load the IRAM image into Emu71/Win. a. Run Emu71/Win. b. Edit the Port Configuration and add a 64K RAM module to Port1. c. Turn on the emulator and execute FREEPORT(1) to create an IRAM. d. Turn off the emulator. e. Open then Port Configuration window for Port1, select the RAM device and right-click. f. Select Load Memory Data... and open EPROM.bin g. Turn on the emulator and CAT :PORT(1). You should see the EPROM catalog. 4. Remove the file protection. a. Execute UNSECURE filename where filename is one of the protected files b. Using UNPRIV LEX from LEXFL1 in the SWAP archive, execute UNPRIV filename. c. Repeat a-b for all protected files

Dave

From my long experience dumping ROM images some additions to Dave's part 1.

As Dave told earlier, some ROM's are protected. This ROM's cannot be read with the build in PEEK$ command. To fix this, replace the internal POKE and PEEK$ command by installing the POKELEX file. This replace the POKE and PEEK$ commands by a version don't care about any protections.

But how to get the size and name of the image?

In my example I plugged in the JPC ROM into PORT slot 3:

With SHOW PORT

>SHOW PORT
0.05 16384 2
3 32768 2
4 16384 2
0 4096 0
0.01 4096 0
0.02 4096 0
0.03 4096 0
2 32768 0

I see that the module in slot 3 has a size of 32768 bytes (=32KB).

With CAT :PORT(3)

>CAT :PORT(3)
NAME S TYPE LEN DATE TIME PORT
JPCF05 LEX 25992 02/26/17 20:54 3

I see that the name of the 1st file is "JPCF05".

Insert this information into the ROMDMP BASIC program:

>LIST
10 DIM A$[64]
20 A=IP(HTD(ADDR$("JPCF05"))/256)*256 ! start address of JPC ROM to transfer
30 FOR I=0 TO 32*32-1 ! length of ROM (here for 32Kb)
40 A$=PEEK$(DTH$(A+I*64),64)
50 OUTPUT :1 ;A$
60 NEXT I

RUN the program:

>RUN
B3DDDDDEA405346403530202802E00450262207151BC01E10F6F05C00000E804
A0DE00611D14327520924957B2EB27F25630931A3495144CA4025D25D45E5549
...

A LIF image with

>PCAT :HD
ROMCOPY LEX 1727 02/14/11 19:08
POKELEX LEX 257 02/14/11 19:08
ROMDMP BASIC 168 02/14/11 19:08

ROMCOPY, POKELEX and the BASIC ROM dumping template ROMDMP is attached.

Don't forget to save the unmodified file EPROM.bin after step 1.g. to a safe place. This is the original image code of the module manufacturer which should exactly behave like the original ROM.

To the result of the

"g. Verify the dump using TITANCHK from the Emu71/Win webpage. Execute TITANCHK EPROM.bin."

step. All modules sold by HP, I checked so far, had correct checksum(s). If 3rd party manufactures really added correct checksums to there image depends on the manufacturer. A valid checksum is not necessary for a proper operation of the module. So the JPC ROM's from the Paris chapter have no valid checksum inside.

BTW, SLOAD until v3.0.9 from the HPTOOLS package has a bug the linker option "CHecksum <Symbol name> <Hex addr> <Hex addr>". If <Symbol name> pointing to an odd address, the calculated checksum is wrong. The bug has been fixed in the original SVN repository at 2010-08-03, so further releases of the package should not contain this bug any more.

Finally, there's an easier method in Emu71/Win to add an IRAM image to the memory configuration

Referring to the Emu71/Win manual 9.1.1.2.2 Combo box "Size"

you can choose "Datafile" at top of the RAM size list instead of choosing the RAM size itself and enter the name IRAM image name EPROM.bin in the Filename section. This creates a RAM module with the neceassary size from the IRAM image and finally load the image into the allocated memory.

This replace the steps

b. Edit the Port Configuration and add a 64K RAM module to Port1.
c. Turn on the emulator and execute FREEPORT(1) to create an IRAM.
e. Open then Port Configuration window for Port1, select the RAM device and right-click.
f. Select Load Memory Data... and open EPROM.bin