[kicad-users] Cvpcb crashed, and I can't make it work again!
Since I can't get the yahoo groups search function to work, Ill just go ahead and post this... I'm sorry if its a duplicate question. I was working on a project 2 days ago, a simple power supply board. Everything was going ok, until I decided I would add a hierarchical sheet to my schematic. Before I did that I had added several components to the schematic one at a time and used cvpcb to add them to the board, with great success. I like to do incremental adds to keep from cluttering up the board, so this is why I do it this way... Well anyway, I added the hierarchical sheet and put a LPC2368 on it from the nxp library I downloaded, and added 2 global net labels. I also added the same 2 global labels on the main sheet (Is that the right way to do it?) I then went to re-annotate my schematic(s) and create the netlist. This all went ok as it normally had. Next I ran (or rather tried to run) cvpcb to assign the footprints to the new parts. BAM it crashed right away. I thought maybe I goofed something up adding the new sheet, so I deleted it and the global net labels an reran the netlist, and tried cvpcb again. It still did not work! I then closed everything out and rebooted (this is vista after all...) and tried again. Still nothing! I thought maybe I had corrupted something in one of my files, so I tried to create a new project and run cvpcb there. Nope still does not work! The last thing I tried was to reinstall the binary, and even that did not fix it... Has anyone else seen this happen? My machine specs are as follows: AMD Turion system 2G ram Windows Vista Home (ick I know, but this laptop came with it and Linux does not work with it yet :() kicad was 'installed' in c:/kicad-new/kicad since I used the snapshot. kicad version: 2007-11-29-RC2 Unicode version. I really wish I knew what I had done. If someone needs exact details or example files I can provide them where possible. Thanks, Mike
[kicad-users] Re: Cvpcb crashed, and I can't make it work again!
I believe this is related to a windows only bug in the
FootprintListBox constructor. CVPCB will crash because of the use of
an unitialized pointer in the constructor.
the fix is to add the line
m_ActiveFootprintList = NULL;
to the constructor, line 74 cvpcb/listboxes.cpp
the error occurs in SetActiveFootprintList ...
#ifdef __WINDOWS__
/* Workaround for a curious bug in wxWidgets:
* if we switch from a long list of footprints to a short list
(a filtered footprint list),
* and if the selected item is near the end of the long list,
* the new list is not displayed from the top of the list box
*/
if ( m_ActiveFootprintList )
{
bool new_selection;
if( FullList ) new_selection = TRUE;
else new_selection = FALSE;
if( new_selection != old_selection )
SetSelection( 0, TRUE ); // the exception
occurs here
}
--- In kicad-users@yahoogroups.com, jean-pierre charras - INPG jean-
[EMAIL PROTECTED] wrote:
ahuitzot a écrit :
Since I can't get the yahoo groups search function to work, Ill
just
go ahead and post this... I'm sorry if its a duplicate question.
I was working on a project 2 days ago, a simple power supply
board.
Everything was going ok, until I decided I would add a
hierarchical
sheet to my schematic. Before I did that I had added several
components to the schematic one at a time and used cvpcb to add
them
to the board, with great success. I like to do incremental adds to
keep from cluttering up the board, so this is why I do it this
way...
Well anyway, I added the hierarchical sheet and put a LPC2368 on
it
from the nxp library I downloaded, and added 2 global net labels.
I
also added the same 2 global labels on the main sheet (Is that the
right way to do it?) I then went to re-annotate my schematic(s)
and
create the netlist. This all went ok as it normally had. Next I
ran
(or rather tried to run) cvpcb to assign the footprints to the new
parts. BAM it crashed right away.
Can you send me (or/and send to Dick H.) your files (zip your
project
and send the zipped file).
--
Jean-Pierre CHARRAS
Maître de conférences
Directeur d'études 2ieme année.
Génie Electrique et Informatique Industrielle 2
Institut Universitaire de Technologie 1 de Grenoble
BP 67, 38402 St Martin d'Heres Cedex
Recherche :
Grenoble Image Parole Signal Automatique (GIPSA - INPG)
46, Avenue Félix Viallet
38031 Grenoble Cedex
[kicad-users] Re: Cvpcb crashed, and I can't make it work again!
I believe this is related to a windows only bug in the FootprintListBox constructor. CVPCB will crash because of the use of an unitialized pointer in the constructor. the fix is to add the line m_ActiveFootprintList = NULL; to the constructor, line 74 cvpcb/listboxes.cpp Mike, Jean-Pierre applied this change to svn HEAD and to tags/kicad-2007-Nov/cvpcb/listboxes.cpp versions both, on December 10th. If you can build either the 2007-Nov release from source or HEAD from source, this *may* be your fix. Dick Hollenbeck SoftPLC Corporation http://softplc.com
[kicad-users] News in my site!
Hello ALL! Again, again, sorry my poor english! Are avaliable in my site: - 210 librarys of modules migrated from Eagle to Kicad, also avaliable in http://library.oshec.com, but, I make very work over this, removed many duplicates, corrected varius orientation pins, agrouped many components etc. Resume of 861 librarys, today 210! - 13 new 3D components RJ45, included multi-modules. - 28 new 3D components trimpots. - new release of my catolog of 3d, modules, etc. Enjoy, []'s Renie
[kicad-users] Re: News in my site!
Sorry! The correct link in my message is : http://library.oshec.org
[kicad-users] Re: News in my site!
Sorry again! I'm fault in grettings to Dmitri, for your work and permission to avaliable my rework!
[kicad-users] Aboute librarys to Eeschema migrated in library.oschec.org
Hi, I still! In my previus post I say about librarys of modules avaliable in my site! Only continue, the librarys of components for Eeschema still in work, I'me attempt adjuste to Kicad filosofy, one draw for very components, the ALIAS just! Is many librarys,but, 1 month or 2, can avaliable too!
[kicad-users] Pcbnew Problems
I use kicad daily for reverse engineeering and occasionally PCBNEW for test fixtures. I have been using the 2007-11-29-RC2 release for Windows, I have not layed out a PCB until today. I started a PCB layout, a small circuit (5X3) with six - 16 pin SO14E footprints and two TQFP-44's, 1206 resistors and capacitors, and some LEDs. I read the netlist into pcbnew and as usual the parts were all stacked up on top of each other, no problem. I place the parts manually, I do the entire process manually, PCBNEW is an excellent tool for manually routing a PCB. The problem I started seeing was that I would move a part, and place it. I would go to move the next part, and I would grab the same part off of the stack that I just placed. About half the time a part I placed would stay where I placed it. I finally gave up and went back to the July release. I completed the board in a couple of hours.
[kicad-users] Re: Pcbnew Problems
--- In kicad-users@yahoogroups.com, daystar1013 [EMAIL PROTECTED] wrote: I use kicad daily for reverse engineeering and occasionally PCBNEW for test fixtures. I have been using the 2007-11-29-RC2 release for Windows, I have not layed out a PCB until today. I started a PCB layout, a small circuit (5X3) with six - 16 pin SO14E footprints and two TQFP-44's, 1206 resistors and capacitors, and some LEDs. I read the netlist into pcbnew and as usual the parts were all stacked up on top of each other, no problem. I place the parts manually, I do the entire process manually, PCBNEW is an excellent tool for manually routing a PCB. The problem I started seeing was that I would move a part, and place it. I would go to move the next part, and I would grab the same part off of the stack that I just placed. About half the time a part I placed would stay where I placed it. I finally gave up and went back to the July release. I completed the board in a couple of hours. One of the changes we made in this release involves mouse clicking. (And for a good reason I'll add right up front. There is no going back.) Many of the program's actions happen now on the mouse release, whereas they used to happen on a mouse press. So you might look at what makes up your environment, including your mouse driver, your mouse, and your version of Windows. Also consider how you are using the mouse. Try slowing down and verifying that when you drop the footprint in place, it stays there. Others do not seem to be having this problem.
