Search results

  1. L

    Future Teensy features & pinout

    Hello Paul, is any chance to require a production of Teensy 4.1 mounting the Industrial version of iMXRT1062 (so the iMXRT1062C version) instead of the Consumer version (iMXRT1062D)? Obviously, such a change wouldn't be requested for a single board but at least for 100 of them.
  2. L

    Any tips for teensy 4.0 availability?

    Thank you Paul. I really appreciate your help and suggestions. Kind regards and keep up with your amazing work.
  3. L

    Any tips for teensy 4.0 availability?

    Hello Paul, thank you for the update. I suppose then TEENSY40 will not be available easily from distributors in the next future. Do you think I can buy some tens of TEENSY41_NE directly from your website? In case, do you know which distributor have enough stock?
  4. L

    Teensy 4.0 Compatibility with 1.71V to 1.95V

    Ok, thanks, I will do the same. I was just wandering if I can use the same PCB I've already made for MPU9250.
  5. L

    Teensy 4.0 Compatibility with 1.71V to 1.95V

    I'm trying to interface teensy with ICM-20948 (I still don't have this chip), previously I was using the MPU9250 that is going out of stock. The chips are pin-to-pin compatible, except that VDDIO is changed from the range [1.7V - 3.5V] to [1.71V - 1.95V]. I've not found anywhere if teensy can...
  6. L

    Teensy 4.0 Compatibility with 1.71V to 1.95V

    Hello everybody, I wonder if someone has already tested the I2C communication to a device that communicate with an I2C bus with voltages in the range 1.71V to 1.95V. Should I add a circuit to adapt tension to 3.3V for the Teensy input?
  7. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    Solved. In https://www.visualmicro.com/forums/YaBB.pl?num=1574749494 the administrator made the new version (1911.23.1) that even on VS2017 doesn't generate any warning. Thanks all!
  8. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    I've just replicated the problem at home. VS2017 (Community, 15.9.17) + Visual Micro 1909.27.1 + Arduino 1.8.9 + Teensyduino 1.47 generate thousand of unmeaningful warnings. And verified that the same configuration, with VS2019 (Community, 16.3.10), it doesn't generate any warning. I will post...
  9. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    Just to check, I reinstalled your configuration, except VS2017 that I cannot remove here at work. VM 1909.27.1 (I didn't find the 1909.27.0) Arduino 1.8.9 Teensyduino 1.47 Unfortunately, the error is the same. Even the most basic project template, goes from zero warnings for Teensy 3.6 to...
  10. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    I'm a lazy programmer, I use Visual studio even for displaying simple (non-code) text... Anyway, if I can't find any other solution, I will give it a try :-)
  11. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    Hello bmillier, thank you for your reply. I suppose the problem may arise because I'm using VS2019, maybe because last version of VM has not been tested fully with VS2017. Consider that I started to have this problem with Teensyduino (1.48), Arduino (1.8.9) and VM(1909.27.0) in VS2017 and I...
  12. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    Thank you Paul for your reply. Just done it, it works without any error/warning, at least for a simple project. I will try for the full project to check if I can make it without using Visual Studio. But, as I mentioned in my first post, it is a "problem" regarding just the intellisense, a stuff...
  13. L

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename"

    Visual Studio 2017+Visual Micro+Teensyduino+Teensy 4.0 warns: "EMIT not typename" Hello guys, I've a little problem here. I'm quite lazy and I like to work with advanced IDEs like VS and all the stuffs that make my work easy. I'm typically working with the following configuration: - VS 2017...
  14. L

    New I2C library for Teensy3

    I'm interested in the topic, my new Teensy 4.0 cannot access I2C buses to control devices I already tested with 3.2 and 3.6. Any news about development? Any suggestion about how to add some modification to the last library version to make it work (even modification not very efficient) for T4.0...
  15. L

    Future Teensy features & pinout

    I've a lot of 3.6 devices (hundreds) out whose computation power is used at their limit, so they need to run with single precision instead of double precision for most of their matrix operations. I actually use 5 out of 6 serial ports and my desire is to have almost the same pinout for serial...
  16. L

    Teensy 4.0 (hypothetical) pin assignments

    Thank you, it was my worrying, to have another super-fast chip on what to use double precision computation (necessary for my flight control algorithms) with software emulation that slows a lot big matrices operations. I did it the same on 3.6, but mathematics optimization was a blood bath.
  17. L

    Teensy 4.0 (hypothetical) pin assignments

    Apologize my ignorance. Will the i.MX RT1052 (or 1060, if or when implemented) perform better than 3.6 in terms of double precision floating point processing, apart from being much faster? I mean, will be this unit "just" 4-5 time faster than the Teensy 3.6 in double math processing? Apart from...
  18. L

    MPU-9250 Teensy Library

    Hello everybody, I'm the proud owner of a Teensy 3.6 and a Drotek MPU9250+MS5611 (Here the schematics). I'm trying to use the Brian's library (very thanks for the huge work). I've connected the two boards as follows (I've indicated the pins by their position on the board, where L and R indicate...
Back
Top