Sounds more like an internal fault related to your n64. What happens with other cartridge games? The 64drive led will show dimly for about 100ms (barely long enough to notice) and then fast extremely quickly for about 200ms. Any activity past that is cart bus activity, normally you see a certain pat...
CIC problems always result in a unrecoverable hang. Since it comes back, I'm inclined to think it is your expansion pak. Spotty RAM would do that. 3rd party expansion paks are notorious for odd issues like this. Have a jumper pak you can try? It could also be a connection problem with the pak, thoug...
You won't like to hear this, but this sounds exactly like what happens with poor cartridge contact. Specifically, the video interface locks up when the CIC can't talk to the PIF anymore. This means interlacing stops working, and you see a pixelated screen (in high res modes). The CIC is independent ...
If they are exactly the same size as a .eep, you might be able to use them just by renaming to the file the 64drive created. SRAM/flash saves may need to be endian-swapped
Edit: The problem ended up being a soldering issue with the SD slot. It wasn't related to upgrading the firmware, but probably caused by changing the SD stressing the slot.
Sounds suspicious. Did these cards work with the old firmware? You can downgrade to 1.05 by extracting these files somewhere and running upgrade.bat: http://64drive.retroactive.be/downgrade_to_105.zip You can then change to 2.00 with the easy upgrader like you did before. The 2.xx upgrader does a RA...
1. Hold L trigger while turning on. You should receive "Undefined error".
2. Do you have a different SD card you can try?
3. You can also try loading something over USB and turning on the N64 then. Like my MGC demo
If the LED inside flashes on boot, the firmware was upgraded properly.
Probably the cart slot is dirty or not making contact. Try the old breathe on contacts & pull out slightly trick.
Did you mess with a bootloader upgrade before doing the firmware?
One of the motivations for doing firmware 2.00 was so that I would have a good code base to use whenever I do a redesign in the future. It will probably happen sometime so long as the 64drive keeps selling, but not in the immediate future. I tried to plan ahead when I originally did the hardware, th...