search

go4retro / Nu6509

Emulate a 6509 with a 6502
MIT License
20 stars 3 forks source link

Success in building, but some tips in the markdown could save some time #1

Closed drshock closed 4 years ago

drshock commented 4 years ago

I successfully built this adapter and it tested out fine in a Commodore B128-80 lo-profile model using Commodores own dealer diagnostics cartridge and loopback connectors. I used OSHPark.com for my PCBs and mouser.com for the parts. I did run into some initial problems that are worthy of updating the markdown at some point for others here to save them time.

A) The particular Xilinx part the project uses is not compatible with any of the Digilent JTAG type cables. I had to use an older and slower Xilinx DLC9LP cable instead to get success. Now to be fair I only use Chinese clone cables, but I suspect this has nothing to do with that. But when getting a DLC9 clone make sure the adapter has the CY7C68013A chip implementation in the sellers description as sometimes they throw the same boards into the differently labeled plastic cases so its not enough to read the DLC9 on the listing photos. Also don't forget you cannot program the device on board without suppling it with 5V Vcc (and Vss ground) at the original 6509 pins of your new PCB (your adapter cable will be amber highlighting the missing vref).

B) I used 64bit Windows 10, and thus the latest Xilinx ISE package (14.7). The installer for this doesn't let you know it has a hard pre-req on Oracle VirtualBox so install that first, separately. I used the latest Oracle version (6.1) as originally this Fake6509 repo didn't include the JEDEC file so I had to build it. The JED file built fine with these toolchain versions as well as, with the right adapter cable, programmed fine as well.

Very cool project and thanks for taking the time to share it.

go4retro commented 4 years ago

On A), I used a Xilinx DLC9C cable, which is quite fast and works fine. While I can note that the Digilent cables do not work with this part (they actually will do the program correctly, but the verify doesn't work, so they look to error out), I feel this could quickly devolve into listing out all the cables that do not work (Bus Pirate?, Byte Blaster?, etc.). The Digilent cables note that they do not work on XL parts, so I'm not sure why folks would try to use such a programmer. B) I actually use 14.7 on Windows 10 without Oracle VirtualBox. 32bit works fine, though 64 bit Windows requires a bit of TLC: (http://forum.6502.org/viewtopic.php?f=10&t=5258).

I'm concerned about putting such information in the project docs, as it's not specific to this project, but is general for all XC9500XL based devices and specifics related to Windows use of the ISE tool. Perhaps you should write an article and I can link to it as one way to get the environment up and running.

Jim

drshock commented 4 years ago

Jim, Alright, I can see that. I guess just having this issue in the repo history might help some not familiar with the toolchain some time. I've never seen the Digilent cable restriction stated on the XL parts, but then I'm using the Chinese clones from eBay that claim to be Xilinx USB cables on the outside so they may be different than the real thing. Thx again.