To reduce size we split the application into two parts, the main axoloti application, and a runtime which contains other required files. You must download and install both initially.
(Usually updates will only require the main application to be downloaded and installed.)
download both application bundle and axoloti_runtime
install runtime zip:
- double click on zip file to unzip the file
- when you unzip the runtime, you should see a folder called axoloti_runtime, which needs to be copied to c:\Program Files (x86)
- now check that you have C:\Program Files (x86)\axoloti_runtime\platform_win
if when unzipped you find a folder other than axoloti_runtime, then look into that folder for axoliti_runtime, it is axoloti_runtime that must be copied to C:\Program Files (x86).
install axoloti application msi:
- double click on the MSI file
- you may get a warning from windows about not trusting, this is due to it not being signed, you can safely ignore this, click on More Info, and then click on "Run Anyway"
Connect axoloti core board, this will start windows installing the necessary drivers (if they are not already installed), and create a device called "Axoloti Core"
Run Axoloti application, you will find it in C:\Program Files(x86)
Thats it, your done!!
Axoloti runs on many platforms and variations, but we are only able to test on limited number of platforms, if you experience issues we recommend the following, as these are our test platforms.
- Windows 7, 8, 10
- Java 1.8 (can be downloaded from https://java.com/en/download/)
Developer installation (from source)
If you are a developer and would like to follow the most up to date developments, and perhaps contribute to Axoloti development you can install from the Axoloti github repo
- clone from github
- run build.bat in platform_windows
- run ./Axoloti.bat
Note: to create the bundles you will need to install the Oracle Java 8 JDK
Advanced installation (Rescue mode)
Usually you can flash the firmware with Axoloti using the regular flashing method, which the above installation will handle.
However, there is a 'rescue mode' (aka DFU mode) which can be used if the board appears to not respond to normal firmware flashing. This is a 'rare' situation, if you have an issue that requires it we will let you know.
(most users will not need this function!)
this 'rescue' mode, also called DFU, requires a different driver from the normal Axoloti driver, unfortunately for windows, the driver installed by default (STM32 Bootloader) is not compatible, and we need to replace it with the generic WinUSB driver.
To do this:
- Enter rescue mode, by powering down the board, press S1 and hold, and power up the board. The two LEDs stay off in this case.
- Windows will then install the incompatible driver, wait for this to complete.
- After, go to C:\Program Files (x86)\axoloti_runtime\platform_win and run Zadig (zadig_2.1.2.exe)
- Initially, the Zadig window is blank
- select "Options > List All Devices"
- While the axoloti board is in DFU mode, it will be listed as STM32 BOOTLOADER in the dropdown menu - select it.
- You will see Driver : Stu* -> WinUSB (v6.1.7600.16385 etc) and underneath, Replace Driver, press "Replace Driver", this will replace the STM driver with the WinUSB driver
- Now Axoloti flash rescue mode will work.
- You can check that this is mode is available by staying in DFU mode, start the Axoloti UI, go to "Board>Select Device...", it will say 'STM DFU' in the description, driver OK. (also Flash (Rescue) will be enabled)