-
Notifications
You must be signed in to change notification settings - Fork 4
/
INSTALL
92 lines (63 loc) · 2.96 KB
/
INSTALL
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
Installation Instructions
*************************
Copyright (C) 2017 wa1tnr
Copying and distribution of this file, with or without modification,
are permitted in any medium without royalty provided the copyright
notice and this notice are preserved. This file is offered as-is,
without warranty of any kind.
Basic Installation
==================
Briefly, you are looking at a skeleton file acting as a place-
holder for any installation instructions offered.
1. July 2017: configured for Circuit Playground Express (#3333),
which is the current target MCU under development.
This changes frequently, and may be near the top
of the list of gotchas to watch for: a different
'Express' series target (Feather M0, Metro M0, et al.)
can break compiles -- or can crash the target MCU
after an upload (generally easy to resolve).
Note that this is not an Arduino IDE problem -- it
persists even after proper selection of the target
MCU in the Arduino IDE interface.
The problem is that, currently, ainsuForth does not
(always) detect (or compensate for) a change in
targets. It is only periodically tested against
each of these four SAMD21 design targets:
Arduino M0 Pro
Adafruit Feather M0 Express
Adafruit Metro M0 Express
Adafruit Circuit Playground Express (#3333)
Currently:
src/periph/neo_pixel.cpp is affected (pin 8 vs pin 40 of the Metro)
There may be other target-specific issues to resolve, when
using another target MCU board in this (Adafruit Express SAMD21) family.
Eventually, some kind of #define-based configuration may be employed.
2. Install something.
3. Install something else. Then install a thing. Continue installing
until installation is complete.
4. These last three line items (2, 3 and 4) are meant as place-holders
for instructions, rather than as instructions.
Compilers and Options
=====================
This would be a good place to talk about the compiler.
Compiling For Multiple Architectures
====================================
This might talk about #define and #include directives to the C
preprocessor.
Installation Names
==================
This section may talk about makefile targets, if there were any.
Optional Features
=================
This would possibly be more specific to individual, well-known
features the program may (optionally) incorporate. Or not.
Particular systems
==================
This might talk about Linux or about some other kind of system
(name your system here; for example, Solaris).
Other
=====
This INSTALL file format doesn't very well fit present needs.
It is here to remind what sorts of standard files are often
seen in distributed packages.
Tue Jun 6 03:03:57 UTC 2017