@ magadam - I can not understand you.
What do you exactly need?
I want to support you but I do not know how in this moment!
atb
@ magadam - I can not understand you.
What do you exactly need?
I want to support you but I do not know how in this moment!
atb
If i understood ok, the PES "say" what programming voltage ant what pulse period is necesary for that gal device. And "say" too the type of gal device.
When i try to write a PES from a .jed file, any group of hexa number tell to galblast some.
But i think that the PES is necesary only if you use "erase all"...
Because any device have PES...and programmer recognize the device from PES
Last edited by magadan; 27th June, 2011 at 09:52 AM.
maybe is usefull that?
GAL programming algorithms
To everybody who has 10.64 dump.
2 weeks ago I programmed my BL cable with 10.64 dump and everything worked perfect, but today when I tried perform full autoscan software stoped after scanned 2 or 3 modules, and cable become unregistered. So I programmed it again, and works fine scaning single modules but when I tried to do full autoscan, cable becomes unregistered and lose FTDI drivers. 2 weeks ago cable works perfect with autoscan and other functions but suddenly something change. Do you know what could be wrong? Do your programmed cables with 10.64 dumps works ok?
Cheers.
Do you wanna mean that if you use your softwear now the tools serials it is erased?
Do you have disable updates installed into your hosts?
Maybe the ross-tech figure it out that this serial is clonned and it is blacklisted now.
Even that om their web site it is stil 10.6.4 version
But if it keeps its driver but it becomes Unregistred this is somethingelse.
Please check the VID PID of the driver.
Good luck
Yes the FTDI VID and PID is change so interface is no longer recognize as Ross Tech cable, and software becomes unregistered version.
Like I said this cable works fine 2 weeks ago with orginal Ross Tech software but now something change. It could be that I didn't disable updates, I have to check it out.
Thanks.
I suppose that now the serial is blacklisted.
"We started to fight again" mates
Good luck
I checked it and updates was disable I had added line 127.0.0.1 into C:WindowsSystem32driversetc folder, so what is wrong?
Not just the 127.0.0.1 it is not enoght
here it is an uplication
If it is against the lows I will erase it
Bookmarks