make_bga.ulp - was (long ago) Re: importing a BMP

On 7/27/2013 11:57 PM, William Toner wrote:

Hi all, I'm getting the same kind of permission error as the guy from

this old thread about importing a BMP:

http://www.eaglecentral.ca/forums/index.php/m/149085/b7a7f12f912cdd48ce7fe51e23f05511/?srch=ulp+permission#msg_149085

 

 

Can't open C:\Program Files(x86)\EAGLE-5.12.0\bga256_package.scr

 

(using the default GUI values that make_bga.ulp fills in for me, no

changes)

 

 

I'm not sure what to do. I removed all $EAGLEDIR things in my directory

options, so I don't expect it to be looking there for anything.

 

As the solution for the thread I linked to suggests, I've made it so

there should only be directories for libs, projects, ulps, scripts, etc.

in the place where I am able to make edits. But It's still trying to go

into the root Eagle install dir for the script file it wants to write out.

 

I am using Eagle 5.12.0 Pro, trying to make a library package using this

BGA ulp, using Windows 7 Ultimate 64bit.

 

The directory location of my library is:

F:\documents\billt\projects\eagle\my_libraries\error_demo.lbr

 

The contents of my directory options window is:

Libraries:

F:\documents\billt\projects\eagle\my_libraries;F:\documents\billt\projects\eagle\others_libraries

 

 

Design Rules: F:\documents\billt\projects\eagle\DesignRules

 

User Language Programs: F:\documents\billt\projects\eagle\ulps

 

Scripts: F:\documents\billt\projects\eagle\scripts

 

CAM Jobs: F:\documents\billt\projects\eagle\CAMjobs

 

Projects:

F:\documents\billt\projects\eagle\my_projects;F:\documents\billt\projects\eagle\others_projects

 

 

So, with all the C:\... tool install dir stuff removed already, how do I

get through this?

 

I run this by starting Eagle and opening my library, which I have

written a small description for, and do have a bga256 package name

defined and saved, but is empty on the footprint layout screen. I've

tried this from the empty bga256 footprint screen, as well as fromt eh

library screen without opening any packages/symbols/devices. Same error

either way.

 

 

