Hello dorkshoei1,
We have tested the same situation here in our lab and found no problem with our device samples of Lattice GAL20V8B. Therefore we would like to ask you to send us some device samples of the mentioned Lattice device for further tests.
If neither of the checkboxes are checked then no actions with the device will be performed.
Considering the Device operation options/Programming parameters "Device without Security fuse" and "Security fuse", it depends on the demands.
- programing of the device arrays but without security fuse: "Device without security fuse" is ON and "Security fuse" is OFF
- programing of the device arrays with security fuse: "Device without Security fuse" is ON and "Security fuse" is ON
- programming just the security fuse: we do not to recommend it as a solo pgm action, "Device without security fuse" is OFF and "Security fuse" is ON
GAL20V8
-
- Posts: 979
- Joined: 10 Nov 2011 09:51
Re: GAL20V8
Best regards,
Neil Parker
Dataman Programmers
Neil Parker
Dataman Programmers
-
- Posts: 3
- Joined: 14 Sep 2025 01:49
Re: GAL20V8
Neil.
Thanks for the reply.
Obviously this programmer/software is obsolete but these options could have been better worded.
Either way I definitely programmed the device using the default.
Is there any documentation that talks about these "XXX as YYY" device types? What is occurring, any limitations etc?
After sucessfully programming the device using "LATTICE GAL20V8B as PAL20L8" I tried to erase it using same device type. I'm not sure if this was the issue and I should have instead used "LATTICE GAL20V8B"? It seems unlikely.
Anyways I will try another device (and save the log this time). Thanks again for all your help.
Thanks for the reply.
Obviously this programmer/software is obsolete but these options could have been better worded.
Either way I definitely programmed the device using the default.
Is there any documentation that talks about these "XXX as YYY" device types? What is occurring, any limitations etc?
After sucessfully programming the device using "LATTICE GAL20V8B as PAL20L8" I tried to erase it using same device type. I'm not sure if this was the issue and I should have instead used "LATTICE GAL20V8B"? It seems unlikely.
Anyways I will try another device (and save the log this time). Thanks again for all your help.
-
- Posts: 979
- Joined: 10 Nov 2011 09:51
Re: GAL20V8
Hello dorkshoei1,
> Is there any documentation that talks about these "XXX as YYY" device types?
In the case of "Lattice GAL20V8 as PAL20L8", you can reference the datasheet for the Lattice GAL20V8 ... and so on for other such implementations.
"
An important subset of the many architecture configurations possible with the GAL20V8 are the PAL architectures listed in the table of the macrocell description section. GAL20V8 devices are capable of emulating any of these PAL architectures with full function/fuse map/parametric compatibility.
"
> What is occurring, any limitations etc?
Limitations of what? As far as we know, any JEDec file for any PAL20L8 device can be used. Please specify what information is needed to fill in the gaps.
> After sucessfully programming the device using "LATTICE GAL20V8B as PAL20L8" I tried to erase it using same device type. I'm not sure if this was the issue and I should have instead used "LATTICE GAL20V8B"? It seems unlikely.
This setting is related to a different type of programming process, but basic operations must always be done as the LATTICE GAL20V8B device. So, the Erase operation is identical as for the LATTICE GAL20V8B.
Conclusion: our implementation is OK, if something doesnt work properly it is because the devices are locked or defective.
> Is there any documentation that talks about these "XXX as YYY" device types?
In the case of "Lattice GAL20V8 as PAL20L8", you can reference the datasheet for the Lattice GAL20V8 ... and so on for other such implementations.
"
An important subset of the many architecture configurations possible with the GAL20V8 are the PAL architectures listed in the table of the macrocell description section. GAL20V8 devices are capable of emulating any of these PAL architectures with full function/fuse map/parametric compatibility.
"
> What is occurring, any limitations etc?
Limitations of what? As far as we know, any JEDec file for any PAL20L8 device can be used. Please specify what information is needed to fill in the gaps.
> After sucessfully programming the device using "LATTICE GAL20V8B as PAL20L8" I tried to erase it using same device type. I'm not sure if this was the issue and I should have instead used "LATTICE GAL20V8B"? It seems unlikely.
This setting is related to a different type of programming process, but basic operations must always be done as the LATTICE GAL20V8B device. So, the Erase operation is identical as for the LATTICE GAL20V8B.
Conclusion: our implementation is OK, if something doesnt work properly it is because the devices are locked or defective.
Best regards,
Neil Parker
Dataman Programmers
Neil Parker
Dataman Programmers
Return to “Devices and Programming”
Who is online
Users browsing this forum: No registered users and 28 guests