Search results

I was seeing this backwards behavior as well in a setup where I have the Teensy connected via USB and powered by a DC adapter. I have a capacitive touch sense board I designed for testing Atmel's QTouch library a while back that I thought would work fine with the Teensy as well. It's basically a...

I wish I could try this but unfortunately the Teensy is soldered directly into protoboard - my fault for not adding another layer of separation using extra headers. I will try this if it happens again.

I actually didn't know about this trick, but I just tried it and it didn't seem to do anything. I confirmed that the fuse and the dual schottky diode are still working with a multimeter, so I guess the issue lies elsewhere.

Hi all, I have some Teensy 3s that are most likely dead because they aren't being detected when connected via USB and powered by an external 5V power supply. Are there any good ways to determine the cause of death? Also, I seem to be alarmingly good at zombifying Teensies, so has anyone else...

Thanks, and yes I'm not sure what I could have done either. It seemed to suddenly die when I was working on the software side of things and now I'm not able to detect it over USB, though it is powered externally.

Thanks, Paul. What is the 1A dual diode-looking component? From the schematic I would assume that's a voltage regulator? Whatever it is, I think I've blown it somehow while running on external power...

Thanks, Doug. Just curious, what was the fix? Did you change the size of the outline? No worries on the github thing, I was just wondering. Maybe once it's been tried and tested a bit more you could publish it somewhere for posterity.

You can instantiate an array of them just like any other array: elapsedMillis foo[10]; (I just tested this to be sure)

Thanks, Doug, that's better. I just noticed that when running a DRC with standard settings, I get "dimension" errors on all of the vias. I'm not familiar enough with DRC rules to know what is causing it, but I've attached a screenshot. I understand I may have to tweak my settings, since the...

Wow, I didn't know about that but it will make life simpler. Thanks!

Try what pixelk suggests (9600 baud) and also see if there are other com ports available. I had a similar issue that was resolved by switching to COM4, even though the program uploaded and the Teensy rebooted on COM3 just fine, somehow...

Another minor issue - you have a stray via for pin 9 waaay off board in the package design.

Glad that worked. However, it looks like you haven't yet extended this to two buttons/keys. You may encounter issues doing that since you are still using a delay() in your main loop, assuming you want a separate LED for each button. For example, consider what will happen if press two buttons in...

Hi Doug, Thanks for taking a shot at the Eagle library. I'm going to be designing some PCBs around the Teensy 3 and I'd be happy to provide feedback as I go along. Just a couple of cosmetic issues I noticed initially: * P7 is labeled as "P5_CS1", but should probably be "P5_TX1"? * P8 is...

Sorry, I've just noticed you said Teensy 2, not 3. If that's the case, I believe you'll only be able to attach interrupts to one of the pins labeled INTn in the diagram for whichever Teensy (2 or 2++) you are using: http://www.pjrc.com/teensy/pinout.html

Hi there, I think what you want to do is handle the button presses with interrupts rather than by polling for status. With interrupts, a button press can trigger a function (interrupt handler) to run, which can either turn your LED on/off itself OR set some variable(s) for your main loop to act...

I did what you suggested with the device manager and saw that COM4, not COM3, was the right port for me. Oddly enough, the software had selected COM3 but was able to upload sketches just fine. After switching to COM4 in the software, my messages are getting printed now. Thanks!

Using the code below, I'm not seeing any text appear in the serial monitor (also tried TeraTerm); however, the LED is blinking just fine: void setup() { Serial.begin(9600); pinMode(13, OUTPUT); } void loop() { Serial.println("led on"); digitalWrite(13, 1); delay(1000)...

If you go with frequency, the PWM duty cycle would have to be parametrized as some sort of percentage. If you go with the period in time units, the duty cycle could be accepted as a pulse width in time units. I personally find the frequency domain more natural, but I'm happy with either so long...

I would like to generate a >1MHz clock signal for an external LED driver chip to use for its PWM cycle. I've been doing this on another microcontroller by setting up a PWM pin with a 50% duty cycle to pulse on and off very quickly, which required access to the low-level registers. I've read this...