Here’s a couple small demos that just toggle ZIF pins high or low. Don’t have an IC plugged when you do this. For these demos, the unused VPP and TOPBUS lines should be commented out in the ucf file. This verilog file contains both demos, and only one should be compiled at a time – comment the other one out as we’ve done here.
module Vtest(MCLK24, ZIF);
input MCLK24;
output [40:1] ZIF;
reg [40:1] ZIF;
// Use the ZIF pins as a binary counter
always @(posedge MCLK24)
begin
ZIF <= ZIF + 1;
end
//
// Rotate a single bit around the pins in a shift register
// always @(posedge MCLK24)
// begin
// ZIF[40:2] <= ZIF[39:1];
// ZIF[1] <= ~(ZIF[40] | ZIF[39] | ZIF[38] | ZIF[37] | ZIF[36] |
// ZIF[35] | ZIF[34] | ZIF[33] | ZIF[32] | ZIF[31] | ZIF[30] |
// ZIF[29] | ZIF[28] | ZIF[27] | ZIF[26] | ZIF[25] | ZIF[24] |
// ZIF[23] | ZIF[22] | ZIF[21] | ZIF[20] | ZIF[19] | ZIF[18] |
// ZIF[17] | ZIF[16] | ZIF[15] | ZIF[14] | ZIF[13] | ZIF[12] |
// ZIF[11] | ZIF[10] | ZIF[9] | ZIF[8] | ZIF[7] | ZIF[6] |
// ZIF[5] | ZIF[4] | ZIF[3] | ZIF[2] | ZIF[1]);
// end
endmodule
More advanced verilog stuff is going to have to go into another article that you'll see in a few days. It's a topic onto itself as you can certainly imagine!
We expect this article is interesting to different people for different reasons. We can see a few target audiences, and have tried to include enough detail for each to get some use out of it. Here's our guess on those audiences:
- Person who just wants a test bench. Maybe not concerned with internals initially and just wants to twiddle pins and write some scripts. But in time, his needs will probably grow to the point where he has to dig in deeper and write some verilog.
- Person who wants to do something specific to an IC, but doesn't know exactly how to develop the hardware to do so. Lots of benefit here, as this hack provides a pretty generous set of capabilities and should have enough detail to allow more complex and semi-custom functions with a small amount of labor.
- Person who hates when EPROM programmers don't support device X. You're always saying to yourself that you'd write it yourself if you just knew how... So here you go, please share your work!
- Guy who just likes taking things apart. Well this thing has been disassembled from the case to the software, to the internal logic structure. Hope we've included enough detail to inspire you to tear down your own device, or at least given you a good story on what process we use in getting into the nuts and bolts.
Stay tuned for some more follow-up stores on this little box. Until then....
Cheers,
-Openschemes
Have you seen the open source toprammer 2049 s/w ? There are lots of info in the docuementation including reverse engineering for the protocol.
Seems like the protocols and the architecture is very similar between the different top programmers. I have a top2048 which seems to work with
the toprammer s/w
http://linux.softpedia.com/get/System/Hardware/Toprammer-57047.shtml
Thanks for the link, that is great stuff. You are right, his work is very similar to own work here. Looks like the programmers are quite similar! Thanks again, we will try to get in touch with the author for some collaboration.
I was hoping for an open source development that lead to support of all TOPxxx devices not only test bench but also universal device programming support.
I have an TOP2048 that I am trying to reverse engineer the usb protocol. It seems very similar to the TOP2049 except the ZIF(47) doesnt have a VPP driver. Funilly enough there is one extra transistor connected to the VPP shift registers that isn’t connected to anything, Thinking about connecting that one to ZIF(47).
The toprammer 0.5 s/w does work to some extent for my TOP2048 after removing some of the status register checks. It bombs when setting VPP voltage shift registers using command 0x0e1400. An error code -0×02 is sent back by the device. all the VDD VSS stuff works though. I am still trying to figure out whats wrong.
Funnily enough the same command does work if I havn’t changed the VPP value from the default one.
Don’t really have the skills or the tools of you and Michael Buesch has
ffff88013b142f00 1434636915 S Bo:10:016:2 -115 18 = 0a50000a 51000a52 000a5300 0a54000a 5500
ffff88013b142f00 1434638896 C Bo:10:016:2 0 18 >
ffff8800b3d0a0c0 1434638941 S Bo:10:016:2 -115 4 = 0e120000
ffff8800b3d0a0c0 1434639895 C Bo:10:016:2 0 4 >
ffff88013b1429c0 1434639921 S Bo:10:016:2 -115 1 = 1b
ffff88013b1429c0 1434640895 C Bo:10:016:2 0 1 >
ffff88013b1429c0 1434640924 S Bo:10:016:2 -115 4 = 0e123300
ffff88013b1429c0 1434641895 C Bo:10:016:2 0 4 >
ffff88013b1429c0 1434641917 S Bo:10:016:2 -115 1 = 1b
ffff88013b1429c0 1434650896 C Bo:10:016:2 0 1 >
ffff88011f3ef240 1434650987 S Bo:10:016:2 -115 4 = 0e140000
ffff88011f3ef240 1434751902 C Bo:10:016:2 -2 0
One suggestion would be to sniff the USB communication of the vendor software to see how the commands are properly used. It’s quite likely that at least some of the framework is different from device to device. Perhaps it’s just that 00 00 is not the way to turn off VPP on the 2048…?
[...] Logic Cube – The Modification! – 7,384 viewsTurning a Top2005 EPROM Programmer into a Desktop … – 7,035 viewsMore FT232 Bit Banging with the Arduino Board – 4,085 viewsExternal WDTV Remote [...]
Hi,
At first, thanks for this hack. Great stuff!
I’m not a good coder in VB (some macro in Excel that’s all)so, when it tell me ”can’t find libusbvb0.dll”, I lose my mind.
I have try to put this famous dll in windows/system then in windows/system32 without any result.
It’s certainly a rooky question but: ”Where do it be ?”
Thank for ”your ligths”.
Regards.
When the compiled tool runs, it will begin looking for the dll in the same directory in which it exists. If not found there, it will look in system32.
However, if you’re running code from inside VB6 (the debugger) then it must be in windows\system32. If it still isn’t found (which it sounds like it is not) you may want to try registering it?
regsvr32 c:\windows\system32\libusbvb0.dll
Hi, this is really great stuff.
Do you think that it will possible by what you’ve found here, to program PROMS/EPROMS that have 16bit wide databuses ie. 27C1024 (maby with the use of an custom adapter)? Or is there some hardware limitations that makes it impossible?
If the pinout fits, then sure – it can be programmed
Hi,
I have the same error: ”can’t find libusbvb0.dll”
It looks like an inevitable error on – regsvr32 c:\windows\system32\libusbvb0.dll .
The error in the dialog: Error in library LoadLibrary(“c:\windows\system32\libusbvb0.dll”) finction – cannot find the requested module
The libusbvb0.dll file was copied as well into c:\windows\system32.
What can be the problem? Can you help?
Thanks forwarding.
Best regards,
Jozsef
Jozsef,
It either goes in the same directory as the exe, or system32 if you’re running in the VB6 code debugger. What windows version are you using?
Hi,
I am using WXP Professional (2002) SP3 on HP8730w laptop, NT Partition on C drive.
Th file “libusbvb0.dll” is in same directory where the exe file – “C:\Program Files\Topwin6\Opentop2\OpenTOP2.exe”
Then .dll file also was copied into directory “C:\WINDOWS\system32″
There is no VB6 installed. Should I install it to run the exe?
Thanks forwarding.
Best regards,
Jozsef
Do you have libusb installed on your machine? It could be that the regsvr is not finding the dependency.
Hi,
It must be the problem. Where from could I download the libusb installer?
Thanks
Sourceforge libusb-win32
http://sourceforge.net/apps/trac/libusb-win32/wiki
Thanks, I have installed the libusb .
I see the properly registrated device on the list by USBView, but there is a next problem.
The result of this command : regsvr32 c:\windows\system32\libusbvb0.dll
as follows, the popup window has contains this message:
The c:\windows\system32\libusbvb.dll has successfully loaded but unable to find the proper access point: DllRegisterServer.
The requested command is unable to register the file.
I am awaiting your kind reply.
Best regards
Jozsef
Glad to see some progress. This error is very puzzling, and without more investigation it is difficult to determine the problem.
Searching on google shows several other DLL’s that cause a similar error. Have you tried the fixes described for those other users?
Pass me a link how to solve if you known a good one.
Looks like the both version of drivers are cannot live together on the same machine, doensn’t works even an assigned USB socket to LibUSB driver.
I have tried out it right now on a clean machine (TOP2005 never seen of this) but accidentally it is not XP -> Win7 32bit.
Driver LibUSB is installed as well.
But the problem is even worse now because – at the starting of OpenTOP2.exe put an error window -> Component “RICHTX32.OCX” or one of its dependencies not correctly registered: a file is missing or invalid
Phh…life is not so easy..
Jozsef
The original TOP software does not seem to work on Win7 regardless. We will check on Opentop as it has never really been tried.
That would be very good. Packed all in one installer version together with driver components also would be very good.
BTW, what is your opinion, doesthis device could be able to functioning as an in-circuit IC tester? Maybe with some external driver circuits, does it possible?
Thanks
Have you any plans of writing software to map a PAL fuse map? This would be so useful.