-
-
Notifications
You must be signed in to change notification settings - Fork 87
Home
Install your favorite development environment:
e.g. Eclipse (Oxygen)
sudo apt install eclipse eclipse-cdt
Start Eclipse and go to the Eclipse Marketplace → Help → Eclipse Marketplace
Search for AVR Eclipse Plugin and install it.
Project→Properties AVR tab on the left? - so you can change the target hardware to atxmega32a4u and rebuild the index.
If not so, you can change the target hardware within C/C++ Build → Environment.
Here change the value of AVRTARGETMCU to atxmega32a4u.
C/C++ Build → Tool Chain Editor: AVR-GCC Toolchain
Maybe you need to check out C/C++ General → Paths and Symbols too:
__ AVR_DEVICE_NAME __ = atxmega32a4u
After all changes rebuild the index.
Debian, Ubuntu, ...
Requirements:
- avr-libc
- binutils-avr
- gcc-avr
- avrdude
- libusb-dev
Install packages:
sudo apt-get install avr-libc binutils-avr gcc-avr avrdude libusb-dev
Clone the latest version to your local system:
git clone https://github.com/iceman1001/ChameleonMini-rebooted.git
cd ChameleonMini-rebooted
cd Firmware/Chameleon-Mini
make
If everything compiles you will find two new files in the current directory:
- Chameleon-Mini.eep
- Chameleon-Mini.hex
You need to upload these two files using either avr-dude or dfu-programmer. On some/most Linux systems there seems to be a problem when using USB3 ports. This can result in errors when trying to upload or not even finding the correct mcu type. A temporary solution might be to bring these two files over to a Windows pc and upload them using the bootloader.exe program of maybe even with the AVR Flip programmer. More on this later.
Requirements:
- AVR GNU Toolchain from Atmel or Atmel Studio 7
- Cygwin
- Add the bin path of Cygwin and AVR Toolchain to the PATH environment variable
Recommended Cygwin-packages:
- make
- gcc-core
- gcc-g++
- util-linux
- binutils
- rsync
- python
- python3
- bash-completition
- vim
- vim-common
- diffutils
- openssh
If the setup is done --> start Cygwin and navigate to the firmware folder where the makefile is located and run make
.
Requirements:
- xcode
- homebrew
- avr-gcc
Install packages:
xcode-select --install
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
brew tap osx-cross/avr
brew install avr-gcc
not needed yet, but maybe in the future, for creating the bootloader:
brew install srecord
There are several solid options for using the RevE device after configuring and flashing the firmware using the steps above. These include the following options for transferring the terminal commands to the device:
- Use a stock serial terminal tty* interface (or
teraterm
on Windows) to communicate directly with the device over USB; - Use a modified USB cable hookup and an Android phone with the Chameleon Mini Live Debugger application available here or on Google Play Store (or non-free APK to support development). This application is primarily designed for use with the related RevG boards, but supports the core functionality of the RevE boards;
- Use another GUI application to communicate with the device over serial USB. For example, see here and this list for GUI applications with full or partial support for both the RevE and RevG devices.
Home
Getting started
Basic usage
Supported cards/config
Windows
Linux
OSX
Development Environment
Terminal commands
Slots configuration
Hardware summary
Program with AVRISP mkII
Program with modified USBASP
Reference fuses and lockbits
Reference SPI Flash
RevE Bootloader