JED File Info

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Is it possible from a JED file to know which pins have been defined as input and which as output?

I don't have a lot of time right now but I've had a quick squizz at some documents which suggest it's defined in the source by what is on the right hand side of the pin assignment, but I don't see anything obvious in the JED file to be able to tell. Obviously I don't have the source or access to the author or I would simply look / ask.

I'm trying to solve a problem on something and the schematics just show the pins as I/O - plus their signal name and I don't know if the GAL is consuming the signal (input), or producing the signal (output). Which is making progress somewhat hit and miss!

Ta.
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
I'll have a look for that EXE when I'm on a Windows PC. For the most part I use Mac.

When I load the JED file up in the programmer and view it I see many, many more values than there are pins, so it's kind of meaningless to me. In fact, it looks like it's just the values from the JED file.

For this 22V8 Gal there are 1153 0's or 1's in the JED file and only 24 pins!!
 

Elgen

Newbie
Credits
90CR
You will not get much info looking at a JED-file with the naked eye. It was never meant to be read by humans. Try the JED2EQN.EXE as stated (it's up on porchys site as well); you migth have to use DOSBOX to run it, but it'll give you the pin assignments as well as the equations.
Elgen2014-04-01 13:03:04
 

cmonkey

Active member
vacBacker
Feedback
4 (100%)
Credits
1,659CR
guddler said:
I'll have a look for that EXE when I'm on a Windows PC. For the most part I use Mac.

Me too, but occasionally you have to bite the bullet and turn to the dark side for apps that simply aren't available on OS X.
smiley36.gif


I'm not aware of a GAL22V8, only a 16V8 or a 22V10. A 22V10 has a programmable AND array of 132x44 (i.e. 5808) fuses. Each of those fuses has to be represented by either a 1 or a 0 in the JED file. A GAL16V8 has a programmable AND array of 64x32 (i.e. 2048) fuses.
 

cmonkey

Active member
vacBacker
Feedback
4 (100%)
Credits
1,659CR
A 20V8 has a 64x40 array (i.e. 2560) of fuses. The JED would contain a few more 0's/1's to dictate the configuration of the output logic macro cells.

Like Elgen has said, you'll never be able to parse them without help of JED2EQN.
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
smiley36.gif
That didn't get me very far - just tried JED2EQN in an XP virtual machine and while the program runs I just get a simple "Could not open file 'IC53.jed'"

The file is in the same directory as the program and not read only. Will have to come back to it later.
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
OK, same question for an LSI ISP1024 CPLD.

I can see now that I have 2 bad or at least incorrect clock signals but again, I don't know if the CPLD is producing them (output) or simply consuming them (input)
 

cmonkey

Active member
vacBacker
Feedback
4 (100%)
Credits
1,659CR
Which pin numbers are they?

I assume you've seen the datasheet for this device, and hence know that pins Y0,Y1,Y2 and Y3 are the dedicated clock input pins?
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
Not that easy
smiley1.gif


They're pins 25 & 29, I/O 3 & I/O 7 respectively. My suspicion is that the CPLD is generating them but I really do need to confirm it really rather than guessing. Main reason for that is the CPLD is new and confirmed working in another board.
 

Judder

Active member
Feedback
2 (100%)
Credits
1,009CR
OK - curiosity killed the cat and I went and started playing with this challenge.

The problem is the DOS binary is so old it only supports the original 8.3 file naming convention of windows.

So, taking my .jed file, renaming it to a shorted (< 8 chars) name means the decompiler finds it fine and produces the equation file correctly.

Here's the resultant generated equation file for DigDug (I have one of these) from this fantastic site of PAL/GAL dumps

http://www.jammarcade.net/pal-dumps/

and how I made it:

C:UsersAlexDOWNLO~1pld>move c:tempdigdug-DD1-6.jed c:tempdig.jed

1 file(s) moved.

C:UsersAlexDOWNLO~1pld>JED2EQN.EXE -d PAL16L8 c:tempdig

JED2EQN -- JEDEC file to Boolean Equations disassembler (Version V063)

Copyright (c) National Semiconductor Corporation 1990-1993

JEDEC file : c:tempdig.jed

Device name : 16L8

Equations file : dig.eqn

Equation File:

; JED2EQN -- JEDEC file to Boolean Equations disassembler (Version V063)

; Copyright (c) National Semiconductor Corporation 1990-1993

; Disassembled from c:tempdig.jed. Date: 4-1-114

chip dig PAL16L8

i1=1 i2=2 i3=3 i4=4 i5=5 i6=6 i7=7 i8=8 i9=9 GND=10 i11=11 o12=12

f13=13 f14=14 f15=15 f16=16 f17=17 f18=18 o19=19 VCC=20

equations

/o19 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14 * /f14

* i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

o19.oe = gnd

/f18 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14

* /f14 * i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f18.oe = gnd

/f17 = i2 * /i2 * i1 * /i1 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14

* /f14 * i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f17.oe = gnd

/f16 = /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14

* /f14 * i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f16.oe = gnd

/f15 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14

* /f14 * i8 * /i8 * f13 * /f13 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f15.oe = gnd

/f14 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * i7 * /i7 * f14

* /f14 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f14.oe = gnd

/f13 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * i6 * /i6 * f15 * /f15 * /i7 * f14 * /f14

* i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

f13.oe = gnd

/o12 = i2 * /i2 * i1 * /i1 * i3 * /i3 * f18 * /f18 * i4 * /i4 * f17 * /f17

* i5 * /i5 * f16 * /f16 * /i6 * f15 * /f15 * i7 * /i7 * f14 * /f14

* i8 * /i8 * f13 * /f13 * i9 * /i9 * /i11

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

+ vcc

o12.oe = gnd
 

guddler

Busting vectors like it's 1982!
vacBacker
Feedback
10 (100%)
Credits
4,058CR
OK, that explains that then - when I renamed them to test.jed, IC53.jed and so on, it worked
smiley36.gif


Now I just need to somehow know which are the inputs and output on the 64 pin isp1024 !
 

cmonkey

Active member
vacBacker
Feedback
4 (100%)
Credits
1,659CR
There's always the possibility that the security bit in the CPLD was set when it was programmed, meaning you won't be able to dump its contents.
 
Top