Commit 137aa61c authored by Jake Read's avatar Jake Read
Browse files

move jake doc

parent 8281849f
Pipeline #2626 passed with stage
in 2 seconds
<h1>XMega Learning</h1>
# XMEGA Hello-Worlds
<h2>Toolchain Installation</h2>
## Using a Commandline Toolchain
<p>This installation is more or less straightforward:</p>
......@@ -19,9 +19,8 @@
<p>Also, as of 11/30/2017, there seems to be some strange behavior when trying to use an Atmel Ice programmer from a mac. When you try to program, you may see an error message from usbdev_open() about not claiming the interface. I used the answer posted <a href=''>here (post 32 and 33)</a> -- the attached kext file already has the correct VID and PID. A full restart was required.</p>
## Examples using the Commandline Toolchain
<p>Below are projects using the xmega peripherals as I'm learning about them. They definitely aren't minimal "hello world" examples, but at some point hopefully I'll get around to boiling them down. For the moment, however, hopefully they demonstrate how to use each capability of the mcu.</p>
......@@ -99,9 +98,58 @@
<li><a href='i2c/loadcell-reading-v-force.png'>Results</a></li>
## Atmel Studio Toolchain
``` !warn! windows only, sorry ```
Another way to make programming these devices easier is to give in to the proprietary software world. I use [Atmel Studio]( for big messy projects that want an IDE, and in unfamiliar environments where I don't know the register structure so well and would like to poke around with autocomplete. The software is available for free download.
#### Start a New Project
To begin, open Atmel Studio, start a new project and select **GCC C Executable Project** - GCC is the 'GNU Compiler Collection' - this just means that atmel is going to start a new C-code project for you.
#### Select the Device
Atmel Studio needs to know what kind of microcontroller it's going to build for. The XMEGA used in most [automatakit]( projects (at the time of writing) is the XMEGA256A3U, but the lab should have available XMEGA8E5's and a few more. They all follow the same basic structure. You can search in the top-right for the chip you're using.
I've also worked with the ATSAMD51, [made popular, and supported by adafruit]( (meaning you can set it up to build code with arduino) and the ATSAMS70. Some example code for each of those should be brain-dumped at [the CBA hello-world gitlab group](
#### Test Build and Flash
To make sure you can build, use **Build > Build Solution** in the top menu, or hit F7.
To flash code, use **Debug > Start Without Debugging** - this will attempt to build and then flash the code onto the micro. If the project is new, it will tell you you haven't set up a tool yet. This is true. With your tool plugged into a USB port, it should appear on the 'selected debugger/programmer' window. I use an Atmel ICE, and they are available in most of the How to Make labs.
You should now be able to flash your code with **Debug > Start Without Debugging** or **CTRL + ALT + F5**.
If you have errors, make sure your pinouts are correct, your board has power, and the ICE cable is plugged into the correct port (i.e. one is labelled 'SAM' and the other 'AVR' - use SAM for ATSAM boards, AVR for XMEGA and anything else).
#### Including Example Code
I've build a few 'libraries' for all of these chips. Each is a .c and .h file. To include them in your project, follow these steps.
In the Atmel Studio 'Solution Explorer' (might not be open, go to View -> Solution Explorer), right-click on the Solution (mkembedded-example in this case) and do Add -> Existing Item
Now select all of the .c and .h files from the example code.
Your Atmel Studio environment and project embedded director should look something like this:
Now we should be ready to build the example:
## Example Circuitry
In in [this subdirectory](circuit) you'll find an example eagle schematic and
\ No newline at end of file
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment