Re: Use of PLCCs

On Tue, 20 Sep 2005 01:53:10 GMT, "Dan" <nospam@nosite.com> wrote:

The PLCC is the new package.  Import the processor to a custom library

(with the existing package).

Import the PLCC socket to the same library.

Make a part, or add the PLCC socket as a new package, giving the PLCC

pins the appropriate signal names by connecting them.

That ought to give you the part in the PLCC socket

I've done this with an ATMEL chip to put it on a 100 pin carrier.

Works fine.

Harvey

 

On 19-Sep-2005, Paul Romanyszyn <pgr@arcelectronicsinc.com> wrote:

 

Dan wrote:

I just purchased Eagle Standard after using Lite for a while.  I am

trying

to create a board with an MC68HC11CFN3, using a 68 pin PLCC.  The F1

part in

the schematic specifies the PLCC, but when I create a board, the

configuration of the pins is that of the processor without the PLCC.

 

If I try to add the PLCC, the program warns me that no back-annotation

will

be done.  Closing the schematic allows me to add the PLCC to the board,

but

the pin arrangement conflicts with the pins of the 6811 itself.

 

How do I go about using the PLCC in my design?

 

Thanks,

Dan

 

If you are you looking for the PLCC socket you will have to add that

package in to the lib part and then connect it.

We have used sockets with the hc11f1 and had problems. Soldering it to

the pcb should be more reliable.

 

Paul

 

Unfortunately, the PLCC is already given as the package for the part.  I'm

not sure what you mean when you say you had problems using the PLCC.  I have

used this PLCC for the F1 in an earlier design (not done with Eagle) and the

socket is indeed soldered to the board.  As far as I know, that's the only

way to do it.  The PLCC is wired internally to route the processor pins to

the hole pattern of the PLCC.  However, the Eagle part seems not to do this.

If I add the PLCC to the board without back-annotation, a DRC gives

multiple errors of clearance between the processor chip and the PLCC.  You

cannot solder the chip itself without destroying it, and the design makes

that impossible anyway.

 

So, the part gives the PLCC as the package, but when I switch to board view,

the PLCC is nowhere to be found.  Perhaps the implementation of the part is

faulty?  I will take a look at the part definition, including the

connections set up in the library.

 

Any ideas?  I am less than pleased if Eagle will not properly allow use of

this processor.  That would make it 600 bucks down the drain.

 

Thanks,

Dan