Well given kickstarter has now changed the rules, and Teensy 3.0 as it was funded would not have been allowed under the new rules. So it may not make any difference whether you tell them or not. Paul himself has spoken out against the new rules, and I imagine hardware projects like the Teensy will just go elsewhere.

Kickstarter can go back to being a tip jar to fund art projects, as it evidently wants to do so. As I said in their blog, I wish them a good life, but I have stopped looking at KS for interesting tech projects to fund. The only things I do on KS now is to check on updates to the 4 tech products I recently backed (RadioBlock, Teensy, Digispark, and JumpShot) as well as the one non-tech product (Deck of Extraordinary Voyages)

I believe the recent rule change was motived mainly to protect Kickstarter from liability, rather than protecting backers from failed projects. I haven't seen anything really conclusive about the Hanfree lawsuit, but the plaintiff publicly said he asked the court to rule the nature of the transaction was an ordinary sale. I'm an engineer, not an attorney, so I'm not going to speculate what that might mean?

It could also be purely coincidental that the "not a store" rule change came about just as the Hanfree lawsuit was making it's way through the legal system.

Here's the failed Hanfree project, where you can read all the ugly details in the comments.

Just wanted to let others know of my progress so far on using my new Teensy 3.0 board. I had to order a micro USB cable and it arrived yesterday. I had previously loaded the modified IDE and the Teensy driver thingee, so I just attached the Teensey to the cable and plugged it in. PC seemed to be happy with the attachment and a led on the Teensey was blinking away so I assumed they ship it with the blink sketch loaded. I opened the IDE, selected the Teensey 3.0 board, loaded the mimumSketch example and it upload. I was a little surprised when the Teesey loader pop window sprung up, as I had no idea how the Teensy works with the arduino IDE, but the loader has a option to follow a scrip log and it seemed to all be working correctly, even though in the IDE results window is says something about compile size is zero bytes, but the Teensy loader pop-up log shows all the correct size info and a lot of other stuff. Anyway the Teensy board did stop blinking it's led, so everything seemed to upload and run OK. I then loaded blink sketch example in the IDE and hit upload and everything worked again and the board did indeed start blinking it's led again.

So I guess the report is that the Teensey 3.0 seems to work right out of the box as designed even for this software-installing-challenged kind of guy that I am. I still haven't a clue what I might do with this board yet. And Paul seems to be releasing a new IDE version every other day to add some new arduino library update, so it seems kind of silly to rush into anything. But it's a great little product with a lot of promise ahead for it I think. I kind of hope a Teensey forum might start up to help support this product, if one is not already around somewhere?

I'm still getting over the shock of how....well teensey this thing is, so small.

@Lefty - glad it's working. I fixed the size reporting in beta4. This evening I'm going to publish beta5, with a master-only port of Wire (slave mode to be filled in next week), and Serial1, Serial2, and Serial3 working.

@fat16lib - I applied the patch. Now the code compiles. It's not quite working, but that's probably a bug on my end. I'm investigating now. Will try to get those 24 Mbit/sec optimized routines written for you.

I'm still getting over the shock of how....well teensy this thing is, so small.

I know how you feel. When I got my first teensy in hands I was also going like "this small"? And indeed it all worked great out of the box and the blink sample is preloaded (This is part of Paul testing the boards).

I would really advice Arduino to look at what Paul is doing (more often). For instance: Even though the teensy 2 uses the same chip as the Leonardo it does not have the 2 com ports issue which is very distracting. The due has 2 com ports. I guess if they had used halfkay (the window that popped up during upload) like Teensy they would not need 2 com ports.

Best regardsJantje

Do not PM me a question unless you are prepared to pay for consultancy.Nederlandse sectie - http://arduino.cc/forum/index.php/board,77.0.html -

I've been working with the SdFat beta for the last hour, digging into why it's not working. Turns out __attribute__((packed)) bit me yet again. Forgot I've started from a clean copy to apply the patch.

I mailed you a version with mods for faster reads/writes. It compiles for Teensy 3.0 but is not tested on Teensy 3.0 since I have not received the replacement for the missing Teensy 3.0 that Robin sent yesterday.

The results for a AVR Mega with 4096 byte writes and reads are promising.

I received my Teensy 3.0 yesterday, it is awesome! I downloaded the latest beta and got the board going on first try! I have used Teensy 2.0 before so maybe that has a bit to do with it working so quickly but, I am impressed!

So far, I have just changed and reloaded the blink code a few times, and found the reload of a sketch is blazing fast!

I'm glad Teensy 3 is working out well, especially the fast upload process.

I actually put months of work into optimizing the upload speed. I spent quite a bit of time analyzing the Teensy 2.0 upload process. The 2.0 bootloader is quite simple (it needs to be, since it fits entirely within 512 bytes of code). It receives a chunk of data, then programs it to the flash, then sends an ACK. That works well, but it doesn't achieve the best speed. First, the entire chip needs to be erased when the first write request shows up. Erasing the chip earlier isn't an option, because users expect to be able to go into bootloader mode, but if nothing is transmitted the chip is expected to remain unmodified. So there's a lag while erasing, and then while writing the first chunk. Then when the ACK is sent, the software on the PC sends the next chunk. Because it's a user space program, it's subjected to ordinary scheduling delays, which can average several milliseconds before the next chunk is sent. Over the span of writing many chunks, those USB latencies and operating system scheduling delays add up. More time is spent waiting than writing.

In 3.0, I implemented quite a lot of buffering in RAM. So while the chip is erasing, several chunks of data are buffered into RAM. Once programming begins, there's plenty of data buffered to keep the speed constrained only by the flash writing. The operating system's userspace scheduling delays result in bursts of incoming data to refill the buffers. With enough on-chip buffering, the flash writing never stalls waiting for more data. So the upload speed runs at very close to the maximum possible speed imposed only by the flash itself. I used the chip's fast DMA engine to copy from the buffers to the flash controller, to minimize the non-writing time. But overall, buffering in the chip's RAM is the key to avoiding delay.

There's another speedup I've designed, which isn't currently in use on Teensy 3.0. While the loading speed is nearly as fast as the flash memory allows, there is about a 1 second delay (longer on some windows machines) from the instant the compiler produces the .hex file to the upload actually beginning. When Teensy reboots into bootloader mode, the USB disconnects, and then it reappears as the new device which accepts the download. Leonardo does the same. Each operating system does USB enumeration slightly differently, but there are delays associated with USB reset signals and other USB stuff, which add up to about 1 second or more.

My hope is to eliminate all that delay by "rebooting" into the bootloader code without disconnecting the USB. The support for it is all in place in Teensy 3.0, so I hope to enable this with a software update sometime next year (2013). But this is a lot of difficult software work to implement successfully on the computer side. The loader needs to deal with requesting the "reboot" and then checking to see if it was successful. There are a number of complications with basically switching a USB device at runtime without going through the proper enumeration process. If it doesn't work, of course the fallback is to disconnect. Success or failure needs to be determined in a matter of milliseconds to be of any value. All that needs to be done times 3, because each operating system has dramatically different low-level USB APIs. But if it is successful, the opportunity for speedup is pretty incredible. That 1+ second USB enumeration is now the single largest delay (assuming your machine is fast and the build-dependency patch is avoiding full recompile). I want to turn that last 1 second delay into only single-digit milliseconds!