Bought Untested... Who knows... GX477 is Shaolins Road
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 7, 2023 #1 Bought Untested... Who knows... GX477 is Shaolins Road
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 7, 2023 #2 Dumped ROMs using Minipro... maincpu and gfx2 ROMs match MAME definitions; gfx1 do NOT match! Curious. These are mine... Code: 0ffb9cfe3737c2b4f842b57607550a656b013d66 *A10_K06.BIN 973baf8f815e6be8ef74d3065cdb9e7079a1efc5 *A11_K07.BIN a9da783b29a63a46912a29715e8d11dc4cd22265 *D10_L04.BIN 52d098386fe87ae97d4dfefab0bd3a902f66d70b *D11_L05.BIN 70a9d81b73bbd4ff6b627a3e4102d5328a946d20 *D9_L03.BIN 97d276099172975499f646f381a6fc587c022435 *H14_K01.BIN 65ae48134a0fe1e910a787714f7ae721734ded5b *H15_K02.BIN Ran MAME with downloaded versions and appears OK. Assuming they are OK, just a variant. Last edited: Apr 7, 2023
Dumped ROMs using Minipro... maincpu and gfx2 ROMs match MAME definitions; gfx1 do NOT match! Curious. These are mine... Code: 0ffb9cfe3737c2b4f842b57607550a656b013d66 *A10_K06.BIN 973baf8f815e6be8ef74d3065cdb9e7079a1efc5 *A11_K07.BIN a9da783b29a63a46912a29715e8d11dc4cd22265 *D10_L04.BIN 52d098386fe87ae97d4dfefab0bd3a902f66d70b *D11_L05.BIN 70a9d81b73bbd4ff6b627a3e4102d5328a946d20 *D9_L03.BIN 97d276099172975499f646f381a6fc587c022435 *H14_K01.BIN 65ae48134a0fe1e910a787714f7ae721734ded5b *H15_K02.BIN Ran MAME with downloaded versions and appears OK. Assuming they are OK, just a variant.
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 7, 2023 #3 Well this is a bit disappointing... it just seems to work.
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 7, 2023 #4 This is intriguing... So the MAME definition is... Code: ROM_REGION( 0x4000, "gfx1", 0 ) ROM_LOAD( "477-k06.a10", 0x0000, 0x2000, CRC(4d156afc) SHA1(29eb66e2ebcf2f1c1d5ece5413d1ebf54663f9cf) ) ROM_LOAD( "477-k07.a11", 0x2000, 0x2000, CRC(ff6ca5df) SHA1(dfcd445c8b233a0a4168eb249472e53784eda25d) ) and the kicker.zip for MAME contains 8K images at A10 and A11. On my PCB I have are 27128 ROMs at A10 and A11 i.e. 16K ROMs.... if you look closely these ROMs have the same 8K content repeated twice and the checksum of the first (or second) 8K matches that of MAME. Weird... it's almost like A13 were not significant for these two ROMs!
This is intriguing... So the MAME definition is... Code: ROM_REGION( 0x4000, "gfx1", 0 ) ROM_LOAD( "477-k06.a10", 0x0000, 0x2000, CRC(4d156afc) SHA1(29eb66e2ebcf2f1c1d5ece5413d1ebf54663f9cf) ) ROM_LOAD( "477-k07.a11", 0x2000, 0x2000, CRC(ff6ca5df) SHA1(dfcd445c8b233a0a4168eb249472e53784eda25d) ) and the kicker.zip for MAME contains 8K images at A10 and A11. On my PCB I have are 27128 ROMs at A10 and A11 i.e. 16K ROMs.... if you look closely these ROMs have the same 8K content repeated twice and the checksum of the first (or second) 8K matches that of MAME. Weird... it's almost like A13 were not significant for these two ROMs!
cliff_poole Active member vacBacker Feedback 6 (100%) Credits 1,069CR Apr 8, 2023 #5 Konami often used mask ROMs in this era. Maybe they switched to EPROMs after the boards were made.
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 8, 2023 #6 My point was more it has decoding for 16K bytes but only 8K content rather than the technology of the device. It could use one less address line than is actually implemented.
My point was more it has decoding for 16K bytes but only 8K content rather than the technology of the device. It could use one less address line than is actually implemented.
N NivagSwerdna Active member Feedback 1 (100%) Credits 744CR Apr 10, 2023 #7 I just realised the K1 at E7 isn't a K1... It has 40pins... just a 6809E I think.