micropython/teensy
Jan Čapek d76c65f599 py: Add rules for automated extraction of qstrs from sources.
- add template rule that converts a specified source file into a qstring file

- add special rule for generating a central header that contains all
  extracted/autogenerated strings - defined by QSTR_DEFS_COLLECTED
  variable. Each platform appends a list of sources that may contain
  qstrings into a new build variable: SRC_QSTR. Any autogenerated
  prerequisities are should be appened to SRC_QSTR_AUTO_DEPS variable.

- remove most qstrings from py/qstrdefs, keep only qstrings that
  contain special characters - these cannot be easily detected in the
  sources without additional annotations

- remove most manual qstrdefs, use qstrdef autogen for: py, cc3200,
  stmhal, teensy, unix, windows, pic16bit:

   - remove all micropython generic qstrdefs except for the special strings that contain special characters (e.g. /,+,<,> etc.)
   - remove all port specific qstrdefs except for special strings
   - append sources for qstr generation in platform makefiles (SRC_QSTR)
2016-04-16 13:18:09 +01:00
..
core
memzip_files
Makefile py: Add rules for automated extraction of qstrs from sources. 2016-04-16 13:18:09 +01:00
README.md
add-memzip.sh
hal_ftm.c
hal_ftm.h
hal_gpio.c
help.c
lcd.c
led.c py: Change first arg of type.make_new from mp_obj_t to mp_obj_type_t*. 2016-01-11 00:49:27 +00:00
led.h
lexerfatfs.c
lexerfrozen.c teensy: Switch over to using frozen modules instead of memzip 2015-11-04 14:21:21 +00:00
lexermemzip.h
main.c py/runtime: mp_stack_ctrl_init() should be called immediately on startup. 2016-01-29 02:13:42 +02:00
make-pins.py
mk20dx256.ld
mk20dx256_af.csv
mk20dx256_prefix.c
modpyb.c lib/pyexec: Move header pyexec.h from stmhal directory. 2015-11-09 13:13:09 +00:00
mpconfigport.h py: Declare help, input, open builtins in core. 2016-04-15 00:07:56 +03:00
pin_defs_teensy.c
pin_defs_teensy.h
qstrdefsport.h py: Add rules for automated extraction of qstrs from sources. 2016-04-16 13:18:09 +01:00
reg.c
reg.h
servo.c
servo.h
std.h
teensy_hal.c
teensy_hal.h
teensy_pins.csv
timer.c py: Change first arg of type.make_new from mp_obj_t to mp_obj_type_t*. 2016-01-11 00:49:27 +00:00
timer.h
uart.c py: Change first arg of type.make_new from mp_obj_t to mp_obj_type_t*. 2016-01-11 00:49:27 +00:00
usb.c
usb.h

README.md

Build Instructions for Teensy 3.1

Currently the Teensy 3.1 port of MicroPython builds under Linux and not under Windows.

The tool chain required for the build can be found at https://launchpad.net/gcc-arm-embedded.

Download the current Linux *.tar.bz2 file. Instructions regarding unpacking the file and moving it to the correct location as well as adding the extracted folders to the enviroment variable can be found at http://eliaselectronics.com/stm32f4-tutorials/setting-up-the-stm32f4-arm-development-toolchain/

In order to download the firmware image to the teensy, you'll need to use the downloader included with TeensyDuino. The following assumes that you have TeensyDuino installed and set the ARDUINO environment variable pointing to the where Arduino with TeensyDuino is installed.

cd teensy
ARDUINO=~/arduino-1.0.5 make

To upload micropython to the Teensy 3.1.

Press the Program button on the Teensy 3.1

sudo ARDUINO=~/arduino-1.0.5/ make deploy

Currently, the Python prompt is through the USB serial interface, i.e.

minicom -D /dev/ttyACM0

TIPS

Install 49-teensy.rules into /etc/udev/rules.d

If you install the 49-teensy.rules file from http://www.pjrc.com/teensy/49-teensy.rules into your /etc/udev/rules.d folder then you won't need to use sudo:

sudo cp ~/Downloads/49-teensy.rules /etc/udev/rules.d
sudo udevadm control --reload-rules

Unplug and replug the teensy board, and then you can use: ARDUINO=~/arduino-1.0.5/ make deploy

Create a GNUmakefile to hold your ARDUINO setting.

Create a file call GNUmakefile (note the lowercase m) in the teensy folder with the following contents:

$(info Executing GNUmakefile)

ARDUINO=${HOME}/arduino-1.0.5
$(info ARDUINO=${ARDUINO})

include Makefile

GNUmakefile is not checked into the source code control system, so it will retain your settings when updating your source tree. You can also add additional Makefile customizations this way.