samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
/*
|
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
|
|
|
*
|
|
|
|
* The MIT License (MIT)
|
|
|
|
*
|
|
|
|
* Copyright (c) 2022 Robert Hammelrath
|
|
|
|
*
|
|
|
|
* Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
|
|
* of this software and associated documentation files (the "Software"), to deal
|
|
|
|
* in the Software without restriction, including without limitation the rights
|
|
|
|
* to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
|
|
* copies of the Software, and to permit persons to whom the Software is
|
|
|
|
* furnished to do so, subject to the following conditions:
|
|
|
|
*
|
|
|
|
* The above copyright notice and this permission notice shall be included in
|
|
|
|
* all copies or substantial portions of the Software.
|
|
|
|
*
|
|
|
|
* THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
|
|
* IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
|
|
* AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
|
|
* LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
|
|
* OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
|
|
|
|
* THE SOFTWARE.
|
|
|
|
*
|
|
|
|
* This file provides and checks pin capabilities as required
|
|
|
|
* for USART, I2C, SPI, PWM, ADC
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include <stdint.h>
|
2022-09-17 11:27:27 -04:00
|
|
|
#include "string.h"
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
|
2022-09-17 11:27:27 -04:00
|
|
|
#include "modmachine.h"
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
#include "py/runtime.h"
|
|
|
|
#include "py/misc.h"
|
|
|
|
#include "pin_af.h"
|
|
|
|
#include "sam.h"
|
|
|
|
|
|
|
|
|
|
|
|
extern const uint8_t tcc_channel_count[];
|
|
|
|
|
2022-06-16 05:32:21 -04:00
|
|
|
#include "pin_af_table.c"
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
|
|
|
|
// Just look for an table entry for a given pin and raise an error
|
|
|
|
// in case of no match (which should not happen).
|
|
|
|
|
2022-09-17 11:27:27 -04:00
|
|
|
const machine_pin_obj_t *get_pin_obj_ptr(int pin_id) {
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
for (int i = 0; i < MP_ARRAY_SIZE(pin_af_table); i++) {
|
|
|
|
if (pin_af_table[i].pin_id == pin_id) { // Pin match
|
|
|
|
return &pin_af_table[i];
|
|
|
|
}
|
|
|
|
}
|
2022-09-17 11:27:27 -04:00
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("not a Pin"));
|
|
|
|
}
|
|
|
|
|
2022-10-09 04:56:29 -04:00
|
|
|
const machine_pin_obj_t *pin_find(mp_obj_t pin) {
|
2022-09-17 11:27:27 -04:00
|
|
|
const machine_pin_obj_t *self = NULL;
|
|
|
|
// Is already a object of the proper type
|
2022-10-09 04:56:29 -04:00
|
|
|
if (mp_obj_is_type(pin, &machine_pin_type)) {
|
2022-09-17 11:27:27 -04:00
|
|
|
return pin;
|
|
|
|
}
|
|
|
|
if (mp_obj_is_small_int(pin)) {
|
|
|
|
// Pin defined by pin number for PAnn, PBnn, etc.
|
|
|
|
self = get_pin_obj_ptr(mp_obj_get_int(pin));
|
|
|
|
} else if (mp_obj_is_str(pin)) {
|
|
|
|
// Search by name
|
|
|
|
size_t slen;
|
|
|
|
const char *s = mp_obj_str_get_data(pin, &slen);
|
|
|
|
// Check for a string like PA02 or PD12
|
|
|
|
if (slen == 4 && s[0] == 'P' && strchr("ABCD", s[1]) != NULL &&
|
|
|
|
strchr("0123456789", s[2]) != NULL && strchr("0123456789", s[2]) != NULL) {
|
|
|
|
int num = (s[1] - 'A') * 32 + (s[2] - '0') * 10 + (s[3] - '0');
|
|
|
|
self = get_pin_obj_ptr(num);
|
|
|
|
} else {
|
|
|
|
for (int i = 0; i < MP_ARRAY_SIZE(pin_af_table); i++) {
|
|
|
|
if (slen == strlen(pin_af_table[i].name) &&
|
|
|
|
strncmp(s, pin_af_table[i].name, slen) == 0) {
|
|
|
|
self = &pin_af_table[i];
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
2022-10-09 04:56:29 -04:00
|
|
|
if (self != NULL) {
|
2022-09-17 11:27:27 -04:00
|
|
|
return self;
|
|
|
|
} else {
|
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("not a Pin"));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const char *pin_name(int id) {
|
|
|
|
static char board_name[5] = "Pxnn";
|
|
|
|
for (int i = 0; i < sizeof(pin_af_table); i++) {
|
|
|
|
if (pin_af_table[i].pin_id == id) {
|
|
|
|
if (pin_af_table[i].name[0] != '-') {
|
|
|
|
return pin_af_table[i].name;
|
|
|
|
} else {
|
|
|
|
board_name[1] = "ABCD"[id / 32];
|
|
|
|
id %= 32;
|
|
|
|
board_name[2] = '0' + id / 10;
|
|
|
|
board_name[3] = '0' + id % 10;
|
|
|
|
return board_name;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return "-";
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
}
|
|
|
|
|
|
|
|
// Test, wether the given pin is defined and has signals for sercom.
|
|
|
|
// If that applies return the alt_fct and pad_nr.
|
|
|
|
// If not, an error will be raised.
|
|
|
|
|
|
|
|
sercom_pad_config_t get_sercom_config(int pin_id, uint8_t sercom_nr) {
|
2022-09-17 11:27:27 -04:00
|
|
|
const machine_pin_obj_t *pct_ptr = get_pin_obj_ptr(pin_id);
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
if ((pct_ptr->sercom1 >> 4) == sercom_nr) {
|
|
|
|
return (sercom_pad_config_t) {ALT_FCT_SERCOM1, pct_ptr->sercom1 & 0x0f};
|
|
|
|
} else if ((pct_ptr->sercom2 >> 4) == sercom_nr) {
|
|
|
|
return (sercom_pad_config_t) {ALT_FCT_SERCOM2, pct_ptr->sercom2 & 0x0f};
|
|
|
|
} else {
|
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("wrong serial device"));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Test, wether the given pin is defined as ADC.
|
|
|
|
// If that applies return the adc instance and channel.
|
|
|
|
// If not, an error will be raised.
|
|
|
|
|
|
|
|
adc_config_t get_adc_config(int pin_id, int32_t flag) {
|
2022-09-17 11:27:27 -04:00
|
|
|
const machine_pin_obj_t *pct_ptr = get_pin_obj_ptr(pin_id);
|
|
|
|
#if defined(MCU_SAMD51)
|
|
|
|
if (pct_ptr->adc1 != 0xff && (flag & (1 << (pct_ptr->adc1 + 16))) == 0) {
|
|
|
|
return (adc_config_t) {1, pct_ptr->adc1};
|
|
|
|
} else
|
|
|
|
#endif
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
if (pct_ptr->adc0 != 0xff && (flag & (1 << pct_ptr->adc0)) == 0) {
|
|
|
|
return (adc_config_t) {0, pct_ptr->adc0};
|
|
|
|
#if defined(MUC_SAMD51)
|
|
|
|
} else if (pct_ptr->adc1 != 0xff && (flag & (1 << (pct_ptr->adc1 + 16))) == 0) {
|
|
|
|
return (adc_config_t) {1, pct_ptr->adc1};
|
|
|
|
#endif
|
|
|
|
} else {
|
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("ADC pin used"));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Test, wether the given pin is defined and has signals for pwm.
|
|
|
|
// If that applies return the alt_fct, tcc number and channel number.
|
|
|
|
// If not, an error will be raised.
|
|
|
|
// The function either supplies a channel from a wanted device, or
|
|
|
|
// tries to provide an unused device, if available.
|
|
|
|
|
|
|
|
pwm_config_t get_pwm_config(int pin_id, int wanted_dev, uint8_t device_status[]) {
|
2022-09-17 11:27:27 -04:00
|
|
|
const machine_pin_obj_t *pct_ptr = get_pin_obj_ptr(pin_id);
|
samd/pin_af: Add the pin af table and its helper functions.
The pin af table is a representation of the MUX table from the data sheet.
It provides information for each pin about the supported device functions.
That information is needed by pin.irq, machine.ADC, machine.PWM,
machine.UART, machine.SPI and machine.I2C. For each of these, the table
tells for each pin, which device number, af number and pad number is
assigned. Using the table gives a straight, uniform access to the
information, where the benefit outweights the size of the table, which is
not that large.
The tables are MCU-specific. It is not required to tell for each board,
which and where each of the above devices is available. That makes addding
boards easy.
Note: The information for DAC and I2S was not included, since it affects
only a few pins.
2022-06-05 03:26:49 -04:00
|
|
|
uint8_t tcc1 = pct_ptr->tcc1;
|
|
|
|
uint8_t tcc2 = pct_ptr->tcc2;
|
|
|
|
|
|
|
|
if (wanted_dev != -1) {
|
|
|
|
if ((tcc1 >> 4) == wanted_dev) {
|
|
|
|
return (pwm_config_t) {ALT_FCT_TCC1, tcc1};
|
|
|
|
} else if ((tcc2 >> 4) == wanted_dev) {
|
|
|
|
return (pwm_config_t) {ALT_FCT_TCC2, tcc2};
|
|
|
|
} else {
|
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("wrong device or channel"));
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
pwm_config_t ret = {};
|
|
|
|
if ((tcc1 >> 4) < TCC_INST_NUM) {
|
|
|
|
ret = (pwm_config_t) {ALT_FCT_TCC1, tcc1};
|
|
|
|
if (tcc2 == 0xff) {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if ((tcc2 >> 4) < TCC_INST_NUM) {
|
|
|
|
// if a device in slot 1 is not available or already in use, use the one in slot 2
|
|
|
|
if (tcc1 == 0xff || device_status[(ret.device_channel >> 4)] != 0) {
|
|
|
|
return (pwm_config_t) {ALT_FCT_TCC2, tcc2};
|
|
|
|
} else {
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
mp_raise_ValueError(MP_ERROR_TEXT("not a PWM pin"));
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|