Search results

That doesn't seem to change anything. I even installed Teensyduino on a Windows 7 laptop, and the pre-production device shows up as "Unrecognized USB device", and the production one works fine.

I didn't. It looked like it had something to do with EEPROM and/or RTC, neither of which I'm using right now. I'm also not using Arduino (unless I have to). So far, the only arduino projects I've run is the blinky one. I've been working on supporting MicroPython on the new boards (which seems...

The 15 second wipe seems to work on my production 3.6, but unfortunately not on my pre-production board. I sent an email to paul at pjrc dot com but never got a repsonse. Which email address should I use? Mine is dhylands at gmail dot com.

I've been working with my pre-production Teensy 3.6 for a while, and today I seem to have bricked it. I'm running Ubuntu 16.04 LTS. I had left the Arduino flashing program running and was also flashing using teensy_loader_cli and it seems to have left my teensy 3.6 in an unusable state. When...

I don't think so. I also tried: USE_ARDUINO_TOOLCHAIN=1 ARDUINO=~/arduino-1.0.6 make deploy (after a make clean) and that also works (the original invocation uses arm-none-eabi-gcc from your path). This invocation uses the toolchain from teensyduino. In both cases, micropython is built with...

Your size looks fine, so it has to be something to do with teensyduino. I just installed arduino-1.0.6 and then installed tensyduino-1.20 on top of that and did: cd micropython/teensy ARDUINO=~/arduino-1.0.6 make deploy and it downloads fine (and shows in the Teensy boot loader as 81%)

When I build the latest, then it reports the following size information: LINK build/micropython.elf text data bss dec hex filename 199884 1252 20328 221464 36118 build/micropython.elf

It sounds like you have an older TeensyDuino. There was a bug in the early versions that only considered the flash size to be 128K. You need to be using version 1.19 or newer. https://www.pjrc.com/teensy/td_download.html

I think that's mostly from the core part of micropython supporting more features.

Actually, it looks like that's the help for the regular pyboard. The teensy doesn't have alll of that implemented yet.

Right. Somewhere along the way I changed things so that teensyduino is no longer required to build micropython. It now uses the same toolchain as is used for the pyboard. I use the toolchain mentioned in the README.md file at the root of the git tree. This has the advantage that the teensy...

The latest master on micropython builds now, but it has a bit less functionality than the earlier build. I've started working on the teensy port again and I'm slowly implementing things. I'll be updating things that work on this wiki page...

The official MicroPython forum is here: http://forum.micropython.org/ There currently isn't a Teensy 3.1 board section, but if people ask questions related to the Teensy, then I'll request that they add one.

Hey Steve, I created a new thread to talk about MicroPython. I just did a pull-request on the main micropython repo which gets the basic teensy build working with the latest micropython tree. This currently includes serial-over-USB and GPIO. The remaining work is primarily peripheral support...

Hi Paul, Thanks for your comments. In addition to what the actual license says, I'm also interested in ensuring I don't offend, and keep to the "spirit" of how you'd like to see the code used. Currently, building for the teensy 3.1 would be: cd micropyton/teensy make So there is a separate...

Hi, This question is probably directed to Paul. I've been working on MicroPython, and, if possible, I'd like to checkin some of the .c and .h files from the hardware/teensy/cores/teensy3 directory in the MicroPython repository. Right now, the list of files that I need is: Arduino.h...

I've only ever built micropython under linux. When building for the Teensy 3.1, it expects that you'll have TeensyDuino 1.18rc2 installed http://forum.pjrc.com/threads/24796-Teensyduino-1-18-Release-Candidate-2-Available and that the ARDUINO environment variable points to the top of the...

If the TX-O output is low when then the voltge on A is > B then that suggests a faulty chip/breakout board. It's also possible that you have a case of a cold solder joint on the breakout. Since the RS485 signal is differential, it might work some of the time if the B input is left unconnected...

Being low for more than a character time or so generates a break condition which might be a factor.

I believe that there is also work under way in the mbed repository to add support as well.

Hi Andy, Yeah - the main source is in a fairly fast state of flux and its been a few days since I updated the port. You can grab a copy that does compile by doing: git clone https://github.com/dhylands/micropython.git git checkout fix-2014-01-14 It looks like we're going to try and use the...

I started with https://github.com/apmorton/teensy-template (which was setup for Teensy 3.0) and modified it for Teensy 3.1. You can find my version here: https://github.com/dhylands/rover/blob/master/Makefile https://github.com/dhylands/rover/blob/master/common.mk It really depends. Some...

I have a Nexus 5. I'd like to be able to plug in my N5 to my Teensy 3.1 and see the serial output on the phone. I already have the requisite OTG to USB adapter cable, and I've been able to connect to an FTDI USB Adapter using one of the terminal programs, but so far no luck using the teensy...

Well, just as a proof of concept, I put together a Solarbotics DragonTail kit, and replaced the Arduino board with a Teensy 3.1 running MicroPython. http://dhylands.blogspot.ca/2014/01/micropython-running-on-teensy-31.html

