text stringlengths 9 39.2M | dir stringlengths 25 226 | lang stringclasses 163 values | created_date timestamp[s] | updated_date timestamp[s] | repo_name stringclasses 751 values | repo_full_name stringclasses 752 values | star int64 1.01k 183k | len_tokens int64 1 18.5M |
|---|---|---|---|---|---|---|---|---|
```restructuredtext
.. _ek_ra2a1:
RA2A1 Evaluation Kit
####################
Overview
********
The EK-RA2A1 is an evaluation kit for Renesas RA2A1 Microcontroller Group.
Renesas RA2A1 Microcontroller Group has following features
- 48MHz, Arm Cortex-M23 core
- 256kB Code Flash, 8kB Data Flash, 32kB SRAM
- USB 2.0 Full-Sppeed
- SCI x 3
- SPI x 2
- I2C x 2
- CAN x 1
- 16-bit A/D Converter
- 24-bit Sigma-Delta A/D Converter
- 12-bit D/A Converter
- 8-bit D/A Converter x 2
- High-Speed Analog Comparator
- Low-Power Analog Comparator
- OPAMP x 3
- Temperature Sensor
- General PWM Timer 32-bit x 1
- General PWM Timer 16-bit x 6
- Low Power Asynchronous General-Purpose Timer x 2
- Watchdog Timer
- 49 Input/Output pins
Hardware
********
EK-RA2A1 has following features.
- Native pin access through 4x 40-pin male headers
- MCU current measurement points
- SEGGER J-Link on-board programmer and debugger
- Two Digilent Pmod (SPI and UART)
- User LED
- Mechanical user button
- Capacitive user button
Supported Features
==================
The Renesas EK-RA2A1 board configuration supports the following
hardware features:
+-----------+------------+-------------------------------+
| Interface | Controller | Driver/components |
+===========+============+===============================+
| PINCTRL | on-chip | pinctrl |
+-----------+------------+-------------------------------+
| CLOCK | on-chip | clock_control |
+-----------+------------+-------------------------------+
| GPIO | on-chip | gpio |
+-----------+------------+-------------------------------+
| UART | on-chip | uart |
+-----------+------------+-------------------------------+
The default configuration can be found in
:zephyr_file:`boards/renesas/ek_ra2a1/ek_ra2a1_defconfig`
Programming and debugging
*************************
Building & Flashing
===================
You can build and flash an application with onboard J-Link debug adapter.
:ref:`build_an_application` and
:ref:`application_run` for more details).
Here is an example for building and flashing the :zephyr:code-sample:`blinky` application.
.. zephyr-app-commands::
:zephyr-app: samples/basic/blinky
:board: ek_ra2a1
:goals: build flash
Debugging
=========
Debugging also can be done with onboard J-Link debug adapter.
The following command is debugging the :zephyr:code-sample:`blinky` application.
Also, see the instructions specific to the debug server that you use.
.. zephyr-app-commands::
:zephyr-app: samples/basic/blinky
:board: ek_ra2a1
:maybe-skip-config:
:goals: debug
References
**********
.. EK-RA2A1 Web site:
path_to_url
``` | /content/code_sandbox/boards/renesas/ek_ra2a1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 699 |
```unknown
/*
*/
&pinctrl {
sci0_default: sci0_default {
group1 {
/* tx rx */
psels = <RA_PSEL(RA_PSEL_SCI_0, 4, 11)>,
<RA_PSEL(RA_PSEL_SCI_0, 4, 10)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m5/ek_ra6m5-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 78 |
```yaml
board:
name: ek_ra6m5
vendor: renesas
socs:
- name: r7fa6m5bh3cfc
``` | /content/code_sandbox/boards/renesas/ek_ra6m5/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra6/r7fa6m5bh3cfc.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "ek_ra6m5-pinctrl.dtsi"
/ {
model = "Renesas EK-RA6M5";
compatible = "renesas,ra6m5", "renesas,ra";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart0;
zephyr,shell-uart = &uart0;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport0 6 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
led2: led2 {
gpios = <&ioport0 7 GPIO_ACTIVE_HIGH>;
label = "LED2";
};
led3: led3 {
gpios = <&ioport0 8 GPIO_ACTIVE_HIGH>;
label = "LED3";
};
};
aliases {
led0 = &led1;
};
};
&sci0 {
pinctrl-0 = <&sci0_default>;
pinctrl-names = "default";
status = "okay";
uart0: uart {
current-speed = <115200>;
status = "okay";
};
};
&ioport0 {
status = "okay";
};
&xtal {
clock-frequency = <DT_FREQ_M(24)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_3>;
mul = <25 0>;
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m5/ek_ra6m5.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 418 |
```cmake
#
#
#
board_runner_args(ezflashcli)
board_runner_args(jlink --device=DA14695)
include(${ZEPHYR_BASE}/boards/common/ezflashcli.board.cmake)
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 58 |
```unknown
# DA14695 Development Kit USB board configuration
config BOARD_DA14695_DK_USB
select SOC_DA14695
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/Kconfig.da14695_dk_usb | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 26 |
```yaml
identifier: da14695_dk_usb
name: DA14695_DK_USB
type: mcu
arch: arm
ram: 512
toolchain:
- zephyr
- gnuarmemb
- xtools
supported:
- arduino_gpio
- gpio
- hwinfo
- watchdog
- i2c
- spi
- usb_device
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/da14695_dk_usb.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 90 |
```yaml
board:
name: da14695_dk_usb
vendor: renesas
socs:
- name: da14695
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 32 |
```restructuredtext
.. _ek_ra6m5:
RA6M5 Evaluation Kit
####################
Overview
********
The Renesas RA6M5 group uses the high-performance Arm Cortex-M33 core with
TrustZone. The RA6M5 is suitable for IoT applications requiring Ethernet, future
proof security, large embedded RAM, and low active power consumption down
to 107uA/MHz running the CoreMark algorithm from Flash.
The key features of the EK-RA6M5 board are categorized in three groups as follow:
**MCU Native Pin Access**
- 200MHz Arm Cortex-M33 based RA6M5 MCU in 176 pins, LQFP package
- Native pin access through 4 x 40-pin male headers
- MCU current measurement points for precision current consumption measurement
- Multiple clock sources - RA6M5 MCU oscillator and sub-clock oscillator crystals,
providing precision 24.000 MHz and 32,768 Hz reference clock.
Additional low precision clocks are avaialbe internal to the RA6M5 MCU
**System Control and Ecosystem Access**
- USB Full Speed Host and Device (micro-AB connector)
- Four 5V input sources
- USB (Debug, Full Speed, High Speed)
- External power supply (using surface mount clamp test points and power input vias)
- Three Debug modes
- Debug on-board (SWD)
- Debug in (ETM, SWD and JTAG)
- Debug out (SWD)
- User LEDs and buttons
- Three User LEDs (red, blue, green)
- Power LED (white) indicating availability of regulated power
- Debug LED (yellow) indicating the debug connection
- Two User buttons
- One Reset button
- Five most popular ecosystems expansions
- Two Seeed Grove system (I2C/Analog) connectors
- One SparkFun Qwiic connector
- Two Digilent Pmod (SPI and UART) connectors
- Arduino (Uno R3) connector
- MikroElektronika mikroBUS connector
- MCU boot configuration jumper
**Special Feature Access**
- Ethernet (RJ45 RMII interface)
- USB High Speed Host and Device (micro-AB connector)
- 32 Mb (256 Mb) External Quad-SPI Flash
- 64 Mb (512 Mb) External Octo-SPI Flash
- CAN (3-pin header)
.. figure:: ek-ra6m5-board.webp
:align: center
:alt: RA6M5 Evaluation Kit
EK-RA6M5 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detailed hardware feature for the RA6M5 MCU group can be found at `RA6M5 Group User's Manual Hardware`_
.. figure:: ra6m5-block-diagram.webp
:width: 442px
:align: center
:alt: RA6M5 MCU group feature
RA6M5 Block diagram (Credit: Renesas Electronics Corporation)
Detailed hardware feature for the EK-RA6M5 MCU can be found at `EK-RA6M5 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA6M5 board:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| CLOCK | on-chip | clock control |
+-----------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra6m5`` board target configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
Flashing
========
Program can be flashed to EK-RA6M5 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA6M5 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA6M5BH
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA6M5 Website`_
- `RA6M5 MCU group Website`_
.. _EK-RA6M5 Website:
path_to_url
.. _RA6M5 MCU group Website:
path_to_url
.. _EK-RA6M5 - User's Manual:
path_to_url
.. _RA6M5 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
``` | /content/code_sandbox/boards/renesas/ek_ra6m5/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,257 |
```unknown
/*
*/
#include <zephyr/dt-bindings/pinctrl/smartbond-pinctrl.h>
&pinctrl {
uart_default: uart_default {
group1 {
pinmux = <SMARTBOND_PINMUX(UART_TX, 0, 9)>;
};
group2 {
pinmux = <SMARTBOND_PINMUX(UART_RX, 0, 8)>;
bias-pull-up;
};
};
uart2_default: uart2_default {
group1 {
pinmux = <SMARTBOND_PINMUX(UART_TX, 0, 17)>;
};
group2 {
pinmux = <SMARTBOND_PINMUX(UART_RX, 1, 8)>;
bias-pull-up;
};
};
uart3_default: uart3_default {
group1 {
pinmux = <SMARTBOND_PINMUX(UART_TX, 0, 29)>;
};
group2 {
pinmux = <SMARTBOND_PINMUX(UART_RX, 0, 28)>;
bias-pull-up;
};
};
i2c_default: i2c_default {
group1 {
pinmux = <SMARTBOND_PINMUX(I2C_SDA, 0, 31)>,
<SMARTBOND_PINMUX(I2C_SCL, 0, 30)>;
bias-pull-up;
};
};
/omit-if-no-ref/ i2c_sleep: i2c_sleep {
group1 {
pinmux = <SMARTBOND_PINMUX(GPIO, 0, 31)>,
<SMARTBOND_PINMUX(GPIO, 0, 30)>;
bias-pull-up;
};
};
i2c2_default: i2c2_default {
group1 {
pinmux = <SMARTBOND_PINMUX(I2C2_SDA, 0, 19)>,
<SMARTBOND_PINMUX(I2C2_SCL, 0, 18)>;
bias-pull-up;
};
};
/omit-if-no-ref/ i2c2_sleep: i2c2_sleep {
group1 {
pinmux = <SMARTBOND_PINMUX(GPIO, 0, 28)>,
<SMARTBOND_PINMUX(GPIO, 0, 29)>;
bias-pull-up;
};
};
/omit-if-no-ref/ spi_sleep: spi_sleep {
group1 {
pinmux = <SMARTBOND_PINMUX(GPIO, 0, 21)>,
<SMARTBOND_PINMUX(GPIO, 0, 24)>,
<SMARTBOND_PINMUX(GPIO, 0, 26)>;
};
};
spi_controller: spi_controller {
group1 {
pinmux = < SMARTBOND_PINMUX(SPI_CLK, 0, 21) >,
<SMARTBOND_PINMUX(SPI_DO, 0, 26)>;
output-enable;
};
group2 {
pinmux = <SMARTBOND_PINMUX(SPI_DI, 0, 24)>;
input-enable;
};
};
/omit-if-no-ref/ spi2_sleep: spi2_sleep {
group1 {
pinmux = <SMARTBOND_PINMUX(GPIO, 1, 3)>,
<SMARTBOND_PINMUX(GPIO, 1, 4)>,
<SMARTBOND_PINMUX(GPIO, 1, 5)>;
};
};
spi2_controller: spi2_controller {
group1 {
pinmux = < SMARTBOND_PINMUX(SPI2_CLK, 1, 3) >,
<SMARTBOND_PINMUX(SPI2_DO, 1, 5)>;
output-enable;
};
group2 {
pinmux = <SMARTBOND_PINMUX(SPI2_DI, 1, 4)>;
input-enable;
};
};
};
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/da14695_dk_usb-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 885 |
```unknown
#
#
#
CONFIG_HW_STACK_PROTECTION=y
CONFIG_GPIO=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_SERIAL=y
CONFIG_BUILD_OUTPUT_HEX=n
CONFIG_I2C=y
CONFIG_I2C_CALLBACK=y
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/da14695_dk_usb_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 47 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/smartbond/da14695.dtsi>
#include "da14695_dk_usb-pinctrl.dtsi"
#include <zephyr/dt-bindings/input/input-event-codes.h>
/ {
model = "DA14695 series Development Kit USB";
compatible = "renesas,da14695_dk_usb";
#address-cells = <1>;
#size-cells = <1>;
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart;
zephyr,shell-uart = &uart;
zephyr,code-partition = &slot0_partition;
};
leds {
compatible = "gpio-leds";
red_led: led_0 {
gpios = <&gpio1 1 GPIO_ACTIVE_HIGH>;
};
};
buttons {
compatible = "gpio-keys";
button0: button_0 {
gpios = <&gpio0 6 (GPIO_PULL_DOWN | GPIO_ACTIVE_HIGH)>;
label = "Push button switch K1";
zephyr,code = <INPUT_KEY_0>;
};
};
mikrobus_header{
mikrobus-connector-1 {
compatible = "mikro-bus";
#gpio-cells = <2>;
gpio-map-mask = <0xffffffff 0xffffffc0>;
gpio-map-pass-thru = <0 0x3f>;
gpio-map = <0 0 &gpio0 25 0>, /* AN */
/* Not a GPIO*/ /* RST */
<2 0 &gpio1 2 0>, /* CS */
<3 0 &gpio1 3 0>, /* SCK */
<4 0 &gpio1 4 0>, /* MISO */
<5 0 &gpio1 5 0>, /* MOSI */
/* +3.3V */
/* GND */
<6 0 &gpio1 6 0>, /* PWM */
<7 0 &gpio1 7 0>, /* INT */
<8 0 &gpio1 8 0>, /* RX */
<9 0 &gpio0 17 0>, /* TX */
<10 0 &gpio0 18 0>, /* SCL */
<11 0 &gpio0 19 0>; /* SDA */
/* +5V */
/* GND */
};
mikrobus-connector-2 {
compatible = "mikro-bus";
#gpio-cells = <2>;
gpio-map-mask = <0xffffffff 0xffffffc0>;
gpio-map-pass-thru = <0 0x3f>;
gpio-map = <0 0 &gpio1 9 0>, /* AN */
/* Not a GPIO*/ /* RST */
<2 0 &gpio0 20 0>, /* CS */
<3 0 &gpio0 21 0>, /* SCK */
<4 0 &gpio0 24 0>, /* MISO */
<5 0 &gpio0 26 0>, /* MOSI */
/* +3.3V */
/* GND */
<6 0 &gpio1 1 0>, /* PWM */
<7 0 &gpio0 27 0>, /* INT */
<8 0 &gpio0 28 0>, /* RX */
<9 0 &gpio0 29 0>, /* TX */
<10 0 &gpio0 30 0>, /* SCL */
<11 0 &gpio0 31 0>; /* SDA */
/* +5V */
/* GND */
};
};
aliases {
led0 = &red_led;
watchdog0 = &wdog;
};
sysclk: system-clock {
compatible = "fixed-clock";
clock-frequency = <32000000>;
#clock-cells = <0>;
};
};
&flash0 {
reg = <0x16000000 DT_SIZE_M(1)>;
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
/*
* Flash area from 0x0000 to 0x2400 is reserved
* for product header added by flasher.
*/
boot_partition: partition@2400 {
label = "mcuboot";
reg = <0x000002400 0x00009c00>;
};
slot0_partition: partition@c000 {
label = "image-0";
reg = <0x0000c000 0x00076000>;
};
slot1_partition: partition@80000 {
label = "image-1";
reg = <0x00082000 0x00076000>;
};
storage_partition: partition@f8000 {
label = "storage";
reg = <0x000f8000 0x00008000>;
};
};
};
&gpio0 {
status = "okay";
};
&gpio1 {
status = "okay";
};
&uart {
current-speed = <115200>;
status = "okay";
pinctrl-0 = <&uart_default>;
pinctrl-names = "default";
};
&uart2 {
current-speed = <115200>;
status = "okay";
pinctrl-0 = <&uart2_default>;
pinctrl-names = "default";
};
&uart3 {
current-speed = <115200>;
status = "okay";
pinctrl-0 = <&uart3_default>;
pinctrl-names = "default";
};
zephyr_udc0: &usbd {
compatible = "renesas,smartbond-usbd";
status = "okay";
};
&rc32m {
status = "disabled";
};
&xtal32m {
status = "okay";
};
&xtal32k {
status = "okay";
};
&lp_clk {
clock-src = <&xtal32k>;
};
&sys_clk {
clock-src = <&xtal32m>;
};
&pll {
status = "okay";
};
&i2c {
status = "okay";
pinctrl-0 = <&i2c_default>;
pinctrl-1 = <&i2c_sleep>;
pinctrl-names = "default", "sleep";
};
&i2c2 {
status = "okay";
pinctrl-0 = <&i2c2_default>;
pinctrl-1 = <&i2c2_sleep>;
pinctrl-names = "default", "sleep";
};
&spi {
status = "okay";
pinctrl-0 = <&spi_controller>;
pinctrl-1 = <&spi_sleep>;
pinctrl-names = "default", "sleep";
};
&spi2 {
status = "okay";
pinctrl-0 = <&spi2_controller>;
pinctrl-1 = <&spi2_sleep>;
pinctrl-names = "default", "sleep";
};
mikrobus_1_i2c: &i2c {};
mikrobus_1_spi: &spi {};
mikrobus_1_uart: &uart2 {};
mikrobus_2_i2c: &i2c2 {};
mikrobus_2_spi: &spi2 {};
mikrobus_2_uart: &uart3 {};
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/da14695_dk_usb.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,712 |
```unknown
config BOARD_RCAR_SALVATOR_X
select SOC_R8A77951_R7
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/Kconfig.rcar_salvator_x | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 22 |
```cmake
board_runner_args(openocd "--use-elf")
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```restructuredtext
.. _da14695_dk_usb:
DA14695 Development Kit USB
###########################
Overview
********
The DA14695 Development Kit USB is a low cost development board for DA14695.
The development kit comes with an integrated debugger and an USB hub
to have both the on-chip USB and the J-Link connected via a single port.
.. figure:: da14695-00hqdevkt-u-usb-board.jpg
:width: 442px
:align: center
:alt: DA14695 Development Kit USB
DA14695 Development Kit USB (Credit: Renesas Electronics Corporation)
Hardware
********
DA14695 Development Kit USB has two external oscillators. The frequency of
the sleep clock is 32768 Hz. The frequency of the system clock is 32 MHz.
Supported Features
==================
The _da14695_dk_usb board configuration supports the following
hardware features:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| FLASH | on-chip | flash |
+-----------+------------+----------------------+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| RTT | Segger | console |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| SPI | on-chip | spi |
+-----------+------------+----------------------+
Other hardware features, including the Configurable MAC (CMAC) controller,
are currently not supported by the port.
For more information about the DA14695 Development Kit see:
- `DA14695 DK USB website`_
System Clock
============
The DA14695 Development Kit USB is configured to use the 32 MHz external oscillator
on the board.
Connections and IOs
===================
The DA14695 Development Kit USB has one LED and one push button which can be used
by applications. The UART is connected to on-board serial converter and accessible
via USB1 port on motherboard.
The pin connections are as follows:
* LED (red), = P1.01
* BUTTON, labeled k1 = P0.06
* UART RX, connected to J-Link serial = P0.08
* UART TX, connected to J-Link serial = P0.09
Programming and Debugging
*************************
Applications for the ``da14695_dk_usb`` board configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
Flashing
========
The DA14695 boots from an external flash connected to QSPI interface. The image
written to flash has to have proper header prepended. The process is simplified
by using dedicated `eZFlashCLI`_ tool that takes care of writing header and can
handle different types of flash chips connected to DA1469x MCU. Follow instructions
on `ezFlashCLI`_ to install the tool. Once installed, flashing can be done in the
usual way.
.. zephyr-app-commands::
:zephyr-app: samples/basic/blinky
:board: da14695_dk_usb
:goals: build flash
Debugging
=========
The DA14695 Development Kit USB includes a `J-Link`_ adaptor built-in
which provides both debugging interface and serial port.
Application can be debugged in the usual way once DA14695 Development Kit USB
is connected to PC via USB.
References
**********
.. target-notes::
.. _DA14695 DK USB website: path_to_url
.. _DA1469x Datasheet: path_to_url
.. _J-Link: path_to_url
.. _ezFlashCLI: path_to_url
``` | /content/code_sandbox/boards/renesas/da14695_dk_usb/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 856 |
```unknown
/*
*
*
*/
/dts-v1/;
#include <arm/renesas/rcar/gen3/r8a77951.dtsi>
#include "rcar_salvator_x_r8a77951_r7-pinctrl.dtsi"
#include <zephyr/dt-bindings/input/input-event-codes.h>
/ {
model = "Renesas h3 Salvator-X board";
compatible = "renesas,h3-salvatorx-cr7";
chosen {
zephyr,sram = &sram0;
zephyr,console = &scif1;
zephyr,shell-uart = &scif1;
zephyr,canbus = &can0;
};
leds {
compatible = "gpio-leds";
user_led_0: led_4 {
gpios = <&gpio6 11 GPIO_ACTIVE_HIGH>;
label = "led4";
};
user_led_1: led_5 {
gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
label = "led5";
};
user_led_2: led_6 {
gpios = <&gpio6 13 GPIO_ACTIVE_HIGH>;
label = "led6";
};
};
gpio_keys {
compatible = "gpio-keys";
user_button_0: sw20 {
gpios = <&gpio6 11 GPIO_ACTIVE_LOW>;
label = "sw20";
zephyr,code = <INPUT_KEY_0>;
};
user_button_1: sw21 {
gpios = <&gpio6 12 GPIO_ACTIVE_LOW>;
label = "sw21";
zephyr,code = <INPUT_KEY_1>;
};
user_button_2: sw22 {
gpios = <&gpio6 13 GPIO_ACTIVE_LOW>;
label = "sw22";
zephyr,code = <INPUT_KEY_2>;
};
};
aliases {
led0 = &user_led_1;
sw0 = &user_button_0;
};
};
&cmt0 {
status = "okay";
clock-frequency = <32000>;
};
&gpio6 {
status = "okay";
};
&can0 {
pinctrl-0 = <&can0_data_a_tx_default &can0_data_a_rx_default>;
pinctrl-names = "default";
status = "okay";
};
&scif1 {
pinctrl-0 = <&scif1_data_a_tx_default &scif1_data_a_rx_default>;
pinctrl-names = "default";
status = "okay";
};
&i2c2 {
status = "okay";
};
&i2c4 {
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/rcar_salvator_x_r8a77951_r7.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 585 |
```unknown
CONFIG_CLOCK_CONTROL=y
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=32000
CONFIG_CONSOLE=y
CONFIG_RAM_CONSOLE=y
CONFIG_FLASH_SIZE=0
CONFIG_FLASH_BASE_ADDRESS=0
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/rcar_salvator_x_r8a77951_r7_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 61 |
```yaml
identifier: rcar_salvator_x/r8a77951/r7
name: Cortex r7 for Renesas H3 Salvator-X
type: mcu
arch: arm
toolchain:
- zephyr
- gnuarmemb
supported:
- i2c
- gpio
- clock_control
- uart
testing:
ignore_tags:
- isotp
vendor: renesas
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/rcar_salvator_x_r8a77951_r7.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 95 |
```yaml
board:
name: rcar_salvator_x
vendor: renesas
socs:
- name: r8a77951
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 34 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/pinctrl/renesas/pinctrl-r8a77951.h>
&pfc {
can0_data_a_tx_default: can0_data_a_tx_default {
pin = <PIN_RD FUNC_CAN0_TX_A>;
};
can0_data_a_rx_default: can0_data_a_rx_default {
pin = <PIN_RD_WR FUNC_CAN0_RX_A>;
};
scif1_data_a_tx_default: scif1_data_a_tx_default {
pin = <PIN_TX1_A FUNC_TX1_A>;
};
scif1_data_a_rx_default: scif1_data_a_rx_default {
pin = <PIN_RX1_A FUNC_RX1_A>;
};
scif2_data_a_tx_default: scif2_data_a_tx_default {
pin = <PIN_TX2_A FUNC_TX2_A>;
};
scif2_data_a_rx_default: scif2_data_a_rx_default {
pin = <PIN_RX2_A FUNC_RX2_A>;
};
};
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/rcar_salvator_x_r8a77951_r7-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 221 |
```ini
# Renesas R-Car Gen3 H3 Salvator-X Cortex-R7 Board Config
source [find interface/ftdi/olimex-arm-usb-ocd-h.cfg]
source [find target/renesas_rcar_reset_common.cfg]
set _CHIPNAME r8a77951
set DAP_TAPID 0x5ba00477
set CA57_0_DBGBASE 0x80410000
set CA57_0_CTIBASE 0x80420000
set CR7_DBGBASE 0x80910000
set CR7_CTIBASE 0x80918000
adapter srst delay 1000
adapter speed 20000
global $_CHIPNAME
transport select jtag
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x01 -irmask 0x0f -expected-id $DAP_TAPID
dap create $_CHIPNAME.dap -chain-position $_CHIPNAME.cpu
cti create $_CHIPNAME.r7.cti -dap $_CHIPNAME.dap -ap-num 1 -baseaddr $CR7_CTIBASE
target create $_CHIPNAME.r7 cortex_r4 -dap $_CHIPNAME.dap -ap-num 1 -dbgbase $CR7_DBGBASE -defer-examine
$_CHIPNAME.r7 configure -rtos auto
cti create $_CHIPNAME.a57.0.cti -dap $_CHIPNAME.dap -ap-num 1 -baseaddr $CA57_0_CTIBASE
target create $_CHIPNAME.a57.0 aarch64 -dap $_CHIPNAME.dap -ap-num 1 -dbgbase $CA57_0_DBGBASE -cti $_CHIPNAME.a57.0.cti
proc reset_cr7 { assert } {
global _CHIPNAME
if { $assert == 1 } {
# Software Reset Register 2 Bit(22) Arm Realtime core
$_CHIPNAME.a57.0 mww 0xe61500b0 0x00400000
} else {
# Software Reset Clearing Register 2 Bit(22) Arm Realtime core
$_CHIPNAME.a57.0 mww 0xe6150948 0x00400000
}
}
# This function make use of A5x processor to:
# - Power on the CR7 (PWRONCR7)
# - Set the boot address (CR7BAR)
# - Halt the processor
# - Deassert the CR7 reset
proc start_cr7 { args } {
global _CHIPNAME
targets $_CHIPNAME.a57.0
$_CHIPNAME.a57.0 arp_halt
# CR7BAR RBAR [31:18] BAREN bit(4)
$_CHIPNAME.a57.0 mww 0xe6160070 0x40040010
# PWRONCR7
$_CHIPNAME.a57.0 mww 0xe618024c 1
# Wait until power is on. Also possible to
# poll PWRSR7 and CR7PSTR register.
sleep 100
$_CHIPNAME.r7 arp_examine
catch { $_CHIPNAME.r7 arp_halt }
reset_cr7 0
# resume a5x processor or cmt timer will not run
resume
# set CR7 processor as default target for future commands
targets $_CHIPNAME.r7
}
$_CHIPNAME.r7 configure -event reset-end {
global _CHIPNAME
targets $_CHIPNAME.a57.0
# Resume the A57 processor and gives
# enough time to A57 bootloaders to set-up dram
# clocks, power management, security groups
resume
sleep 500
$_CHIPNAME.a57.0 arp_halt
$_CHIPNAME.a57.0 arp_poll
start_cr7
}
$_CHIPNAME.a57.0 configure -event examine-end {
start_cr7
}
$_CHIPNAME.r7 configure -event gdb-attach {
reset halt
}
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/support/openocd.cfg | ini | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 879 |
```cmake
board_runner_args(jlink "--device=R7FA6E2BB")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=200000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_CONSOLE=y
CONFIG_CONSOLE=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
CONFIG_CLOCK_CONTROL=y
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/ek_ra6e2_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra6/r7fa6e2bb3cfm.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "ek_ra6e2-pinctrl.dtsi"
/ {
model = "Renesas EK-RA6E2";
compatible = "renesas,ra6e2", "renesas,ra";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart0;
zephyr,shell-uart = &uart0;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport2 7 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
led2: led2 {
gpios = <&ioport4 0 GPIO_ACTIVE_HIGH>;
label = "LED2";
};
led3: led3 {
gpios = <&ioport1 13 GPIO_ACTIVE_HIGH>;
label = "LED3";
};
};
aliases {
led0 = &led1;
};
};
&sci0 {
pinctrl-0 = <&sci0_default>;
pinctrl-names = "default";
status = "okay";
uart0: uart {
current-speed = <115200>;
status = "okay";
};
};
&ioport1 {
status = "okay";
};
&ioport2 {
status = "okay";
};
&ioport4 {
status = "okay";
};
&flash0 {
partitions {
compatible = "fixed-partitions";
#address-cells = <1>;
#size-cells = <1>;
boot_partition: partition@0 {
label = "application";
reg = <0x00000000 DT_SIZE_K(128)>;
};
storage_partition: partition@20000 {
label = "storage";
reg = <0x20000 DT_SIZE_K(128)>;
};
};
};
&xtal {
clock-frequency = <DT_FREQ_M(20)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_1>;
mul = <10 0>;
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/ek_ra6e2.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 547 |
```unknown
/*
*/
&pinctrl {
sci0_default: sci0_default {
group1 {
/* tx rx */
psels = <RA_PSEL(RA_PSEL_SCI_0, 4, 11)>,
<RA_PSEL(RA_PSEL_SCI_0, 4, 10)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/ek_ra6e2-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 78 |
```restructuredtext
.. _rcar_h3_salvatorx_boards:
Renesas R-Car H3 Salvator-X
###########################
Overview
********
- The H3 Salvator-X board is designed for evaluating the features and performance
of the R-CAR H3 device from Renesas Electronics and it is also used for developing
and evaluating application software for these R-CAR H3.
- The H3 Salvator-X, based on the R-CAR H3 SIP, comes with LPDDR4 @4GB in 2-channel,
each 64-bit wide+Hyperflash @64MB, CSI2 interfaces and several communication interfaces
like USB, Ethernet, HDMI and can work standalone or can be adapted to other boards,
via 440pin connector on bottom side.
.. figure:: img/rcar_h3_salvatorx.jpg
:align: center
:alt: R-Car Salvator-X kit
More information about the board can be found at `Renesas R-Car Development Support website`_.
Hardware
********
Hardware capabilities for the H3 Salvator-X for can be found on the `eLinux H3 Salvator-X page`_
of the board.
.. figure:: img/rcar_h3_features.jpg
:align: center
:alt: R-Car Salvator-X features
.. note:: Zephyr will be booted on the CR7 processor provided for RTOS purpose.
More information about the SoC that equips the board can be found here:
- `Renesas R-Car H3 chip`_
Supported Features
==================
Here is the current supported features when running Zephyr Project on the R-Car Salvator-X CR7:
+-----------+------------------------------+--------------------------------+
| Interface | Driver/components | Support level |
+===========+==============================+================================+
| PINCTRL | pinctrl | |
+-----------+------------------------------+--------------------------------+
| CLOCK | clock_control | |
+-----------+------------------------------+--------------------------------+
| GPIO | gpio | |
+-----------+------------------------------+--------------------------------+
| UART | uart | serial port-polling |
+ + + +
| | FT232RQ / CP2102 | serial port-interrupt |
+-----------+------------------------------+--------------------------------+
| CAN | can | normal mode |
+ + + +
| | TCAN332GDCNT | loopback mode |
+-----------+------------------------------+--------------------------------+
| I2C | i2c | interrupt driven |
+-----------+------------------------------+--------------------------------+
It's also currently possible to write on the ram console.
Connections and IOs
===================
.. figure:: img/r-car-h3-salvator-x-connections.jpg
:align: center
:alt: R-Car Salvator-X connections
GPIO
----
By running Zephyr on H3 Salvator-X, the software readable push buttons 'SW20',
'SW21', 'SW22' can be used as input, and the software contollable LEDs 'LED4',
'LED5', 'LED6' can be used as output.
UART
----
Salvator-X board is providing two serial ports:
- one is for A53/A57 processors
- the other one is for CR7
Both ports are converted to USB through CP2102 converters and they are exposed
as follows:
+-----------+-----------+
| Connector | Processor |
+===========+===========+
| CN25 | A53/A57 |
+-----------+-----------+
| CN26 | CR7 |
+-----------+-----------+
Programming and Debugging
*************************
Build and flash applications as usual (see :ref:`build_an_application` and
:ref:`application_run` for more details).
Supported Debug Probe
=====================
The "Olimex ARM-USB-OCD-H" probe is the only officially supported probe. This
probe is supported by OpenOCD that is shipped with the Zephyr SDK.
The "Olimex ARM-USB-OCD-H" probe needs to be connected to CN1 on Salvator-X.
Configuring a Console
=====================
Connect a USB cable from your PC to CN25 and/or CN26 then use the following
settings with your serial terminal of choice (minicom, putty,
etc.):
- Speed: 115200
- Data: 8 bits
- Parity: None
- Stop bits: 1
Flashing
========
First of all, open your serial terminal.
Applications for the ``rcar_salvator_x`` board configuration can be built
in the usual way (see :ref:`build_an_application` for more details).
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: rcar_salvator_x
:goals: flash
You should see the following message in the terminal:
.. code-block:: console
*** Booting Zephyr OS build v2.6.0-rc1 ***
Hello World! rcar_salvator_x
Debugging
=========
First of all, open your serial terminal.
Here is an example for the :ref:`hello_world` application.
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: rcar_salvator_x
:goals: debug
You will then get access to a GDB session for debug.
By continuing the app, you should see the following message in the terminal:
.. code-block:: console
*** Booting Zephyr OS build v2.6.0-rc1 ***
Hello World! rcar_salvator_x
References
**********
- `Renesas R-Car H3 chip`_
- `Renesas R-Car Development Support website`_
- `eLinux H3 Salvator-X page`_
.. _Renesas R-Car H3 chip:
path_to_url
.. _Renesas R-Car Development Support website:
path_to_url
.. _eLinux H3 Salvator-X page:
path_to_url
.. _Install a toolchain:
path_to_url#install-a-toolchain
``` | /content/code_sandbox/boards/renesas/rcar_salvator_x/doc/rcar_salvator_x.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,306 |
```unknown
config BOARD_EK_RA6E2
select SOC_R7FA6E2BB3CFM
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/Kconfig.ek_ra6e2 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 24 |
```yaml
board:
name: ek_ra6e2
vendor: renesas
socs:
- name: r7fa6e2bb3cfm
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```yaml
identifier: ek_ra6e2
name: Renesas EK-RA6E2
type: mcu
arch: arm
ram: 40
flash: 256
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/ek_ra6e2.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 62 |
```unknown
config BOARD_EK_RA6M1
select SOC_R7FA6M1AD3CFP
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/Kconfig.ek_ra6m1 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 24 |
```cmake
board_runner_args(jlink "--device=R7FA6M1AD")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```yaml
identifier: ek_ra6m1
name: Renesas EK-RA6M1
type: mcu
arch: arm
ram: 256
flash: 512
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
- uart
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/ek_ra6m1.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 66 |
```unknown
/*
*/
&pinctrl {
sci8_default: sci8_default {
group1 {
/* tx rx */
psels = <RA_PSEL(RA_PSEL_SCI_8, 1, 5)>,
<RA_PSEL(RA_PSEL_SCI_8, 1, 4)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/ek_ra6m1-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 78 |
```yaml
board:
name: ek_ra6m1
vendor: renesas
socs:
- name: r7fa6m1ad3cfp
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=120000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
CONFIG_CLOCK_CONTROL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_CONSOLE=y
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/ek_ra6m1_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```restructuredtext
.. _ek_ra6e2:
RA6E2 Evaluation Kit
####################
Overview
********
The EK-RA6E2, an Evaluation Kit for RA6E2 MCU Group, enables users to
seamlessly evaluate the features of the RA6E2 MCU group and develop
embedded systems applications using Flexible Software Package (FSP)
and e2 studio IDE. The users can use rich on-board features along with
their choice of popular ecosystems add-ons to bring their big ideas to life
The key features of the EK-RA6E2 board are categorized in three groups as follow:
**MCU Native Pin Access**
- 200MHz Arm Cortex-M33 based RA6E2 MCU in 64 pins, LQFP package
- 256 kB Code Flash, 40 kB SRAM
- Native pin access through 2 x 14-pin and 1 x 40-pin male headers
- MCU current measurement points for precision current consumption measurement
- Multiple clock sources - RA6E2 MCU oscillator and sub-clock oscillator crystals,
providing precision 20.000 MHz and 32,768 Hz reference clock.
Additional low precision clocks are avaialbe internal to the RA6E2 MCU
**System Control and Ecosystem Access**
- USB Full Speed Host and Device (micro-AB connector)
- Three 5V input sources
- USB (Debug, Full Speed)
- External power supply (using surface mount clamp test points and J31 through holes)
- Three Debug modes
- Debug on-board (SWD)
- Debug in (SWD)
- Debug out (JTAG, SWD)
- User LEDs and buttons
- Three User LEDs (red, blue, green)
- Power LED (white) indicating availability of regulated power
- Debug LED (yellow) indicating the debug connection
- Two User buttons
- One Reset button
- Five most popular ecosystems expansions
- Two Seeed Grove system (I3C/Analog) connectors
- One SparkFun Qwiic connector
- Two Digilent Pmod (SPI and UART) connectors
- Arduino (Uno R3) connector
- MikroElektronika mikroBUS connector
- MCU boot configuration jumper
**Special Feature Access**
- 16 Mb (128 Mb) External Quad-SPI Flash
- CAN (3-pin header)
.. figure:: ek-ra6e2-board.webp
:align: center
:alt: RA6E2 Evaluation Kit
EK-RA6E2 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detailed hardware feature for the RA6E2 MCU group can be found at `RA6E2 Group User's Manual Hardware`_
.. figure:: ra6e2-block-diagram.webp
:width: 442px
:align: center
:alt: RA6E2 MCU group feature
RA6E2 Block diagram (Credit: Renesas Electronics Corporation)
Detailed hardware feature for the EK-RA6E2 MCU can be found at `EK-RA6E2 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA6E2 board:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| CLOCK | on-chip | clock control |
+-----------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra6e2`` board target configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
Flashing
========
Program can be flashed to EK-RA6E2 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA6E2 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA6E2BB
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA6E2 Website`_
- `RA6E2 MCU group Website`_
.. _EK-RA6E2 Website:
path_to_url
.. _RA6E2 MCU group Website:
path_to_url
.. _EK-RA6E2 - User's Manual:
path_to_url
.. _RA6E2 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
``` | /content/code_sandbox/boards/renesas/ek_ra6e2/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,249 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra6/r7fa6m1ad3cfp.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "ek_ra6m1-pinctrl.dtsi"
/ {
model = "Renesas EK-RA6M1";
compatible = "renesas,ra6m1", "renesas,ra";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart8;
zephyr,shell-uart = &uart8;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport1 12 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
};
aliases {
led0 = &led1;
};
};
&sci8 {
pinctrl-0 = <&sci8_default>;
pinctrl-names = "default";
status = "okay";
uart8: uart {
current-speed = <115200>;
status = "okay";
};
};
&ioport1 {
status = "okay";
};
&xtal {
clock-frequency = <DT_FREQ_M(20)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_1>;
mul = <20 0>;
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/ek_ra6m1.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 352 |
```yaml
identifier: rcar_h3ulcb/r8a77951/r7
name: Cortex r7 for Renesas H3ULCB
type: mcu
arch: arm
toolchain:
- zephyr
- gnuarmemb
supported:
- i2c
- can
- gpio
- clock_control
- uart
testing:
ignore_tags:
- isotp
vendor: renesas
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_r7.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 98 |
```cmake
if(CONFIG_BOARD_RCAR_H3ULCB_R8A77951_R7)
board_runner_args(openocd "--use-elf")
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
endif()
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 51 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/pinctrl/renesas/pinctrl-r8a77951.h>
&pfc {
can0_data_a_tx_default: can0_data_a_tx_default {
pin = <PIN_RD FUNC_CAN0_TX_A>;
};
can0_data_a_rx_default: can0_data_a_rx_default {
pin = <PIN_RD_WR FUNC_CAN0_RX_A>;
};
scif1_data_a_tx_default: scif1_data_a_tx_default {
pin = <PIN_TX1_A FUNC_TX1_A>;
};
scif1_data_a_rx_default: scif1_data_a_rx_default {
pin = <PIN_RX1_A FUNC_RX1_A>;
};
scif2_data_a_tx_default: scif2_data_a_tx_default {
pin = <PIN_TX2_A FUNC_TX2_A>;
};
scif2_data_a_rx_default: scif2_data_a_rx_default {
pin = <PIN_RX2_A FUNC_RX2_A>;
};
pwm0_default: pwm0_default {
pin = <PIN_PWM0 FUNC_PWM0>;
};
};
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_r7-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 244 |
```restructuredtext
.. _ek_ra6m1:
RA6M1 Evaluation Kit
####################
Overview
********
The Renesas RA6M1 microcontroller is the entry point to the Renesas RA6 product
series for applications that require a high-performance Arm Cortex-M4 core at
a very attractive price point. The RA6M1 is built on a highly efficient 40nm process
and is supported by an open and flexible ecosystem conceptthe Flexible Software
Package (FSP), built on FreeRTOSand is expandable to use other RTOSes and middleware.
The RA6M1 is suitable for IoT applications requiring security, large embedded RAM and
low power consumption.
The key features of the EK-RA6M1 board are categorized in three groups as follow:
**MCU Native Pin Access**
- R7FA6M1AD3CFP
- 100-pin LQFP package
- 120 MHz Arm Cortex-M4 core with Floating Point Unit (FPU)
- 256 KB SRAM
- 512 KB code flash memory
- 8 KB data flash memory
**Connectivity**
- A Device USB connector for the Main MCU
- S124 MCU-based SEGGER J-Link On-Board interface for debugging and programming of the
RA6M1 MCU. A 10-pin JTAG/SWD interface is also provided for connecting optional external
debuggers and programmers.
- Two PMOD connectors, allowing use of appropriate PMOD compliant peripheral plug-in modules for
rapid prototyping
- Pin headers for access to power and signals for the Main MCU
**Multiple clock sources**
- Main MCU oscillator crystals, providing precision 12.000 MHz and 32,768 Hz external reference
clocks
- Additional low-precision clocks are available internal to the Main MCU
**General purpose I/O ports**
- One jumper to allow measuring of Main MCU current
- Copper jumpers on PCB bottom side for configuration and access to selected MCU signals
**Operating voltage**
- External 5 V input through the Debug USB connector supplies the on-board power regulator to power
logic and interfaces on the board. External 5 V or 3.3 V may be also supplied through alternate
locations on the board.
- A two-color board status LED indicating availability of regulated power and connection status of the J-Link
interface.
- A red User LED, controlled by the Main MCU firmware
- A User Push-Button switch, User Capacitive Touch Button sensor, and an optional User Potentiometer,
all of which are controlled by the Main MCU firmware
- MCU reset push-button switch
- MCU boot configuration jumper
**Special Feature Access**
- USB Full Speed Debug and Device (micro-AB connector)
.. figure:: ek-ra6m1-board.webp
:align: center
:alt: RA6M1 Evaluation Kit
EK-RA6M1 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detailed hardware feature for the RA6M1 MCU group can be found at `RA6M1 Group User's Manual Hardware`_
.. figure:: ra6m1-block-diagram.webp
:width: 442px
:align: center
:alt: RA6M1 MCU group feature
RA6M1 Block diagram (Credit: Renesas Electronics Corporation)
Detailed hardware feature for the EK-RA6M1 MCU can be found at `EK-RA6M1 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA6M1 board:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| CLOCK | on-chip | clock control |
+-----------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra6m1`` board target configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
Flashing
========
Program can be flashed to EK-RA6M1 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA6M1 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA6M1AD
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA6M1 Website`_
- `RA6M1 MCU group Website`_
.. _EK-RA6M1 Website:
path_to_url
.. _RA6M1 MCU group Website:
path_to_url
.. _EK-RA6M1 - User's Manual:
path_to_url
.. _RA6M1 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
``` | /content/code_sandbox/boards/renesas/ek_ra6m1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,310 |
```yaml
board:
name: rcar_h3ulcb
vendor: renesas
socs:
- name: r8a77951
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 34 |
```unknown
config BOARD_RCAR_H3ULCB
select SOC_R8A77951_R7 if BOARD_RCAR_H3ULCB_R8A77951_R7
select SOC_R8A77951_A57 if BOARD_RCAR_H3ULCB_R8A77951_A57
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/Kconfig.rcar_h3ulcb | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 61 |
```unknown
/*
*
*
*/
/dts-v1/;
#include <mem.h>
#include <arm64/renesas/r8a77951.dtsi>
#include <zephyr/dt-bindings/gpio/gpio.h>
#include "rcar_h3ulcb_r8a77951_a57-pinctrl.dtsi"
/ {
model = "H3ULCB CA57";
chosen {
zephyr,sram = &ram;
zephyr,console = &scif2;
zephyr,shell-uart = &scif2;
};
ram: memory@48000000 {
device_type = "mmio-sram";
reg = <0x0 0x48000000 0x0 DT_SIZE_M(512)>;
};
/* These aliases are provided for compatibility with samples */
aliases {
sdhc0 = &emmc2;
};
vcc_sd0: regulator-vcc-sd0 {
compatible = "regulator-fixed";
regulator-name = "SD0 Vcc";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
enable-gpios = <&gpio5 2 GPIO_ACTIVE_HIGH>;
};
vccq_sd0: regulator-vccq-sd0 {
compatible = "regulator-gpio";
regulator-name = "SD0 VccQ";
regulator-min-microvolt = <1800000>;
regulator-max-microvolt = <3300000>;
gpios = <&gpio5 1 GPIO_ACTIVE_HIGH>;
states = <3300000 1>, <1800000 0>;
regulator-always-on;
};
};
&gpio5 {
status = "okay";
};
&sd0 {
pinctrl-0 = <&sd0_clk &sd0_cmd &sd0_cd &sd0_wp
&sd0_data0 &sd0_data1 &sd0_data2 &sd0_data3>;
pinctrl-1 = <&sd0_clk_uhs &sd0_cmd_uhs &sd0_cd &sd0_wp
&sd0_data0_uhs &sd0_data1_uhs &sd0_data2_uhs &sd0_data3_uhs>;
pinctrl-names = "default", "uhs";
disk {
compatible = "zephyr,sdmmc-disk";
status = "okay";
};
vmmc-supply = <&vcc_sd0>;
vqmmc-supply = <&vccq_sd0>;
bus-width = <4>;
mmc-sdr104-support;
status = "okay";
};
&scif2 {
pinctrl-0 = <&scif2_data_a_tx_default &scif2_data_a_rx_default>;
pinctrl-names = "default";
status = "okay";
};
&emmc2 {
pinctrl-0 = <&emmc2_clk &emmc2_cmd &emmc2_ds
&emmc2_data0 &emmc2_data1 &emmc2_data2 &emmc2_data3
&emmc2_data4 &emmc2_data5 &emmc2_data6 &emmc2_data7>;
pinctrl-1 = <&emmc2_clk &emmc2_cmd &emmc2_ds
&emmc2_data0 &emmc2_data1 &emmc2_data2 &emmc2_data3
&emmc2_data4 &emmc2_data5 &emmc2_data6 &emmc2_data7>;
pinctrl-names = "default", "uhs";
disk {
compatible = "zephyr,mmc-disk";
status = "disabled";
};
bus-width = <8>;
mmc-hs200-1_8v;
mmc-hs400-1_8v;
non-removable;
};
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_a57.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 841 |
```unknown
CONFIG_CLOCK_CONTROL=y
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=32000
CONFIG_CONSOLE=y
CONFIG_RAM_CONSOLE=y
CONFIG_FLASH_SIZE=0
CONFIG_FLASH_BASE_ADDRESS=0
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_r7_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 61 |
```yaml
identifier: rcar_h3ulcb/r8a77951/a57
name: Renesas H3ULCB based on r8a77951
type: mcu
arch: arm64
toolchain:
- zephyr
- cross-compile
ram: 512
supported:
- clock_control
- uart
testing:
ignore_tags:
- net
- bluetooth
- isotp
vendor: renesas
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_a57.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 100 |
```unknown
# Cache management
CONFIG_CACHE_MANAGEMENT=y
# Enable UART driver
CONFIG_SERIAL=y
CONFIG_AARCH64_IMAGE_HEADER=y
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=8300000
CONFIG_XIP=n
CONFIG_MAX_XLAT_TABLES=24
CONFIG_ARMV8_A_NS=y
# Enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
# Enable clock control
CONFIG_CLOCK_CONTROL=y
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_a57_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 88 |
```unknown
if BOARD_RCAR_H3ULCB
config BUILD_OUTPUT_BIN
default y
endif # BOARD_RCAR_H3ULCB
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/Kconfig.defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 29 |
```unknown
/*
*
*
*/
/dts-v1/;
#include <arm/renesas/rcar/gen3/r8a77951.dtsi>
#include "rcar_h3ulcb_r8a77951_r7-pinctrl.dtsi"
#include <zephyr/dt-bindings/input/input-event-codes.h>
/ {
model = "Renesas h3ulcb board";
compatible = "renesas,h3ulcb-cr7";
chosen {
zephyr,sram = &sram0;
zephyr,console = &scif1;
zephyr,shell-uart = &scif1;
zephyr,canbus = &can0;
};
leds {
compatible = "gpio-leds";
user_led: led_5 {
gpios = <&gpio6 12 GPIO_ACTIVE_HIGH>;
label = "User LED";
};
};
gpio_keys {
compatible = "gpio-keys";
user_button: sw3 {
gpios = <&gpio6 11 GPIO_ACTIVE_LOW>;
label = "User switch";
zephyr,code = <INPUT_KEY_0>;
};
};
aliases {
pwm-0 = &pwm0;
led0 = &user_led;
sw0 = &user_button;
};
};
&cmt0 {
status = "okay";
clock-frequency = <32000>;
};
&gpio6 {
status = "okay";
};
&pwm0 {
pinctrl-0 = <&pwm0_default>;
pinctrl-names = "default";
};
&can0 {
pinctrl-0 = <&can0_data_a_tx_default &can0_data_a_rx_default>;
pinctrl-names = "default";
status = "okay";
can-transceiver {
max-bitrate = <5000000>;
};
};
&scif1 {
pinctrl-0 = <&scif1_data_a_tx_default &scif1_data_a_rx_default>;
pinctrl-names = "default";
status = "okay";
};
&i2c2 {
status = "okay";
};
&i2c4 {
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_r7.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 466 |
```unknown
/*
*
*/
#include <zephyr/dt-bindings/pinctrl/renesas/pinctrl-r8a77951.h>
&pfc {
scif2_data_a_tx_default: scif2_data_a_tx_default {
pin = <PIN_TX2_A FUNC_TX2_A>;
};
scif2_data_a_rx_default: scif2_data_a_rx_default {
pin = <PIN_RX2_A FUNC_RX2_A>;
};
sd0_clk: sd0_clk {
pin = <PIN_SD0_CLK FUNC_SD0_CLK>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_cmd: sd0_cmd {
pin = <PIN_SD0_CMD FUNC_SD0_CMD>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_data0: sd0_data0 {
pin = <PIN_SD0_DATA0 FUNC_SD0_DAT0>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_data1: sd0_data1 {
pin = <PIN_SD0_DATA1 FUNC_SD0_DAT1>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_data2: sd0_data2 {
pin = <PIN_SD0_DATA2 FUNC_SD0_DAT2>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_data3: sd0_data3 {
pin = <PIN_SD0_DATA3 FUNC_SD0_DAT3>;
power-source = <PIN_VOLTAGE_3P3V>;
};
sd0_clk_uhs: sd0_clk_uhs {
pin = <PIN_SD0_CLK FUNC_SD0_CLK>;
power-source = <PIN_VOLTAGE_1P8V>;
};
sd0_cmd_uhs: sd0_cmd_uhs {
pin = <PIN_SD0_CMD FUNC_SD0_CMD>;
power-source = <PIN_VOLTAGE_1P8V>;
};
sd0_data0_uhs: sd0_data0_uhs {
pin = <PIN_SD0_DATA0 FUNC_SD0_DAT0>;
power-source = <PIN_VOLTAGE_1P8V>;
};
sd0_data1_uhs: sd0_data1_uhs {
pin = <PIN_SD0_DATA1 FUNC_SD0_DAT1>;
power-source = <PIN_VOLTAGE_1P8V>;
};
sd0_data2_uhs: sd0_data2_uhs {
pin = <PIN_SD0_DATA2 FUNC_SD0_DAT2>;
power-source = <PIN_VOLTAGE_1P8V>;
};
sd0_data3_uhs: sd0_data3_uhs {
pin = <PIN_SD0_DATA3 FUNC_SD0_DAT3>;
power-source = <PIN_VOLTAGE_1P8V>;
};
/* note: CD pin is fixed at 3.3V */
sd0_cd: sd0_cd {
pin = <PIN_SD0_CD FUNC_SD0_CD>;
power-source = <PIN_VOLTAGE_3P3V>;
};
/* note: WP pin is fixed at 3.3V */
sd0_wp: sd0_wp {
pin = <PIN_SD0_WP FUNC_SD0_WP>;
power-source = <PIN_VOLTAGE_3P3V>;
};
emmc2_clk: emmc2_clk {
pin = <PIN_SD2_CLK FUNC_SD2_CLK>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_cmd: emmc2_cmd {
pin = <PIN_SD2_CMD FUNC_SD2_CMD>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data0: emmc2_data0 {
pin = <PIN_SD2_DATA0 FUNC_SD2_DAT0>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data1: emmc2_data1 {
pin = <PIN_SD2_DATA1 FUNC_SD2_DAT1>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data2: emmc2_data2 {
pin = <PIN_SD2_DATA2 FUNC_SD2_DAT2>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data3: emmc2_data3 {
pin = <PIN_SD2_DATA3 FUNC_SD2_DAT3>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data4: emmc2_data4 {
pin = <PIN_SD1_DATA0 FUNC_SD2_DAT4>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data5: emmc2_data5 {
pin = <PIN_SD1_DATA1 FUNC_SD2_DAT5>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data6: emmc2_data6 {
pin = <PIN_SD1_DATA2 FUNC_SD2_DAT6>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_data7: emmc2_data7 {
pin = <PIN_SD1_DATA3 FUNC_SD2_DAT7>;
power-source = <PIN_VOLTAGE_1P8V>;
};
emmc2_ds: emmc2_ds {
pin = <PIN_SD2_DS FUNC_SD2_DS>;
};
};
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_a57-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,198 |
```restructuredtext
.. _rcar_h3ulcb_ca57:
R-CAR H3 ARM CA57 (ARMv8)
#########################
Overview
********
The R-Car H3 is an SOC that features the basic functions for next-generation
car navigation systems.
Hardware
********
The R-Car H3 includes:
* four 1.5-GHz ARM Cortex-A57 MPCore cores;
* four 1.2-GHz ARM Cortex-A53 MPCore cores;
* memory controller for LPDDR4-3200 with 32 bits x 4 channels;
* 2 channels for HDMI1.4b output and 1channel for RGB888 output and 1channel for LVDS;
* 4 channels MIPI-CSI2 Video Input, 2channels digital Video Input;
* serial ATA interface;
* USB3.0 x 2ch and USB2.0 x 3ch interfaces;
* 800-MHz ARM Cortex-R7 core;
* two- and three-dimensional graphics engines;
* video processing units;
* sound processing units;
* MediaLB interface;
* SD card host interface;
* USB3.0 and USB2.0 interfaces;
* PCI Express interface;
* CAN interface;
* EtherAVB.
Connections and IOs
===================
H3ULCB Board
------------
Here are official IOs figures from eLinux for H3ULCB board:
.. figure:: img/rcar_h3ulcb_top.jpg
:align: center
.. figure:: img/rcar_h3ulcb_bottom.jpg
:align: center
Supported Features
==================
The Renesas rcar_h3ulcb_ca57 board configuration supports the following
hardware features:
+-----------+------------------------------+--------------------------------+
| Interface | Driver/components | Support level |
+===========+==============================+================================+
| PINCTRL | pinctrl | |
+-----------+------------------------------+--------------------------------+
| CLOCK | clock_control | |
+-----------+------------------------------+--------------------------------+
| UART | uart | serial port-polling |
+-----------+------------------------------+--------------------------------+
| MMC | renesas_rcar_mmc | DMA and SCC |
+-----------+------------------------------+--------------------------------+
Other hardware features have not been enabled yet for this board.
The default configuration can be found in
:zephyr_file:`boards/renesas/rcar_h3ulcb/rcar_h3ulcb_r8a77951_a57_defconfig`
Programming and Debugging
*************************
Flashing
========
The flash on board is not supported by Zephyr at this time.
References
**********
- `Renesas R-Car Development Support website`_
- `eLinux R-Car Starter Kit page`_
.. _Renesas R-Car Development Support website:
path_to_url
.. _eLinux R-Car Starter Kit page:
path_to_url
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/doc/rcar_h3ulcb_a57.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 600 |
```unknown
/*
*/
&pinctrl {
sci3_default: sci3_default {
group1 {
/* tx */
psels = <RA_PSEL(RA_PSEL_SCI_3, 3, 10)>;
drive-strength = "medium";
};
group2 {
/* rx */
psels = <RA_PSEL(RA_PSEL_SCI_3, 3, 9)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/mck_ra8t1-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 100 |
```cmake
board_runner_args(jlink "--device=R7FA8T1AH")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
config BOARD_MCK_RA8T1
select SOC_R7FA8T1AHECBD
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/Kconfig.mck_ra8t1 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 23 |
```yaml
identifier: mck_ra8t1
name: Renesas MCK-RA8T1
type: mcu
arch: arm
ram: 1024
flash: 2048
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
- uart
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/mck_ra8t1.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 70 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=480000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_CONSOLE=y
CONFIG_CLOCK_CONTROL=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/mck_ra8t1_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```yaml
board:
name: mck_ra8t1
vendor: renesas
socs:
- name: r7fa8t1ahecbd
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra8/r7fa8t1ahecbd.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "mck_ra8t1-pinctrl.dtsi"
/ {
model = "Renesas MCK-RA8T1";
compatible = "renesas,ra8t1", "renesas,ra8";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart3;
zephyr,shell-uart = &uart3;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioporta 12 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
led2: led2 {
gpios = <&ioporta 14 GPIO_ACTIVE_HIGH>;
label = "LED2";
};
led3: led3 {
gpios = <&ioport6 6 GPIO_ACTIVE_HIGH>;
label = "LED3";
};
led4: led4 {
gpios = <&ioporta 6 GPIO_ACTIVE_HIGH>;
label = "LED4";
};
};
aliases {
led0 = &led1;
};
};
&xtal {
clock-frequency = <DT_FREQ_M(24)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_2>;
mul = <80 0>;
divp = <RA_PLL_DIV_2>;
freqp = <DT_FREQ_M(480)>;
divq = <RA_PLL_DIV_2>;
freqq = <DT_FREQ_M(480)>;
divr = <RA_PLL_DIV_2>;
freqr = <DT_FREQ_M(480)>;
status = "okay";
};
&sciclk {
clk_src = <RA_CLOCK_SOURCE_PLL1P>;
clk_div = <RA_SCI_CLOCK_DIV_4>;
status = "okay";
};
&ioport6 {
status = "okay";
};
&ioporta {
status = "okay";
};
&sci3 {
pinctrl-0 = <&sci3_default>;
pinctrl-names = "default";
status = "okay";
uart3: uart {
current-speed = <115200>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/mck_ra8t1.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 566 |
```restructuredtext
.. _rcar_h3ulcb_boards:
Renesas R-Car H3ULCB
####################
Overview
********
- The H3 Starter Kit board is designed for evaluating the features and performance of the R-CAR H3 device from Renesas Electronics and it is also used for developing and evaluating application software for these R-CAR H3.
- The H3 Starter Kit, based on the R-CAR H3 SIP, comes with LPDDR4 @4GB in 2-channel, each 64-bit wide+Hyperflash @64MB, CSI2 interfaces and several communication interfaces like USB, Ethernet, HDMI and can work standalone or can be adapted to other boards, via 440pin connector on bottom side.
It is possible to order 2 different types of H3 Starter Kit Boards, one with Ethernet connection onboard and one with Ethernet connection on ComExpress.
.. figure:: img/rcar_h3ulcb_starter_kit.jpg
:align: center
:alt: R-Car starter kit
.. note:: The H3ULCB board can be plugged on a Renesas Kingfisher Infotainment daughter board through COM Express connector in order to physically access more I/O. CAUTION: In this case, power supply is managed by the daughter board.
More information about the board can be found at `Renesas R-Car Starter Kit website`_.
Hardware
********
Hardware capabilities for the H3ULCB for can be found on the `eLinux H3SK page`_ of the board.
.. figure:: img/rcar_h3ulcb_features.jpg
:align: center
:alt: R-Car starter kit features
.. note:: Zephyr will be booted on the CR7 processor provided for RTOS purpose.
More information about the SoC that equips the board can be found here:
- `Renesas R-Car H3 chip`_
Supported Features
==================
Here is the current supported features when running Zephyr Project on the R-Car ULCB CR7:
+-----------+------------------------------+--------------------------------+
| Interface | Driver/components | Support level |
+===========+==============================+================================+
| PINMUX | pinmux | |
+-----------+------------------------------+--------------------------------+
| CLOCK | clock_control | |
+-----------+------------------------------+--------------------------------+
| GPIO | gpio | |
+-----------+------------------------------+--------------------------------+
| UART | uart | serial port-polling |
+ + + +
| | FT232RQ / CP2102 | serial port-interrupt |
+-----------+------------------------------+--------------------------------+
| CAN | can | normal mode |
+ + + +
| | TCAN332GDCNT | loopback mode |
+-----------+------------------------------+--------------------------------+
| I2C | i2c | interrupt driven |
+-----------+------------------------------+--------------------------------+
| PWM | pwm | All channels |
+-----------+------------------------------+--------------------------------+
It's also currently possible to write on the ram console.
More features will be supported soon.
Connections and IOs
===================
H3ULCB Board
------------
Here are official IOs figures from eLinux for H3ULCB board:
`H3SK top view`_
`H3SK bottom view`_
Kingfisher Infotainment daughter board
--------------------------------------
When connected to Kingfisher Infotainment board through COMExpress connector, the board is exposing much more IOs.
Here are official IOs figures from eLinux for Kingfisher Infotainment board:
`Kingfisher top view`_
`Kingfisher bottom view`_
GPIO
----
By running Zephyr on H3ULCB, the software readable push button 'SW3' can be used as input, and the software controllable LED 'LED5' can be used as output.
UART
----
H3ULCB board is providing two serial ports, only one is commonly available on the board, however, the second one can be made available either by welding components or by plugging the board on a Kingfisher Infotainment daughter board.
Here is information about these serial ports:
+--------------------+-------------------+--------------------+-----------+--------------------------------------+
| Physical Interface | Physical Location | Software Interface | Converter | Further Information |
+====================+===================+====================+===========+======================================+
| CN12 DEBUG SERIAL | ULCB Board | SCIF2 | FT232RQ | Used by U-BOOT & Linux |
+--------------------+-------------------+--------------------+-----------+--------------------------------------+
| CN10 DEBUG SERIAL | ULCB Board | SCIF1 | CP2102 | Non-welded |
+--------------------+-------------------+--------------------+-----------+--------------------------------------+
| CN04 DEBUG SERIAL | Kingfisher | SCIF1 | | Secondary UART // Through ComExpress |
+--------------------+-------------------+--------------------+-----------+--------------------------------------+
.. note:: The Zephyr console output is assigned to SCIF1 (commonly used on Kingfisher daughter board) with settings 115200 8N1 without hardware flow control by default.
Here is CN04 UART interface pinout (depending on your Kingfisher board version):
+--------+----------+----------+
| Signal | Pin KF03 | Pin KF04 |
+========+==========+==========+
| RXD | 3 | 4 |
+--------+----------+----------+
| TXD | 5 | 2 |
+--------+----------+----------+
| RTS | 4 | 1 |
+--------+----------+----------+
| CTS | 6 | 3 |
+--------+----------+----------+
| GND | 9 | 6 |
+--------+----------+----------+
CAN
---
H3ULCB board provides two CAN interfaces. Both interfaces are available on the Kingfisher daughter board.
+--------------------+--------------------+--------------+
| Physical Interface | Software Interface | Transceiver |
+====================+====================+==============+
| CN17 | CAN0 | TCAN332GDCNT |
+--------------------+--------------------+--------------+
| CN18 | CAN1 | TCAN332GDCNT |
+--------------------+--------------------+--------------+
.. note:: Interfaces are set to 125 kbit/s by default.
The following table lists CAN physical interfaces pinout:
+-----+--------+
| Pin | Signal |
+=====+========+
| 1 | CANH |
+-----+--------+
| 2 | CANL |
+-----+--------+
| 3 | GND |
+-----+--------+
I2C
---
H3ULCB board provides two I2C buses. Unfortunately direct access to these buses is not available through connectors.
I2C is mainly used to manage and power on multiple of onboard chips on the H3ULCB and Kingfisher daughter board.
Embedded I2C devices and I/O expanders are not yet supported. The current I2C support therefore does not make any devices available to the user at this time.
PWM
---
ULCB boards provide one PWM controller with a maximum of 7 channels [0..6]. H3ULCB does provide the pwm0 from test pin CP8 only.
When plugged on a Kingfisher daughter board, pwm4 channel is available on CN7 LVDS connector.
Programming and Debugging
*************************
Build and flash applications as usual (see :ref:`build_an_application` and
:ref:`application_run` for more details).
Supported Debug Probe
=====================
The "Olimex ARM-USB-OCD-H" probe is the only officially supported probe. This probe is supported by OpenOCD that is shipped with the Zephyr SDK.
The "Olimex ARM-USB-OCD-H" probe needs to be connected with a SICA20I2P adapter to CN3 on H3ULCB.
.. note::
See `eLinux Kingfisher page`_ "Known issues" section if you encounter problem with JTAG.
Configuring a Console
=====================
Connect a USB cable from your PC to CN04 of your Kingfisher daughter board.
Use the following settings with your serial terminal of choice (minicom, putty,
etc.):
- Speed: 115200
- Data: 8 bits
- Parity: None
- Stop bits: 1
Flashing
========
First of all, open your serial terminal.
Applications for the ``rcar_h3ulcb/r8a77951/r7`` board configuration can be built in the usual way (see :ref:`build_an_application` for more details).
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: rcar_h3ulcb/r8a77951/r7
:goals: flash
You should see the following message in the terminal:
.. code-block:: console
*** Booting Zephyr OS build v2.6.0-rc1 ***
Hello World! rcar_h3ulcb
Debugging
=========
First of all, open your serial terminal.
Here is an example for the :ref:`hello_world` application.
.. zephyr-app-commands::
:zephyr-app: samples/hello_world
:board: rcar_h3ulcb/r8a77951/r7
:goals: debug
You will then get access to a GDB session for debug.
By continuing the app, you should see the following message in the terminal:
.. code-block:: console
*** Booting Zephyr OS build v2.6.0-rc1 ***
Hello World! rcar_h3ulcb
References
**********
- `Renesas R-Car Starter Kit website`_
- `Renesas R-Car H3 chip`_
- `eLinux H3SK page`_
- `eLinux Kingfisher page`_
.. _Renesas R-Car Starter Kit website:
path_to_url
.. _Renesas R-Car H3 chip:
path_to_url
.. _eLinux H3SK page:
path_to_url
.. _H3SK top view:
path_to_url
.. _H3SK bottom view:
path_to_url
.. _eLinux Kingfisher page:
path_to_url
.. _Kingfisher top view:
path_to_url
.. _Kingfisher bottom view:
path_to_url
.. _Install a toolchain:
path_to_url#install-a-toolchain
``` | /content/code_sandbox/boards/renesas/rcar_h3ulcb/doc/rcar_h3ulcb_r7.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 2,234 |
```unknown
/*
*/
&pinctrl {
sci7_default: sci7_default {
group1 {
/* tx rx */
psels = <RA_PSEL(RA_PSEL_SCI_7, 4, 1)>,
<RA_PSEL(RA_PSEL_SCI_7, 4, 2)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/ek_ra6m2-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 78 |
```cmake
board_runner_args(jlink "--device=R7FA6M2AF")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
config BOARD_EK_RA6M2
select SOC_R7FA6M2AF3CFB
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/Kconfig.ek_ra6m2 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 24 |
```restructuredtext
.. _mcb_ra8t1:
RA8T1 Evaluation Kit
####################
Overview
********
The **MCK-RA8T1** is a development kit that enables easy evaluation of motor control using permanent magnet synchronous
motors (brushless DC motors). More detailed information about the features of this toolkit and it's applications can be
found here: `MCK-RA8T1 Website`_
MCK-RA8T1 kit includes the items below:
- RA8T1 CPU board (`MCB-RA8T1`_)
- Inverter board (`MCI-LV-1`_)
- Communication board (`MC-COM`_)
- Permanent magnet synchronous motors
- Accessories (cables, standoffs, etc.)
.. figure:: mck-ra8t1-product-contents.jpg
:align: center
:alt: RA8T1 Evaluation Kit
MCK-RA8T1 product contents (Credit: Renesas Electronics Corporation)
**MCB-RA8T1** is a CPU board for motor control equipped with RA8T1. Motor control using RA8T1 can be easily realized by
using it in combination with a supported inverter board. The RA8T1 MCU can be evaluated using this board alone.
By using a supported communication board, the CPU board can be electrically isolated from the PC for safe motor control
evaluation and debugging.
The specifications of the CPU board are shown below:
**MCU specifications**
- 480MHz Arm Cortex-M85 based RA8T1 MCU in 224 pins, BGA package
- ROM/RAM size: 2MB/1MB
- MCU input clock: 24MHz (Generate with external crystal oscillator)
- Power supply: DC 5V, select one way automatically from the below:
- Power is supplied from compatible inverter board
- Power is supplied from USB connector
**Connector**
- Inverter board connector (2 pair)
- USB connector for J-Link OB
- USB connector for RA8T1
- SCI connector for Renesas Motor Workbench communication
- Through hole for CAN communication
- 20 pin through hole for Arm debugger
- Pmod connectors (Type6A + Type2A/3A)
- Ethrnet connector
- microSD card connector
.. figure:: ra8t1-cpu-board-block-diagram.jpg
:align: center
:alt: RA8T1 Evaluation Kit
CPU Board Layout (Credit: Renesas Electronics Corporation)
**Onboard debugger**
This product has the onboard debugger circuit, J-Link On-Board (hereinafter called J-Link-OB). You can
write a program (firmware) of RA8T1 with it.
Hardware
********
Detail Hardware feature for the RA8T1 MCU group can be found at `RA8T1 Group User's Manual Hardware`_
.. figure:: ra8t1-block-diagram.png
:width: 442px
:align: center
:alt: RA8T1 MCU group feature
RA8T1 Block diagram (Credit: Renesas Electronics Corporation)
Detail Hardware feature for the MCB-RA8T1 board can be found at `MCB-RA8T1 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for MCB-RA8T1 board:
+--------------+------------+----------------------+
| Interface | Controller | Driver/Component |
+==============+============+======================+
| GPIO | on-chip | gpio |
+--------------+------------+----------------------+
| MPU | on-chip | arch/arm |
+--------------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+--------------+------------+----------------------+
| UART | on-chip | serial |
+--------------+------------+----------------------+
| CLOCK | on-chip | clock control |
+--------------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``mcb_ra8t1`` board configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
**Note:** Only support from SDK v0.16.6 in which GCC for Cortex Arm-M85 was available.
To build for EK-RA8M1 user need to get and install GNU Arm Embedded toolchain from path_to_url
Flashing
========
Program can be flashed to MCB-RA8T1 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `MCB-RA8T1 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA8T1AH
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that debug is OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `MCB-RA8T1 Website`_
- `RA8T1 MCU group Website`_
.. _MCB-RA8T1 Website:
path_to_url
.. _RA8T1 MCU group Website:
path_to_url
.. _MCB-RA8T1 - User's Manual:
path_to_url
.. _RA8T1 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
.. _MCK-RA8T1 Website:
path_to_url
.. _MCB-RA8T1:
path_to_url
.. _MCI-LV-1:
path_to_url
.. _MC-COM:
path_to_url
``` | /content/code_sandbox/boards/renesas/mck_ra8t1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,389 |
```yaml
board:
name: ek_ra6m2
vendor: renesas
socs:
- name: r7fa6m2af3cfb
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```yaml
identifier: ek_ra6m2
name: Renesas EK-RA6M2
type: mcu
arch: arm
ram: 384
flash: 1024
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/ek_ra6m2.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 63 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=120000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
CONFIG_CLOCK_CONTROL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_CONSOLE=y
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/ek_ra6m2_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra6/r7fa6m2af3cfb.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "ek_ra6m2-pinctrl.dtsi"
/ {
model = "Renesas EK-RA6M2";
compatible = "renesas,ra6m2", "renesas,ra";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart7;
zephyr,shell-uart = &uart7;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport1 6 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
};
aliases {
led0 = &led1;
};
};
&sci7 {
pinctrl-0 = <&sci7_default>;
pinctrl-names = "default";
status = "okay";
uart7: uart {
current-speed = <115200>;
status = "okay";
};
};
&ioport1 {
status = "okay";
};
&xtal {
clock-frequency = <DT_FREQ_M(12)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_1>;
mul = <20 0>;
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/ek_ra6m2.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 352 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra8/r7fa8d1bhecbd.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include "ek_ra8d1-pinctrl.dtsi"
/ {
model = "Renesas EK-RA8D1";
compatible = "renesas,ra8d1", "renesas,ra8";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart9;
zephyr,shell-uart = &uart9;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport6 0 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
led2: led2 {
gpios = <&ioport4 14 GPIO_ACTIVE_HIGH>;
label = "LED2";
};
led3: led3 {
gpios = <&ioport1 7 GPIO_ACTIVE_HIGH>;
label = "LED3";
};
};
aliases {
led0 = &led1;
};
};
&xtal {
clock-frequency = <DT_FREQ_M(20)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_2>;
mul = <96 0>;
divp = <RA_PLL_DIV_2>;
freqp = <DT_FREQ_M(480)>;
divq = <RA_PLL_DIV_2>;
freqq = <DT_FREQ_M(480)>;
divr = <RA_PLL_DIV_2>;
freqr = <DT_FREQ_M(480)>;
status = "okay";
};
&sciclk {
clk_src = <RA_CLOCK_SOURCE_PLL1P>;
clk_div = <RA_SCI_CLOCK_DIV_4>;
status = "okay";
};
&ioport1 {
status = "okay";
};
&ioport4 {
status = "okay";
};
&ioport6 {
status = "okay";
};
&sci0 {
/* sci0 and spi0 cannot be enabled together */
pinctrl-0 = <&sci9_default>;
pinctrl-names = "default";
};
&sci9 {
pinctrl-0 = <&sci9_default>;
pinctrl-names = "default";
status = "okay";
uart9: uart {
current-speed = <115200>;
status = "okay";
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/ek_ra8d1.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 579 |
```cmake
board_runner_args(jlink "--device=R7FA8D1BH")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```unknown
/*
*/
&pinctrl {
sci9_default: sci9_default {
group1 {
/* tx */
psels = <RA_PSEL(RA_PSEL_SCI_9, 10, 14)>;
drive-strength = "medium";
};
group2 {
/* rx */
psels = <RA_PSEL(RA_PSEL_SCI_9, 10, 15)>;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/ek_ra8d1-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 100 |
```yaml
identifier: ek_ra8d1
name: Renesas EK-RA8D1
type: mcu
arch: arm
ram: 1024
flash: 2048
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
- uart
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/ek_ra8d1.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 68 |
```yaml
board:
name: ek_ra8d1
vendor: renesas
socs:
- name: r7fa8d1bhecbd
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 37 |
```restructuredtext
.. _ek_ra6m2:
RA6M2 Evaluation Kit
####################
Overview
********
The Renesas RA6M2 microcontroller is the entry point to the Renesas RA6 product series
for applications that require a high-performance Arm Cortex-M4 core at a very attractive
price point. The RA6M2 is suitable for IoT applications requiring security, large embedded
RAM and low power consumption.
The key features of the EK-RA6M2 board are categorized in three groups as follow:
**MCU Native Pin Access**
- 120MHz Arm Cortex-M4 based RA6M2 MCU in 144 pins, LQFP package
- Native pin access through 4 x 40-pin male headers
- MCU and USB current measurement points for precision current consumption measurement
- Multiple clock sources - RA6M2 MCU oscillator and sub-clock oscillator crystals,
providing precision 24.000 MHz and 32,768 Hz reference clock.
Additional low precision clocks are avaialbe internal to the RA6M2 MCU
**System Control and Ecosystem Access**
- USB Full Speed device
- 5V input through USB debug
- Three Debug modes
- Debug on-board (SWD)
- Debug in (SWD and JTAG)
- Debug out (SWD)
- User LEDs and buttons
- One User LEDs
- One User buttons
- One Reset button
- Three most popular ecosystems expansions
- Two Digilent Pmod (SPI and UART) connectors
- Arduino (Uno R3) connector
- MikroElektronika mikroBUS connector
- MCU boot configuration jumper
**Special Feature Access**
- USB Full Speed Host and Device (micro-AB connector)
.. figure:: ek-ra6m2-board.webp
:align: center
:alt: RA6M2 Evaluation Kit
EK-RA6M2 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detailed hardware feature for the RA6M2 MCU group can be found at `RA6M2 Group User's Manual Hardware`_
.. figure:: ra6m2-block-diagram.webp
:width: 871px
:align: center
:alt: RA6M2 MCU group feature
RA6M2 Block diagram (Credit: Renesas Electronics Corporation)
Detailed hardware feature for the EK-RA6M2 MCU can be found at `EK-RA6M2 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA6M2 board:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| CLOCK | on-chip | clock control |
+-----------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra6m2`` board target configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
Flashing
========
Program can be flashed to EK-RA6M2 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA6M2 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA6M2AD
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA6M2 Website`_
- `RA6M2 MCU group Website`_
.. _EK-RA6M2 Website:
path_to_url
.. _RA6M2 MCU group Website:
path_to_url
.. _EK-RA6M2 - User's Manual:
path_to_url
.. _RA6M2 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
``` | /content/code_sandbox/boards/renesas/ek_ra6m2/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,115 |
```unknown
config BOARD_EK_RA8D1
select SOC_R7FA8D1BHECBD
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/Kconfig.ek_ra8d1 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 23 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=480000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_CONSOLE=y
CONFIG_CLOCK_CONTROL=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/ek_ra8d1_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```unknown
/*
*/
/dts-v1/;
#include <renesas/ra/ra8/r7fa8m1ahecbd.dtsi>
#include <dt-bindings/gpio/gpio.h>
#include <zephyr/dt-bindings/adc/adc.h>
#include "ek_ra8m1-pinctrl.dtsi"
/ {
model = "Renesas EK-RA8M1";
compatible = "renesas,ra8m1", "renesas,ra8";
chosen {
zephyr,sram = &sram0;
zephyr,flash = &flash0;
zephyr,console = &uart9;
zephyr,shell-uart = &uart9;
};
leds {
compatible = "gpio-leds";
led1: led1 {
gpios = <&ioport6 0 GPIO_ACTIVE_HIGH>;
label = "LED1";
};
led2: led2 {
gpios = <&ioport4 14 GPIO_ACTIVE_HIGH>;
label = "LED2";
};
led3: led3 {
gpios = <&ioport1 7 GPIO_ACTIVE_HIGH>;
label = "LED3";
};
};
mikrobus_header: mikrobus-connector {
compatible = "mikro-bus";
#gpio-cells = <2>;
gpio-map-mask = <0xffffffff 0xffffffc0>;
gpio-map-pass-thru = <0 0x3f>;
gpio-map = <0 0 &ioport0 4 0>, /* AN */
<1 0 &ioport5 2 0>, /* RST */
<2 0 &ioport4 13 0>, /* CS */
<3 0 &ioport4 12 0>, /* SCK */
<4 0 &ioport4 10 0>, /* MISO */
<5 0 &ioport4 11 0>, /* MOSI */
/* +3.3V */
/* GND */
<6 0 &ioport9 7 0>, /* PWM */
<7 0 &ioport0 10 0>, /* INT */
<8 0 &ioport3 9 0>, /* RX */
<9 0 &ioport3 10 0>, /* TX */
<10 0 &ioport4 0 0>, /* SCL */
<11 0 &ioport4 1 0>; /* SDA */
/* +5V */
/* GND */
};
aliases {
led0 = &led1;
};
};
&xtal {
clock-frequency = <DT_FREQ_M(20)>;
mosel = <0>;
#clock-cells = <0>;
status = "okay";
};
&subclk {
status = "okay";
};
&pll {
source = <RA_PLL_SOURCE_MAIN_OSC>;
div = <RA_PLL_DIV_2>;
mul = <96 0>;
divp = <RA_PLL_DIV_2>;
freqp = <DT_FREQ_M(480)>;
divq = <RA_PLL_DIV_2>;
freqq = <DT_FREQ_M(480)>;
divr = <RA_PLL_DIV_2>;
freqr = <DT_FREQ_M(480)>;
status = "okay";
};
&sciclk {
clk_src = <RA_CLOCK_SOURCE_PLL1P>;
clk_div = <RA_SCI_CLOCK_DIV_4>;
status = "okay";
};
&ioport0 {
status = "okay";
};
&ioport1 {
status = "okay";
};
&ioport3 {
status = "okay";
};
&ioport4 {
status = "okay";
};
&ioport5 {
status = "okay";
};
&ioport6 {
status = "okay";
};
&ioport9 {
status = "okay";
};
&sci3 {
pinctrl-0 = <&sci3_default>;
pinctrl-names = "default";
status = "okay";
uart3: uart {
current-speed = <115200>;
status = "okay";
};
};
&sci9 {
pinctrl-0 = <&sci9_default>;
pinctrl-names = "default";
status = "okay";
uart9: uart {
current-speed = <115200>;
status = "okay";
};
};
mikrobus_serial: &uart3 {};
&iic1 {
#address-cells = <1>;
#size-cells = <0>;
clock-frequency = <DT_FREQ_M(1)>;
pinctrl-0 = <&iic1_default>;
pinctrl-names = "default";
};
&adc0 {
status = "okay";
pinctrl-0 = <&adc0_default>;
pinctrl-names = "default";
};
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/ek_ra8m1.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,087 |
```cmake
board_runner_args(jlink "--device=R7FA8M1AH")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 33 |
```restructuredtext
.. _ek_ra8d1:
RA8D1 Evaluation Kit
####################
Overview
********
The EK-RA8D1 is an Evaluation Kit for Renesas RA8D1 MCU Group which are the industrys first 32-bit
graphics-enabled MCUs based on the Arm Cortex-M85 (CM85) core, delivering breakthrough performance
of over 3000 Coremark points at 480 MHz and superior graphics capabilities that enable high-resolution
displays and Vision AI applications.
The key features of the EK-RA8D1 board are categorized in three groups as follow:
**MCU Native Pin Access**
- 480MHz Arm Cortex-M85 based RA8D1 MCU in 224 pins, BGA package
- Native pin acces througgh 2 x 50-pin, and 2 x 40-pin male headers
- MCU current measurement points for precision current consumption measurement
- Multiple clock sources - RA8D1 MCU oscillator and sub-clock oscillator crystals,
providing precision 20.000MHz and 32,768 Hz refeence clocks.
Additional low precision clocks are avaialbe internal to the RA8D1 MCU
**System Control and Ecosystem Access**
- USB Full Speed Host and Device (micro-AB connector)
- Four 5V input sources
- USB (Debug, Full Speed, High Speed)
- External power supply (using surface mount clamp test points and power input vias)
- Three Debug modes
- Debug on-board (SWD)
- Debug in (ETM, SWD and JTAG)
- Debug out (SWD)
- User LEDs and buttons
- Three User LEDs (red, blue, green)
- Power LED (white) indicating availability of regulated power
- Debug LED (yellow) indicating the debug connection
- Two User buttons
- One Reset button
- Five most popular ecosystems expansions
- Two Seeed Grove system (I2C/I3C) connectors
- One SparkFun Qwiic connector
- Two Digilent Pmod (SPI, UART and I2C/I3C) connectors
- Arduino (Uno R3) connector
- MikroElektronika mikroBUS connector
- MCU boot configuration jumper
**Special Feature Access**
- Ethernet (RJ45 RMII interface)
- USB High Speed Host and Device (micro-AB connector)
- 512 Mb (64 MB) External Octo-SPI Flash (present in the MCU Native Pin Access area of the EK-RA8D1 board)
- CAN FD (3-pin header)
.. figure:: ek-ra8d1-board.jpg
:align: center
:alt: RA8D1 Evaluation Kit
EK-RA8D1 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detail Hardware feature for the RA8D1 MCU group can be found at `RA8D1 Group User's Manual Hardware`_
.. figure:: ra8d1-block-diagram.png
:width: 442px
:align: center
:alt: RA8D1 MCU group feature
RA8D1 Block diagram (Credit: Renesas Electronics Corporation)
Detail Hardware feature for the EK-RA8D1 MCU can be found at `EK-RA8D1 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA8D1 board:
+--------------+------------+------------------+
| Interface | Controller | Driver/Component |
+==============+============+==================+
| GPIO | on-chip | gpio |
+--------------+------------+------------------+
| MPU | on-chip | arch/arm |
+--------------+------------+------------------+
| NVIC | on-chip | arch/arm |
+--------------+------------+------------------+
| UART | on-chip | serial |
+--------------+------------+------------------+
| CLOCK | on-chip | clock control |
+--------------+------------+------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra8d1`` board configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
**Note:** Only support from SDK v0.16.6 in which GCC for Cortex Arm-M85 was available.
To build for EK-RA8M1 user need to get and install GNU Arm Embedded toolchain from path_to_url
Flashing
========
Program can be flashed to EK-RA8D1 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA8D1 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA8D1BH
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that debug is OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA8D1 Website`_
- `RA8D1 MCU group Website`_
.. _EK-RA8D1 Website:
path_to_url
.. _RA8D1 MCU group Website:
path_to_url
.. _EK-RA8D1 - User's Manual:
path_to_url
.. _RA8D1 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
``` | /content/code_sandbox/boards/renesas/ek_ra8d1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,340 |
```yaml
identifier: ek_ra8m1
name: Renesas EK-RA8M1
type: mcu
arch: arm
ram: 1024
flash: 2048
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
- uart
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/ek_ra8m1.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 68 |
```unknown
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=480000000
# Enable GPIO
CONFIG_GPIO=y
CONFIG_PINCTRL=y
# Enable Console
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_CONSOLE=y
CONFIG_BUILD_OUTPUT_HEX=y
CONFIG_BUILD_NO_GAP_FILL=y
CONFIG_CLOCK_CONTROL=y
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/ek_ra8m1_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 71 |
```yaml
board:
name: ek_ra8m1
vendor: renesas
socs:
- name: r7fa8m1ahecbd
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 37 |
```unknown
/*
*/
&pinctrl {
sci3_default: sci3_default {
group1 {
/* tx */
psels = <RA_PSEL(RA_PSEL_SCI_3, 3, 10)>;
drive-strength = "medium";
};
group2 {
/* rx */
psels = <RA_PSEL(RA_PSEL_SCI_3, 3, 9)>;
};
};
sci9_default: sci9_default {
group1 {
/* tx */
psels = <RA_PSEL(RA_PSEL_SCI_9, 10, 14)>;
drive-strength = "medium";
};
group2 {
/* rx */
psels = <RA_PSEL(RA_PSEL_SCI_9, 10, 15)>;
};
};
iic1_default: iic1_default {
group1 {
/* SCL1 SDA1*/
psels = <RA_PSEL(RA_PSEL_I2C, 5, 12)>,<RA_PSEL(RA_PSEL_I2C, 5, 11)>;
drive-strength = "medium";
};
};
adc0_default: adc0_default {
group1 {
/* input */
psels = <RA_PSEL(RA_PSEL_ADC, 0, 4)>;
renesas,analog-enable;
};
};
};
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/ek_ra8m1-pinctrl.dtsi | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 326 |
```unknown
config BOARD_EK_RA8M1
select SOC_R7FA8M1AHECBD
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/Kconfig.ek_ra8m1 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 23 |
```yaml
identifier: rzt2m_starter_kit
name: Renesas RZ/T2M Starter Kit+
type: mcu
arch: arm
ram: 2048
toolchain:
- zephyr
supported:
- counter
- uart
- gpio
vendor: renesas
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/rzt2m_starter_kit.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 70 |
```cmake
#
#
#
board_set_debugger_ifnset(jlink)
board_set_flasher_ifnset(jlink)
board_runner_args(jlink "--device=R9A07G075M2")
include(${ZEPHYR_BASE}/boards/common/jlink.board.cmake)
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 56 |
```unknown
config BOARD_RZT2M_STARTER_KIT
select SOC_RENESAS_RZT2M
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/Kconfig.rzt2m_starter_kit | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 25 |
```unknown
CONFIG_SERIAL=y
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/rzt2m_starter_kit_renesas_rzt2m_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 22 |
```unknown
/*
*
*/
/dts-v1/;
#include <dt-bindings/pinctrl/renesas-rzt2m-pinctrl.h>
#include <arm/renesas/rz/rzt2m.dtsi>
/ {
model = "RZT/2M Starter Kit";
compatible = "renesas,rzt2m_starter_kit";
chosen {
zephyr,sram = &cpu0_atcm;
zephyr,console = &uart0;
zephyr,shell-uart = &uart0;
};
aliases {
led0 = &led0;
sw0 = &sw1;
};
leds {
compatible = "gpio-leds";
led0: led0 {
gpios = <&gpio19 6 0>;
label = "led0";
};
led1: led1 {
gpios = <&gpio19 4 0>;
label = "led1";
};
led2: led2 {
gpios = <&gpio20 0 0>;
label = "led2";
};
led3: led3 {
gpios = <&gpio23 4 0>;
label = "led3";
};
};
gpio_keys {
compatible = "gpio-keys";
sw1: sw1 {
label = "sw1";
gpios = <&gpio10 5 0>;
};
sw2: sw2 {
label = "sw2";
gpios = <&gpio16 3 0>;
};
};
};
&pinctrl {
uart0_default: uart0_default {
group1 {
pinmux = <UART0TX_P16_5>;
};
group2 {
pinmux = <UART0RX_P16_6>;
input-enable;
};
};
uart3_default: uart3_default {
group1 {
pinmux = <UART3TX_P18_0>;
};
group2 {
pinmux = <UART3RX_P17_7>;
input-enable;
};
};
};
&uart0 {
status = "okay";
pinctrl-0 = <&uart0_default>;
pinctrl-names = "default";
};
&uart3 {
status = "okay";
pinctrl-0 = <&uart3_default>;
pinctrl-names = "default";
};
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/rzt2m_starter_kit_renesas_rzt2m.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 533 |
```yaml
board:
name: rzt2m_starter_kit
vendor: renesas
socs:
- name: renesas_rzt2m
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 38 |
```restructuredtext
.. _ek_ra8m1:
RA8M1 Evaluation Kit
####################
Overview
********
The EK-RA8M1 is an Evaluation Kit for Renesas RA8M1 MCU Group which is the first
32-bits MCUs based on new Arm Cortex-M85. The kit offer multiple external interface
and peripherals set optimized on board allows user to seamlessly evaluate the features
of the RA8M1 MCU and develop embedded system application in various field.
The key features of the EK-RA8M1 board are categorized in three groups as follow:
**MCU Native Pin Access**
- 480MHz Arm Cortex-M85 based RA8M1 MCU in 224 pins, BGA package
- Native pin acces througgh 2 x 50-pin, and 2 x 40-pin male headers
- MCU current measurement points for precision current consumption measurement
- Multiple clock sources - RA8M1 MCU oscillator and sub-clock oscillator crystals,
providing precision 20.000MHz and 32,768 Hz refeence clocks.
Additional low precision clocks are avaialbe internal to the RA8M1 MCU
**System Control and Ecosystem Access**
- USB Full Speed Host and Device (micro-AB connector)
- Four 5V input sources
- USB (Debug, Full Speed, High Speed)
- External power supply (using surface mount clamp test points and power input vias)
- Three Debug modes
- Debug on-board (SWD)
- Debug in (ETM, SWD and JTAG)
- Debug out (SWD)
- User LEDs and buttons
- Three User LEDs (red, blue, green)
- Power LED (white) indicating availability of regulated power
- Debug LED (yellow) indicating the debug connection
- Two User buttons
- One Reset button
- Five most popular ecosystems expansions
- Two Seeed Grove system (I2C/I3C) connectors
- One SparkFun Qwiic connector
- Two Digilent Pmod (SPI, UART and I2C/I3C) connectors
- Arduino (Uno R3) connector
- MikroElektronika mikroBUS connector
- MCU boot configuration jumper
**Special Feature Access**
- Ethernet (RJ45 RMII interface)
- USB High Speed Host and Device (micro-AB connector)
- 512 Mb (64 MB) External Octo-SPI Flash (present in the MCU Native Pin Access area of the EK-RA8M1 board)
- CAN FD (3-pin header)
.. figure:: ek-ra8m1-board.jpg
:align: center
:alt: RA8M1 Evaluation Kit
EK-RA8M1 Board Functional Area Definitions (Credit: Renesas Electronics Corporation)
Hardware
********
Detail Hardware feature for the RA8M1 MCU group can be found at `RA8M1 Group User's Manual Hardware`_
.. figure:: ra8m1-block-diagram.jpg
:width: 442px
:align: center
:alt: RA8M1 MCU group feature
RA8M1 Block diagram (Credit: Renesas Electronics Corporation)
Detail Hardware feature for the EK-RA8M1 MCU can be found at `EK-RA8M1 - User's Manual`_
Supported Features
==================
The below features are currently supported on Zephyr OS for EK-RA8M1 board:
+-----------+------------+----------------------+
| Interface | Controller | Driver/Component |
+===========+============+======================+
| GPIO | on-chip | gpio |
+-----------+------------+----------------------+
| MPU | on-chip | arch/arm |
+-----------+------------+----------------------+
| NVIC | on-chip | arch/arm |
+-----------+------------+----------------------+
| UART | on-chip | serial |
+-----------+------------+----------------------+
| CLOCK | on-chip | clock control |
+-----------+------------+----------------------+
| I2C | on-chip | i2c |
+-----------+------------+----------------------+
Other hardware features are currently not supported by the port.
Programming and Debugging
*************************
Applications for the ``ek_ra8m1`` board configuration can be
built, flashed, and debugged in the usual way. See
:ref:`build_an_application` and :ref:`application_run` for more details on
building and running.
**Note:** Only support from SDK v0.16.6 in which GCC for Cortex Arm-M85 was available.
To build for EK-RA8M1 user need to get and install GNU Arm Embedded toolchain from path_to_url
Flashing
========
Program can be flashed to EK-RA8M1 via the on-board SEGGER J-Link debugger.
SEGGER J-link's drivers are avaialbe at path_to_url
To flash the program to board
1. Connect to J-Link OB via USB port to host PC
2. Make sure J-Link OB jumper is in default configuration as describe in `EK-RA8M1 - User's Manual`_
3. Execute west command
.. code-block:: console
west flash -r jlink
Debugging
=========
You can use Segger Ozone (`Segger Ozone Download`_) for a visual debug interface
Once downloaded and installed, open Segger Ozone and configure the debug project
like so:
* Target Device: R7FA8M1AH
* Target Interface: SWD
* Target Interface Speed: 4 MHz
* Host Interface: USB
* Program File: <path/to/your/build/zephyr.elf>
**Note:** It's verified that we can debug OK on Segger Ozone v3.30d so please use this or later
version of Segger Ozone
References
**********
- `EK-RA8M1 Website`_
- `RA8M1 MCU group Website`_
.. _EK-RA8M1 Website:
path_to_url
.. _RA8M1 MCU group Website:
path_to_url
.. _EK-RA8M1 - User's Manual:
path_to_url
.. _RA8M1 Group User's Manual Hardware:
path_to_url
.. _Segger Ozone Download:
path_to_url#Ozone
.. _zephyr-sdk-0.16.5-6-ge895c4e_linux-x86_64:
path_to_url
``` | /content/code_sandbox/boards/renesas/ek_ra8m1/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 1,391 |
```unknown
# Cache management
CONFIG_CACHE_MANAGEMENT=y
# Enable UART driver
CONFIG_SERIAL=y
# Enable console
CONFIG_CONSOLE=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
# Enable clock control
CONFIG_CLOCK_CONTROL=y
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=16666666
CONFIG_AARCH64_IMAGE_HEADER=y
CONFIG_XIP=n
CONFIG_MAX_XLAT_TABLES=24
CONFIG_ARMV8_A_NS=y
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_a55_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 94 |
```cmake
if(CONFIG_BOARD_RCAR_SPIDER_S4_R8A779F0_R52)
board_runner_args(openocd "--use-elf")
include(${ZEPHYR_BASE}/boards/common/openocd.board.cmake)
endif()
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/board.cmake | cmake | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 51 |
```restructuredtext
.. _rzt2m_starterkit:
Renesas Starter Kit+ for RZ/T2M
###############################
Overview
********
The Renesas Starter Kit+ for RZ/T2M is an evaluation and development kit for the RZ/T2M MPU.
The board is powered through a 5V input via a DC Power Jack or USB Type-C Connector.
.. figure:: rzt2m_starterkit.png
:width: 800px
:align: center
:alt: Starter Kit+ for RZ/T2M
Starter Kit+ for RZ/T2M (Credit: Renesas)
Hardware
********
The board utilizes the SoC of part no. R9A07G075M24GBG, with 2MB of RAM.
It has several on-board memory components:
* SDRAM (256MBit),
* NOR Flash (256MBit),
* Octa Flash (512MBit),
* HyperRAM (512Mbit),
* QSPI Serial Flash (512Mbit),
* I2C EEPROM (32Kbit).
The communication interfaces include:
* Debug interfaces (J-Link, MIPI-10, MIPI-20),
* Ethernet,
* CAN,
* USB,
* RS485,
* UART,
* I2C,
* SPI.
Supported Features
==================
+-----------+------------+-------------------------------------+
| Interface | Controller | Driver/Component |
+===========+============+=====================================+
| NVIC | on-chip | nested vector interrupt controller |
+-----------+------------+-------------------------------------+
| SYSTICK | on-chip | systick |
+-----------+------------+-------------------------------------+
| PINCTRL | on-chip | pinctrl |
+-----------+------------+-------------------------------------+
| UART | on-chip | serial |
+-----------+------------+-------------------------------------+
| GPIO | on-chip | gpio |
+-----------+------------+-------------------------------------+
Other hardware features are not currently supported by the port.
Connections and IOs
===================
By default, the board is configured for use with:
* UART0 connected to the USB serial port (pins K18, K19),
* UART3 connected to the PMOD Header (J25, pins H16, G20),
* LEDs defined as `led0`, `led1`, `led2` and `led3`,
The Zephyr console uses UART0.
Programming and Debugging
*************************
Debugging
=========
Connect to the board using the J-Link On-board USB connector.
Use `west` to start the debug server:
.. code-block:: console
west debugserver
Connect GDB to the server and load an application:
.. code-block::
target remote :2331
file build/zephyr/zephyr.elf
load
References
**********
.. _RZT2M Product page: path_to_url
``` | /content/code_sandbox/boards/renesas/rzt2m_starterkit/doc/index.rst | restructuredtext | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 617 |
```unknown
CONFIG_CLOCK_CONTROL=y
CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=12500000
CONFIG_CONSOLE=y
CONFIG_RAM_CONSOLE=y
CONFIG_FLASH_SIZE=0
CONFIG_FLASH_BASE_ADDRESS=0
CONFIG_SERIAL=y
CONFIG_UART_CONSOLE=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_GPIO=y
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_r52_defconfig | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 62 |
```unknown
config BOARD_RCAR_SPIDER_S4
select SOC_R8A779F0_R52 if BOARD_RCAR_SPIDER_S4_R8A779F0_R52
select SOC_R8A779F0_A55 if BOARD_RCAR_SPIDER_S4_R8A779F0_A55
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/Kconfig.rcar_spider_s4 | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 65 |
```unknown
/*
*
*
*/
/dts-v1/;
#include <arm/renesas/rcar/gen4/r8a779f0.dtsi>
#include "rcar_spider_s4_r8a779f0_r52-pinctrl.dtsi"
#include <zephyr/dt-bindings/input/input-event-codes.h>
/ {
model = "Renesas Spider board";
compatible = "renesas,spider-s4-cr52";
chosen {
zephyr,sram = &sram0;
zephyr,console = &scif0;
zephyr,shell-uart = &scif0;
};
leds {
compatible = "gpio-leds";
user_led: led_8 {
gpios = <&gpio0 14 GPIO_ACTIVE_HIGH>;
label = "User LED";
};
};
gpio_keys {
compatible = "gpio-keys";
user_button: sw10 {
gpios = <&gpio4 13 GPIO_ACTIVE_LOW>;
label = "User switch";
zephyr,code = <INPUT_KEY_0>;
};
};
aliases {
led0 = &user_led;
sw0 = &user_button;
};
};
&scif0 {
pinctrl-0 = <&scif0_data_tx_default &scif0_data_rx_default>;
pinctrl-names = "default";
status = "okay";
};
&gpio0 {
status = "okay";
};
&gpio4 {
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_r52.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 328 |
```yaml
board:
name: rcar_spider_s4
vendor: renesas
socs:
- name: r8a779f0
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/board.yml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 35 |
```unknown
/*
*
*
*/
/dts-v1/;
#include <mem.h>
#include <arm64/renesas/r8a779f0.dtsi>
#include "rcar_spider_s4_r8a779f0_a55-pinctrl.dtsi"
/ {
model = "Renesas Spider CA55";
chosen {
zephyr,sram = &ram;
zephyr,console = &hscif0;
zephyr,shell-uart = &hscif0;
};
ram: memory@48000000 {
device_type = "mmio-sram";
reg = <0x0 0x48000000 0x0 DT_SIZE_M(512)>;
};
};
&hscif0 {
pinctrl-0 = <&hscif0_data_tx_default &hscif0_data_rx_default>;
pinctrl-names = "default";
current-speed = <1843200>;
status = "okay";
};
&mmc0 {
pinctrl-0 = <&mmc_clk &mmc_cmd &mmc_ds
&mmc_data0 &mmc_data1 &mmc_data2 &mmc_data3
&mmc_data4 &mmc_data5 &mmc_data6 &mmc_data7>;
pinctrl-1 = <&mmc_clk &mmc_cmd &mmc_ds
&mmc_data0 &mmc_data1 &mmc_data2 &mmc_data3
&mmc_data4 &mmc_data5 &mmc_data6 &mmc_data7>;
pinctrl-names = "default", "uhs";
disk {
compatible = "zephyr,mmc-disk";
status = "okay";
};
bus-width = <8>;
mmc-hs200-1_8v;
mmc-hs400-1_8v;
non-removable;
status = "okay";
};
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_a55.dts | unknown | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 399 |
```yaml
identifier: rcar_spider_s4/r8a779f0/r52
name: Cortex r52 for Renesas Spider
type: mcu
arch: arm
toolchain:
- zephyr
- gnuarmemb
supported:
- gpio
- clock_control
- uart
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_r52.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 69 |
```yaml
identifier: rcar_spider_s4/r8a779f0/a55
name: Cortex A55 for Renesas Spider
type: mcu
arch: arm64
toolchain:
- zephyr
- cross-compile
supported:
- pinctrl
- gpio
- clock_control
- uart
``` | /content/code_sandbox/boards/renesas/rcar_spider_s4/rcar_spider_s4_r8a779f0_a55.yaml | yaml | 2016-05-26T17:54:19 | 2024-08-16T18:09:06 | zephyr | zephyrproject-rtos/zephyr | 10,307 | 75 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.