kazzo cnrom overdump

Discuss hardware-related topics, such as development cartridges, CopyNES, PowerPak, EPROMs, or whatever.

Moderator: Moderators

Post Reply
Pickle
Posts: 14
Joined: Sat Jul 04, 2015 9:08 am

kazzo cnrom overdump

Post by Pickle »

ive got 2 cnrom carts that give runable roms but the chr only works at the 8000 size. The carts should only need 4000, but any time i change the ppu size kazzo reports the data is all 0xFF's. Id like to get get clean matching roms according to the bootgod database.
Anybody have any idea what is wrong?

Two games in question are:
Banana: http://bootgod.dyndns.org:7777/profile.php?id=2690
Bird Week: http://bootgod.dyndns.org:7777/profile.php?id=1262

I have noticed bird week is odd with the security bit and is set to mapper 185

Edit: Ive had some success on my own. I dont if these would be the proper way, but they work.

Bird Week:

Code: Select all

board <- {
  mappernum = 185,
  cpu_rom = {
    size_base = 0x8000, size_max = 0x8000, banksize = 0x8000
  },
  ppu_rom = {
    size_base = 0x2000, size_max = 0x2000, banksize = 0x2000
  },
  ppu_ramfind = false, vram_mirrorfind = true		
};
function cpu_dump(d, pagesize, banksize)
{
	cpu_read(d, 0x8000, 0x4000);
	cpu_read(d, 0xc000, 0x4000);
}
function ppu_dump(d, pagesize, banksize)
{
		cpu_write(d, 0x8000, 3);
		ppu_read(d, 0, banksize);
}
Banana:

I can almost get a perfect dump by using:
I dont see the same pixel errors on my famicom, so i think the cart is good.

Code: Select all

function ppu_dump(d, pagesize, banksize)
{
		cpu_write(d, 0x8000, 2);
		ppu_read(d, 0, banksize);	
	
		cpu_write(d, 0x8000, 3);
		ppu_read(d, 0, banksize);
}
Edit 2:

So the banana pcb has the diodes and i confirmed my cart diode config matches boot god' image:

http://bootgod.dyndns.org:7777/image.php?ImageID=7953

Ive tried 0,1,2,3 for those diode bits when writing to 0x8000, but the same random noise appears. Its usually the most significant bit.
So a clean rom might have 0x00 and ill get 0x80. The PRG is always good so the game runs, but ill get pixel glitches in the chr images.
Can anyone confirm that diode layout number? Since they alternate i expects it either 1 or 2. But since neither changes the output i dont know what im missing.
Pins 51 and 51 do look exposed on the trace slighty, but theres no burnt marks and they look ok. If i had a trace issue id expect it always wrong giving vertical stripes (ive seen that with one cart before and fixed it)
Post Reply