[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: gEDA-user: DRC2 Problem (gEDA-2005080313)



Hi Carlos, Hi Neal,

I just stumbled across the same problem (I simply tried to 
run "gnetlist -v -g drc2 one.sch two.sch" with the 
schematics described in the gschem-> gsch2pcb -> PCB tutorial)
and gnetlists answer ended with:
...
ERROR: In procedure apply:
ERROR: Wrong type argument in position 1: #<variable 8059f10 binding: #<primitive-procedure <>>

Do you happen to know, whether this problem has been solved in the meantime?

Best regards,
Holger.

On Mon, 09 May 2005 20:02:36,  Carlos Nieves Ónega wrote:
> Hi Neal,
> the call to scm_sort_list_x "only" sorts the list returned by the
> function g_get_slots, which is used by the backends to get the slots
> used in a package. For example: if you use slots 1 and 3 of U1 in your
> schematic, g_get_slots will always return a list (1, 3) after calling
> scm_sort_list_x. Commenting out that call, g_get_slots may return (3,
> 1), so it will only affect to the backends relying on a sorted list.
> IIRC, it shouldn't affect any report made by the drc2 backend. I think
> others backends are not affected, but I can't tell it for sure. Just try
> it.
> 
> Regards,
> 
> Carlos
> 
> El lun, 09-05-2005 a las 12:32 -0500, Neal Baer escribió:
>> Carlos,
>> Thanks for your response. 
>> Do know, by commenting out the "scm_sort_list_x" call  in function "g_get_slots",
>>    
>>     * Will this affect "gnetlist -g drc2" report generation ?
>>     * Will this affect "gnetlist -g PCB"  netlist generation?
>> 
>> Thanks,
>> 
>> Neal
>> 
>> Carlos Nieves Ónega wrote:
>> 
> >Hi Neal,
> >this is not a drc2 bug, but a gnetlist one. I found where the problem
> >is, but I'm not a scheme guru, so I don't understand yet what is
> >happening.
> >The problem is in g_get_slots function, in g_netlist.c. There is a call
> >to scm_sort_list_x just before the function's end. This is where this
> >error is generated. I tried to just commenting out the call to
> >scm_sort_list_x, and gnetlist worked well.
> >The list passed to scm_sort_list_x is (1, 1).
> >
> >Anyone knows what's the problem here?
> >
> >Thanks,
> >
> >Carlos
> >
> >El sáb, 07-05-2005 a las 23:05 -0500, Neal Baer escribió:
> >  
> >
> >>I just compiled gEDA-2005080313, SuSE 9.2 yesterday.
> >>
> >>I found what seems to be a bug with gnet-drc2.scm.  Creating a simple 
> >>schematic of 2 resistors, having the same  reference (i.e. R1), same or 
> >>different values, causes the DRC2 output as shown below.
> >>
> >>I found the problem with a slotted part, thus each slot instance has the 
> >>same reference designator.  This stops the DRC2 testing to complete, 
> >>which deems it useless in this scenario.  I had to ensure that the 
> >>reference numbers differ for the slotted parts to get DRC2 to complete 
> >>its test.
> >>
> >>Creating a netlist with the same reference numbers for slotted parts 
> >>worked properly.
> >>
> >>Any suggestions or workarounds?
> >>
> >>Thanks,
> >>
> >>Neal  
> >>
> >>DRC OUTPUT OF TEST SCHEMATIC WITH DUPLICATE REFERENCES
> >>
> >>    
> >>
> >>>nbaer@linux:~/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER> 
> >>>gnetlist -g drc2 test.sch -o -
> >>>gEDA/gnetlist version 20050313
> >>>gEDA/gnetlist comes with ABSOLUTELY NO WARRANTY; see COPYING for more 
> >>>details.
> >>>This is free software, and you are welcome to redistribute it under 
> >>>certain
> >>>conditions; please see the COPYING file for more details.
> >>>
> >>>Remember to check that your schematic has no errors using the drc2 
> >>>backend.
> >>>You can do it running 'gnetlist -g drc2 your_schematic.sch -o 
> >>>drc_output.txt'
> >>>and seeing the contents of the file drc_output.txt.
> >>>
> >>>Loading schematic 
> >>>[/home/nbaer/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER/test.sch]
> >>>Checking non-numbered parts...
> >>>
> >>>Checking duplicated references...
> >>>ERROR: Duplicated reference R1.
> >>>
> >>>Checking nets with only one connection...
> >>>ERROR: Net has only one connected pin: dgnd
> >>>ERROR: Net has only one connected pin: unnamed_net1
> >>>
> >>>Checking type of pins connected to a net...
> >>>
> >>>Checking unconnected pins...
> >>>
> >>>Checking slots...
> >>>
> >>>Checking duplicated slots...
> >>>ERROR: In procedure apply:
> >>>ERROR: Wrong type argument in position 1: #<variable 80661b8 binding: 
> >>>#<primitive-procedure <>>
> >>>nbaer@linux:~/Projects/Terrigena/FILTER-DESIGN/FRONT-END-FILTER>       

-- 
Holger Oehm <holger.oehm@xxxxxxxxxxxxxx>
Public key <A HREF="http://www.holger-oehm.de/public-key.asc";>here</A>,
KeyID: B50E51A9, Key-Length: 1024 Bit,
Key fingerprint: E92A 5C2C 497A 44ED 23C0  DB66 1DD9 3EF7 B50E 51A9

Attachment: pgpYs05vW2ClK.pgp
Description: PGP signature