1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
|
.. highlight:: sh
.. _unix-toolchain-linux-setup:
Unix Toolchain Linux Setup
==========================
This page contains instructions for setting up a Linux computer for
use with the :ref:`Unix toolchain <unix-toolchain>`. (Setup
instructions for :ref:`other operating systems <toolchain-setup>` are
also available.)
These instructions have been tested successfully on:
- Ubuntu 10.04 and 12.04 (32- and 64-bit)
- Fedora 17 (64-bit)
Generic instructions for other distributions are also provided. Please
`contact`_ us with any updates for distros not already covered!
.. contents:: Contents
:local:
Collect and Install Tools
-------------------------
First, you'll need some tools.
.. warning:: Due to firmware bugs in our :ref:`bootloader
<bootloader>`, you must use recent versions of ``dfu-util``, or
uploads will not work. ``dfu-util`` versions 0.6 and greater
should work.
**Debian-based distributions (Debian, Ubuntu, Mint, etc.)**:
Install mandatory and optional tools with ::
$ sudo apt-get install build-essential git-core screen dfu-util python python-serial
On *64-bit distros only*, you will also need to install some 32-bit
libraries needed by the LeafLabs-supported :ref:`ARM GCC toolchain
<arm-gcc>` with ::
# 64-bit systems only!
$ sudo apt-get install ia32-libs
You may also need to remove `brltty <http://mielke.cc/brltty/>`_
with ::
# Optional
$ sudo apt-get remove brltty
Brltty provides braille access to the console. It has been reported
to cause conflicts with Maple.
**Red Hat-based distributions (RHEL, Fedora, Centos, etc.)**:
Install mandatory and optional tools with ::
$ sudo yum install screen git python pyserial dfu-util make
On *64-bit distros only*, you will also need to install 32-bit
libraries needed by the LeafLabs-supported :ref:`ARM GCC toolchain
<arm-gcc>` with ::
# 64-bit systems only!
$ sudo yum install glibc.i686
You may also need to remove `brltty <http://mielke.cc/brltty/>`_
with one of these::
# Optional, 64-bit systems:
$ sudo yum erase brltty.x86_64
# Optional, 32-bit systems:
$ sudo yum erase brltty.i686
Brltty provides braille access to the console. It has been
reported to cause conflicts with Maple.
**Other Linux distributions**:
On other distributions, you'll need to figure this out for yourself
(please `contact`_ us if you have instructions for distros not
covered here!).
Mandatory tools:
* `Git`_ is a distributed version control system. We use it to track
our source code.
* `dfu-util`_ is a tool from the `OpenMoko`_ project. It is used to
upload programs to the Maple over USB.
* `Make <http://www.gnu.org/software/make/>`_ is used to direct
compilation.
* `Python`_ is a programming language. Our reset script, which sends
control signals to the board which cause it to to reset and enter
the :ref:`bootloader <bootloader>`, is written in Python (and
works with Python 2 or 3). Most Linux distributions these days
include Python by default.
* `PySerial`_ is a Python library for interacting with serial port
devices. It's needed by our reset script. PySerial can also be
installed with `easy_install`_.
Optional tools:
* `screen <http://www.gnu.org/s/screen/>`_ is a screen manager used
here to connect to serial port devices. (Some popular
alternatives are `Minicom
<http://alioth.debian.org/projects/minicom/>`_ and `Kermit
<http://www.kermitproject.org/>`_).
Fetch ``libmaple`` and Compiler Toolchain
-----------------------------------------
First, make a Git clone of :ref:`libmaple`::
$ cd ~
$ git clone git://github.com/leaflabs/libmaple.git libmaple
Next, download the `Linux ARM GCC toolchain
<http://static.leaflabs.com/pub/codesourcery/gcc-arm-none-eabi-latest-linux32.tar.gz>`_
you'll use to build your programs. Extract the archive into a
directory named :file:`arm`. Put the resulting :file:`arm/bin`
subdirectory somewhere in your ``PATH``. For example, if you have
`wget <http://www.gnu.org/software/wget/>`_ installed, you can run::
$ cd ~/libmaple
$ wget http://static.leaflabs.com/pub/codesourcery/gcc-arm-none-eabi-latest-linux32.tar.gz
$ tar xvf gcc-arm-none-eabi-latest-linux32.tar.gz
$ export PATH=$PATH:~/libmaple/arm/bin
You can check that this worked by entering ``arm-none-`` and hitting
tab to auto-complete; your shell should show a bunch of results. After
you're done, you'll probably want to update your shell startup script
so the :file:`arm/bin` directory stays in your ``PATH``.
.. _toolchain-udev:
Install udev Rules
------------------
From the libmaple directory, copy our udev rules [#fudev]_ to
``/etc/udev/rules.d``::
$ sudo cp support/scripts/45-maple.rules /etc/udev/rules.d/45-maple.rules
Then restart udev.
**Debian-based distros**:
Make sure you are in the plugdev group (e.g. by running ``$ groups``
and seeing if the output includes "plugdev"). If not, add yourself
to plugdev with ::
$ sudo usermod -a -G plugdev $USER
then log back out and log back in.
After that's done, restart udev::
$ sudo restart udev
**Red Hat-based distros**:
::
$ udevadm control --reload-rules
After restarting ``udev``, you'll need to unplug and re-plug your
Maple.
So far, so good?
----------------
Great! Move on by :ref:`compiling a sample program <toolchain-test>`.
.. rubric:: Footnotes
.. [#fudev] As a security precaution on Linux, unknown USB devices can
only be accessed by root. This udev script identifies the Maple
based on its vendor and product IDs, mounts it to
:file:`/dev/maple`, and (for Debian-based distros) grants
read/write permissions to the ``plugdev`` group.
|
