Error Footprint Wizard -- BGA

When I open the Footprint Wizard, I select row 5 BGA. Afterwards, I get a alert window with some cryptic debugging output. When I dismiss the alert window, there is no generated footprint. Also, if I modify pitch, size, columns or rows parameters the alert window appears again.

If I choose another option, like the wizard for SOIC, then Kicad appears to run normally without an error message.

Any suggested would help. I’m running on Ubuntu.

Linux clyde 5.8.0-7625-generic #26~1603389471~20.04~f6b125f~dev-Ubuntu SMP Thu Oct 22 20:29:31 x86_64 x86_64 x86_64 GNU/Linux

Here is a screenshot of the alert window: something about an object type error in a python script called bga_wizard.py line 87 and PadArray.py line 215.

ErrorMessage

Version Info:

Application: ModEdit
Version: 5.1.7-a382d34a8~87~ubuntu20.04.1, release build
Libraries:
wxWidgets 3.0.4
libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.7 libidn2/2.2.0 libpsl/0.21.0 (+libidn2/2.2.0) libssh/0.9.3/openssl/zlib nghttp2/1.40.0 librtmp/2.3
Platform: Linux 5.8.0-7625-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8) GTK+ 3.24
Boost: 1.71.0
OpenCASCADE Community Edition: 6.9.1
Curl: 7.68.0
Compiler: GCC 9.3.0 with C++ ABI 1013

Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=ON
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_PYTHON3=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_WXPYTHON_PHOENIX=ON
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_USE_OCC=OFF
KICAD_SPICE=ON

This is a known bug, and a fix was already committed.
However, the fix was reversed, as it apparently caused some problems on KiCad Installations (I think it’s for the people who still use Python2.)

You can get to the fix by following:

Which links to:

If you compare it with other commits, you will find references to the “PadArrayGrid, self” text in about 5 or 6 different locations.

Ah, I see. I tweaked the python script like commit e622627 and the problem went away. Should work for now.

Thanks for your help. Much appreciated.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.