Skip to content

Latest commit

 

History

History
104 lines (58 loc) · 4.82 KB

README.md

File metadata and controls

104 lines (58 loc) · 4.82 KB
Raw

Sonic Potions LXR Drumsynth Firmware

The LXR is a digital drum synthesizer based on the 32-bit Cortex-M4 processor and an Atmega644 8-bit CPU. Developed by Julian Schmidt.

The 'front' folder contains the AVR code

The 'mainboard' folder contains the STM32F4 code

The 'tools' folder contains the firmware image builder tool, to combine AVR and Cortex code into a single file, usable by the bootloader.

Please note that there are libraries from ST and ARM used in the mainboard code of this project. They are all located in the Libraries subfolder of the project. Those come with their own license. The libraries are:

ARM CMSIS library
ST STM32_USB_Device_Library
ST STM32_USB_OTG_Driver
ST STM32F4xx_StdPeriph_Driver

Many Thanks to user Rudeog who contributet a lot of bugfixes and features for version 0.26 and 0.33 as well as Patrick Dowling for the Makefiles for the Linux build system!

Instructions for building on Linux using the provided makefiles:

You will need:

  • the ARM GCC compiler
  • the AVR GCC compiler
  • the AVR c libs

GNU Tools for ARM Embedded Processors

project homepage: https://launchpad.net/gcc-arm-embedded

For Ubuntu 10.04/12.04/13.04 32/64-bit user, PPA is available at https://launchpad.net/~terry.guo/+archive/gcc-arm-embedded.

otherwise you can download the 32bit binaries here https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q1-update/+download/gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2

--- Installing the ARM GCC binaries ----

download the binary package: 'wget https://launchpad.net/gcc-arm-embedded/4.8/4.8-2014-q1-update/+download/gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2'

extract it: 'tar xvjf gcc-arm-none-eabi-4_8-2014q1-20140314-linux.tar.bz2 '

move it to /opt/ARM: 'sudo mv gcc-arm-none-eabi-4_8-2014q1 /opt/ARM'

include it permanently in your PATH variable 'echo "PATH=$PATH:/opt/ARM/bin" >> ~/.bashrc'

IMPORTANT! for x64 systems, you have to install the 32-bit version of libc6 or you will get an 'arm-none-eabi-gcc: not found' error when invocing arm-none-eabi-gcc: 'sudo apt-get install libc6-dev-i386'

--- Installing the AVR GCC compiler and AVR libc---

These should normaly be available from you package manager 'sudo apt-get install gcc-avr avr-libc'

Now you are ready to go. To build the firmware, go to the LXR folder containing this file and type: 'make firmware'

you should now find a new FIRMWARE.BIN file in the 'firmware image' subfolder

Thanks a lot to Patrick Dowling and Andrew Shakinovsky for their code contributions!

Instructions for building on windows using Eclipse:

  1. Install Eclipse Juno CDT (You could install a later version, but this is the version I have working)

  2. Install the Eclipse GNU ARM plugin. Go into the help menu, Install new Software, add a site: http://gnuarmeclipse.sourceforge.net/updates. Then check the box to install that plugin.

  3. Download and install the GCC ARM toolchain https://launchpad.net/gcc-arm-embedded/+download

  4. Download and install gnu make: http://gnuwin32.sourceforge.net/packages/make.htm

  5. Download and install Atmel AVR toolchain from http://www.atmel.com/tools/ATMELAVRTOOLCHAINFORWINDOWS.aspx (you don't need the headers package)

  6. Ensure that the bin directory from 3, 4, and 5 are on the path. I made a batch file that adds these 3 bin directories to my path and launches eclipse.

  7. Fetch the LXR sources from github. You can either install git and do it the git way, or download a zip and unzip it.

  8. In Eclipse, create a workspace in root folder of whole tree that you unzipped (or git'd).

  9. Add two project dirs mainboard\firmware\DrumSynth_FPU and front\AVR to the workspace. To do this, use File/Import/General/Existing projects into workspace. Then select root directory and browse to these dirs. Do this step once for each of these two dirs. You will end up with two projects in your workspace.

  10. These should build. Eclipse is a bit squirrely, so you might need to do a make clean first to create the first makefiles, or rebuild indexes.

  11. I've built the firmwareimagebuilder.exe in the \tools\bin folder. I've also put a batch file that launches it and copies the binaries from the respective output directories to create FIRMWARE.BIN in that same dir. If you don't trust the .EXE I built, you will need to build it from tools\FirmwareImageBuilder\FirmwareImageBuilder. As is you will need visual studio. If you don't have it, you can try to install the free version, mingw, etc and compile the one file FirmwareImageBuilder.cpp (I've fixed it so it should build with any tool) and make your own exe and copy it to that dir.

  12. Thats it, after running the batch file you will have your firmware file.