I think I know what is wrong. The CMSIS folder is found in the Arduino 1.5.2 distribution only. So I have to copy it and paste it into my Arduino 1.0.5 distribution.
I thought that's what I said earlier today! I guess it wasn't very clear. Sorry.
I think I know what is wrong. The CMSIS folder is found in the Arduino 1.5.2 distribution only. So I have to copy it and paste it into my Arduino 1.0.5 distribution.
This is what I did:
teensy3.build.additionalobject1=/full/pathname/to/libarm_cortexM4l_math.a
fatal error: arm_math.h: No such file or directory
But when I check the version, its showing up as Teensy Loader 1.07.
Wow, that's a lot of complex steps!!!!
Several months ago I added hpyle's patch to Teensyduino, so you should not need to do all that crazy stuff.
I'm considering adding the math library and header to Teensyduino 1.15.
Does anyone have any input or ideas about how (or if) I ought to do this?
My inclination is to link the .a file by default as part of the build, and put the header somewhere the compiler can find it, but you'd still need to put a #include "arm_math.h" into your program if you want to use it. How does that sound?
seconded, that would be very convenient...I'm considering adding the math library and header to Teensyduino 1.15.
I wonder how much floating point is being done on Teensy 3.0's, and whether there is enough of a market for Paul to consider using a chip with hardware floating point for Teensy 3.0++. The Cortex M4F has single precision floating point built in (but not double, so you would need to use 'float' as a type, and add 'f' suffixes to constants to keep the calculations in single precision). Some things naturally lend themselves to being done in floating point, but is it a significant share of the market to justify going to a more expensive chip?
Believe me, I know about NDA's and how frustrating it can be not to talk about them in wider contexts, particularly as people are asking for new and better stuff. I have various war stories over the years, but this probably isn't the forum to elaborate on them.@MichaelMeissner - I can't talk about Teensy++ 3.0 at this time, because we're still waiting for a new chip from Freescale. Until they officially release it, all the technical details are under NDA. The best I can say at this moment is that I believe you'll agree (in hindsight) that it was worth the wait.
I've attached a ZIP archive of 7 CMSIS sketches that I've got working on Teensy 3.
A complete sketch that compiles and produces output from the FFT on serial is at: https://gist.github.com/TJC/5633491
Thanks!!!
Of course, faster hardware is pretty enticing too. You know I can't discuss Teensy++ 3.0 yet, but you'd be pretty safe to assume it will be faster. Even then, it's the software that makes the biggest difference, especially for people using Arduino and not looking to dig into low-level programming, so I'm going to keep investing most of my effort into the software side.
It seems to be missing arm_fft_bin_data.h