GOAL - Renesas RZ/T2M RSK

RZ/T2M-RSK

 

Introduction

Porting GOAL to Renesas RZ/T2M-RSK is in progress.

Information about the state of development, requirements, supported and upcoming features, resources and software handling are prospected in following chapters.

More information and documents are available at Renesas RZ/T2M-RSK.

Network protocols

The following network protocols are supported on RZ/T2M-RSK Arm® Cortex®-R52 single core.

Upcoming network protocols.

Please follow the links for detailed stack description.

In the first step of porting our network protocols to the new device, we focusing on single core solution only. Providing the multi-core versions of all network protocols is scheduled.

Features

Upcoming features:

Components

LEDs

The user LEDs 0…3 are used by GOAL for visual interaction. They can be set by calling goal_targetSetLeds(). Reading the current LED state is possible by goal_targetGetLeds().

LEDs can also be accessed via GOAL LED API.

Memory

The general RZ/T2M memory map is shown in following table. The addresses indicates the maximal reserved memory.

Address

Size

Region

Usage

Address

Size

Region

Usage

0x0010_0000 - 0x0010_7FFF

32k

BTCM

Second stage bootloader: used during startup to load GOAL application from QSPI0 flash into RAM.

0x3000_0000 - 0x3017_FFFF

1500k

Mirror area of System RAM

CPU0 GOAL (max. occupied: 800kByte)

0x3016_0000 - 0x3016_FFFF

64k

Mirror area of System RAM

Shared noncache buffer

0x3017_0000 - 0x3017_FFFF

64k

Mirror area of System RAM

Noncache buffer

0x6000_0000 - 0x6000’004b

75b

External address space xSPI0

Parameter for the bootloader

0x6000_004c - 0x6000_804b

32k

External address space xSPI0

Second stage bootloader image

0x6008_0000 - 0x6008_FFFF

64k

External address space xSPI0

CPU0 Loader Table

0x6010_0000 - 0x6027_FFFF

1500k

External address space xSPI0

CPU0 GOAL image (max. occupied: 800kByte)

0x67FF_E000 - 0x67FF_FFFF

8k

External address space xSPI0

CPU0 GOAL CM variables

Switches

The DIP switches SW3:1..SW3:8 can be used as input signal to GOAL software. Their state is polled when calling goal_targetGetButtons(). The function returns the input state as a bit mask, which assign is specified in goal_target_board.h.

UART

UART0 is used by GOAL as serial interface for sending log messages or receiving Command line interface. The interface speed is 115200 by default.

Tracing

Data tracing is possible by GOAL API via following pins.

GOAL TRACE ID

mapped to

PIN

GOAL TRACE ID

mapped to

PIN

GOAL_MA_TRACE_USER_0

IOPORT_PORT_21_PIN_2 (BSP_IO_PORT_21_PIN_2)

CN3 - PIN18

GOAL_MA_TRACE_USER_1

IOPORT_PORT_21_PIN_3 (BSP_IO_PORT_21_PIN_3)

CN3 - PIN15

GOAL_MA_TRACE_USER_2

IOPORT_PORT_21_PIN_4 (BSP_IO_PORT_21_PIN_4)

CN3 - PIN16

GOAL_MA_TRACE_USER_3

IOPORT_PORT_21_PIN_7 (BSP_IO_PORT_21_PIN_7)

CN3 - PIN7

GOAL_MA_TRACE_USER_4

IOPORT_PORT_22_PIN_0 (BSP_IO_PORT_22_PIN_0)

CN8 - PIN8

Tools

These software tools are required to run GOAL and its network protocol stacks on RZ/T2M-RSK. You may choose between e² studio or IAR Embedded Workbench.

Please ensure to use the correct IDE and FSP version! If the any of the required software version is not available anymore at Renesas Website, please contact Renesas Support.

  • IAR Embedded Workbench Version 9.30.1

    • RZ/T2M FSP Smart Configurator and FSP Installer (for IAR Embedded Workbench) v1.2.0 (available at Renesas RZ/T2M-RSK), the installer includes following software

      • RZ/T Flexible Software Package (FSP) v.1.2.0

      • RZ/T FSP Smart Configurator 2022-07 v1.2.0

  • e² studio and RZ/T2M FSP Installer v1.2.0 (available at Renesas RZ/T2M-RSK)

Running a sample project

Handling a sample project on RZ/T2M-RSK is described in following sections. This includes the process of loading software into RAM for debugging and flashing it to non-volatile storage.

Setup RZ/T2M-RSK

Before running a sample project on Renesas RZ/T2M-RSK, ensure to setup the board correctly. This chapter summary most important components, which are used by GOAL. A detailed explanation of each unit is available in Renesas Starter Kit+ for RZ/T2M User’s Manual at Renesas RZ/T2M-RSK.

All important components for handling GOAL on RZ/T2M-RSK are marked below.

