Follow on now that I am back to my computer...
Personally I would suggest not insulting those of us who try to help out... It is sometimes hard when know what some one is asking when there is no context given. I mainly mentioned the electrical aspect as I have seen it more than once up on forums, where someone thinks they can use one of the Analog only pins for something like a button, and they give it +5v and blow the processor...
WHERE ARE THEY DEFINED? - Again hard to know what you mean... That is
a) where there is a #define mentioned? Well grep is your friend... Example:
In pins_arduino.h under the section for the T3.2 (__MK20DX256__) You will see:
And several lines down you will see:
Code:
const static uint8_t A14 = PIN_A14;
So you can see that for THIS chip internally it maps to 40...
b) Or do you mean what physical pin on the processor does this Correspond to? Many ways to find this, but you could look at schematic:
https://www.pjrc.com/teensy/schematic.html
And see that it connects to the physical pin: DAC0
c) Or you could mean how does this map to how analogRead works? This is define in the table in cores\teensy3\analog.c again depending on processor:
I believe that currently is line 401...
d) Or maybe how it is used in analogWrite to do digital to analog conversions... That is in analog.c again and there is code that for this processor specifically looks for (pin == 14) and calls off to analogWriteDAC0...
Edit: But if you are instead asking why this pin is not included in the table: const struct digital_pin_bitband_and_config_table_struct digital_pin_to_info_PGM[] = {
in pins_teensy.c (line 41...) which for T3.2 only goes up pin 33... Again that is because this pin does not support digital stuff.. Again this is constrained by the definitions in core_pins.h
Code:
#elif defined(__MK20DX256__)
#define CORE_NUM_TOTAL_PINS 34
#define CORE_NUM_DIGITAL 34
#define CORE_NUM_INTERRUPT 34
#define CORE_NUM_ANALOG 21
#define CORE_NUM_PWM 12