The only problem could be how Paul's boot-loader works on Teensy 3.0. You need a hook to load you hex file.

This is what the page says about the boot-loader (not sure what it means but it sounds like it does not impact the tool chain )

Quote

Teensy 3.0 features an off-chip bootloader design. On Teensy 2.0 and all Arduino(R)** brand boards, the bootloader consumes a small portion of the available flash memory. On most boards, the bootloader executes briefly before your own program. By storing the bootloader in a separate chip, your code can use all of the flash memory. Your code can also run immediately after a reset event, without bootloader interference.

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 wasn't very clear, I am sure you can generate a hex file with any Cortex M4 tool chain.

Here is my question. How easy is it to load an arbitrary hex file?

I read this also

Quote

Teensy 3.0 features an off-chip bootloader design. On Teensy 2.0 and all Arduino(R)** brand boards, the bootloader consumes a small portion of the available flash memory. On most boards, the bootloader executes briefly before your own program. By storing the bootloader in a separate chip, your code can use all of the flash memory. Your code can also run immediately after a reset event, without bootloader interference.

I wonder how you start the boot loader?

My guess is that the button copies the boot-loader into RAM. The boot-loader can then program all flash.

Perhaps the boot-loader uses FlexMemory. I don't have a clear understanding of FlexMemory.

If anyone here has any experience with the Leaflab Maple boards, you will know what a massive undertaking the porting of much of the AVR-based Arduino code over to the ARM architecture is. The Leaflab boards are great little Cortex-3 prototyping boards, with an Arduino derived IDE and a "wirish" port of the basic wiring stuff, but much of the promise of the hardware (DMA, advanced interrupt handling etc.) even to this day has yet to be really fully realised because of the at times painfully slow rate of porting across (or creation from scratch) of many of the libs we take for granted on the Arduino.

I have developed using the Maple boards, and to be honest, despite the raw hardware advantages, the Mega2560 is in many ways far more capable prototyping platform, apart from some niche applications. As a sage once said, "it's the software, stupid."

So, recent history ponts to where the challenge is. Building a good ARM dev board -- certainly not trivial, but pales into comparison to the effort required in building a complete software development environment that would be comparable to the Arduino ecosystem.

Having said all this, I might add I'm not surprised that the announced "team Arduino" development effort for an ARM based Arduino product is today a year old -- and not a public beta release in sight.

So good luck to Paul. But he's going to need more than good luck -- he's also going to need considerable community support if this platform is really going to take off.

Mine has shown up and is blinking (and the IDE works, so I've modified the blink rate and whatnot, and it uploads/etc.) I've soldered pins on "upside down" for easier access to the extra backside signals, although this hides the reset button and I'll have to remember to be really careful when trying to remove the board from the protoboard.Pretty cool. It's very tiny (teensy!)