key componets for GOAL on RZ/T2M-RSK

The following configuration is used as default.

DIP-Switch

1

2

3

4

5

6

7

8

9

0

DIP-Switch

1

2

3

4

5

6

7

8

9

0

SW6

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

OFF

SW4

On

On

On

On

On

OFF

OFF

OFF

-

-

SW5

OFF

OFF

On

OFF

On

OFF

OFF

OFF

On

OFF

Reference

Jumper Position

Explanation

Reference

Jumper Position

Explanation

CN8

Sort 2-3

Using QSPI0 Serial Flash

CN17

Sort 2-3

Using VCC1833_4 domain at 1.8V

CN18

Sort 1-2

Using all three ports in the same PHY mode

CN19

Sort 1-2

Using all three ports in the same PHY mode

CN20

Sort 1-2

Using all three ports in the same PHY mode

J9

Short/ Open

Using external/ internal debugger

  • plug USB to Serial Port for serial communication

    • After powering on the board, check the hardware manager for the assigned COM interface.

    • The interface speed is 115200 by default.

  • plug DC Power In (USB Type-C) for power supply

  • plug ETH0..ETH2 for network communication

Board components are designed and configured by Flexible Software Package (FSP) | Renesas Smart Configurator. The tool generates the source files of low level drivers, which are used by GOAL.

RZ/T2M-RSK with IAR Workbench

GOAL example projects for IAR Workbench is located at projects/<protocol>/<application>/iar/renesas/rzt2m_rsk*/rzt2m_rsk*.eww.

Before first use, the Smart Configurator needs to be added as external tool in IAR Workbench once by following steps:

  • open IAR Workbench IDE and select Tools → Configure Tools…

  • add a new tool by choosing New and enter the following properties

    • Menu Text: FSP Smart Configurator

    • Command1: C:\Renesas\fsp_sc\eclipse\rasc.exe
      1: Absolute path to the Flexible Software Package Smart Configurator.

    • Argument: --compiler IAR configuration.xml

    • Initial Directory: $PROJ_DIR$

setup FSP Smart Configurator Tool in IAR Workbench IDE

Setup Board for debugger as followed.

  • connect I-Jet to external debugger (MIPI-20) Connector

  • short J9 for usage of external debugger

Flexible Software Package in FSP Smart Configurator

Flexible Software Package is used for board configuration. Each GOAL project is preconfigured for RZ/T2M-RSK. The files must be generated manually before building IAR projects. Customer’s modification by FSP Smart Configurator is possible.

FSP Configuration do not cover all GOAL setting. Some modifications must still be done in GOAL.

Generating the FSP sources is required, even in library (demo) projects.

  • open an example projects in IAR Workbench (see section below for project import description).

  • choose a Workspace from the selector or via context menu → Set as Active

    • rzt2m_rsk_ram - Single-Core for Debug

    • rzt2m_rsk_bootloader - Bootloader-ROM for flashing

  • select Tools → FSP Smart Configurator from the menu to open Flexible Software Package (FSP) | Renesas

    • (optional) choose device family: Renesas RZ/T

    • a preconfigured project for the Smart Configurator is loaded and ready to use

  • press Generate Project Content to generate FSP sources

Debugging RZ/T2M-RSK with IAR Workbench

  • setup board

  • open an example projects in IAR Workbench

  • select Workspace rzt2m_rsk_ram - Single-Core

  • generate project content with FSP Smart Configurator (see section above)

  • select Project → Rebuild All to build the project

  • power up the board

  • press S3 to reset the board

  • select Project → Download and Debug to download the project into RAM and start the debug session

Flashing RZ/T2M-RSK with IAR Workbench

  • setup board

  • open an example projects in IAR Workbench

  • build RAM binary (see section above)

  • select Workspace rzt2m_rsk_bootloader - Bootloader-ROM

  • generate project content with FSP Smart Configurator (see section above)

  • select Project → Rebuild All to compile the project

  • power up the board

  • select Project → Download → Download active application to flash the second stage bootloader and RAM binary into xSPI0
    Source and destination sections are defined in the linker file.

  • press S3 to reset the board

When the device is powered up, the bootloader switches LED0 on to indicate application program copy start. After GOAL has been copied from xSPI0 flash to RAM, LED1 indicates application program copy end.

Debugging the second stage bootloader and its RAM binary is possible. But debug information of sflash’s RAM binary have to be included first. Therefore, open options of Bootloader workspace via Project → Options. Navigate to Debugger → Images and check the first box to Download extra image. Note, that Debug info only is enabled.

RZ/T2M-RSK with e2studio

GOAL example projects for e2studio is located at projects/<protocol>/<application>/e2studio/renesas/rzt2m_rsk*/

Setup Board by debugger as followed.

  • connect Mico-USB to internal debugger (Micro-USB) connector J10

  • open J9 for usage of internal debugger

Flexible Software Package in e2studio

