Recent content by UrQuan3

It is really hard to find DIMM firmware online and 4.02 is the only "known good" firmware I have. 3.17 would be fine, but I don't know if that failed because I am doing something wrong, or because the file is bad. 3.03 doesn't seem to ....*blink*.... wait, now the whole netboot thing is...

Anything unusual about pushing a firmware update to a Triforce Type-1? I tried the same "TransferGame.exe" and "FW_Netdimm_402.bin" that upgraded a 256mb NETDIMM on a Naomi just fine. On the Triforce, it seems to accept the transfer, the screen goes black for awhile, then it reboots, still...

No firmware changes needed. You're not too far off on JVS. It is RS485 over the D+/D- lines. Same ground. The +5 volt line is instead a "sense" line used on startup for each device on the JVS chain to be identified by the master. While the ground and data are bridged across the JVS input...

Oh good. I used the same pinout. Thank you for letting me verify.

(replying to a question on ebay) I'm not sure what device is the "UD USB". Is that the "Undamned USB Decoder"? (Had to go research that) So, um, it would work...Let me tell you why this project exists. I was intending to build a single one-off of this JVS adapter, with hand soldered custom...

I don't think any rewiring is needed, you should just plug the USB2DB15 (or rather, all 4) into the DB15-to-JVS and it would all work.

Let me try explaining. Every GD-ROM title is encrypted using a unique encryption key (think very long password) the key chip stores the decryption key (password). You can't mix and match keys and titles. The deal with the zero key is for preservation using copied titles. GD-ROMs at this...

Had a slightly odd NETDIMM upgrade, so I thought I'd post. NETDIMM (sourced from Hong Kong) reported itself as version 3.13 in the BIOS test. It would not accept "FW_Dimm317.bin" (maybe I wasn't supposed to use that one), but accepted the file "FW_Netdimm_402.bin" directly. Oddly, the upgrade...

Got it. I was trying to upload the wrong NETDIMM update ROM. The steps above absolutely create a valid zero key using the PicKit 4. Thanks everyone.

Thank you both. That seems to be what I needed. MPLAB read the file, set the flags, recorded, and verified. ... I can't test it. (Oh look, NETDIMM firmware version 3.13, not 3.17 !@#!). Oh well. That's a project for another day. EDIT: I don't want to derail a thread focused on the zero...

Just in time for the weekend! I'll give it a try.

Ah, what the heck. The TL866II is cheap. I don't have all that much to lose. the .hex is for the Microchip software. (pickit programmers)

Hmm, maybe I can bait out some advice if I better define the question. Several times the author, rtw, mentions posting a *.hex file. Several other people refer to a hex file. Later one person mentions having to convert the *.bin to a *.hex file. However, the hex file no longer seems to be...

Forgive me if this is the wrong place to post. I've been meaning to learn how to program PICs and thought this would be a cool starting point since it is tested code and well documented flags. Since I saw a couple of people mention success with a PICKIT 2, I picked up the current model (4) and...

Ok