Search results

  1. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    Duly noted. Will do and report. ;-) Thank you
  2. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    I would like to circle around and mention this as it looks like it was lost in the primary discussion... I am unable to tell the difference between T3.1 and T3.2 when connected. My point is that it looks to me like the Teensey reports "who is connected" during the upload process. So the message...
  3. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    In my case I did not see appreciable difference before 1000 and in my case 2000 works best, this said I think that there are two separate issues. During development the delay can be cranked up so that the uploads are stable and for final application download it can be reduced for the fast start...
  4. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    Works So.... EUREKA! sort off.... Things started working flawlessly and for now I am not screwing with anything until I can confirm that things continue to be stable. Several things to mention though... my /teensy/avr/cores/teensy3/pins_teensy.c. is clearly a different version from the one...
  5. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    Thank you all for helping with this ;-) I would like to mention this in trying to be helpful and solving this issue... The 3.1 works flawlessly on my systems (regardless of OS, etc. etc) that is just one fact that I do have. The 3.2 fails 95% of the time as described. There are few things...
  6. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    Yes... I just confirmed that it does not care what I send to it. Blink will gag it just as well. So to re-iterate this interesting behavior... When I compile and upload the loader "pings" the 3.2 and at that point it goes dark... Once I switch to different USB the 3.2 comes up alive running...
  7. I

    Teensey 3.2 Teensey Loader 1.24 Issues

    Hello, I have an identical project using Teensey 3.1 and now 3.2. All of my 3.1's upload code flawlessly. The 3.2 most of the time fails to upload. The Teensey actually goes dark as if there was no power from the USB port as soon as I upload the code from the Arduino 1.6.5 The only remedy is to...
  8. I

    (FreqMeasure.available() timeout semaphore

    Thank you very much. This is very helpful. Things are for some reason much clearer in the morning ;-)
  9. I

    (FreqMeasure.available() timeout semaphore

    My apologies for not being clear as I did conflate two issues. I have a need to do both. My application measures the time between each pulse in the train but also the time from the start of the first pulse To the last falling edge in that train. It looks to me like the first read() returns the...
  10. I

    (FreqMeasure.available() timeout semaphore

    Hello, I am struggling with the FreqMeasure library. My problem is that I need to detect a train of pulses. With the FreqMeasure.available() I painfully realized that I am not able to use !FreqMeasure.available() to signal an end of a pulse. The function toggles only once from FALSE For...
  11. I

    Small Bug in FreqMeasure_capture.h

    Actually it was a great learning experience for me ;-)
  12. I

    Small Bug in FreqMeasure_capture.h

    It looks like I worked with different version (and presumably an old one) that I downloaded from your site https://www.pjrc.com/teensy/td_libs_FreqMeasure.html (Version 1.1) It would be helpful to have the Version numbers commented in the libraries. My mistake clearly was getting it directly...
  13. I

    Small Bug in FreqMeasure_capture.h

    Hello, While playing with the FreqMeasure Library I was hoping to get two independent channels to measure frequency. This brought me to looking at the FreqMeasure_capture.h and realizing that the #if defined(CAPTURE_USE_FTM1_CH0) was the same for the CH1 as well as the FTM2 CH0 and CH1. The...
Back
Top