Daniel,
I started
this thread to ask a question about excessive product terms while programming an ATF22V10, but it has evolved into a discussion about a problem I discovered with pin 13. I have been able to boil it down to a simple example.
Code:
Name GAL_Test ;
PartNo 00 ;
Date 4/24/2020 ;
Revision 01 ;
Designer Engineer ;
Company Shawn Odekirk ;
Assembly None ;
Location ;
Device g22v10 ;
/* *************** INPUT PINS *********************/
PIN 13 = INP_A;
PIN 14 = INP_B;
/* *************** OUTPUT PINS *********************/
PIN 20 = OUT_A;
PIN 21 = OUT_A_INV;
PIN 22 = OUT_B;
PIN 23 = OUT_B_INV;
OUT_A = INP_A;
OUT_A_INV = !INP_A;
OUT_B = INP_B;
OUT_B_INV = !INP_B;
In this example, OUT_A seems to be correct, but OUT_A_INV is always high. OUT_B and OUT_B_INV work correctly. This problem only seems to occur when the input is pin 13. You are using pin 13 as the input for your OE signal. I wonder if you moved your OE signal to another pin if your outputs would tri-state correctly.
Daniel, would you be willing to program an ATF22V10 with my example using your programmer and see if your results match mine?
floobydust wrote:
I've been using a Dataman 40pro for about 7 years now... it wasn't cheap, but (software) updates are still frequent and it handles the Atmel versions without any issue.
floobydust, would you be willing to program an ATF22V10 with my example using your Dataman programmer and see if it works correctly?
SteveD wrote:
I've used both the ATF22V10C and ATF16V8B, programmed successfully with a genuine TL866II+.
SteveD, would you also be willing to program an ATF22V10 with my example using your programmer and see if your results also match mine?
Hopefully, the results of these tests will help us determine if it's the TL866II+ programmer or something else.
I am including my .jed file in case it is my WinCupl settings that are causing the problem.
Thanks,
Shawn