It is currently Mon Nov 20, 2017 5:00 am

All times are UTC - 7 hours





Post new topic Reply to topic  [ 52 posts ]  Go to page Previous  1, 2, 3, 4  Next
Author Message
PostPosted: Wed Oct 11, 2017 9:10 pm 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
lidnariq wrote:
You ... could try this?

cpu_write(d, 0xF800 | (i & 31) | ((i << 4) & 0x200) | (i << 2) & 0x100), i);

There's this problem that iNES only really handles the notion of contiguous memory. However, that assumption isn't true for either the known mapper 235 hardware, and is also unlikely for yours.

The known mapper 235 hardware has only ROMs #s "0" and "2", but the iNES dump stores them contiguously. So we can try doing the same reordering—the above line will dump the ROMs in the order of 0,2,1,3 ...

You could also PM me the image you have and I can tell you if the dump worked at all.


Hummm, no chance.

Any ideas? I am open to try anything ! I will do some search also on my side.


Top
 Profile  
 
PostPosted: Wed Oct 11, 2017 9:14 pm 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6446
Location: UK (temporarily)
One first difficulty:
* This board has a diode that detects when user is pressing the reset button, and changes what bank is present at that time. I don't know if the Kazzo correctly drives its outputs to keep this from getting in the way, but if it doesn't, then modifying the board to support this will be required.

Other than that, there's basically two ways forward:

* Actually trace the connectivity of the parts on the board. Go back to what I said earlier, and use a multimeter or continuity meter to figure out what connects to what. I can write a Kazoo script for whatever that turns out to be.

* Send someone the first 32 KiB dump that you got, which is almost certainly the menu. It is likely possible to deduce what hardware the menu expects is present based on the contents.


Top
 Profile  
 
PostPosted: Fri Oct 13, 2017 6:06 am 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
lidnariq wrote:
One first difficulty:
* This board has a diode that detects when user is pressing the reset button, and changes what bank is present at that time. I don't know if the Kazzo correctly drives its outputs to keep this from getting in the way, but if it doesn't, then modifying the board to support this will be required.

Other than that, there's basically two ways forward:

* Actually trace the connectivity of the parts on the board. Go back to what I said earlier, and use a multimeter or continuity meter to figure out what connects to what. I can write a Kazoo script for whatever that turns out to be.

* Send someone the first 32 KiB dump that you got, which is almost certainly the menu. It is likely possible to deduce what hardware the menu expects is present based on the contents.

Will do. I will try to identify which pin goes to which pin and which chip.

I seems I have the same PCB than the 1001-in-1 multicart : http://justinpaulin.com/tag/pirate-carts/


Top
 Profile  
 
PostPosted: Sat Oct 14, 2017 12:01 pm 
Offline

Joined: Sun Jun 12, 2011 12:06 pm
Posts: 245
Location: Poland
https://forums.nesdev.com/viewtopic.php?f=9&t=9866


Top
 Profile  
 
PostPosted: Sat Oct 14, 2017 12:08 pm 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6446
Location: UK (temporarily)
Hm, well, then we could try
cpu_write(d, 0xFC00 | (i & 31) | ((i << 4) & 0x200) | ((i << 2) & 0x100), i);


Nevermind, toggling the 0x400s bit wouldn't help; only the nametable modes change between krzsiobal's board and m235

It's so very close to m235 but just enough different... there may not be a mapper for it.


Last edited by lidnariq on Sat Oct 14, 2017 5:34 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Sat Oct 14, 2017 4:55 pm 
Offline
User avatar

Joined: Wed Apr 07, 2010 12:46 pm
Posts: 6
Location: Poland
labatt24 wrote:
Dwedit wrote:
The real question is what actual games are on it?

It's a 700-in-1 special games exactly like the 260-in-1.


Does the cartridge has this label?

Image

_________________
ContraBanda.eu


Top
 Profile  
 
PostPosted: Mon Oct 16, 2017 5:12 am 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
krzysiobal wrote:
https://forums.nesdev.com/viewtopic.php?f=9&t=9866

Hummmm, it's pretty much the same cart !


Top
 Profile  
 
PostPosted: Mon Oct 16, 2017 5:14 am 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
MWK wrote:
labatt24 wrote:
Dwedit wrote:
The real question is what actual games are on it?

It's a 700-in-1 special games exactly like the 260-in-1.


Does the cartridge has this label?

Image

Nope, I don't have the original case. 15 years ago, I remember we changed the case because the original was broken (threw it on the floor by accident).


Top
 Profile  
 
PostPosted: Mon Oct 16, 2017 8:10 am 
Offline

