de1f1dd164
Before, both uwTick and mp_hal_ticks_ms() were used as clock source. That assumes, that these two are synchronous and start with the same value, which may be not the case for all ports. If the lag between uwTick and mp_hal_ticks_ms() is larger than the timer interval, the timer would either rush up until the times are synchronous, or not start until uwTick wraps over. As suggested by @dpgeorge, MICROPY_SOFT_TIMER_TICKS_MS is now used in softtimer.c, which has to be defined in a port's mpconfigport.h with the variable that holds the SysTick counter. Note that it's not possible to switch everything in softtimer.c to use mp_hal_ticks_ms() because the logic in SysTick_Handler that schedules soft_timer_handler() uses (eg on mimxrt) the uwTick variable directly (named systick_ms there), and mp_hal_ticks_ms() uses a different source timer. Thus it is made fully configurable. |
||
---|---|---|
.. | ||
boards | ||
ra | ||
boardctrl.c | ||
boardctrl.h | ||
build_all_boards.sh | ||
extint.c | ||
extint.h | ||
factoryreset.c | ||
factoryreset.h | ||
fatfs_port.c | ||
flash.c | ||
flash.h | ||
flashbdev.c | ||
gccollect.c | ||
gccollect.h | ||
help.c | ||
irq.c | ||
irq.h | ||
led.c | ||
led.h | ||
machine_adc.c | ||
machine_i2c.c | ||
machine_pin.c | ||
machine_rtc.c | ||
machine_spi.c | ||
machine_uart.c | ||
main.c | ||
Makefile | ||
modmachine.c | ||
modmachine.h | ||
moduos.c | ||
modutime.c | ||
mpconfigboard_common.h | ||
mpconfigport.h | ||
mpconfigport.mk | ||
mphalport.c | ||
mphalport.h | ||
mpthreadport.c | ||
mpthreadport.h | ||
pendsv.c | ||
pendsv.h | ||
pin.h | ||
powerctrl.c | ||
powerctrl.h | ||
powerctrlboot.c | ||
pybthread.c | ||
pybthread.h | ||
qstrdefsport.h | ||
RA4M1_hal.h | ||
RA4W1_hal.h | ||
RA6M1_hal.h | ||
RA6M2_hal.h | ||
ra_it.c | ||
ra_it.h | ||
README.md | ||
rtc.h | ||
spi.h | ||
storage.c | ||
storage.h | ||
systick.c | ||
systick.h | ||
timer.c | ||
timer.h | ||
uart.c | ||
uart.h | ||
usrsw.c | ||
usrsw.h |
The Renesas RA port
This is a port of MicroPython to the Renesas RA family of microcontrollers. Currently supported features are:
- Filesystem on the internal flash using FatFs.
utime
module with sleep, time, and ticks functions.uos
module with VFS support.machine
module with the following classes:Pin
,ADC
,I2C
,SPI
,SoftI2C
,SoftSPI
,UART
,RTC
- sdcard driver if frozen driver is installed.
Currently supported board product names are:
- EK-RA6M2
- RA4M1 CLICKER
- EK-RA6M1
- EK-RA4M1
- EK-RA4W1
Please refer to the quick reference of renesas-ra
port for more
information about the boards.
Build instructions
-
MicroPython cross-compier The MicroPython cross-compiler must be built first, which will be used to pre-compile (freeze) built-in Python code. THis cross-compiler is built and run on the host machine, using:
$ make -C mpy-cross
This command should be executed from the root directory of this repository. All other commands below should be executed from the ports/renesas-ra/ directory.
-
Arm compiler An
Arm compiler
is required for the build, along with the associated binary utilities. The default compiler isarm-none-eabi-gcc
, which is available for Linux, Mac and Windows hosts via https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads. The compiler can be changed using theCROSS_COMPILE
variable when invokingmake
. -
Obtain submodules First the submodules must be obtained using:
$ make submodules
-
Build binary image
.hex
Then to build for a given board subdirectory name, run:$ make BOARD=RA6M2_EK clean $ make BOARD=RA6M2_EK
The default board subdirectory name is RA6M2_EK (which is for EK-RA6M2 board) but any of the names of the subdirectories in the
boards/
directory can be passed as the argument toBOARD=
; for exampleRA4M1_CLICKER
,RA4M1_EK
,RA4W1_EK
andRA6M1_EK
. The above command should produce binary imagesfirmware.hex
in the build-RA6M2_EK/` subdirectory (or the equivalent directory for the board specified).
Supported/Unsupprted funtions
Please refer to the renesas-ra
quick reference.
Known issues
all boards
-
machine.lightsleep(time_ms) and machine.deepsleep(time_ms) raise uncaught exceptions.
machine.deepsleep(1000) Uncaught exception in ExtInt interrupt handler line 16 TypeError:
RA4M1-CLICKER
- mpremote: mount command is not available due to limited memory resources.
EK-RA4M1
- mpremote: mount command is not available due to limited memory resources.
EK-RA4W1
- mpremote: "Execution: timeout waiting for remote" error happens when importing a file on /remote.