Teensy 4.0 what does the orange LED mean?

[jcun4128]

I have not seen this LED turn on before, and I've been using the Teensy 4.0 for a while.

This is not the same LED that turns on while programming/resetting/blink. It's by pins 13/14 (by the reset button).

It just came on and I'm wondering does it mean something like the Teensy 4.0 was subjected to a short or something.

It is possible I fed 5V into pins 14 or 15, I was poking around with my Tfmini-s that I stripped the pads on (delicate connector).

Maybe that's it? The Teensy still works to my knowledge, don't think anything is "broken" but I'm concerned about this LED that I didn't turn on myself coming on.

 

[KurtE]

This just means that pin 13 has a high value:

From the product page: https://www.pjrc.com/store/teensy40.html

LED Pin
    Pin 13 has an orange LED connected. The LED can be very convenient to show status info. When pin 13 is used as an input, the external signal must be able to drive the LED when logic HIGH. pinMode INPUT_PULLUP should not be used with pin 13.

Note: If you look at the Teensy version of Blink, you will see:

// Teensy 2.0 has the LED on pin 11
// Teensy++ 2.0 has the LED on pin 6
// Teensy 3.x / Teensy LC have the LED on pin 13
const int ledPin = 13;

// the setup() method runs once, when the sketch starts

void setup() {
  // initialize the digital pin as an output.
  pinMode(ledPin, OUTPUT);
}

// the loop() methor runs over and over again,
// as long as the board has power

void loop() {
  digitalWrite(ledPin, HIGH);   // set the LED on
  delay(1000);                  // wait for a second
  digitalWrite(ledPin, LOW);    // set the LED off
  delay(1000);                  // wait for a second
}

Note: Most board types have a define for which pin is the LED pin: LED_BUILTIN

So: you can simply use it like: pinMode(LED_BUILTIN, OUTPUT);

 

[jcun4128]

Right now it's not connected to anything/I'm not trying to use it (Pin 13).
It just randomly turned on today after several months of use... that's why I'm concerned thinking maybe I shorted something while I was screwing around with the pins going to 14/15 (serial 3).
But I could write some code to write it to 0/low and see if that turns it off.

Thanks

edit: yeah I wrote it to LOW and it's off, so I guess we're good...