[FRAM71] Pre-Production Batch

[Dave Frederickson]

The FRAM71 manual has some important notes at the end of the Memory Configuration chapter. Note 6 states that memory for ROM images should be configured the same as the physical module. 32k ROM's, like the Math ROM, are comprised of 2-16k ROM's. That means that a FRAM71 Chip shouldn't be configured as a single 32k ROM. While this appears to work, the Diag ROM reports a checksum error with the Math ROM configured this way.
Firmware v430 sports a new feature allowing the same FRAM address space to be assigned to multiple chips. It should be possible to configure one 32k block of FRAM as two 16k ROM's, in accordance with Note 6.

When the config string is set to "24A4" the setting DISPLAY IS PRINTER is lost. Restoring the setting:

Code:

>SHOWPORT
0.05  16384  2
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0
5     32768  0

This appears to configure the Chip as Port(5) as required. The Diag ROM reports 2-32k nibbles of RAM at 0x30000 as expected.

Code:

>FREEPORT(5)
0.05  16384  2
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0
5     32768  0

Port(5) didn't get freed. Not giving up, yet.

Code:

>POKE"2C000","A4A4"
>SHOWPORT
0.05  16384  2
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0
5     16384  0
5.01  16384  0
>FREEPORT(5)
>SHOWPORT
0.05  16384  2
5     16384  1
5.01  16384  1
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0

Two ports freed with one command. Wasn't expecting that behavior.

Code:

>POKE"2C000","24A4"
>SHOWPORT
0.05  16384  2
5     32768  1
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0

Okay. There is now a 32k IRAM comprised of 2-16k RAM's. The Diag ROM reports the port as 2-32k nibble RAM's and the P/I RAM test passes both RAM's.
DISPLAY IS again had to be reassigned.

Code:

>SHOWPORT
0.05  16384  2
5     32768  1
0      4096  0
0.01   4096  0
0.02   4096  0
0.03   4096  0
>
>COPY ROMCOPY:TAPE
>ROMCOPY MATHROM:TAPE TO :PORT(5)
ERR:Device Not Found
>CLAIMPORT(5)
ERR:Device Not Found

Now the port isn't being detected. Can't to get this new feature to work.

Dave