[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [N8VEM-S100:3225] Re: GAL's and PALASM

I suspect that the gate splitting warning is issued because you're
using the value of an output pin as an input to another equation.

For example, mA0 is an output pin.   It is also used to create msXTRQ.

I normally don't do that...

Is the msXTRQ# equation generating the warning?

I've sent some files to you off-list.

Rob.

On 4/24/2014 11:29 AM, John Monahan wrote:

Rob, with the "Path" problem fixed and saying "Y" to all the compile options I find I can get the following equations
For the attached schematic to yield a .jed file

mA1 =  /mBE0 * /mBE1

BHE  =  /mBE1 * /mBE3

/mA0  =  /(/mBE0 *  /mBE2)
              *  /(/mBE0 * mBE1)

msXTRQ  = BHE + /mA0

What is interesting is that I can now use brackets and even a  "/"  before one.
The PALASM4 complains with a " Warning L1810, Gate splitting is not supported for device PAL22V10"
But it seems to go ahead and generate the .jed file anyway.
  Doe the above equations look right to you?

John


-----Original Message-----
From: n8vem...@googlegroups.com [mailto:n8vem...@googlegroups.com] On Behalf Of Rob Doyle
Sent: Thursday, April 24, 2014 1:39 AM
To: n8vem...@googlegroups.com
Subject: Re: [N8VEM-S100:3211] Re: GAL's and PALASM

I was looking at the schematic that you attached previously.

It accurately replicates the schematic illustrated in Figure 5-7 (Page 72) of the Intel 386DX data sheet.

I'm referencing the data sheet at:

http://media.digikey.com/pdf/Data%20Sheets/Intel%20PDFs/Intel386%20DX.pdf

I'd like to look at this two ways:

1. Replicate the schematic exactly.
2. Replicate the truth table of Table 5-7 (Page 71)

They'll be slightly difference because the Karnaugh Map logic minimization shown utilizes a bunch of "don't care" conditions.

I'm also trying set up the PALASM4 simulation environment with "test vectors". Not only should that test the design - but when you program the device, the programmer should actually test the programmed device with the test vectors. It seems like that would be useful as folks try to figure out the proper settings for their programmer.

The two approaches above /should/ pass the same test vectors if I encode the "don't care" conditions into the simulator.  The test vectors will be per Table 5-7.

Funny. I used to do this all the time but I barely remember any of it.
Hopefully a running though some examples will help dust off the cob webs.

Rob.

On 4/23/2014 11:10 PM, John Monahan wrote:

You were right Rob, the path was wrong.  I have F:\DOSBOX as the root
directory but use Mount F F:\DOSBOX

So I should have had
PATH F:\PALASM\EXE
SET PALASM=F:\PALASM\

Using that, the Minimize Boolean option seems to work.   And the F3 now explains errors.

Next question,
Could you write the equations for mA0 and /msXTRQ for me from the attached figure.
I cannot  figure out how you get more than one layer down without using brackets in these equations.

John




-----Original Message-----
From: n8vem...@googlegroups.com [mailto:n8vem...@googlegroups.com]
On Behalf Of Rob Doyle
Sent: Wednesday, April 23, 2014 9:55 PM
To: n8vem...@googlegroups.com
Subject: Re: [N8VEM-S100:3205] Re: GAL's and PALASM

I think we have the same directory layout but I've mounted my "J drive" differently.

I have:

PALASM.EXE is in J:\PALASM\EXE
PDS files are in J:\S100

Environment variables are:

PATH=J:\PALASM\EXE
PALASM=J:\PALASM\

The trailing slash on PALASM variable is important - but you seem to have that correct.

After compiling, there is an note at the bottom of the screen about:

<F3>Help-errors

When the path is wrong and I press <F3>, I get a notice about which EXE palasm can't find.

Rob.


On 4/23/2014 6:51 PM, John Monahan wrote:


It's been so long ago since I did that MSDOS path stuff!

Here is how I actually have my PALASM4 setup It's on drive F:
The actual PALASM.EXE file is in the directory F:\DOSBOX\PALASM
    That directory has sub directories \DAT \EXAMPLES \EXE \DOC
\S100  <- my GAL .PDS files

These directories were setup that way during the install (except the S100 one).

The only PATH & SET scripts I have are:-

PATH F:\DOSBOX\PALASM\EXE;F\;"%PATH;F:\DOSBOX\PALASM4\EXE"
SET PALASM=F:\PALASM\

Does seem screwed up Rob, now that I see it.
What do you have?

John



-----Original Message-----
From: n8vem...@googlegroups.com
[mailto:n8vem...@googlegroups.com]
On Behalf Of Rob Doyle
Sent: Wednesday, April 23, 2014 5:32 PM
To: n8vem...@googlegroups.com
Subject: Re: [N8VEM-S100:3194] Re: GAL's and PALASM

On 4/22/2014 2:52 PM, monahanz wrote:



However if I set “Y” for “Minimize Boolean” in the Compilation
Options,  the compile does not give an error but no .JED file is
written.



[snip]


Bob, I'm just learning how to use PALASM4.  What I'm trying to
figure out is how to emulate in software the circuit attached here:-


Funny.   I was going to follow up on this.

But first I wanted to play with some of my 'known good' Heath H89 PAL designs.  To my surprise, PALASM4 didn't generate a .JED file...

Once I set the DOS PATH statement correctly, everything worked.

The executable sequence should be:

PARSE
BPP
EXPAND
BPP
MINIMIZE
PALXPT

With the path is not set correctly, PALXPT does not execute and the JED file is not created.

Can you verify?

I'll follow-up on the memory decoder question soon.

Rob.



--
You received this message because you are subscribed to the Google Groups "N8VEM-S100" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem-s100+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
You received this message because you are subscribed to the Google Groups "N8VEM-S100" group.
To unsubscribe from this group and stop receiving emails from it, send an email to n8vem-s100+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.