Search results

Definitely. That's what I liked about the Teensy++2, apt-get avr tools, download and compile the loader, and I'm ready to go. While I'm waiting on my Teensy3 order to come in, why are you needing to compile gcc? The gcc on raspbian already is an ARM compiler, and from the Makefile arguments...

Just thought I would let you know that post earned you a sale of 4 Tennsy3's. As my Teensy++2 is connected up to an ARM system having source code to load from that system was a requirement for me. Thanks for posting the link.

See my earlier comment. With the addition of libusb-dev the loader compiled and ran out of the box, same with my existing teensy++ 2.0 program. My desktop took 1.26 seconds to compile the teensy program and 22.8 seconds on the Raspberry Pi, and I have the 256 MB early board version. It is a...

I have the Teensy++2.0 compiling and loading on my Raspberry Pi. The steps are outlined on the pjrc.com webpage starting at http://www.pjrc.com/teensy/loader_cli.html for the Teensy Loader, Command Line, source code. You'll need these packages to compile for avr and libusb for the Teensy...

source/repo? I have more projects than teensy++ 2.0's, and since the 3.0 is out I thought I would give it a try. With Debian and the teensy++ 2.0 I just `apt-get install gcc-avr binutils-avr avr-libc` compile the teensy_loader_cli.c and go. The gcc here is taking the command lines...

I'm running avr-gcc (GCC) 4.7.0 and found that usb_serial.c version 1.1 from http://www.pjrc.com/teensy/usb_serial.html no longer compiles with the following error, error: variable 'device_descriptor' must be const in order to be put into read-only section by means of '__attribute__((progmem))'...