So I think I already know the answer, but I'll put this out anyway, to get more insight.
Over the weekend, I burned a NROM to eproms and my Willem verified them as good; used 27c256s for both (4xCHR bin). Then I tested them on my socketed cart and the program seemed to work, but thinking back I was too hasty because there were a few bad/wrong tiles that I wrote off to a bad cart edge connection.
So today I transferred the eproms to a ReproPak board. The program itself runs fine but the CHR issue with the tiles remains. Maybe 6 or 7 bad tiles that show up at the same spots after a powercycle; so bad data or bad hardware?
What gets me is the Willem verified the eprom as good, I assume it's just a bad device; was a pull from god knows where. Or could this be an issue with the split .nes; I used a web page version of readNES that will pad the bin as needed, http://www.kevinselwyn.com/ReadNES/. I've used it before and it seemed to work fine, but I haven't compared the output from two different runs. Can someone recommend a free Hex editor that can compare two bin files?
I'm going to burn the same image to different chips and test on the devCart, a bad bin should be apparent if the errors are the same on both carts.
Yogi
Over the weekend, I burned a NROM to eproms and my Willem verified them as good; used 27c256s for both (4xCHR bin). Then I tested them on my socketed cart and the program seemed to work, but thinking back I was too hasty because there were a few bad/wrong tiles that I wrote off to a bad cart edge connection.
So today I transferred the eproms to a ReproPak board. The program itself runs fine but the CHR issue with the tiles remains. Maybe 6 or 7 bad tiles that show up at the same spots after a powercycle; so bad data or bad hardware?
What gets me is the Willem verified the eprom as good, I assume it's just a bad device; was a pull from god knows where. Or could this be an issue with the split .nes; I used a web page version of readNES that will pad the bin as needed, http://www.kevinselwyn.com/ReadNES/. I've used it before and it seemed to work fine, but I haven't compared the output from two different runs. Can someone recommend a free Hex editor that can compare two bin files?
I'm going to burn the same image to different chips and test on the devCart, a bad bin should be apparent if the errors are the same on both carts.
Yogi