(SOLVED) 41CL - DOUBLE HEPAX ACCESS and MMU CONFIG

[Monte Dalrymple]

(08-17-2019 02:22 PM)Sylvain Cote Wrote:  Notes:

1. An XR of -- means there is not FAT for the ROM
2. Error in document cl_memory.pdf (2018-12-26), page 32, configuration table: [PLUG: 9INF], [Page: F] should be FRMX and not FRML
3. Error in document mem_xref.pdf (2019-07-31), page 12, CITY XROM should be 30 and not 18
4. There are duplicate XROM in 9SCI => [XROM:17 > NONL & EPTC]
5. There are duplicate XROM in 9ELE => [XROM:10 > ETS5 & UNIT] and [XROM:15 > YFNX & EENG]
6. There are duplicate XROM in 9MEC => [XROM:12 > ETS3 & MCHN]
7. There are duplicate XROM in 9MAP => [XROM:30 > METX & CITY]
   

edit: typo

I could have sworn that I checked these when I got them from 'Angel, but apparently not. I'll have to figure out which ones to remove and release a new version of YFNF in the next Flash update.

I tried using CHKXROM in YFNX on one of these collisions and it didn't report a conflict like it's supposed to, so there if a bug somewhere in that function. Something else to look into.