[FRAM71] Pre-Production Batch

[J-F Garnier]

(12-20-2014 08:34 PM)Dave Frederickson Wrote:  

(12-20-2014 07:15 PM)J-F Garnier Wrote:  Changing the module type from IRAM to ROM without precautions can produce several side effects and strange errors...

I believe we're looking at two different situations here. The first has to do with copying ROM images to a FRAM71 IRAM and the difference between leaving the memory configured as IRAM or reconfiguring it as ROM. The second situation is what you describe which is to create a ROM image. In that case ROMCOPY is the correct method as it creates an image with the proper checksums.

Yes, you're right, my comment was unclear. It is perfectly correct to load a ROM image (with ROMCOPY) in IRAM then change the module type to ROM. This is what I'm used to do also in Emu71.
My comment was about using the ROM type to protect a IRAM built manually by program entry or normal COPY.
Note that this has to do not only with wrong checksum (that will not harm in normal use), but with Basic programs 'compiling' - actually the right term here is 'chaining', meaning the calculations of the GOTO/GOSUB targets.