-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Electrical Rules Checker dialog not responding" error when running ERC #33
Comments
Hi @LIV2 ! Which version are you using? Try using the current git code. The ERC fails when no interposer is available, which is the case of ARM64. BTW: the interposer mechanism is faster and more reliable. We could try to make it work for ARM64. There are some interest of other people (using docker images on macOS with CPU emulation). |
Hi @set-soft I was using the latest from the Master branch, I've installed v2.2.8 via pip now but still have the same issue What would be required to get the interposer working on ARM64? I wonder if there's any way I can help?
|
Hi @LIV2 !
I'll suggest trying with KiCad 7.0.8. The regression tests passed for 7.0.5 and 7.0.8, never tried 7.0.6 and 7.0.7. For 7.0.8 I found changes in the dialogs.
If you can try code from GitHub I'll suggest trying:
|
Hi, Yep it does indeed work with 7.0.8 (without interposer) thanks for that :) I built libinterposer.so and renamed it to libinterposer_aarch64.so and found that when I run eeschema_do it mostly works but gets stuck at "Wait for ERC file creation" run_erc_eeschema_screencast 2.ogv.zip |
Hi @LIV2 ! Sorry for the big delay. The problem seems to be a missing call to close the ERC report file. Can you try defining the environment variable KIAUTO_USE_PID_FOR_CREATE to 1? Something like It looks like I'm missing some of the close calls. The bizarre thing is that the above workaround was designed to be used when using VirtioFS on an emulated docker image running on macOS! I'm catching fclose and close. But looking at the code on the open side I'm catching: fopen64, fopen, open64 and open. I think this is because I found that fclose64 and close64 doesn't really exist. But perhaps they do on ARM64. I'm adding them to the interposer. You can try recompiling it, define KIAUTO_USE_PID_FOR_CREATE to 0 and then check if this is the real problem. The patch is e7d5edd |
Hi @LIV2 ! Any news about it? This issue may be related to INTI-CMNB/KiBot#367, INTI-CMNB/KiBot#509 and INTI-CMNB/kicad_auto#14 |
Hi, Sorry for the late response! I will try to test this out again soon and get back to you |
Testing in a Debian trixie docker container, Kicad 7.0.10 with the latest kiauto commit (19ec2fa) With interposer:
|
With 7.0.10 ERC fails even with interposer disabled, I guess something has changed with the Dialog again and that using interposer should fix such issues Works fine without interposer on 7.0.8 though This is running inside a docker container on an Apple silicon machine if that makes any difference |
Hi @LIV2 ! I didn't have time to check 7.0.10, the last working is 7.0.9 |
@set-soft with kicad 7.0.9 and interposer disabled it times out after
But works fine on 7.0.8 All versions time-out with the same timeout error as my previous comment when interposer is enabled. VirtioFS works fine now though so that particular patch works |
Hi @LIV2 ! Just to make things clear: Are you using the KIAUTO_USE_PID_FOR_CREATE environment variable? |
Hi @LIV2 ! New updates on this:
This issue should be solved upgrading to KiCad 8, any issue related to the new mechanism should be reported separately. So now the status is: for ARM64 if you can't solve ERC problems with the previously discussed mechanisms, just go for KiCad 8. |
Hi,
I'm attempting to use KiAuto on Ubuntu Mantic on ARM64
Kicad version 7.0.7 installed from the Ubuntu package repository
I get "ERROR:Electrical Rules Checker dialog not responding" when attempting to run ERC
Attached are the screencast & logs
run_erc_eeschema_screencast.ogv.zip
The text was updated successfully, but these errors were encountered: