[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: gEDA-user: hierarchy and refdes_renum
Hi Anthony,
If I add netname to the offended net, the spnet goes to the next net and
report next error. Does it mean that all nets should be named?
Thanks,
Alex.
On 06/24/2009 12:19 AM, Anthony Shanks wrote:
> Hi Alex, please download the newest spnet on my site and let me know
> how it goes, it should be a bit more compatible.
>
> Here is whats new:
>
> * Comments in both .spnetlibs and .spentrc (# is the comment character)
> * Won't bail out on empty lines in either file above
> * NMOS_TRANSISTOR and PMOS_TRANSISTOR as 4 terminal mosfets
> * It doesnt matter if a component has brackets or not like in your
> original example. If there is no brackets (therefore no attributes)
> the component is ignored.
> * All power symbols that come with gschem now work properly
>
> Eager to here how this new version works and how compatible it is. In
> the next release (perhaps tomorrow) I will add the support to pull
> librarys already defined in gedarc files. Will also try to add autonet
> naming for unnamed nets.
>
> -Anthony
>
> On Tue, Jun 23, 2009 at 2:46 PM, Anthony Shanks<yamazakir2@xxxxxxxxx> wrote:
>
>> Are titleblocks "legal" (without lack of a better term) without
>> brackets or were they just that way in your schematic for some reason?
>> I thought all components had brackets but maybe only components with
>> attributes have brackets?
>>
>> I took a look at v2i_2v.sym, it doesn't look like it has any schematic
>> file attached to it. Also spnet requires subckts with lower level
>> schematics to have the attribute to device=SUBCKT. There is no
>> standard attribute in the gEDA flow to define a subckt so thats what I
>> choose for spnet. Take a look at my latch example on my website for
>> what the properties of subckts look like.
>>
>> Net stitch failure happens usually when there is a net without a
>> netname attached to one of the nets its connected too. There is no
>> autonet name feature yet but I plan to add it.
>>
>> Also which devices in your schematic don't have refdes?
>>
>> -Anthony
>>
>> On Tue, Jun 23, 2009 at 1:59 PM, A.Burinskiy<alexbour@xxxxxxxxx> wrote:
>>
>>> Hi Anthony,
>>>
>>> The reason for the message
>>>
>>> -E- Fatal Error: Invalid Component attr "C 42200 44200 1 0 0 gnd-1.sym"
>>>
>>> Was that first component, that is title-B block listed in the
>>> test_v2i_2.sch without pair of { } !
>>>
>>> Symbol spice-lib.sym is a special symbol. I did it. I think netlister
>>> should support custom symbols.
>>> v 20090328 2
>>> B 0 400 1900 300 3 0 0 0 -1 -1 0 -1 -1 -1 -1 -1
>>> T 100 300 9 10 0 1 0 0 1
>>> device=library
>>> T 100 500 9 10 1 1 0 0 1
>>> refdes=A?
>>> T 600 500 9 10 1 0 0 0 1
>>> SPICE LIBR
>>> T 500 200 8 10 1 1 0 0 1
>>> file=?
>>> T 100 200 9 10 1 0 0 0 1
>>> File:
>>> T 0 -5 8 10 1 0 0 0 1
>>> corner=TYP
>>>
>>> And v2i_2v.sym is real subcircuit.
>>>
>>> After artificially adding this braces I've got (please note, that
>>> (42300;44500) corresponds to connection point of gnd symbol pin)
>>>
>>> $ spnet test_v2i.sch
>>>
>>> spNet v0.9.1.2
>>> gEDA/gschem Netlister
>>> Copyright 2009 Anthony Shanks
>>>
>>> -I- Starting Build of Cell: test_v2i
>>> -I- Adding Library: "sym"
>>> -I- Adding Library: "power"
>>> -I- Combining Cells
>>> -W- Device in cell test_v2i does not have a refdes, ignoring.
>>> -W- Device in cell test_v2i does not have a refdes, ignoring.
>>> -E- Net stitch failure in cell test_v2i near point 42300,44500.
>>>
>>> Thanks,
>>> Alex.
>>>
>>>
>>>
>>> On 06/23/2009 10:54 AM, Anthony Shanks wrote:
>>>
>>>> Hmm, a few things.
>>>>
>>>> Is that ground symbol the default that comes with gschem (device=none,
>>>> netname=0)? Can't look right now, at work.
>>>>
>>>> I also noticed a few things in your schematic that is definitely not
>>>> supported (right now):
>>>>
>>>> C 47000 49500 1 0 0 spice-lib.sym
>>>> C 50000 44900 1 0 0 v2i_2v.sym
>>>>
>>>> What are these? I assume the spice-lib.sym is a subckt netlist but I
>>>> don't know what the other is.
>>>>
>>>> A quick fix in your case with the ground symbol is just to add the
>>>> attribute device=globalnode and net=0.
>>>>
>>>> -Anthony
>>>>
>>>> On Tue, Jun 23, 2009 at 10:00 AM, A.Burinskiy<alexbour@xxxxxxxxx> wrote:
>>>>
>>>>
>>>>> Hi Anthony,
>>>>>
>>>>> Yes, there is device that is not in the list and this is ground symbol.
>>>>> Please find diff file and test_v2i.sch attached. That is what I have (Please
>>>>> note, that your search for '=' sign, while there is no any '=' sign in the
>>>>> string...)
>>>>>
>>>>> $ spnet test_v2i.sch
>>>>>
>>>>> spNet v0.9.1.2
>>>>> gEDA/gschem Netlister
>>>>> Copyright 2009 Anthony Shanks
>>>>>
>>>>> -I- Starting Build of Cell: test_v2i
>>>>> -I- Adding Library: "sym"
>>>>> -I- Adding Library: "power"
>>>>> -I- Combining Cells
>>>>>
>>>>> -E- Fatal Error: Invalid Component attr "C 42200 44200 1 0 0 gnd-1.sym".
>>>>>
>>>>> $ more ~/.spnetlibs
>>>>> library: /home/username/tsmc "sym"
>>>>> library: /usr/local/share/gEDA/sym "power"
>>>>>
>>>>>
>>>>>
>>>>> On 06/23/2009 09:39 AM, Anthony Shanks wrote:
>>>>>
>>>>>
>>>>>> Comments are not supported yet, it's on the todo list.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Is the new code working yet? the invalid compoent error will come up
>>>>>> with there is a symbol in your schematic without a valid device
>>>>>> attribute. Here is a list of devices that are current supported
>>>>>> (device=)
>>>>>>
>>>>>>
>>>>>>
>>>>>> RESISTOR
>>>>>>
>>>>>> CAPACITOR
>>>>>>
>>>>>> INDUCTOR
>>>>>>
>>>>>> NPN_TRANSISTOR
>>>>>>
>>>>>> PNP_TRANSISTOR
>>>>>> NMOS3T
>>>>>>
>>>>>> NMOS4T
>>>>>>
>>>>>> PMOS3T
>>>>>>
>>>>>> PMOS3T
>>>>>>
>>>>>> SUBCKT
>>>>>> VOLTAGE_SOURCE
>>>>>> CURRENT_SOURCE
>>>>>>
>>>>>> PIN
>>>>>>
>>>>>>
>>>>>>
>>>>>> As stated I will add suport for [N|P]MOS_TRANSISTOR in the next
>>>>>> release as a 4 terminal mosfet device. Besides this, do you have any
>>>>>> components in your schematic that is not on the above list?
>>>>>>
>>>>>>
>>>>>>
>>>>>> BTW, thanks for all your help in debugging.
>>>>>>
>>>>>>
>>>>>>
>>>>>> -Anthony
>>>>>>
>>>>>> On Tue, Jun 23, 2009 at 3:12 AM, A.Burinskiy<[1]alexbour@xxxxxxxxx>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Anthony,
>>>>>> Yes, the cause of segfault are empty strings at the end of file. Do
>>>>>> you
>>>>>> support comment out in .spnetlibs? I will go ahead and try your new
>>>>>> code.
>>>>>> Thanks,
>>>>>> Alex
>>>>>>
>>>>>> On 06/23/2009 03:03 AM, Anthony Shanks wrote:
>>>>>> > Wow. I guess I have a lot to learn as far as releasing code and
>>>>>> > compiling versions go because it works fine on my end with gcc 4.3.
>>>>>> > Sorry this is the first time I've released code (this big), please
>>>>>> > bare with me.
>>>>>> >
>>>>>> > I tried one lib in spnetlibs with your line exactly and it works
>>>>>> fine
>>>>>> > without a segfault. Can you attach your spnetlibs to ensure I'm 100%
>>>>>> > using exactly? One thing I did notice though is that if the file
>>>>>> > exists but is empty it does segfault. I just fixed this error and
>>>>>> > reuploaded it but I think it may go back to giving you the invalid
>>>>>> lib
>>>>>> > error (you can redownload it from the same link). Are you sure there
>>>>>> > are not blank lines or anything in your file?
>>>>>> >
>>>>>> > Also about number 1 and number 2 thoughts. That plan was already in
>>>>>> > the works for the official release. Most of the symbols from gschem
>>>>>> > work with spnet except the mosfets since geda does not have a 3
>>>>>> > terminal symbol. I plan on making [N,P]MOS_TRANSISTOR work for 4
>>>>>> > terminal devices. Also I plan for spnet to read the libraries
>>>>>> already
>>>>>> > defined in the gEDA rc files. This will also be done in the next
>>>>>> > release. I'll try to get a version that does this by the end of the
>>>>>> > week however.
>>>>>> >
>>>>>> > Let me know how it goes after you try the newest update.
>>>>>> >
>>>>>> > -Anthony
>>>>>> >
>>>>>> >
>>>>>>
>>>>>> _______________________________________________
>>>>>> geda-user mailing list
>>>>>> [2]geda-user@xxxxxxxxxxxxxx
>>>>>> [3]http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>>>
>>>>>> References
>>>>>>
>>>>>> 1. mailto:alexbour@xxxxxxxxx
>>>>>> 2. mailto:geda-user@xxxxxxxxxxxxxx
>>>>>> 3. http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> geda-user mailing list
>>>>>> geda-user@xxxxxxxxxxxxxx
>>>>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> geda-user mailing list
>>>>> geda-user@xxxxxxxxxxxxxx
>>>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>>
>>>>>
>>>>>
>>>>>
>>>> _______________________________________________
>>>> geda-user mailing list
>>>> geda-user@xxxxxxxxxxxxxx
>>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> geda-user mailing list
>>> geda-user@xxxxxxxxxxxxxx
>>> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>>>
>>>
>
>
> _______________________________________________
> geda-user mailing list
> geda-user@xxxxxxxxxxxxxx
> http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
>
>
_______________________________________________
geda-user mailing list
geda-user@xxxxxxxxxxxxxx
http://www.seul.org/cgi-bin/mailman/listinfo/geda-user