Error , impossible to load a patch anymore

i have a gills, that was working fine.
last patch i loaded was the polysynth , sounding great , all fine.
but then i’ve tested to power the gills with an ac power supply, i used the one from my monopoly, 12v and good polarity , and it turned on fine.
don’t know if its related but now, i can’t load any patch…
i have this error :
Compiling patch…
! C:\Users\Lol PC\ksoloti/build/xpatch.h.gch
internal error in mingw32_gt_pch_use_address, at config/i386/host-mingw32.c:190: MapViewOfFileEx: Tentative d�acc�s � une adresse non valide.

make: *** [C:\Users\Lol PC\ksoloti/build/xpatch.bin] Error 1
Shell task failed, exit value: 1
Patch compilation failed: C:\Users\Lol PC\ksoloti\1.0.12\axoloti-factory\patches\tutorials\01_sine_oscillator.axp

no matter which patch i’m trying to load.
the kso app , says the board i sright powered , connected , with sd card mounted.

anyone experienced something like that?
any clue what could fix the problem?

thanks a lot
Laurent

Hi, yeah that is an old and known issue, somehow it can happen on Windows, possibly the patch creation is interrupted by a system service (like anti virus or similar) or automatic update.

Go to C:\Users\{username}\ksoloti\build\ and delete the files inside there. Restarting Windows won’t hurt either.

This should fix it? Let me know if not!

Cf.
https://sebiik.github.io/community.axoloti.com.backup/t/error-when-going-live-with-the-patching/5839ba9.html?page=3

BTW this error will (hopefully) be handled automatically after the v1.1.0 update (currently in beta)

1 Like

I had this happen a couple of weeks back, and deleting the build files worked. Just make sure the patcher isn’t running when you delete the files because it confuses things even more.

1 Like

thank you for the infos.
i think i did a mistake , before seeing your answers.
i though that maybe i needed to flash the firmware from the app , so i tried this but after it started it looked like looped , with the diodes keeping blinking . i "ve wait for like 3 minutes , but no evolution so i uplugged and reconnect and since then the red and green diodes keeps blinking and the app says no matching usb devices found.
i think i need more damages than fixing things.
is there a way to initialise back the ksoloti card?
thanks you
Laurent

ok , i managed to do a succesfull firmware flash rescue
now the add says:
Ksoloti Core found.
Not accessible: driver not installed

so i guess i need to reinstall the driver in the ksoloti …
but i don’t really know how to do it, as i didn’t have to do it when i made the gills. everything was working fine , first try

This is weird. You’re correct in that you don’t need to install any drivers (except if you need rescue mode).

Could it be you installed the “Zadig” type of driver for Ksoloti Core not in rescue mode but in normal mode? It’s complicated.

Maybe try to go to the device manager, find Ksoloti Core (it it exists) and “uninstall device”

Something like this:

Then disconnect ksoloti, restart windows and reconnect ksoloti to automatically re-register it.

If the ksoloti is not in the list you may retry the rescue flash. Make sure to do the “Zadig” driver part if Ksoloti Core in rescue mode cant be found.
https://ksoloti.github.io/3-4-rescue_mode.html

1 Like

ok , i found the device , and i did what you said but it did not fix the pb , now when i try to connect the app , it says:
Patcher version 1.0.12-8-19-g2c91ddeb-dirty | Build time 1 May 2024, 00:01:02

Link to firmware CRC EB8B6CD0
Ksoloti Core found.
Not accessible: -12
Ksoloti Core found.
org.usb4java.LibUsbException: USB error 12: Unable to claim interface: Operation not supported or unimplemented on this platform
org.usb4java.LibUsbException: USB error 12: Unable to claim interface: Operation not supported or unimplemented on this platform
at axoloti.USBBulkConnection.connect(USBBulkConnection.java:296)
at axoloti.MainFrame$4.run(MainFrame.java:340)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:773)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:720)
at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:714)
at java.base/java.security.AccessController.doPrivileged(AccessController.java:400)
at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:742)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)

Library status: factory (1.0.12,anon) - OK (1.0.12,clean)
Library status: community (1.0.12,anon) - OK (1.0.12,clean)
Library status: ksoloti-objects (1.0.12,anon) - OK (1.0.12,clean)
Library status: ksoloti-community (1.0.12,anon) - OK (1.0.12,clean)

Object search path: C:\Users\Lol PC\ksoloti\1.0.12\axoloti-factory\objects
Object search path: C:\Users\Lol PC\ksoloti\1.0.12\axoloti-contrib\objects
Object search path: C:\Users\Lol PC\ksoloti\1.0.12\ksoloti-objects\objects
Object search path: C:\Users\Lol PC\ksoloti\1.0.12\ksoloti-contrib\objects
Finished loading objects.

Ksoloti Core found.
Not accessible: busy?
Matching USB device found.
Not accessible: busy?
No matching USB devices found.

and by the way, when i’m not booting the card in rescue mode , in my windows devices manager list , i see 2 ksoloti things:
ksoloti bulk interface
ksoloti core

This is normal: “Ksoloti Bulk Interface” is the communication channel between Patcher and Core, and “Ksoloti Core” is the MIDI device

Seems very odd whatever is happening. But it doesn’t look like a hardware fault, more like a driver mess-up on Windows.

At this point you could try Zadig on “Ksoloti Core” itself (not in rescue mode) and the “Ksoloti Bulk Interface”

I just did both and Gills works the same here, so maybe this will fix your drivers

thanks a lot !!
somehow it worked and solved my problem :pray:

1 Like

I got this error today and I did delete the suggested files. It seems like it fixed it. Is there anything else to prevent this from happening again?

1 Like

Wait for 1.1.0 :grinning:

2 Likes