Joined: Sun Sep 19, 2004 11:12 pm
Posts: 19233
Location: NE Indiana, USA (NTSC)
labatt24 wrote:
15 years ago, I remember we changed [a pirate multicart's] case because the original was broken (threw it on the floor by accident).

I guess that's one way to tell a pirate cart: Official Game Paks are Tonka Tough.


Top
 Profile  
 
PostPosted: Mon Oct 16, 2017 11:29 am 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6446
Location: UK (temporarily)
Since the m235 earlier dumper script should have worked to produce an accurate (if non functional) image, the only real question is whether you got a valid dump.

If you have a hex editor or similar, you could check if the entire file is the same 16 KiB repeated over and over.

If you don't have a hex editor, you could try just compressing the resultant 4 MiB image using zip or 7zip or rar or something. If the result is tiny (like, 16 KiB-ish) then that also indicates that the file contains a gazillion repeats of the same data.

If the entire file indicates the file is the same repeated 16 KiB over and over, then you'll either need to temporarily disable the reset detection circuit, or maybe there's a way to tell Kazoo/Anago/Unagi to drive M2.

We still would need to figure out how to encapsulate this image; with multiple noncontiguous ROMs it's a particularly bad mismatch to the iNES format.


Top
 Profile  
 
PostPosted: Sun Oct 29, 2017 6:25 pm 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
lidnariq wrote:
I swear I've seen those big silkscreened "MK008" and "MK009" somewhere else recently, but I can't remember where.

Since it's a pirate multicart, it'll probably need a custom kazoo script. Given that the only hardware on the board is two 74'174s, a 74'139, and a 74'153, it'll be pretty easy to reverse-engineer it even without knowing what mapper it corresponds to.

Ideally, we'll find that "MK008" ROM somewhere in a thread and be able to write—or maybe even find already existing—the kazoo script from that data.

BUT IF WE CAN'T: this board is simple enough that we know approximately how it's going to work: Twelve of the pins on the two '174s are going to connect to the card edge; two will go to the 74'153, and the other ten will go to the three ROMs. Sitting down with a multimeter and determining what pins connect to what pins will let us tell you exactly what the hardware is doing, and then write a script from that.



Alright, I did a conductivity test on the board. Some pins seems not having conductivity or are connected to the PINS cart. Please tell me if something seems wrong on my readings. The first 9122VG (174) is the first starting at the left of the cart (front picture of the cart).

9122VG (174)

PIN1 : PIN1 of 2nd 174
PIN2 : PIN1 of EPROM, PIN3 of MK009 & PIN3 of MK008
PIN3 : PIN10 of EPROM, PIN12 of MK009, PIN12 of MK008
PIN4 : PIN9 of EPROM, PIN11 of MK009 & PIN11 of MK008
PIN5 : PIN2 of MK009 & PIN2 of MK008
PIN6 : PIN8 of EPROM, PIN10 of MK009 & PIN10 of MK008
PIN7 : PIN30 of MK009 & PIN30 of MK008
PIN8 : PIN16 of EPROM, PIN16 of MK009 & PIN16 of MK008, PIN14 of HY6264P, PIN 8 & 15 of 139, PIN8 of 2nd 174, PIN 8 & 15 of 153
PIN9 : PIN5 of 139, PIN9 of 2nd 174
PIN10 : PIN31 of MK009, PIN31 of MK008
PIN11 : PIN9 of MK009, PIN9 of MK008
PIN12 : PIN1 of MK009. PIN1 of MK008
PIN13 : PIN8 of MK009, PIN8 of MK008
PIN14 : PIN7 of MK009, PIN7 of MK008
PIN15 : NONE
PIN16 : PIN32 of MK009, PIN32 of MK008, PIN1, 26 & 28 of HY6264P, PIN16 of 139, PIN16 of 2nd 174, PIN16 of 153

9138 (139)

PIN1 : CART PIN
PIN2 : PIN32 of MK009, PIN32 of MK008, PIN1, 26 & 28 of HY6264P
PIN3 : CART CONNECTOR
PIN4 : NONE
PIN5 : PIN9 of both 174
PIN6 : NONE
PIN7 : PIN24 of MK009, PIN24 of MK008
PIN8 : PIN16 of MK009, PIN16 of MK008, PIN14 of HY6264P, PIN8 of both 174, PIN8 & 15 of 153.
PIN9 : PIN20 EPPROM
PIN10 : NONE
PIN11 : PIN22 of MK009
PIN12 : PIN22 of MK008
PIN13 : PIN5 of 2nd 274
PIN14 : PIN2 of 2nd 174
PIN15 : PIN14 of EPROM, PIN8 of 1st 174, PIN16 of MK009, PIN16 of MK008, PIN14 of HY6264P, PIN8 of 2nd 174, PIN8 & 15 of 153
PIN16 : PIN16 of both 174, PIN16 of 153, PIN32 of MK009, PIN32 of MK008, PIN1 & 26 & 28 of HY6264P

9122VG (174)

PIN1 : NONE
PIN2 : PIN14 of 139
PIN3 : PIN25 of EPPROM, PIN27 of MK009, PIN27 of MK008
PIN4 : PIN24 EPPROM, PIN26 of MK009, PIN26 of MK008
PIN5 : PIN13 of 139
PIN6 : PIN21 of EPPROM, PIN23 of MK009, PIN23 of MK008
PIN7 : NONE
PIN8 : PIN14 of EPPROM,PIN16 of MK009, PIN16 of MK008, PIN14 of HY6264P, PIN8 & PIN15 of 139, PIN8 & PIN15 of 153
PIN9 : PIN9 of 1st 174, PIN5 of 139
PIN10 : PIN14 of 9128
PIN11 : PIN22 of EPPROM, PIN25 of MK009, PIN25 of MK008
PIN12 : PIN11 & PIN13 of 153
PIN13 : PIN2 of EPROM, PIN4 of MK009, PIN4 of MK008
PIN14 : PIN26 of EPROM, PIN28 of MK009, PIN28 of MK008
PIN15 : NONE
PIN16 : PIN1 of both 174, PIN1 of 139, PIN1 of 153, PIN28 of EPROM, PIN32 of MK009, PIN32 of MK008, PIN1, PIN26 & 28 of HY6264P

9128 (153)

PIN1 : PIN7 of 2nd 174
PIN2 : PIN15 of 2nd 174
PIN3 : PIN23 of HY6264P
PIN4 : PIN23 of HY6264P
PIN5 : PIN21 of HY6264P
PIN6 : PIN21 of HY6264P
PIN7 : CART PIN
PIN8 : PIN8 of 1st 174, PIN15 of 139, PIN8 of 2nd 174, PIN14 of EPROM, PIN16 of MK009, PIN16 of MK008, PIN14 of HY6264P
PIN9 : PIN27 of EPROM, PIN29 of MK009, PIN29 of MK008
PIN10 : NONE
PIN11 : PIN12 of 2nd 174
PIN12 : NONE
PIN13 : PIN12 of 2nd 174
PIN14 : PIN10 of 2nd 174
PIN15 : PIN8 of both 174, PIN8 of 139, PIN14 of EPROM, PIN16 of MK009, PIN16 of MK008, PIN14 of HY2624P
PIN16 : PIN16 of both 174, PIN16 of 139, PIN28 of EPROM, PIN32 of MK009, PIN32 of MK008, PIN1, 26 & 28 of HY2624P


Top
 Profile  
 
PostPosted: Sun Oct 29, 2017 8:28 pm 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6446
Location: UK (temporarily)
That's definitely "just" mapper an instance of the same hardware that's on 235. The existing dumping scripts should work... as long as the Kazzo is keeping the "clear the registers" pin from resetting things.

Did you ever look at the resulting file you got with a hex editor or something? If you have a bad dump, it should obviously repeat every 16 or 32 KiB. And you'll probably need to remove the resistor?

If you have a good dump, we may need to figure out how to adjust things in an emulator so that your multicart can be run correctly.


Top
 Profile  
 
PostPosted: Mon Oct 30, 2017 10:25 am 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
lidnariq wrote:
That's definitely "just" mapper an instance of the same hardware that's on 235. The existing dumping scripts should work... as long as the Kazzo is keeping the "clear the registers" pin from resetting things.

Did you ever look at the resulting file you got with a hex editor or something? If you have a bad dump, it should obviously repeat every 16 or 32 KiB. And you'll probably need to remove the resistor?

If you have a good dump, we may need to figure out how to adjust things in an emulator so that your multicart can be run correctly.


I will try this as soon as I can !

Regarding the resistor, it is that thing? (See attachment) Do I need to just desolder one pin and try to dump? Do I need to desolder the resistor itself and solder something else to keep the conductivity of the circuit?


Attachments:
Resistor.PNG
Resistor.PNG [ 420.81 KiB | Viewed 140 times ]
Top
 Profile  
 
PostPosted: Mon Oct 30, 2017 11:11 am 
Offline

Joined: Sun Apr 13, 2008 11:12 am
Posts: 6446
Location: UK (temporarily)
labatt24 wrote:
Regarding the resistor, it is that thing? (See attachment) Do I need to just desolder one pin and try to dump? Do I need to desolder the resistor itself and solder something else to keep the conductivity of the circuit?
The circuitry there should look something like:
Code:
M2 --|>|---+-+--- both 74ls174 pin 1
           | |
           C R
           | |
           gnd
If so, removing the resistor (desoldering one side is fine) should let the dumper work correctly. (the cartridge won't go back to the menu when you press the reset button until you resolder it)


Top
 Profile  
 
PostPosted: Tue Oct 31, 2017 3:50 pm 
Offline

Joined: Thu Oct 05, 2017 5:20 am
Posts: 26
lidnariq wrote:
labatt24 wrote:
Regarding the resistor, it is that thing? (See attachment) Do I need to just desolder one pin and try to dump? Do I need to desolder the resistor itself and solder something else to keep the conductivity of the circuit?
The circuitry there should look something like:
Code:
M2 --|>|---+-+--- both 74ls174 pin 1
           | |
           C R
           | |
           gnd
If so, removing the resistor (desoldering one side is fine) should let the dumper work correctly. (the cartridge won't go back to the menu when you press the reset button until you resolder it)

Alright, I removed one side of the resistor. I tried a dump (4MB) and no chance. Here in attachment the first 32kib of the dump using the very first script you gave me.

Do you think I need to remove one side of the diode also?


Attachments:
700-in.1_32kib.zip [284 Bytes]
Downloaded 4 times
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 52 posts ]  Go to page Previous  1, 2, 3, 4  Next

All times are UTC - 7 hours


Who is online

Users browsing this forum: No registered users and 13 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group