FRAM71B

[Erwin]

(01-22-2017 05:30 PM)Dave Frederickson Wrote:  

(01-22-2017 10:18 AM)Erwin Wrote:  You can try this with POKE "2C012"; "109100" and then try to FREE it.

Hi Erwin,

This is interesting. The problem appears to be with F-Block 0 as it can't be FREEPORT'ed either and I suspect this affects all subsequent Chips.

I think you found a bug, or at least a caveat. This could be why it is advised to use F-Blocks 0 and 1 last.

(01-22-2017 02:02 PM)Erwin Wrote:  maybe some could use it too - regards Erwin

I'm not sure if this program is useful anymore. Per a note by Joe Horn on my copy of the ROMCOPY doc, "Checksums are fully automatic in Rev. E".

Note that this program is for computing IRAM checksums in preparation for creating a ROM image. ROM chips all have checksums of "01".

Code:

>titanchk datacq.bin
TITAN ROM Test V1.10
Unpacking data...
ROM Chip 1 = 01 -> Ok
ROM Chip 2 = 01 -> Ok
ROM Chip 3 = 01 -> Ok
ROM Chip 4 = 01 -> Ok
Checksum(s) ok!

Regards Dave

Hi Dave,

do you tried out similar configurations with the FRAMB? About the R64KCOPY I think we talk about different programs? The result with the program I did with the DATA-ACQ ROM module in SLOT 1 - my workaround for the FRAMB configuration :-)

Code:

LEX3421  78008
BIN3421  7BAED  7542.5
TCONV    7BDE6  7923.0
FMTLEX   7BFF1  8184.5
KEYSLEEP 7C4BF  8799.5
MERGEBUF 7C55F  8879.5
UTILITY  7C9CE  9447.0
STATUS   7E676 13115.0
FRONT    801E9 16628.5
CK1      816B3 19289.5
STRIP    816E8 19316.0
MONITOR  859D4 27882.0
CK2      8B72E 39831.0
SETUP    8B763 39857.5
LOG      90325 49554.5
REPORT   93676 56123.0
TRANSFER 9637D 61886.5
VERIFY   97608 64260.0
csum 1:     30 LEX3421 
csum 2:  33279 FRONT   
csum 3:  79684 CK2     
csum 4: 128542 VERIFY

I think its necessary for the old version of ROMCOPY.

regards
Erwin