This topic provides board-specific information about Renesas' EK-RA6M3G.

Board features

• R7FA6M3AH3CFC MCU featuring ARM® Cortex®-M4, 2 MB Flash, 640 KB RAM
• 4.3” 480x272 LCD Touch Display
• 32 MB External QSPI Flash

Supported color depths

The reference port for this board supports 16bpp color depth. The board also supports 24bpp and 32bpp, but they are not implemented in the reference port. See QUL_COLOR_DEPTH and Color depth for more information.

Configure the operating mode

Select an operating mode for the MCU using the J16 jumper on the board, depending on the software used with the MCU.

See Renesas RA6M3 Group - User’s Manual: Hardware for the details.

Flashing the firmware

Select an appropriate boot mode for the MCU before flashing the firmware using one of the tools listed below.

Prebuilt demos and examples

The Qt for MCUs package for EK-RA6M3G board comes with a prebuilt thermo demo binary. You can find it in the demos_images directory.

Building applications with prebuilt Qt Quick Ultralite libraries

Open the CMake project file for the example you want to build and configure it with the kit you created earlier. Once the project is configured, select Run or press Ctrl+r on your keyboard to build and flash the binary to the target.

Reading debug messages

By default, log data is redirected to UART on the Serial Communications Interface channel 0 (SCI0).

Port settings

Debugging

Renesas e² studio

Renesas e² studio lets you debug a project using a custom configuration.

• Open Run from the top menu
• Select Debug Configurations...
• Select Renesas GDB Hardware Debugging
• Click Browse... from the C/C++ Application: and select .elf file to be debugged
• Click Apply and Close
• Click Launch in 'Debug' mode

SEGGER J-Link GDB Server

Use SEGGER J-Link GDB Server to create GDB server.

This page uses QUL_ROOT and QUL_TOOLS in command line examples as if they were set as environment variables. For example:

export QUL_ROOT=$HOME/Qt/QtMCUs/2.5.4
export QUL_TOOLS=$HOME/Qt/Tools/QtMCUs

set QUL_ROOT=C:\Qt\QtMCUs\2.5.4
set QUL_TOOLS=C:\Qt\Tools\QtMCUs

• Select Connection to J-Link as USB
• Select Target device as R7FA6M3AH
• Select Target interface as SWD
• Select Speed as Fixed 4000 kHz
• Click OK

  GDB Server is now listening for TCP connections on the default port, 2331.

• Run arm-none-eabi-gdb in a separate console LinuxWindows

  $QUL_TOOLS/arm_gcc_10/bin/arm-none-eabi-gdb <PATH_TO>/your_app.elf

  %QUL_TOOLS%\arm_gcc_10\bin\arm-none-eabi-gdb.exe <PATH_TO>\your_app.elf

• Connect to the target via the gdbserver in the arm-none-eabi-gdb console using

  Note: Actual TCP port used is printed out on gdbserver's console.

  (gdb) target remote 127.0.0.1:2331

Notes

• Excludes demos, examples, and tests that do not fit into the flash memory or require more RAM than available on the MCU.
• Set stack region to overlap with the heap region in the default platform adaptation, to enable building tests and demos, which have different stack and heap requirements.
• Define size for the stack and heap to ensure that the Memory Protection Unit detects stack overflow and underflow.
• Image and font data are stored into the MCU's internal flash memory by default. The larger Qt Quick Ultralite demos do not fit into internal flash memory for release or debug builds. In that case, sections QulResourceDataExtFlash and QulFontResourceDataExtFlash can be used to move image or font data into the external flash memory. For reference, see ImageFiles.MCU.resourceStorageSection, MCU.Config.fontFilesStorageSection, and MCU.Config.glyphsStorageSection.

Default FSP Configuration in Renesas e² studio

BSP

Notes:

• The values listed earlier are relevant for initial testing only, as the stack and heap sizes are application-specific.
• On default platform adaptation, these values do not have any effect as custom implementation allows the stack region to overlap with the heap region.
• Use the startup.c and system.c files from the e² Studio project to set the stack and heap size. You can find these system files in the ra/fsp/src/bsp/cmsis/Device/RENESAS/Source directory.
• Use the script/fsp.ld linker script generated by e² Studio as a reference to set stack and heap regions properly.

Stacks

Add the following stacks and configure them:

Analog > ADC (r_adc)

Connectivity > I2C Master (r_iic_master)

Connectivity > UART (r_sci_uart)

Graphics > D/AVE 2D Port Interface (r_drw)

Graphics > Graphics LCD (r_glcdc)

Input > External IRQ (r_icu)

Storage > QSPI (r_qspi)

Timers > Timer, General PWM (r_gpt)

Known limitations

• Does not support asset preloading due to limited amount of RAM and non-availability of SDRAM on the evaluation kit board.
• Uses single-buffering technique by default due to limited amount of RAM. This might result in on-screen flickering. Double-buffering can be enabled from the Renesas e² studio Graphics LCD (r_glcdc) stack configuration.
• To prevent visual artifacts from appearing, try to reduce the use of rotated or perspective-transformed images that need to be blended using the CPU. Rebuilding the Qt Quick Ultralite core library in Release might help reducing such artifacts.