user42225: It is possible to access the Physical Pin 93, Pin PC11 on ATSAM3X8E in Arduino Due  from the Arduino IDE?
I am programming a Barebone ATSAM3X8E, and it do not seems to be allocated by Arduino Due nor by ATSAM3X8E for any other purpose than the PC Port.




user70020: Modifying/Making a variant
If you wanted to do it in an Arduino-like way it would require editing the Arduino Due variant.cpp or copying the making your own variant, say from a copy of the Due, and editing the extern const PinDescription g_APinDescription[] array to include an entry that matches for PC11.
Example changes
As an experiment I made the following changes to files in the packages/arduino/hardware/sam/1.6.12/variants/arduino_due_x under the arduino15 directory.
In variant.cpp, an entry for in the g_APinDescription array is insert an index number 79, between the existing two entries (shown for context):
  { PIOB, PIO_PB23B_SPI0_NPCS3,ID_PIOB,PIO_PERIPH_B,PIO_DEFAULT, PIN_ATTR_DIGITAL,                  NO_ADC, NO_ADC, NOT_ON_PWM,  NOT_ON_TIMER }, // NPCS3
  // Addition line here VVVV (this is the line for PC12, copied with PIO_PC12 changed to PIO_PC11
  { PIOC, PIO_PC11,          ID_PIOC, PIO_OUTPUT_0, PIO_DEFAULT, PIN_ATTR_DIGITAL,                  NO_ADC, NO_ADC, NOT_ON_PWM,  NOT_ON_TIMER }, //
  // 79 .. 84 - "All pins" masks

  // 79 - TWI0 all pins
  { PIOA, PIO_PA17A_TWD0|PIO_PA18A_TWCK0, ID_PIOA, PIO_PERIPH_A, PIO_DEFAULT, (PIN_ATTR_DIGITAL|PIN_ATTR_COMBO), NO_ADC, NO_ADC, NOT_ON_PWM, NOT_ON_TIMER },

This is a copy of the entry for PC12, with PIO_PC12 changed to PIO_PC11.
In variant.h, PINS_COUNT changes to 80u, because we've inserted  the pin:
#define PINS_COUNT           (80u)

and later in the file the pin number associate with CAN are bumped up by one also because they're all numbered after the point of insertion:
/*
 * Complementary CAN pins
 */
static const uint8_t CAN1RX = 89;
static const uint8_t CAN1TX = 90;

// CAN0
#define PINS_CAN0            (91u)
// CAN1
#define PINS_CAN1            (92u)

I programmed a sketch the blinks PC11 by way of digitalWrite(79, state); and carefully placed a logic probe on the the unrouted pin on the Due board, and it "blinks" just fine.  That's as far as I've tested.
Direct control
Alternately you could control the pin in your code manually, doing what digitalWrite or digitalRead would normally do.  In other words, you could read the description of something like digitalWrite here and substitute all of the references that it would have gotten from g_APinDescription with hard-coded values.

42225: <p>It is possible to access the Physical Pin 93, Pin PC11 on ATSAM3X8E in <a href="https://www.arduino.cc/en/Hacking/PinMappingSAM3X" rel="nofollow noreferrer">Arduino Due</a>  from the Arduino IDE?</p>
<p>I am programming a Barebone ATSAM3X8E, and it do not seems to be allocated by <a href="https://forum.arduino.cc/t/due-pinout-diagram/129258" rel="nofollow noreferrer">Arduino Due</a> nor by ATSAM3X8E for any other purpose than the PC Port.</p>
<p><a href="https://i.stack.imgur.com/mfC61.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/mfC61.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/rJh43.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/rJh43.png" alt="enter image description here" /></a>
<a href="https://i.stack.imgur.com/ZIuZU.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/ZIuZU.png" alt="enter image description here" /></a></p>
 70020: <h1>Modifying/Making a variant</h1>
<p>If you wanted to do it in an Arduino-like way it would require editing the Arduino Due <a href="https://github.com/arduino/ArduinoCore-sam/blob/c43d4be/variants/arduino_due_x/variant.cpp" rel="nofollow noreferrer">variant.cpp</a> or copying the making your own variant, say from a copy of the Due, and editing the <code>extern const PinDescription g_APinDescription[]</code> array to include an entry that matches for PC11.</p>
<h2>Example changes</h2>
<p>As an experiment I made the following changes to files in the <code>packages/arduino/hardware/sam/1.6.12/variants/arduino_due_x</code> under the arduino15 directory.</p>
<p>In variant.cpp, an entry for in the <code>g_APinDescription</code> array is insert an index number 79, between the existing two entries (shown for context):</p>
<pre class="lang-c prettyprint-override"><code>  { PIOB, PIO_PB23B_SPI0_NPCS3,ID_PIOB,PIO_PERIPH_B,PIO_DEFAULT, PIN_ATTR_DIGITAL,                  NO_ADC, NO_ADC, NOT_ON_PWM,  NOT_ON_TIMER }, // NPCS3
  // Addition line here VVVV (this is the line for PC12, copied with PIO_PC12 changed to PIO_PC11
  { PIOC, PIO_PC11,          ID_PIOC, PIO_OUTPUT_0, PIO_DEFAULT, PIN_ATTR_DIGITAL,                  NO_ADC, NO_ADC, NOT_ON_PWM,  NOT_ON_TIMER }, //
  // 79 .. 84 - &quot;All pins&quot; masks

  // 79 - TWI0 all pins
  { PIOA, PIO_PA17A_TWD0|PIO_PA18A_TWCK0, ID_PIOA, PIO_PERIPH_A, PIO_DEFAULT, (PIN_ATTR_DIGITAL|PIN_ATTR_COMBO), NO_ADC, NO_ADC, NOT_ON_PWM, NOT_ON_TIMER },
</code></pre>
<p>This is a copy of the entry for PC12, with <code>PIO_PC12</code> changed to <code>PIO_PC11</code>.</p>
<p>In variant.h, <code>PINS_COUNT</code> changes to <code>80u</code>, because we've inserted  the pin:</p>
<pre class="lang-c prettyprint-override"><code>#define PINS_COUNT           (80u)
</code></pre>
<p>and later in the file the pin number associate with CAN are bumped up by one also because they're all numbered after the point of insertion:</p>
<pre class="lang-c prettyprint-override"><code>/*
 * Complementary CAN pins
 */
static const uint8_t CAN1RX = 89;
static const uint8_t CAN1TX = 90;

// CAN0
#define PINS_CAN0            (91u)
// CAN1
#define PINS_CAN1            (92u)
</code></pre>
<p>I programmed a sketch the blinks PC11 by way of <code>digitalWrite(79, state);</code> and carefully placed a logic probe on the the unrouted pin on the Due board, and it &quot;blinks&quot; just fine.  That's as far as I've tested.</p>
<h1>Direct control</h1>
<p>Alternately you could control the pin in your code manually, doing what <code>digitalWrite</code> or <code>digitalRead</code> would normally do.  In other words, you could read the description of something like digitalWrite <a href="https://github.com/arduino/ArduinoCore-sam/blob/c43d4be431bd5673f6bb26f83411bbd8f9ef89ef/cores/arduino/wiring_digital.c#L91" rel="nofollow noreferrer">here</a> and substitute all of the references that it would have gotten from <code>g_APinDescription</code> with hard-coded values.</p>
