Page 3 of 3
Re: Teensy 3.5 & 3.6 support
Posted: Thu Dec 01, 2016 8:14 pm
by Roberthh
Hello @dhylands. I just stumbled over an issue. When you call
and push Ctrl-C twice, the device locks up. Id does not matter, if you push the Ctrl-C twice in a row or other characters in between. I know it's WIP, so I just wanted to note,
Re: Teensy 3.5 & 3.6 support
Posted: Sun Jan 08, 2017 3:23 am
by dhylands
@roberthh - I fixed the Control-C problem, and I think I found the data loss issue.
I rebased to the latest master (1.8.6) and updated the .hex files.
https://github.com/dhylands/micropython/tree/teensy-usb
https://github.com/dhylands/micropython ... /hex-files
I also put a copy of the hex-files here:
https://www.dropbox.com/sh/ubvenq4onpid ... 7x3aa?dl=0
Re: Teensy 3.5 & 3.6 support
Posted: Sun Jan 08, 2017 10:33 am
by Roberthh
Hello @dhylands, thank you for the update.
I was able to update my local copy of the repository, compiled & load it, and it seems to work.
I just compared the Ctrl-C handling with sys.stdin.read(1) on the various port, and all behave different.
The behavior I like most is that of the ESP8266 port, in that it interrupts your code, if no exception handler is set, and triggers that handler, if set. and all of that on the first Ctrl-C.
Best Regards, Robert
Re: Teensy 3.5 & 3.6 support
Posted: Sun Jan 08, 2017 9:57 pm
by dhylands
Roberthh wrote:Hello @dhylands, thank you for the update.
I was able to update my local copy of the repository, compiled & load it, and it seems to work.
I just compared the Ctrl-C handling with sys.stdin.read(1) on the various port, and all behave different.
The behavior I like most is that of the ESP8266 port, in that it interrupts your code, if no exception handler is set, and triggers that handler, if set. and all of that on the first Ctrl-C.
Best Regards, Robert
Currently, that behaviour is determined by code in the stmhal port wihch is shared by the teensy port (so stmhal and teensy both behave the same).
When (
softirq's get merged, then I expect we'll see this behaviour become more consistent.
If I had to guess, I would bet that if you called the delay function for several seconds and hit a single Control-C in the middle of the delay, then it won't get processed until the delay actually completes.
Re: Teensy 3.5 & 3.6 support
Posted: Fri Nov 03, 2017 1:11 am
by kamikaze
any progress on this?
Re: Teensy 3.5 & 3.6 support
Posted: Sat Dec 28, 2019 1:21 am
by rcolistete
I'd like to have I2C working on MicroPython for Teensy 3.2/3.5/3.6.
Anyone currently working on MicroPython for Teensy 3.2/3.5/3.6 or even 4.0 ?
I can try to help developing I2C with some spare time in January, if guided by a more experient developer.
Re: Teensy 3.5 & 3.6 support
Posted: Sat Jan 18, 2020 4:41 pm
by rcolistete
Branch teensy-rtc from dhylands/micropython repository seems to be the newest MicroPython code for Teensy 3.1/3.2/3.5/3.6, with good documentation of the machine functions :
https://github.com/dhylands/micropython ... ine-module
It has ADC, RTC (+ time module), SD (Teensy 3.5/3.6), rng (Teensy 3.5/3.6), USB_VCP, etc.
The .hex firmware files in :
https://github.com/dhylands/micropython ... /hex-files
are from 20170107, not updated with commits from teensy-rtc, so they lack RTC and time modules.
To have the firmware with RTC (+ time module), compile :
Code: Select all
$ git clone https://github.com/dhylands/micropython.git
$ cd micropython
$ git checkout teensy-rtc
$ cd teensy
$ make BOARD=TEENSY_3.1
$ make BOARD=TEENSY_3.5
$ make BOARD=TEENSY_3.6
PS: dhylands, feel free to comment.