Renesas RZ/V2H Linux BSP and Distribution, Release 1.0.0-12

...

• U-Boot firmware:

  • Runs on the Cortex-A55 core;

  • U-Boot v2021.10;

  • Target initialization from power-on / reset;

  • Loads from QSPI Flash and runs from DDR;

  • Serial console;

  • Ethernet driver for loading images to the target from network;

  • Device driver for eMMC / SD Card;4. Setting Up Kit and Development Host

    Connect to the Evaluation Kit board:

    • Serial console into CN10.

    • Power supply into CN40.

    • Ethernet cable connected to the LAN, into CN5.

    Requirements for the development host:

    • Ubuntu 20, 64 bit version.

    • 100 GB of free space.

    • Terminal software (picocom, minicom or similar) installed.4. Setting Up Kit and Development Host

      Connect to the Evaluation Kit board:

      • Serial console into CN10.

      • Power supply into CN40.

      • Ethernet cable connected to the LAN, into CN5.

      Requirements for the development host:

      • Ubuntu 20, 64 bit version.

      • 100 GB of free space.

      • Terminal software (picocom, minicom or similar) installed.

  • Auto-boot feature, allowing boot of OS images from eMMC or other storage with no operator intervention;

  • Persistent environment for customization of target operation;

  • Sophisticated command interface for maintenance and development of the target.

• Linux:

  • Runs on the Cortex-A55 cores;

  • Linux kernel v5.10.145;

  • Device drivers for key I/O interfaces;

• FreeRTOS:

  • Runs on the Cortex-CM33 or CR8 core;

  • Device drivers for select I/O interfaces.

  • [NOTE: FreeRTOS is not available in this release].

• Development environment:

  • Linux-hosted cross-development environment;

  • Yocto v3.1 (dunfell) distribution.

...

9. Known Problems and Limitations

The following are known problems and limitations of this software release:

• RNS-8: Booting from eMMC is not supported.requires QSPI Flash

• RNS-9: Booting from SD Card is not supported.requires QSPI Flash

• RNS-10: "ASoC: error at soc_component_read_no_lock" messages flood on the serial console