Can anyone tell me which software was used to compile following code into burnable PAL 16L8 image? [===code===] #include "cp6.dsc"

RG0 CS = false VV CS = false

VS CS = true VS = v3 v4 v5 ~vv v8 rg0 VS = v2 v3 ~vv v4 v5 v8 ~rg0 VS = ~v2 ~v3 ~vv ~v4 ~v5 ~v8

BL CS = true BL = ~h4 ~h5 h6 rg0 BL = ~b3 ~b2 h4 ~h5 h6 rg0 BL = b3 ~h4 ~h5 h6 ~rg0 BL = ~b3 h4 ~h5 h6 ~rg0 BL = b3 ~b2 h4 ~h5 h6 ~rg0 BL = ~vv v4 v5 v8 BL = ~vv ~v4 ~v5 ~v8

HS CS = true HS = ~h6 HS = ~b3 ~h4 ~h5 h6 ~rg0 HS = b3 ~h4 ~h5 h6 rg0 HS = h4 ~h5 h6 HS = h5 h6

HE CS = true HE = h4 h5 ~h6 rg0 ~z1 HE = ~h5 h6 HE = ~vv v8 HE = rg0 ~vv HE = ~rg0 ~vv ~v5 ~v8 HE = ~rg0 ~vv ~v4 v5 ~v8 HE = ~rg0 ~v3 ~vv v4 v5 ~v8

//HE = ~v8 ~vv ~v5 ~v4 ~v3 v2 h6 ~h5 ~h4 b3 b2 z1 rg0

Z1 CS = true Z1 = ~v8 ~z1 Z1 = ~v8 ~vv ~v5 ~v4 v3 ~v2 hs h6 ~h5 ~h4 b3 rg0 Z1 = ~v8 vv v5 ~v4 v3 ~v2 hs h6 ~h5 ~h4 b3 rg0

Z2 CS = true Z2 = ~z1 ~rg0 v2 ~v3 v4 ~v8 h5 h4 ~hs Z2 = ~z1 ~rg0 ~v2 v3 ~v4 ~v8 h4 ~b3 Z2 = ~z1 ~rg0 ~v2 ~v3 v4 ~v8 h5 ~hs bl Z2 = ~z1 ~rg0 v2 v3 v4 v5 ~v8 ~h6 h4 ~b3

Z2 = ~z1 ~rg0 ~v2 ~v3 ~v4 ~v8 vv h6 ~h5 b3 he

Z2 = z1 ~v2 ~vv ~v4 v5 ~h4 b3 Z2 = z1 v2 ~vv ~v4 v5 ~bl b3 ~h4

Reply to
Loading thread data ...

Doesn't look like PALASM, CUPL, or ABEL. It's certainly not VHDL or Verilog. Maybe one of the proprietary languages that PAL vendors each seemed to have back in the day?

Looks reasonable to convert into something modern: each line seems to define a minterm for an output.

If you have an old JEDEC file there are JEDEC->PALASM converters out there, according to google.


Reply to
Kelly Hall

Well software produces some sort of files with *.$(2065 bytes long) extension, which are converted with prom.exe to binary image with

*.img(2048 bytes long) extension. And unprom.exe converts *.img back to *.$. The other two utiles i have from this software pakage are trd.exe and trw.exe they do not report there names and written in Borland C++. Hey may be there is a tool to convert binary images to jedec?
Reply to

Hmmm, not an easy one... The code below is nothing that is still alive, or widespread, afaik.

However, it will convert to CUPL resonably easily ( eg)

VS = v3 & v4 & v5 & !vv & v8 & rg0 # v2 & v3 & !vv & v4 & v5 & v8 &!rg0 # !v2 & !v3 & !vv & !v4 &!v5 &!v8;

This can then go to 16V8 code using current CUPLs ( eg Atmel's WinCUPL )

- but if you have a truckload of 16L8's at 2c each, and so really do want a 16L8 file, then you'll need to find an old version of the CUPL evals, that did have library support for 16L8's. Try a search for "CUPL evaluation download", and go from there...

CUPL can also create test vectors and append these to the JED file, so you can PGM and verify it actually works (on a good programmer )..


Reply to
Jim Granville

Well now i heed the programming algorithm of AMPAL 16L8, because my programmer wants a binary file.

Reply to

Is it PLPL?

Its 16 years since I last used it so my memory is a bit hazy. PLPL was an AMD PAL programming language. I do remember that the compiler was rubbish.

Cheers TW

cr0acker wrote:

Reply to

Well PLPL looks more like pascal ond/or ahdl.

Reply to

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.