(P.S. I do plan to upgrade to Eagle 6.x Pro when my finances give me a

break, but someone I am collaborating with on some of this design has

5.x and last I heard no plans for 6.x. so I'm sortof stuck with 5 anyway)

 

I really do appreciate some help with this. I intend to meddle with a

very large 43x43 BGA (reference design is 20 layers, I hope to reduce

that to at least no more than Eagle 5's 16 max. Does 6 go above 16 now?)

 

Bill Toner

amigabill at that gee mail place

OK, I spent some time in help and hacked up what I think is an

improvement to the original make_bga.ulp script:

     /* package_file = package_name + "_package.scr"; */

     package_file = path_scr[0] + '/' + package_name + "_package.scr";

Do path/filenames by default start at the eagle tool install dir? Is

there a better way to output elsewhere?

Bill Toner

amigabill at that gee mail place

On 7/28/2013 12:15 AM, William Toner wrote:

On 7/27/2013 11:57 PM, William Toner wrote:

Hi all, I'm getting the same kind of permission error as the guy from

this old thread about importing a BMP:

http://www.eaglecentral.ca/forums/index.php/m/149085/b7a7f12f912cdd48ce7fe51e23f05511/?srch=ulp+permission#msg_149085

 

 

 

Can't open C:\Program Files(x86)\EAGLE-5.12.0\bga256_package.scr

 

(using the default GUI values that make_bga.ulp fills in for me, no

changes)

 

 

I'm not sure what to do. I removed all $EAGLEDIR things in my directory

options, so I don't expect it to be looking there for anything.

 

As the solution for the thread I linked to suggests, I've made it so

there should only be directories for libs, projects, ulps, scripts, etc.

in the place where I am able to make edits. But It's still trying to go

into the root Eagle install dir for the script file it wants to write

out.

 

I am using Eagle 5.12.0 Pro, trying to make a library package using this

BGA ulp, using Windows 7 Ultimate 64bit.

 

The directory location of my library is:

F:\documents\billt\projects\eagle\my_libraries\error_demo.lbr

 

The contents of my directory options window is:

Libraries:

F:\documents\billt\projects\eagle\my_libraries;F:\documents\billt\projects\eagle\others_libraries

 

 

 

Design Rules: F:\documents\billt\projects\eagle\DesignRules

 

User Language Programs: F:\documents\billt\projects\eagle\ulps

 

Scripts: F:\documents\billt\projects\eagle\scripts

 

CAM Jobs: F:\documents\billt\projects\eagle\CAMjobs

 

Projects:

F:\documents\billt\projects\eagle\my_projects;F:\documents\billt\projects\eagle\others_projects

 

 

 

So, with all the C:\... tool install dir stuff removed already, how do I

get through this?

 

I run this by starting Eagle and opening my library, which I have

written a small description for, and do have a bga256 package name

defined and saved, but is empty on the footprint layout screen. I've

tried this from the empty bga256 footprint screen, as well as fromt eh

library screen without opening any packages/symbols/devices. Same error

either way.

 

 

(P.S. I do plan to upgrade to Eagle 6.x Pro when my finances give me a

break, but someone I am collaborating with on some of this design has

5.x and last I heard no plans for 6.x. so I'm sortof stuck with 5 anyway)

 

I really do appreciate some help with this. I intend to meddle with a

very large 43x43 BGA (reference design is 20 layers, I hope to reduce

that to at least no more than Eagle 5's 16 max. Does 6 go above 16 now?)

 

Bill Toner

amigabill at that gee mail place

 

OK, I spent some time in help and hacked up what I think is an

improvement to the original make_bga.ulp script:

 

 

     /* package_file = package_name + "_package.scr"; */

     package_file = path_scr[0] + '/' + package_name + "_package.scr";

 

 

Do path/filenames by default start at the eagle tool install dir? Is

there a better way to output elsewhere?

 

Bill Toner

amigabill at that gee mail place

 

Eh, while this corrected the error abotu writing out the script file, it

does not yet get me my giant BGA footprint. I get errors that Pad Name

A1, A2, A3 etc. already exist. I'm guessing this happens instead of

stepping to AA1, AA2 etc., then AB1, AB2, etc... :/ More hacking to go...

Bill Toner

amigabill at that gee mail place

William Toner wrote:

On 7/28/2013 12:15 AM, William Toner wrote:

On 7/27/2013 11:57 PM, William Toner wrote:

Hi all, I'm getting the same kind of permission error as the guy

from this old thread about importing a BMP:

 

http://www.eaglecentral.ca/forums/index.php/m/149085/b7a7f12f912cdd48ce7fe51e23f05511/?srch=ulp+permission#msg_149085

 

 

Can't open C:\Program Files(x86)\EAGLE-5.12.0\bga256_package.scr

 

(using the default GUI values that make_bga.ulp fills in for me, no

changes)

 

 

I'm not sure what to do. I removed all $EAGLEDIR things in my

directory options, so I don't expect it to be looking there for

anything.

 

As the solution for the thread I linked to suggests, I've made it so

there should only be directories for libs, projects, ulps, scripts,

etc. in the place where I am able to make edits. But It's still

trying to go into the root Eagle install dir for the script file it

wants to write out.

 

I am using Eagle 5.12.0 Pro, trying to make a library package using

this BGA ulp, using Windows 7 Ultimate 64bit.

 

The directory location of my library is:

F:\documents\billt\projects\eagle\my_libraries\error_demo.lbr

 

The contents of my directory options window is:

Libraries:

 

F:\documents\billt\projects\eagle\my_libraries;F:\documents\billt\projects\e

agle\others_libraries

 

 

Design Rules: F:\documents\billt\projects\eagle\DesignRules

 

User Language Programs: F:\documents\billt\projects\eagle\ulps

 

Scripts: F:\documents\billt\projects\eagle\scripts

 

CAM Jobs: F:\documents\billt\projects\eagle\CAMjobs

 

Projects:

 

F:\documents\billt\projects\eagle\my_projects;F:\documents\billt\projects\ea

gle\others_projects

 

 

So, with all the C:\... tool install dir stuff removed already, how

do I get through this?

 

I run this by starting Eagle and opening my library, which I have

written a small description for, and do have a bga256 package name

defined and saved, but is empty on the footprint layout screen. I've

tried this from the empty bga256 footprint screen, as well as fromt

eh library screen without opening any packages/symbols/devices.

Same error either way.

 

 

(P.S. I do plan to upgrade to Eagle 6.x Pro when my finances give

me a break, but someone I am collaborating with on some of this

design has

5.x and last I heard no plans for 6.x. so I'm sortof stuck with 5

anyway)

 

I really do appreciate some help with this. I intend to meddle with

a very large 43x43 BGA (reference design is 20 layers, I hope to

reduce that to at least no more than Eagle 5's 16 max. Does 6 go

above 16 now?)

 

Bill Toner

amigabill at that gee mail place

 

OK, I spent some time in help and hacked up what I think is an

improvement to the original make_bga.ulp script:

 

 

     /* package_file = package_name + "_package.scr"; */

     package_file = path_scr[0] + '/' + package_name +

"_package.scr";

 

 

Do path/filenames by default start at the eagle tool install dir? Is

there a better way to output elsewhere?

 

Bill Toner

amigabill at that gee mail place

 

 

Eh, while this corrected the error abotu writing out the script file,

it does not yet get me my giant BGA footprint. I get errors that Pad

Name A1, A2, A3 etc. already exist. I'm guessing this happens instead

of stepping to AA1, AA2 etc., then AB1, AB2, etc... :/ More hacking

to go...

 

Bill Toner

amigabill at that gee mail place

Hi Bill

make_BGA.ulp is a bit old (2004) and so does not cater well for large BGAs.

The ULP is taking rows from the ASCII table so an array  over about 20x20

goes all wrong and shoots past the end of capital letters, does some

punctuation and then starts on lowercase letters. so eventually you get an

'a1' which matches your already created 'A1'

Try another ULP;  make-symbol-device-package-bsdl.ulp (by the same author).

It seems it can take an input file to create/ match signal names to balls.

That would save a lot of work connecting pins to pads.

All the best

Warren

--

Viewed / responded via the newsgroup at

news.cadsoft.de

On 7/28/2013 3:22 AM, Warren Brayshaw wrote:

Hi Bill

make_BGA.ulp is a bit old (2004) and so does not cater well for large BGAs.

The ULP is taking rows from the ASCII table so an array  over about 20x20

goes all wrong and shoots past the end of capital letters, does some

punctuation and then starts on lowercase letters. so eventually you get an

'a1' which matches your already created 'A1'

 

Try another ULP;  make-symbol-device-package-bsdl.ulp (by the same author).

It seems it can take an input file to create/ match signal names to balls.

That would save a lot of work connecting pins to pads.

 

All the best

Warren

Hi Warren,

Thank you, this works much better! I need to look into the other ulp

about splitting symbols as well, to see if that will help make this

giant sea of pins symbol into something more manageable. Trying to

figure out the best way to get things to look like my reference design

symbols they provided.

Bill