Well, that sounds like the classic "uninitialized pointer" behaviour. This is notorious for stack variables. If they're uninitialized, then they just get whatever random data happens to be on the stack leftover from previous functions running. uninitialized pointers and writing to memory you're...

I also noticed a typo in the teensy-template Makefile. It has: OPTIONS += -D__MK20DX128__ -DARDUIO=104 and ARDUINO (in -DARDUIO=104) is mis-spelled.

And if you want to leave your sketch as a .ino file, you can do: $(BUILDDIR)/%.o: %.ino @echo "[CXX]\t$<" @mkdir -p "$(dir $@)" @$(CXX) $(CPPFLAGS) $(CXXFLAGS) $(L_INC) -o "$@" -c -x c++ -include Arduino.h "$<"

One of the first things I do when faced with a problem like this, is to take your numbers and convert them to hexadecimal. 808333360 = 0x302e3030 and since the teensy is little endian, this becomes 30 30 2e 30 when looking at raw memory. This happens to correspond to the ASCII characters "00.0"...

So, if you go into micropython/teensy and do: make upload then it already calls teensy_post_compile and teensy_reboot :) However, I'd much rather use a purely command line tool like load_linux_only.c The only thing missing from load_linux_only.c is that it doesn't reboot the teensy. How...

I do know that for MicroPython, the byte-codes are NOT compatible with the regular full python. This has to do with wanting to minimze heap allocations. See dpgeorge's comment here (2nd to the last comment when I wrote this email). Obviously, using bytecode would be preferred to using source...

ok - here's how I think I'll approach it. 1 - Append the python source script to the micropython.hex file and burn it along with micropython. 2 - Add support for zip files and allow the zip file to be appended to the micropython .hex. You could probably just use the zip as a storage container...

And what I'm considering is option number #4. I've used this method on previous projects and basically you create a super-simple read-only file-system. You set it up to that it goes at the high end of flash. You use teensy loader to write it (this assumes that I can write to arbitray locations...

Just an FYI: My changes have been merged into the official micropython repository I will continue to work in my fork and submit PRs (pull requests) to the micropython project.

I think that any approach that has persistence would be good. Personally, I'm impartial to the actual implementation. I need to figure out what exactly the MicroPython board will be doing and then decide if I should go that route or go the more Teensy influenced route makes the most sense. This...

Err we have 256K of flash and are currently using 70K. So we can probably go upto 128K (although I'd rather start out smaller and leave room for more code features). 64K or 96K seems like a better size to start with.

I can confirm that the loader 1.18rc2 works great with large hex files. I've rewritten the MicroPython port to be purely in C. I created a new branch here: https://github.com/dhylands/micropython/tree/teensy-3.1 and I've done a pull request on the official micropython port. Incidently, the C...

Hi Steve, Sure. The initial version is here: http://www.davehylands.com/Misc/micropython.hex You can't do much with this version (yet). I noticed that there was a version of printf included with the STM port of MicroPython (this is the one which will go with the MicroPython board). So I...

I've got the initial port of MicroPython for the Teensy 3.1 working (just the REPL, no I/O - i.e. GPIO/ADC etc) I made a fork of the micropython repository here: https://github.com/dhylands/micropython All of my changes are in the teensy directory, with the exception of an edit to py/misc.h...

Hi, I'd like to find out the origins of libc that comes with the ARM toolchain for the Teensy 3.1. I'll guess newlib, but I thought it would be good for confirmation. Ideally, I'd like to find out which actual version is included. I'm in the process of porting micropython to the Teensy 3.1...

Hi Len, I got the loader working with the following additional changes: 2404 >diff ~/Downloads/load_linux_only.c load_linux_only.c 270a271,272 > libusb_teensy_handle = open_usb_device(0x16C0, 0x0483); // testing only > if (libusb_teensy_handle) return 1; 772c774 < #define MAX_MEMORY_SIZE...

Hi Len, Thanks. It seems to be failing with the same error message (no surprise there), but at least now that I have source I can debug the problem. The port has been relatively straight forward so far. The biggest issue I've faced is that micropython is pure C code, and the Arduino support...

I'm trying to port micropython to the Teensy 3.1. My micropython.elf file looks like: micropython.elf: file format elf32-little Sections: Idx Name Size VMA LMA File off Algn 0 .text 000211a0 00000000 00000000 00008000 2**3...

You might be able to get away with using some type of SPI interface, but since it looks like its 10 bits, I'd be inclined to just bit bang it http://en.wikipedia.org/wiki/Bit_banging You'd configure the clock signal as a GPIO output, and the data line as a GPIO input. Page 7 of the data sheet...

Hi, Just wanted to say thanks for putting this together. I got it working with my Teensy 3.1 by making the following modifications in the main Makefille: Changed -DF_CPU=48000000 to be -DF_CPU=96000000 Changed -D__MK20DX128__ -DARDUIO=104 to be -D__MK20DX256__ -DARDUIO=105 (I'm not sure if...

Hi, I just finished putting together some libraries and a serial monitor program for my Teensy 3.1, so I thought I would share. The first library, is called StrPrintf. It allows printf style output, but you get to provide a pointer to a function which actually does the output. It's based on...