Flexible Software Package is used for board configuration. Each GOAL project is preconfigured for RZ/T2M-RSK. The files will be generated on build automatically. Customer’s modification is possible by following steps.

  • Open configuration.xml lying in the project root (see section below for project import description).

  • The preconfiguration for the FSP Configuration is loaded and ready to use.

  • Press Generate Project Content to generate the FSP sources after modifications.

Note: There is a “FSP configuration” perspective available in e²studio. It can be enabled by Window → Perspective → Open Perspective → Other… and selecting FSP Configuration.

Debugging RZ/T2M-RSK with e2studio

  • setup board

  • open e2studio for RZ/T2M

  • importing a new project is possible by selecting File → Import and choosing Existing Project into Workspace.

    • Select root directory and Browse… into sub-directory projects of goal. All e2studio projects are listed and can be selected or deselected for import. Choose at least the *_ram version. Even if the *_bootloader version is not required for debugging, it is recommended to select it too in case the firmware should be flashed later on. Confirm by Finish.

  • Optional: configuring board by FSP Configuration

  • select the (in ram) project at Project Explorer and choose Project → Build Project. FSP sources are generated and project is build.

  • click the bug symbol at the upper right corner while (in ram) project is highlighted to start debug session.

Flashing RZ/T2M-RSK with e²studio

  • setup board

  • open e2studio for RZ/T2M

  • importing a new project is possible by selecting File → Import and choosing Existing Project into Workspace.

    • Select root directory and Browse… into sub-directory projects of goal. All e2studio projects are listed and can be selected or deselected for import. Choose *_ram and *_bootloader version of the project. Confirm by Finish.

  • Optional: configuring board by FSP Configuration

  • select the (in ram) project at Project Explorer and choose Project → Build Project. FSP sources are generated and project is build.

  • select the (in bootloader) project at Project Explorer and choose Project → Build Project. FSP sources are generated and project is build including the RAM binary.

  • power up the board

  • click the bug symbol at the upper right corner while (in bootloader) project is highlighted to flash the target and start debugging the bootloader.

When the device is powered up, the bootloader switches LED0 on to indicate application program copy start. After GOAL has been copied from xSPI0 flash to RAM, LED3 indicates application program copy end.

Downloads

GOAL Profinet Demo

A Profinet Demo is available by following download. The ZIP includes a 3h time limited, full feature protocol stack library, next to some basic (00410) and web-server (goal_http) examples.

The GSDML is located in protos/pnio/gsdml.

All projects are created for Renesas RZ/T2M-RSK WS2.1. The board configuration is fixed in library projects and can not be modified by FSP SC.

Stack documentation and a Quick Start Guide is available at Documents & Manuals.

>> download Profinet Demo for RZ/T2M-RSK (Date of update: 29.09.2023)

GOAL Ethernet/IP Demo

A EtherNet/IP Demo is available by following download. The ZIP includes a 3h time limited, full feature protocol stack, next to some basic (00410) and web-server (goal_http) examples.

The soc device description is located in application sub-directory at appl/goal_eip/.

All projects are created for Renesas RZ/T2M-RSK WS2.1. The board configuration is fixed in library projects and can not be modified by FSP SC.

Stack documentation and a Quick Start Guide is available at Documents & Manuals.

>> download Ethernet/IP Demo for RZ/T2M-RSK (Date of update: 29.09.2023)

GOAL Modbus/TCP

The Modbus TCP/IP Software is available by following download.

All projects are created for Renesas RZ/T2M-RSK WS2.1.

Application description is available at Application Examples.

>> download Modbus/TCP for RZ/T2M-RSK (Date of update: 29.09.2023)

GOAL OPC-UA Demo

A OPC-UA Demo is available by following download. The ZIP includes a 3h time limited, full feature protocol stack, next to some basic (00410) and web-server (goal_http) examples.

The device application is located in sub-directory at appl/goal_opcua/.

All projects are created for Renesas RZ/T2M-RSK. The board configuration is fixed in library projects and can not be modified by FSP SC.

Stack documentation and a Quick Start Guide is available at Documents & Manuals.

The software is under development and purposed for validation only.

>> download OPC-UA for RZ/T2M-RSK (Date of update: 29.09.2023)

Known issues

Slowed down software

The software is slowed down due to an internal bug, causing e.g. a delayed Ethernet or UART communication.

Bug fix

Open project configuration Project->Options…->General Options->Library Configuration->Library low-level interface implementation and select None.



USB-Device could not be detected

If Windows is unable to detect the USB-Device after power on please try following workaround:

  • power off the device

  • unplug external debugger and UART to serial port on PC side

  • power on the device

  • plug the external debugger and UART to serial port

 

Software development is still in progress. If any further issues are detected, please contact us.


In case of any specific questions, you can contact our support team via support@port.de.

You are interested in other protocols for this device? Please contact the sales team for commercial questions via service@port.de.

Sep 30, 2022