Thanks for the replies. It's fairly much as Lukas states but I'll try to explain a bit more in detail to confirm for others.
After selecting a new pin as Lukas states default values populate the lower panel. At this stage if the code is updated the code such as below is generated in the file pin_mux.c:
gpio_pin_config_t misc_config = {
.pinDirection = kGPIO_DigitalOutput,
.outputLogic = 0U,
};
/* Initialize GPIO functionality on pin PIO0_0 (pin 19) */
GPIO_PinInit(BOARD_INITPINS_misc_GPIO, BOARD_INITPINS_misc_PORT, BOARD_INITPINS_misc_PIN, &misc_config);
But it's only after after all default values in the lower panel are changed/ confirmed that the code below is generated:
const uint32_t misc = (/* Selects pull-up function */
IOCON_PIO_MODE_PULLUP |
/* Disable hysteresis */
IOCON_PIO_HYS_DI |
/* Input not invert */
IOCON_PIO_INV_DI |
/* Disables Open-drain function */
IOCON_PIO_OD_DI |
/* Bypass input filter */
IOCON_PIO_SMODE_BYPASS |
/* IOCONCLKDIV0 */
IOCON_PIO_CLKDIV0);
/* PIO0 PIN0 (coords: 19) is configured as GPIO, PIO0, 0. */
IOCON_PinMuxSet(IOCON, IOCON_INDEX_PIO0_0, misc);
It might not be clear to others but it seems to me that the code is only fully generated when all the default values are changed/ confirmed, so although a GPIO might be set as an output it won't be programmed as one until all the rest of the values (even though they may be acceptable) are changed/ confirmed.
Hope this helps,
Leo
