Any PALASM gurus here?

[Rod Wright]

I'm trying to use PALASM4 ver. 1.5 to disassemble a jedec file. The source
of the file is a hardcopy printout which I typed in with a text editor and
saved as a .jdc file. When I try to disassemble it, PALASM gives an error
j140 (not a valid jedec file). Here's what's in the file:

PALASM XPLOT, V2.22 - MARKET RELEASE (11-19-86)
(C) - COPYRIGHT MONOLITHIC MEMORIES INC, 1986

Title : Servo Logic Author : none
Pattern : 3355750-901-105 (serv_lo Company : none
Revision : Original Date : 08/18/88


PAL20S10
BM42*
G0*F0*
L0000 1111111111111111111111111111111111111111*
L0040 1110111101111111111111111111111111111111*
L0080 1101111110111111111111111111111111111111*
L0320 1111111111111111111111111111111111111111*
L0360 1110111111110111111111111111111111111111*
L0400 1101111111111011111111111111111111111111*
L0840 1101111111111111101111111111111111111111*
L0880 1110111111111111011111111111111111111111*
L0920 1111111111111111111111111111111111111111*
L0960 1111111111111111111111111111111111111111*
L1000 0111011111111111111111111111111111111111*
L3200 1111000000*
L3210 0101*
L3214 000000000000000000001010*
L3238 01*
L3240 00000000000000000000000000*
L3266 0000000000000000000000000000*
L3294 0000000000000000000000000000*
V0001 0XX111XXXXXNXXXXXXXXHHHN*
V0002 1XX111XXXXXNXXXXXXXXLLLN*
V0003 0XX000XXXXXNXXXXXXXXLLLN*
V0004 1XX000XXXXXNXXXXXXXXHHHN*
V0005 100000XXXXXNXXXXXXXLHHHN*
V0006 110000XXXXXNXXXXXXXLHHHN*
V0007 111000XXXXXNXXXXXXXHHHHN*
C3729*
C93F

Is PALASM sensitive to tabs or some other formatting that wouldn't be
visible in the printout? Is there an incompatibility between the older
version of PALASM that generated the file and the one I'm using?

Thanks in advance for any help.
Rod

 

[James T. White]

I'm trying to use PALASM4 ver. 1.5 to disassemble a jedec file. The source
of the file is a hardcopy printout which I typed in with a text editor and
saved as a .jdc file. When I try to disassemble it, PALASM gives an error
j140 (not a valid jedec file). Here's what's in the file:

PALASM XPLOT, V2.22 - MARKET RELEASE (11-19-86)
(C) - COPYRIGHT MONOLITHIC MEMORIES INC, 1986

Title : Servo Logic Author : none
Pattern : 3355750-901-105 (serv_lo Company : none
Revision : Original Date : 08/18/88


PAL20S10
BM42*
G0*F0*
L0000 1111111111111111111111111111111111111111*
L0040 1110111101111111111111111111111111111111*
L0080 1101111110111111111111111111111111111111*
L0320 1111111111111111111111111111111111111111*
L0360 1110111111110111111111111111111111111111*
L0400 1101111111111011111111111111111111111111*
L0840 1101111111111111101111111111111111111111*
L0880 1110111111111111011111111111111111111111*
L0920 1111111111111111111111111111111111111111*
L0960 1111111111111111111111111111111111111111*
L1000 0111011111111111111111111111111111111111*
L3200 1111000000*
L3210 0101*
L3214 000000000000000000001010*
L3238 01*
L3240 00000000000000000000000000*
L3266 0000000000000000000000000000*
L3294 0000000000000000000000000000*
V0001 0XX111XXXXXNXXXXXXXXHHHN*
V0002 1XX111XXXXXNXXXXXXXXLLLN*
V0003 0XX000XXXXXNXXXXXXXXLLLN*
V0004 1XX000XXXXXNXXXXXXXXHHHN*
V0005 100000XXXXXNXXXXXXXLHHHN*
V0006 110000XXXXXNXXXXXXXLHHHN*
V0007 111000XXXXXNXXXXXXXHHHHN*
C3729*
C93F

Is PALASM sensitive to tabs or some other formatting that wouldn't be
visible in the printout? Is there an incompatibility between the older
version of PALASM that generated the file and the one I'm using?

Thanks in advance for any help.
Rod

Rod,

I don't claim to be a PALASM Guru, but the .JED files that my WinCUPL generates
look a bit different. Aside from the header comment lines, all the data lines
begin with an *.

For example:

*G0
*F0
*L0000 ...
*L0040 ...

 

[Tilmann Reh]

I'm trying to use PALASM4 ver. 1.5 to disassemble a jedec file. The
source of the file is a hardcopy printout which I typed in with a
text editor and saved as a .jdc file. When I try to disassemble it,
PALASM gives an error j140 (not a valid jedec file). Here's what's in
the file:
...
Is PALASM sensitive to tabs or some other formatting that wouldn't be
visible in the printout? Is there an incompatibility between the
older version of PALASM that generated the file and the one I'm
using?

Invisible in the printout, the files generated by PALASM contain an STX
character (02h) before the PAL type identifier, and an ETX (03h)
character between the JEDEC checksum and the file checksum.

In HEX, these parts would then look like:
.... 0D 0A 02 0D 0A 50 41 4C ...
.... 37 32 39 2A 0D 0A 03 43 39 33 ...

It sounds reasonable that PALASM also need these boundary markers for
disassembly.

 

[Al]

I'm trying to use PALASM4 ver. 1.5 to disassemble a jedec file. The source
of the file is a hardcopy printout which I typed in with a text editor and
saved as a .jdc file. When I try to disassemble it, PALASM gives an error
j140 (not a valid jedec file). Here's what's in the file:

PALASM XPLOT, V2.22 - MARKET RELEASE (11-19-86)
(C) - COPYRIGHT MONOLITHIC MEMORIES INC, 1986

Title : Servo Logic Author : none
Pattern : 3355750-901-105 (serv_lo Company : none
Revision : Original Date : 08/18/88


PAL20S10
BM42*
G0*F0*
L0000 1111111111111111111111111111111111111111*
L0040 1110111101111111111111111111111111111111*
L0080 1101111110111111111111111111111111111111*
L0320 1111111111111111111111111111111111111111*
L0360 1110111111110111111111111111111111111111*
L0400 1101111111111011111111111111111111111111*
L0840 1101111111111111101111111111111111111111*
L0880 1110111111111111011111111111111111111111*
L0920 1111111111111111111111111111111111111111*
L0960 1111111111111111111111111111111111111111*
L1000 0111011111111111111111111111111111111111*
L3200 1111000000*
L3210 0101*
L3214 000000000000000000001010*
L3238 01*
L3240 00000000000000000000000000*
L3266 0000000000000000000000000000*
L3294 0000000000000000000000000000*
V0001 0XX111XXXXXNXXXXXXXXHHHN*
V0002 1XX111XXXXXNXXXXXXXXLLLN*
V0003 0XX000XXXXXNXXXXXXXXLLLN*
V0004 1XX000XXXXXNXXXXXXXXHHHN*
V0005 100000XXXXXNXXXXXXXLHHHN*
V0006 110000XXXXXNXXXXXXXLHHHN*
V0007 111000XXXXXNXXXXXXXHHHHN*
C3729*
C93F

Is PALASM sensitive to tabs or some other formatting that wouldn't be
visible in the printout? Is there an incompatibility between the older
version of PALASM that generated the file and the one I'm using?

Thanks in advance for any help.
Rod

Many, many moons ago, I wrote a Pascal program which would convert the
code into a logic diagram. Unfortunaately, I don't have a copy. Sorry to
whet your appetite. But maybe you could search for such a program on the
web. If I did it, I'm sure someone else did.

I did this for a military program. The customer wanted logic diagrams
but none existed as the cicuit functionallity was generated used boolean
equations. No logic diagram ever existed.

Al

 

[Bob Stephens]

I'm trying to use PALASM4 ver. 1.5 to disassemble a jedec file. The source
of the file is a hardcopy printout which I typed in with a text editor and
saved as a .jdc file. When I try to disassemble it, PALASM gives an error
j140 (not a valid jedec file). Here's what's in the file:

PALASM XPLOT, V2.22 - MARKET RELEASE (11-19-86)
(C) - COPYRIGHT MONOLITHIC MEMORIES INC, 1986

Title : Servo Logic Author : none
Pattern : 3355750-901-105 (serv_lo Company : none
Revision : Original Date : 08/18/88


PAL20S10
BM42*
G0*F0*
L0000 1111111111111111111111111111111111111111*
L0040 1110111101111111111111111111111111111111*
L0080 1101111110111111111111111111111111111111*
L0320 1111111111111111111111111111111111111111*
L0360 1110111111110111111111111111111111111111*
L0400 1101111111111011111111111111111111111111*
L0840 1101111111111111101111111111111111111111*
L0880 1110111111111111011111111111111111111111*
L0920 1111111111111111111111111111111111111111*
L0960 1111111111111111111111111111111111111111*
L1000 0111011111111111111111111111111111111111*
L3200 1111000000*
L3210 0101*
L3214 000000000000000000001010*
L3238 01*
L3240 00000000000000000000000000*
L3266 0000000000000000000000000000*
L3294 0000000000000000000000000000*
V0001 0XX111XXXXXNXXXXXXXXHHHN*
V0002 1XX111XXXXXNXXXXXXXXLLLN*
V0003 0XX000XXXXXNXXXXXXXXLLLN*
V0004 1XX000XXXXXNXXXXXXXXHHHN*
V0005 100000XXXXXNXXXXXXXLHHHN*
V0006 110000XXXXXNXXXXXXXLHHHN*
V0007 111000XXXXXNXXXXXXXHHHHN*
C3729*
C93F

Is PALASM sensitive to tabs or some other formatting that wouldn't be
visible in the printout? Is there an incompatibility between the older
version of PALASM that generated the file and the one I'm using?

Thanks in advance for any help.
Rod

Don't know if it applies here, but I've had problems in the past with
different compilers formatting JEDEC files differently especially when
generated from a hex dump. Some programmers dump the entire fuse map, while
others only show the areas that are programmed, skipping over blank areas.
You might try different compilers for disassembly. Or burn it into a PAL
and dump the image to a file for disassembly. Or even run it through
PALTOGAL.EXE and see what pops out.

Good luck!


Bob

 

[Rod Wright]

Invisible in the printout, the files generated by PALASM contain an STX
character (02h) before the PAL type identifier, and an ETX (03h)
character between the JEDEC checksum and the file checksum.

In HEX, these parts would then look like:
... 0D 0A 02 0D 0A 50 41 4C ...
... 37 32 39 2A 0D 0A 03 43 39 33 ...

It sounds reasonable that PALASM also need these boundary markers for
disassembly.

By jove, that was it! Thanks for the help!