2017-12-21 07:49:14 -05:00
|
|
|
/*
|
|
|
|
|
* This file is part of the MicroPython project, http://micropython.org/
|
|
|
|
|
*
|
|
|
|
|
* The MIT License (MIT)
|
|
|
|
|
*
|
|
|
|
|
* Copyright (c) 2016 Scott Shawcroft for Adafruit Industries
|
|
|
|
|
*
|
|
|
|
|
* 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.
|
|
|
|
|
*/
|
|
|
|
|
|
2019-01-30 18:50:07 -05:00
|
|
|
#include "py/mphal.h"
|
|
|
|
|
#include "py/obj.h"
|
|
|
|
|
#include "py/runtime.h"
|
|
|
|
|
|
2017-12-21 07:49:14 -05:00
|
|
|
#include "common-hal/microcontroller/Pin.h"
|
|
|
|
|
#include "common-hal/microcontroller/Processor.h"
|
|
|
|
|
|
2019-01-30 18:50:07 -05:00
|
|
|
#include "shared-bindings/nvm/ByteArray.h"
|
2018-01-03 16:50:57 -05:00
|
|
|
#include "shared-bindings/microcontroller/__init__.h"
|
2017-12-21 07:49:14 -05:00
|
|
|
#include "shared-bindings/microcontroller/Pin.h"
|
|
|
|
|
#include "shared-bindings/microcontroller/Processor.h"
|
|
|
|
|
|
2018-06-27 14:14:25 -04:00
|
|
|
#include "supervisor/filesystem.h"
|
2020-01-30 09:52:06 -05:00
|
|
|
#include "supervisor/port.h"
|
2019-07-14 14:02:01 -04:00
|
|
|
#include "supervisor/shared/safe_mode.h"
|
2018-06-27 14:14:25 -04:00
|
|
|
#include "nrfx_glue.h"
|
2020-01-30 09:52:06 -05:00
|
|
|
#include "nrf_nvic.h"
|
2018-06-27 14:14:25 -04:00
|
|
|
|
2018-07-16 09:01:46 -04:00
|
|
|
// This routine should work even when interrupts are disabled. Used by OneWire
|
|
|
|
|
// for precise timing.
|
2017-12-21 07:49:14 -05:00
|
|
|
void common_hal_mcu_delay_us(uint32_t delay) {
|
2018-06-27 14:14:25 -04:00
|
|
|
NRFX_DELAY_US(delay);
|
2017-12-21 07:49:14 -05:00
|
|
|
}
|
|
|
|
|
|
2020-01-30 09:52:06 -05:00
|
|
|
static volatile uint32_t nesting_count = 0;
|
|
|
|
|
static uint8_t is_nested_critical_region;
|
2017-12-21 07:49:14 -05:00
|
|
|
void common_hal_mcu_disable_interrupts() {
|
nRF: Always use sd_nvic_critical_region calls
The motivation for doing this is so that we can allow
common_hal_mcu_disable_interrupts in IRQ context, something that works
on other ports, but not on nRF with SD enabled. This is because
when SD is enabled, calling sd_softdevice_is_enabled in the context
of an interrupt with priority 2 or 3 causes a HardFault. We have chosen
to give the USB interrupt priority 2 on nRF, the highest priority that
is compatible with SD.
Since at least SoftDevice s130 v2.0.1, sd_nvic_critical_region_enter/exit
have been implemented as inline functions and are safe to call even if
softdevice is not enabled. Reference kindly provided by danh:
https://devzone.nordicsemi.com/f/nordic-q-a/29553/sd_nvic_critical_region_enter-exit-missing-in-s130-v2
Switching to these as the default/only way to enable/disable interrupts
simplifies things, and fixes several problems and potential problems:
* Interrupts at priority 2 or 3 could not call common_hal_mcu_disable_interrupts
because the call to sd_softdevice_is_enabled would HardFault
* Hypothetically, the state of sd_softdevice_is_enabled
could change from the disable to the enable call, meaning the calls
would not match (__disable_irq() could be balanced with
sd_nvic_critical_region_exit).
This also fixes a problem I believe would exist if disable() were called
twice when SD is enabled. There is a single "is_nested_critical_region"
flag, and the second call would set it to 1. Both of the enable()
calls that followed would call critical_region_exit(1), and interrupts
would not properly be reenabled. In the new version of the code,
we use our own nesting_count value to track the intended state, so
now nested disable()s only call critical_region_enter() once, only
updating is_nested_critical_region once; and only the second enable()
call will call critical_region_exit, with the right value of i_n_c_r.
Finally, in port_sleep_until_interrupt, if !sd_enabled, we really do
need to __disable_irq, rather than using the common_hal_mcu routines;
the reason why is documented in a comment.
2020-07-14 18:34:45 -04:00
|
|
|
if (nesting_count == 0) {
|
|
|
|
|
// Unlike __disable_irq(), this should only be called the first time
|
|
|
|
|
// "is_nested_critical_region" is sd's equivalent of our nesting count
|
|
|
|
|
// so a nested call would store 0 in the global and make the later
|
2023-03-18 11:17:02 -04:00
|
|
|
// exit call not actually re-enable interrupts
|
nRF: Always use sd_nvic_critical_region calls
The motivation for doing this is so that we can allow
common_hal_mcu_disable_interrupts in IRQ context, something that works
on other ports, but not on nRF with SD enabled. This is because
when SD is enabled, calling sd_softdevice_is_enabled in the context
of an interrupt with priority 2 or 3 causes a HardFault. We have chosen
to give the USB interrupt priority 2 on nRF, the highest priority that
is compatible with SD.
Since at least SoftDevice s130 v2.0.1, sd_nvic_critical_region_enter/exit
have been implemented as inline functions and are safe to call even if
softdevice is not enabled. Reference kindly provided by danh:
https://devzone.nordicsemi.com/f/nordic-q-a/29553/sd_nvic_critical_region_enter-exit-missing-in-s130-v2
Switching to these as the default/only way to enable/disable interrupts
simplifies things, and fixes several problems and potential problems:
* Interrupts at priority 2 or 3 could not call common_hal_mcu_disable_interrupts
because the call to sd_softdevice_is_enabled would HardFault
* Hypothetically, the state of sd_softdevice_is_enabled
could change from the disable to the enable call, meaning the calls
would not match (__disable_irq() could be balanced with
sd_nvic_critical_region_exit).
This also fixes a problem I believe would exist if disable() were called
twice when SD is enabled. There is a single "is_nested_critical_region"
flag, and the second call would set it to 1. Both of the enable()
calls that followed would call critical_region_exit(1), and interrupts
would not properly be reenabled. In the new version of the code,
we use our own nesting_count value to track the intended state, so
now nested disable()s only call critical_region_enter() once, only
updating is_nested_critical_region once; and only the second enable()
call will call critical_region_exit, with the right value of i_n_c_r.
Finally, in port_sleep_until_interrupt, if !sd_enabled, we really do
need to __disable_irq, rather than using the common_hal_mcu routines;
the reason why is documented in a comment.
2020-07-14 18:34:45 -04:00
|
|
|
//
|
|
|
|
|
// This only disables interrupts of priority 2 through 7; levels 0, 1,
|
|
|
|
|
// and 4, are exclusive to softdevice and should never be used, so
|
|
|
|
|
// this limitation is not important.
|
2020-01-30 09:52:06 -05:00
|
|
|
sd_nvic_critical_region_enter(&is_nested_critical_region);
|
|
|
|
|
}
|
nRF: Always use sd_nvic_critical_region calls
The motivation for doing this is so that we can allow
common_hal_mcu_disable_interrupts in IRQ context, something that works
on other ports, but not on nRF with SD enabled. This is because
when SD is enabled, calling sd_softdevice_is_enabled in the context
of an interrupt with priority 2 or 3 causes a HardFault. We have chosen
to give the USB interrupt priority 2 on nRF, the highest priority that
is compatible with SD.
Since at least SoftDevice s130 v2.0.1, sd_nvic_critical_region_enter/exit
have been implemented as inline functions and are safe to call even if
softdevice is not enabled. Reference kindly provided by danh:
https://devzone.nordicsemi.com/f/nordic-q-a/29553/sd_nvic_critical_region_enter-exit-missing-in-s130-v2
Switching to these as the default/only way to enable/disable interrupts
simplifies things, and fixes several problems and potential problems:
* Interrupts at priority 2 or 3 could not call common_hal_mcu_disable_interrupts
because the call to sd_softdevice_is_enabled would HardFault
* Hypothetically, the state of sd_softdevice_is_enabled
could change from the disable to the enable call, meaning the calls
would not match (__disable_irq() could be balanced with
sd_nvic_critical_region_exit).
This also fixes a problem I believe would exist if disable() were called
twice when SD is enabled. There is a single "is_nested_critical_region"
flag, and the second call would set it to 1. Both of the enable()
calls that followed would call critical_region_exit(1), and interrupts
would not properly be reenabled. In the new version of the code,
we use our own nesting_count value to track the intended state, so
now nested disable()s only call critical_region_enter() once, only
updating is_nested_critical_region once; and only the second enable()
call will call critical_region_exit, with the right value of i_n_c_r.
Finally, in port_sleep_until_interrupt, if !sd_enabled, we really do
need to __disable_irq, rather than using the common_hal_mcu routines;
the reason why is documented in a comment.
2020-07-14 18:34:45 -04:00
|
|
|
__DMB();
|
|
|
|
|
nesting_count++;
|
2017-12-21 07:49:14 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void common_hal_mcu_enable_interrupts() {
|
nRF: Always use sd_nvic_critical_region calls
The motivation for doing this is so that we can allow
common_hal_mcu_disable_interrupts in IRQ context, something that works
on other ports, but not on nRF with SD enabled. This is because
when SD is enabled, calling sd_softdevice_is_enabled in the context
of an interrupt with priority 2 or 3 causes a HardFault. We have chosen
to give the USB interrupt priority 2 on nRF, the highest priority that
is compatible with SD.
Since at least SoftDevice s130 v2.0.1, sd_nvic_critical_region_enter/exit
have been implemented as inline functions and are safe to call even if
softdevice is not enabled. Reference kindly provided by danh:
https://devzone.nordicsemi.com/f/nordic-q-a/29553/sd_nvic_critical_region_enter-exit-missing-in-s130-v2
Switching to these as the default/only way to enable/disable interrupts
simplifies things, and fixes several problems and potential problems:
* Interrupts at priority 2 or 3 could not call common_hal_mcu_disable_interrupts
because the call to sd_softdevice_is_enabled would HardFault
* Hypothetically, the state of sd_softdevice_is_enabled
could change from the disable to the enable call, meaning the calls
would not match (__disable_irq() could be balanced with
sd_nvic_critical_region_exit).
This also fixes a problem I believe would exist if disable() were called
twice when SD is enabled. There is a single "is_nested_critical_region"
flag, and the second call would set it to 1. Both of the enable()
calls that followed would call critical_region_exit(1), and interrupts
would not properly be reenabled. In the new version of the code,
we use our own nesting_count value to track the intended state, so
now nested disable()s only call critical_region_enter() once, only
updating is_nested_critical_region once; and only the second enable()
call will call critical_region_exit, with the right value of i_n_c_r.
Finally, in port_sleep_until_interrupt, if !sd_enabled, we really do
need to __disable_irq, rather than using the common_hal_mcu routines;
the reason why is documented in a comment.
2020-07-14 18:34:45 -04:00
|
|
|
if (nesting_count == 0) {
|
2023-02-11 23:50:20 -05:00
|
|
|
// This is very very bad because it means there was mismatched disable/enables.
|
|
|
|
|
reset_into_safe_mode(SAFE_MODE_INTERRUPT_ERROR);
|
2020-01-30 09:52:06 -05:00
|
|
|
}
|
nRF: Always use sd_nvic_critical_region calls
The motivation for doing this is so that we can allow
common_hal_mcu_disable_interrupts in IRQ context, something that works
on other ports, but not on nRF with SD enabled. This is because
when SD is enabled, calling sd_softdevice_is_enabled in the context
of an interrupt with priority 2 or 3 causes a HardFault. We have chosen
to give the USB interrupt priority 2 on nRF, the highest priority that
is compatible with SD.
Since at least SoftDevice s130 v2.0.1, sd_nvic_critical_region_enter/exit
have been implemented as inline functions and are safe to call even if
softdevice is not enabled. Reference kindly provided by danh:
https://devzone.nordicsemi.com/f/nordic-q-a/29553/sd_nvic_critical_region_enter-exit-missing-in-s130-v2
Switching to these as the default/only way to enable/disable interrupts
simplifies things, and fixes several problems and potential problems:
* Interrupts at priority 2 or 3 could not call common_hal_mcu_disable_interrupts
because the call to sd_softdevice_is_enabled would HardFault
* Hypothetically, the state of sd_softdevice_is_enabled
could change from the disable to the enable call, meaning the calls
would not match (__disable_irq() could be balanced with
sd_nvic_critical_region_exit).
This also fixes a problem I believe would exist if disable() were called
twice when SD is enabled. There is a single "is_nested_critical_region"
flag, and the second call would set it to 1. Both of the enable()
calls that followed would call critical_region_exit(1), and interrupts
would not properly be reenabled. In the new version of the code,
we use our own nesting_count value to track the intended state, so
now nested disable()s only call critical_region_enter() once, only
updating is_nested_critical_region once; and only the second enable()
call will call critical_region_exit, with the right value of i_n_c_r.
Finally, in port_sleep_until_interrupt, if !sd_enabled, we really do
need to __disable_irq, rather than using the common_hal_mcu routines;
the reason why is documented in a comment.
2020-07-14 18:34:45 -04:00
|
|
|
nesting_count--;
|
|
|
|
|
if (nesting_count > 0) {
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
__DMB();
|
|
|
|
|
sd_nvic_critical_region_exit(is_nested_critical_region);
|
2017-12-21 07:49:14 -05:00
|
|
|
}
|
|
|
|
|
|
2018-01-03 16:50:57 -05:00
|
|
|
void common_hal_mcu_on_next_reset(mcu_runmode_t runmode) {
|
2019-07-14 14:02:01 -04:00
|
|
|
enum { DFU_MAGIC_UF2_RESET = 0x57 };
|
2023-01-19 16:58:03 -05:00
|
|
|
if (runmode == RUNMODE_BOOTLOADER || runmode == RUNMODE_UF2) {
|
|
|
|
|
sd_power_gpregret_set(0,DFU_MAGIC_UF2_RESET);
|
2021-03-15 09:57:36 -04:00
|
|
|
} else {
|
2023-01-19 16:58:03 -05:00
|
|
|
sd_power_gpregret_set(0,0);
|
2021-03-15 09:57:36 -04:00
|
|
|
}
|
|
|
|
|
if (runmode == RUNMODE_SAFE_MODE) {
|
2023-02-11 23:50:20 -05:00
|
|
|
safe_mode_on_next_reset(SAFE_MODE_PROGRAMMATIC);
|
2021-03-15 09:57:36 -04:00
|
|
|
}
|
2018-01-03 16:50:57 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void common_hal_mcu_reset(void) {
|
2018-06-27 14:14:25 -04:00
|
|
|
filesystem_flush();
|
2020-05-22 07:34:54 -04:00
|
|
|
reset_cpu();
|
2018-01-03 16:50:57 -05:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
// The singleton microcontroller.Processor object, bound to microcontroller.cpu
|
2017-12-21 07:49:14 -05:00
|
|
|
// It currently only has properties, and no state.
|
2018-01-03 16:50:57 -05:00
|
|
|
const mcu_processor_obj_t common_hal_mcu_processor_obj = {
|
2017-12-21 07:49:14 -05:00
|
|
|
.base = {
|
|
|
|
|
.type = &mcu_processor_type,
|
|
|
|
|
},
|
|
|
|
|
};
|
2018-08-30 21:42:25 -04:00
|
|
|
|
2019-01-30 18:50:07 -05:00
|
|
|
#if CIRCUITPY_INTERNAL_NVM_SIZE > 0
|
|
|
|
|
// The singleton nvm.ByteArray object.
|
|
|
|
|
const nvm_bytearray_obj_t common_hal_mcu_nvm_obj = {
|
|
|
|
|
.base = {
|
|
|
|
|
.type = &nvm_bytearray_type,
|
|
|
|
|
},
|
2021-03-15 09:57:36 -04:00
|
|
|
.start_address = (uint8_t *)CIRCUITPY_INTERNAL_NVM_START_ADDR,
|
2019-10-20 23:50:12 -04:00
|
|
|
.len = CIRCUITPY_INTERNAL_NVM_SIZE,
|
2019-01-30 18:50:07 -05:00
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
|
2020-05-21 01:47:23 -04:00
|
|
|
#if CIRCUITPY_WATCHDOG
|
2020-05-22 00:35:29 -04:00
|
|
|
// The singleton watchdog.WatchDogTimer object.
|
|
|
|
|
watchdog_watchdogtimer_obj_t common_hal_mcu_watchdogtimer_obj = {
|
2020-05-21 01:47:23 -04:00
|
|
|
.base = {
|
2020-05-22 00:35:29 -04:00
|
|
|
.type = &watchdog_watchdogtimer_type,
|
2020-05-21 01:47:23 -04:00
|
|
|
},
|
2020-05-22 00:35:29 -04:00
|
|
|
.timeout = 0.0f,
|
|
|
|
|
.mode = WATCHDOGMODE_NONE,
|
2020-05-21 01:47:23 -04:00
|
|
|
};
|
|
|
|
|
#endif
|
|
|
|
|
|
2018-08-30 21:42:25 -04:00
|
|
|
STATIC const mp_rom_map_elem_t mcu_pin_globals_table[] = {
|
2021-03-15 09:57:36 -04:00
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_00), MP_ROM_PTR(&pin_P0_00) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_01), MP_ROM_PTR(&pin_P0_01) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_02), MP_ROM_PTR(&pin_P0_02) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_03), MP_ROM_PTR(&pin_P0_03) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_04), MP_ROM_PTR(&pin_P0_04) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_05), MP_ROM_PTR(&pin_P0_05) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_06), MP_ROM_PTR(&pin_P0_06) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_07), MP_ROM_PTR(&pin_P0_07) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_08), MP_ROM_PTR(&pin_P0_08) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_09), MP_ROM_PTR(&pin_P0_09) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_10), MP_ROM_PTR(&pin_P0_10) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_11), MP_ROM_PTR(&pin_P0_11) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_12), MP_ROM_PTR(&pin_P0_12) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_13), MP_ROM_PTR(&pin_P0_13) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_14), MP_ROM_PTR(&pin_P0_14) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_15), MP_ROM_PTR(&pin_P0_15) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_16), MP_ROM_PTR(&pin_P0_16) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_17), MP_ROM_PTR(&pin_P0_17) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_18), MP_ROM_PTR(&pin_P0_18) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_19), MP_ROM_PTR(&pin_P0_19) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_20), MP_ROM_PTR(&pin_P0_20) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_21), MP_ROM_PTR(&pin_P0_21) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_22), MP_ROM_PTR(&pin_P0_22) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_23), MP_ROM_PTR(&pin_P0_23) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_24), MP_ROM_PTR(&pin_P0_24) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_25), MP_ROM_PTR(&pin_P0_25) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_26), MP_ROM_PTR(&pin_P0_26) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_27), MP_ROM_PTR(&pin_P0_27) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_28), MP_ROM_PTR(&pin_P0_28) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_29), MP_ROM_PTR(&pin_P0_29) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_30), MP_ROM_PTR(&pin_P0_30) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P0_31), MP_ROM_PTR(&pin_P0_31) },
|
|
|
|
|
#ifdef NRF52840
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_00), MP_ROM_PTR(&pin_P1_00) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_01), MP_ROM_PTR(&pin_P1_01) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_02), MP_ROM_PTR(&pin_P1_02) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_03), MP_ROM_PTR(&pin_P1_03) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_04), MP_ROM_PTR(&pin_P1_04) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_05), MP_ROM_PTR(&pin_P1_05) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_06), MP_ROM_PTR(&pin_P1_06) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_07), MP_ROM_PTR(&pin_P1_07) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_08), MP_ROM_PTR(&pin_P1_08) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_09), MP_ROM_PTR(&pin_P1_09) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_10), MP_ROM_PTR(&pin_P1_10) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_11), MP_ROM_PTR(&pin_P1_11) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_12), MP_ROM_PTR(&pin_P1_12) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_13), MP_ROM_PTR(&pin_P1_13) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_14), MP_ROM_PTR(&pin_P1_14) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_15), MP_ROM_PTR(&pin_P1_15) },
|
|
|
|
|
#endif
|
|
|
|
|
#ifdef NRF52833
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_00), MP_ROM_PTR(&pin_P1_00) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_01), MP_ROM_PTR(&pin_P1_01) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_02), MP_ROM_PTR(&pin_P1_02) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_03), MP_ROM_PTR(&pin_P1_03) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_04), MP_ROM_PTR(&pin_P1_04) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_05), MP_ROM_PTR(&pin_P1_05) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_06), MP_ROM_PTR(&pin_P1_06) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_07), MP_ROM_PTR(&pin_P1_07) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_08), MP_ROM_PTR(&pin_P1_08) },
|
|
|
|
|
{ MP_ROM_QSTR(MP_QSTR_P1_09), MP_ROM_PTR(&pin_P1_09) },
|
|
|
|
|
#endif
|
2018-08-30 21:42:25 -04:00
|
|
|
};
|
|
|
|
|
MP_DEFINE_CONST_DICT(mcu_pin_globals, mcu_pin_globals_table);
|
