mirror of
https://github.com/elua/elua.git
synced 2025-01-08 20:56:17 +08:00
- Added "installing on AVR32" page
- Minor changes to the other "installing" pages
This commit is contained in:
parent
1e2e05ee55
commit
fc98d482a7
@ -25,7 +25,7 @@
|
||||
tedious to use. If you still want to use it though, you might want to check the forementioned <a target="_blank" href="http://www.olimex.com/dev/sam7-ex256.html">Olimex page</a>, they have some OpenOCD related links there.
|
||||
That said, from now on I'm going to assume that you use Windows. I'm using XP, Vista should work too.</li>
|
||||
<li>you have installed the <a target="_blank" href="http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3883">AT91 In-system Programmer (ISP)</a> package from Atmel.</li>
|
||||
<li>you already built your <b>eLua</b> image for the AT91SAM7X256 CPU.</li>
|
||||
<li>you already have your <b>eLua</b> image for the AT91SAM7X256 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>).</li>
|
||||
</ul>
|
||||
<h3>Programming eLua on the SAM7-EX256 board</h3>
|
||||
<p>This involves some jumper tricks, but it's still easy enough to do. We'll need to play with four jumpers: the "USB/EXT" jumper (located to the right of the USB connector
|
||||
|
81
doc/en/installing_avr32.html
Normal file
81
doc/en/installing_avr32.html
Normal file
@ -0,0 +1,81 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Strict//EN">
|
||||
<html><head>
|
||||
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
|
||||
<link rel="stylesheet" type="text/css" href="../style.css"></head>
|
||||
<body style="background-color: rgb(255, 255, 255);">
|
||||
<meta http-equiv="Content-Language" content="en-us"><title> Installing eLua on AVR32 CPUs</title>
|
||||
<h3>Installing <b>eLua</b> on the AVR32 CPUs from Atmel</h3>
|
||||
<p><a target="_blank" href="http://www.atmel.com/products/AVR32/">AVR32</a> is a family of high performance 32-bit CPUs from <a target="_blank"
|
||||
href="http://www.atmel.com">Atmel</a>. They were built as direct competitors for the various ARM core implementation of the market, and offer very good
|
||||
performance (91 MIPS @ 66MHz) and power efficieny (1.3mW/MHz). Atmel claims that their AVR32 core outperforms ARMv5 (in ARM and Thumb mode) in terms of
|
||||
both performance and code size. It's a proprietary architecture (so it's only implemented by Atmel), yet it has a very good support package, and an
|
||||
open source toolchain based on GCC, which made it an ideal candidate for the first non-ARM (and also the first big endian) <b>eLua</b> target. Atmel
|
||||
also sells a number of development boards based on their AVR23 CPUs. The one used for <b>eLua</b> is the
|
||||
<a target="_blank" href="http://www.atmel.com/dyn/Products/tools_card.asp?tool_id=4114">ATEVK1100 board</a>, built around the
|
||||
<a target="_blank" href="http://www.atmel.com/dyn/products/product_card.asp?part_id=4117">AT32UC3A0512 AVR32 MCU</a> (512k internal Flash/64k internal ARM).
|
||||
It's a very powerful board, featuring (among other things) an external 32 MByte SDRAM memory, which is more than enough to run any <b>eLua</b>
|
||||
program I can think of :).</p>
|
||||
<h3>Prerequisites</h3>
|
||||
<p>Before you'll be able to use <b>eLua</b> on the AT32UC3A0512 CPU, make sure that:</p>
|
||||
<ul>
|
||||
<li>you're using Linux or Windows. It's easier to install and use Atmel's programming software on Windows, so use Windows version if you want to save
|
||||
yourself from quite a bit of hassle.</li>
|
||||
<li>you installed Atmel's <a target="_blank" href="http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3886">FLIP programming software</a>, which is what you need
|
||||
in order to install your <b>eLua</b> image. Installation in easy under Windows (you just need to run a setup paclage), but quite tricky under Linux.
|
||||
The next paragraph outlines the procedure for installing FLIP in Linux.
|
||||
<li>you already have your <b>eLua</b> image for the AT32UC3A0512 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>).
|
||||
Note that unlike other platforms, the ATEVK1100 needs a .hex file for programming, not a .bin.</li>
|
||||
</ul></p>
|
||||
<h2>Installing FLIP in Ubuntu Linux</h2>
|
||||
<p>Follow the steps below to install FLIP under Linux:
|
||||
<ol>
|
||||
<li>download the Linux version of FLIP from <a target="_blank" href="http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3886">the Atmel FLIP page</a>. Save it
|
||||
(or move it later) to your <i>/usr/local/</i> directory (you need to have superuser privileges to do that). At the moment of writing this tutorial, the
|
||||
latest FLIP version is 3.2.1, so this is what we're going to use here.</li>
|
||||
<li>untar the FLIP archive:
|
||||
<p><pre><code>$ cd /usr/local
|
||||
$ sudo tar xvzf flip_linux_3-2-1.tgz</code></pre>
|
||||
This will create the <i>/usr/local/flip.3.2.1</i> directory.</li>
|
||||
<li>you need to install OpenJDK if it is not installed:
|
||||
<p><pre><code>$ sudo apt-get install openjdk-6-jre</code></pre></p>
|
||||
</li>
|
||||
<li>edit <i>/usr/local/flip.3.2.1/bin/batchisp3.sh</i> and add the two bolded lines before at the beginning of the file:
|
||||
<p><pre><code>#!/bin/bash -f
|
||||
|
||||
<b>export JAVA_HOME=/usr/lib/jvm/java-6-openjdk/jre/
|
||||
export FLIP_HOME=/usr/local/flip.3.2.1/bin/</b>
|
||||
|
||||
if [ "$FLIP_HOME" = "" ]; then</code></pre></p>
|
||||
</li>
|
||||
<li>you need to edit a binary file this time (<i>/usr/local/flip.3.2.1/libatlibusbdfu.so</i>). This happens because FLIP comes compiled for RedHat by
|
||||
default, and Ubuntu some different system paths. See <a target="_blank" href="http://www.avrfreaks.net/index.php?name=PNphpBB2&file=viewtopic&t=56562">this topic</a>
|
||||
for full details. All you have to do is change all the <b>/sys/bus/usb</b> strings inside <i>libatlibusbdfu.so</i> to <b>/dev/bus/usb</b>.</li>
|
||||
<li>add the FLIP directory to your PATH:
|
||||
<p><pre><code>$ export PATH=/usr/local/flip.3.2.1/bin:$PATH</code></pre></p>
|
||||
</li>
|
||||
<li>FLIP interferes with a program that comes pre-installed on Ubuntu system, called <b>brltty</b>. It's meant to help the visually
|
||||
impaired, so if you're not one of them, simply remove it (as it seems to interfere with a lot of other USB devices too):
|
||||
<p><pre><code>$ sudo apt-get remove brltty</code></pre></p>
|
||||
</li>
|
||||
</ol>
|
||||
</p>
|
||||
<h3>Burning <b>eLua</b> to the EVK1100 board</h3>
|
||||
<p>After you installed FLIP and added it to your $PATH, burning the <b>eLua</b> image should be quite easy:
|
||||
<ul>
|
||||
<li>connect your ATEVK1100 board with the PC using an USB cable</li>
|
||||
<li>put your board in DFU mode (this is required for FLIP interaction). To do this:
|
||||
<p><ol>
|
||||
<li>press <b>on</b> the on-board joystick (and keep it pressed)</li>
|
||||
<li>press the RESET button on the board briefly</li>
|
||||
<li>release the RESET button</li>
|
||||
<li>release the joystick</li>
|
||||
</ol></p>
|
||||
</li>
|
||||
<li>if you're using Windows and it asks you for a driver, you should install it manually from <i>c:\Program Files\Atmel\Flip <version>\usb</i></li>
|
||||
<li>Execute this from the command line (the command is the same on Windows and Linux, with a single exception: the FLIP executable name is <b>batchisp3</b> in Linux and <b>batchisp</b> (without a 3) in Windows):
|
||||
<p><pre><code>$ batchisp3 -hardware usb -device at32uc3a0512 -operation erase f memory flash blankcheck
|
||||
loadbuffer <image name>.hex program verify start reset 0</code></pre></p>
|
||||
</ul></p>
|
||||
<p>That's all, your <b>eLua</b> image is (finally) installed on your ATEVK1100 board.</p>
|
||||
</body></html>
|
||||
|
@ -21,7 +21,7 @@
|
||||
an emulator in Linux, it doesn't matter, you can even try to run it from <a target="_blank" href="http://www.winehq.org/">Wine</a> if you're really, really brave. I'm using XP, Vista should work too.</li>
|
||||
<li>you have installed the LM Flash Programmer tool from Luminary. Look for it on <a target="_blank" href="http://www.luminarymicro.com/products/ekk-lm3s8962_can_ethernet_evaluation_kit.html">this page</a>,
|
||||
for example (the link is in the "Software updates" table).</li>
|
||||
<li>you already built your <b>eLua</b> image for the LM3S8962 CPU. </li>
|
||||
<li>you already have your <b>eLua</b> image for the LM3S8962 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>). </li>
|
||||
</ul>
|
||||
<h3>Installing <b>eLua</b> on EKx-LM3S8962EK and EKx-LM3S6965</h3>
|
||||
<p>Fortunately, this is as easy and painless as possible. One of the nicest things about these two kits is they use the on-board USB port for both firmware downloading and for
|
||||
|
@ -27,7 +27,7 @@
|
||||
<li>if you're using DFU, you have installed the LPC2888 flash programming utility from <a target="_blank" href="http://www.standardics.nxp.com/support/documents/microcontrollers/zip/flash.utility.mass.dfu.lpc2888.zip">here</a> (the package also
|
||||
contains the Windows DFU drivers).</li>
|
||||
<li>if you're using OpenOCD, you have followed the instructions from my <a href="tut_openocd.html">OpenOCD</a> tutorial.</li>
|
||||
<li>you already built your <b>eLua</b> image for the LPC2888 CPU.</li>
|
||||
<li>you already have your <b>eLua</b> image for the LPC2888 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>).</li>
|
||||
</ul>
|
||||
<h3>Burning <b>eLua</b> to the LPC2888 using the DFU tool from NXP</h3>
|
||||
<p>The DFU flashing application doesn't work directly on the .bin files you get after building <b>eLua</b>, you need to run them though NXP's "hostcrypt" program (which is part of the LPC2888 DFU package). After you have your <b>eLua</b> .bin file,
|
||||
|
@ -11,7 +11,7 @@ based on this STR711FR2 variant of the STR7 family. Since this is not a full-fle
|
||||
<p>Before you'll be able to use <b>eLua</b> on the STR711FR2 CPU, make sure that:</p>
|
||||
<ul>
|
||||
<li>you're using Linux, Windows, or any other OS that has support for <a target="_blank" href="http://openocd.berlios.de/web/">OpenOCD</a>. You might have a look at my <a href="tut_openocd.html">OpenOCD tutorial</a> before continuing.</li>
|
||||
<li>you already built your <b>eLua</b> image for the STR711FR2 CPU.</li>
|
||||
<li>you already have your <b>eLua</b> image for the STR711FR2 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>).</li>
|
||||
</ul>
|
||||
<h3>Burning <b>eLua</b> to the MOD711 board</h3>
|
||||
<p>You need OpenOCD to do this. Just follow the instructions from my <a href="tut_openocd.html">OpenOCD tutorial </a>. On the tutorial page you'll also find links to the OpenOCD
|
||||
|
@ -16,7 +16,7 @@
|
||||
<ul>
|
||||
<li>you're using Linux, Windows, or any other OS that has support for <a target="_blank" href="http://openocd.berlios.de/web/">OpenOCD</a>. You might have a look at my <a href="tut_openocd.html">OpenOCD tutorial</a> before continuing.</li>
|
||||
<li>if you're on Windows, you have installed the STR9-comStick support package from the accompanying CD.</li>
|
||||
<li>you already built your <b>eLua</b> image for the STR912FAW44 CPU.</li>
|
||||
<li>you already have your <b>eLua</b> image for the STR912FAW44 CPU (<a href="building.html">built</a> or <a href="downloads.html">downloaded</a>).</li>
|
||||
</ul>
|
||||
<h3>Burning <b>eLua</b> to the STR9-comStick</h3>
|
||||
<p>You need OpenOCD to do this. Just follow the instructions from my <a href="tut_openocd.html">OpenOCD tutorial </a>. On the tutorial page you'll also find links to the OpenOCD
|
||||
|
@ -34,6 +34,7 @@ pre {
|
||||
line-height: 125%;
|
||||
margin-left: 1em;
|
||||
margin-right: 1em;
|
||||
overflow: auto;
|
||||
}
|
||||
p.info {
|
||||
margin-left: 3em;
|
||||
|
Loading…
x
Reference in New Issue
Block a user