3c658a4e75
Because (for Thumb) a function pointer has the LSB set, pointers to dynamic functions in RAM (eg native, viper or asm functions) were not being traced by the GC. This patch is a comprehensive fix for this. Addresses issue #820. |
||
---|---|---|
.. | ||
core | ||
memzip_files | ||
Makefile | ||
README.md | ||
add-memzip.sh | ||
hal_gpio.c | ||
help.c | ||
import.c | ||
lcd.c | ||
led.c | ||
led.h | ||
lexerfatfs.c | ||
lexermemzip.c | ||
lexermemzip.h | ||
main.c | ||
make-pins.py | ||
memzip.c | ||
memzip.h | ||
mk20dx256.ld | ||
mk20dx256_af.csv | ||
mk20dx256_prefix.c | ||
modpyb.c | ||
mpconfigport.h | ||
pin_defs_teensy.c | ||
pin_defs_teensy.h | ||
qstrdefsport.h | ||
servo.c | ||
servo.h | ||
std.h | ||
teensy_hal.c | ||
teensy_hal.h | ||
teensy_pins.csv | ||
uart.c | ||
usb.c |
README.md
Build Instructions for Teensy 3.1
Currently the Teensy 3.1 port of Micro Python builds under Linux and not under Windows.
The tool chain required for the build can be found at https://launchpad.net/gcc-arm-embedded.
Downlaod 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/
Previous Instructions Shown Below (no longer valid)
This 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
make upload
Currently, the python prompt is through the USB serial interface.