c046b23ea2
Helps prevent the filesystem from getting formatted by mistake, among other things. For example, on a Pico board, entering Ctrl+D and Ctrl+C fast many times will eventually wipe the filesystem (without warning or notice). Further rationale: Ctrl+C is used a lot by automation scripts (eg mpremote) and UI's (eg Mu, Thonny) to get the board into a known state. If the board is not responding for a short time then it's not possible to know if it's just a slow start up (eg in _boot.py), or an infinite loop in the main application. The former should not be interrupted, but the latter should. The only way to distinguish these two cases would be to wait "long enough", and if there's nothing on the serial after "long enough" then assume it's running the application and Ctrl+C should break out of it. But defining "long enough" is impossible for all the different boards and their possible behaviour. The solution in this commit is to make it so that frozen start-up code cannot be interrupted by Ctrl+C. That code then effectively acts like normal C start-up code, which also cannot be interrupted. Note: on the stm32 port this was never seen as an issue because all start-up code is in C. But now other ports start to put more things in _boot.py and so this problem crops up. Signed-off-by: David Grayson <davidegrayson@gmail.com> |
||
|---|---|---|
| .. | ||
| core | ||
| memzip_files | ||
| Makefile | ||
| README.md | ||
| add-memzip.sh | ||
| hal_ftm.c | ||
| hal_ftm.h | ||
| hal_gpio.c | ||
| help.c | ||
| lcd.c | ||
| led.c | ||
| led.h | ||
| lexerfrozen.c | ||
| lexermemzip.h | ||
| main.c | ||
| make-pins.py | ||
| manifest.py | ||
| mk20dx256.ld | ||
| mk20dx256_af.csv | ||
| mk20dx256_prefix.c | ||
| modpyb.c | ||
| mpconfigport.h | ||
| pin_defs_teensy.c | ||
| pin_defs_teensy.h | ||
| qstrdefsport.h | ||
| reg.c | ||
| reg.h | ||
| servo.c | ||
| servo.h | ||
| std.h | ||
| teensy_hal.c | ||
| teensy_hal.h | ||
| teensy_pins.csv | ||
| timer.c | ||
| timer.h | ||
| uart.c | ||
| uart.h | ||
| 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 environment 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.
Tips for OSX
Set the ARDUINO environment variable to the location where Arduino with TeensyDuino is installed.
export ARDUINO=~/Downloads/Arduino.app/Contents/Java/
Search /dev/ for USB port name, which will be cu.usbmodem followed by a few numbers. The name of the port maybe different depending on the version of OSX. To access the Python prompt type:
screen <devicename> 115200