Patch Won't Go Live


#1

Hi,

I'm having a problem with my Axoloti board where I can't get new patches to go live, for some reason when I click the live button it un ticks itself and the background on the patcher stays the same colour.

I've tried using various USB cables and tried loading patches i've made myself and ones from the library but for some reason a old patch is still loaded on the board.

I am on firmware version 1.0.0.1 hopefully this is just me being stupid and there is a easy fix so I can get the axoloti working again!

Thanks,
Dan

Edit: just realised I probably should have mentioned, I am using Windows 10!


#2

Ever find a solution to this? Having this exact same problem as of today. Click the button and it immediately un-ticks and background stays the same color. The DSP load jitters around 15% and claims to be running a live patch but it doesn't seem to want to run anything new.

Also windows 10.

all firmware is up to date and I tried uninstalling / reinstalling several times. Still no luck

Any help would be greatly appreciated!


#3

if you have the editor open, and axoloti is unplugged, what happens when you plug it into the computer, and then hit connect on the axoloti window do you see messages in the log screen, can you post them here? also, if it does indeed connect, can you load a patch and post the log-messages as it fails?


#4

Weird, So I opened everything up and was doing a step by step to report back on this and everything worked just fine... Nothing changed as far as I know. The only thing I can think of is that I connected the Axoloti and took the patch live without having my Akai MPK mini plugged in yet (wasn't expecting it to work).

Anyway seems to be fine now. Hopefully all is well!

Thanks!


#5

Hey,

Sorry for taking almost a year to come back to you here but I've just been trying to get my axoloti working again and I'm still having the same issues.

The messages I get in the log screen are below, I'm opening one of the demo patches from library so I don't believe its the patch that should be causing any issues.

Any help would be greatly appreciated!

"Link to firmware CRC CDEEEFDA
Axoloti version : 2.0.0-0-g88b60fe build time : 18/12/2019 02:50:06 CET
Status: factory (2.0.0,anon) : OK ( 2.0.0,clean )
Status : home : OK
Status: community (2.0.0,anon) : OK ( 2.0.0,clean )
'mode' is not recognized as an internal or external command,
operable program or batch file.
search path : C:\Users\dango\Documents\axoloti-2.0.0\axoloti-factory\objects
search path : C:\Users\dango\Documents\axoloti-2.0.0\objects
search path : C:\Users\dango\Documents\axoloti-2.0.0\axoloti-contrib\objects
finished loading objects
USB device found
connected
Authentic Axoloti Core
Firmware version: 2.0.0.0, crc=0xCDEEEFDA
Generate code complete
'mode' is not recognized as an internal or external command,
operable program or batch file.
Compiling patch failed
Generate code complete
'mode' is not recognized as an internal or external command,
operable program or batch file.
Compiling patch failed"


#6

this points to something with your PATH settings being wrong, do you have both the application and runtime still installed?


#7

I do have both installed, I just copied runtime over to to my program files folder again to be sure and I'm still getting the "Compiling patch failed" message.


#8

Looks like you're using Axoloti 2.0, this doesn't use the runtime that the earlier version used.
Is gcc-arm-none-eabi-7-2018-q2-update installed in the appropriate location?


#9

ah yes... not sure he intends to use 2.0 though.


#10

I installed 2.0 when reinstalling to see if that fixed the issue, however I didn’t realise runtime was not required now.

I will check if the gcc-arm-none-eabi-7-2018-q2-update is installed in the correct location when I’m at my pc.


#11

I've had a look and don't believe I will have had this installed, I've found the site below on google however there only seems to be a 32-bit option for Windows.

https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-rm/downloads/7-2018-q2-update

Is this what I should be installing regardless?


#12

I use Mac, I have no experience with Axoloti on Windows.
BUT, I expect that's the one you want.


#13

Ahhh okay, I've just installed it and I'm still getting the message saying "Compiling patch error".


#14

Where did you install the toolchain?

Are there any Windows users who can figure this out?


#15

I installed it in c:/program files if memory serves.


#16

To be precise I installed the toolkit in "C:\Program Files (x86)".

I never had this installed when my Axoloti used to work however, would maybe uninstalling everything and searching for any registry keys associated with Axoloti to get a complete clean slate help?

Thanks to everyone who's offered help so far and apologies for my persistence, I would just like to get my Axoloti working again if possible!


#17

well your axoloti was working with the version 1, and now you are trying to install version 2. i for one would opt to remove axoloti version 2 and install the old "known to work" axoloti version 1. it will be easier for you to find help on that one.


#18

I've gone back to version 1.0.12-2, however when I run Axoloti it says there is a firmware mismatch and when I say to flash the new firmware it seems to get stuck.

FYI, I did update the firmware when I installed version 2, should it be possible for me to downgrade the firmware?


#19

if i remember correctly you either have to downgrade from axoloti 2 (there should be an option to downgrade to 1.0.12) or do it via dfu mode, i think that could also work.
so, downgrading via ver.1 editor is not possible.


#20

see here: https://sebiik.github.io/community.axoloti.com.backup/t/axoloti-release-2-0-0/6273?u=lokki