Renesas R-Car H3

These instructions explain how to prepare a Renesas R-Car H3 target hardware platform to boot and run the QNX Hypervisor.

Preparing a board for a hypervisor system is no different from preparing a board for a non-virtualized system. You need to set DIP switches to configure board behavior (such as where it looks for IPL and startup code), and connect Ethernet, USB and serial cables so you can connect to your host system and your network (see the QNX BSP User's Guide for the Renesas R-Car H3, and the board manufacturer's documentation).

Updating the firmware to boot into EL2

To run a virtualized system, ARM boards such as the R-Car H3 Salvator-X and the R-Car H3 Starter Kit require firmware that boots into EL2. Currently, the required firmware isn't installed on these boards when they are shipped.

If you attempt to boot the hypervisor without the appropriate firmware on the board, the boot will fail with a message like the following:

# qvm @qnx7.qvmconf
QVM disabled: hypervisor support not available

To update your R-Car H3 (or other ARM) board to boot into EL2, you can either request the appropriate bootloader from Renesas or other manufacturer, or build the bootloader yourself.

Building the bootloader

The following information should be helpful if you choose to build the bootloader yourself for an R-Car H3 board:

Flashing the bootloader to the board firmware

When you have a bootloader that will boot into EL2, you must flash it into your board's firmware (see the QNX BSP User's Guide for the Renesas R-Car H3 for instructions).

We recommend flashing all the firmware files together as a precaution against possible mismatches. Please see the manufacturer's documentation for the latest board information.

Set the DIP switches

Assuming that your R-Car H3 board includes a bootloader that provides EL2 (see “Updating the firmware to boot into EL2” above), you can boot in HyperFlash mode. To support the QNX Hypervisor, your board must also be in 64-bit mode. For these configurations, different DIP switch settings are required on different silicon revision of this board.

Note:
  • In the diagrams, the black blocks represent the physical lever inside a switch. “ON” and “1” are silk-screened on the board.
  • The settings below are for the R-Car H3 Salvator-X board. When you have the appropriate bootloader flashed into the Starter Kit firmware, you should be able to use the factory switch settings to boot this board. If these settings don't work, refer to your Renesas R-Car H3 Starter Kit User Manual for more information about the switch settings.

Revision WS 1.0

For the WS 1.0 silicon revision, set the following switches as shown below.

To set Hyperflash mode, set the SW1, SW2, SW3, and SW10 switches as follows:

Figure 1. SW1: HyperFlash (WS1.0).
Figure 2. SW2: HyperFlash.
Figure 3. SW3: HyperFlash (WS1.0)
Figure 4. SW10: HyperFlash (WS1.0).

To set 64-bit mode, set the SW12 switch as follows::

Figure 5. SW12: 64-bit mode (WS1.0).

Revision WS 1.1

For the WS 1.1 silicon revision, set the following switches as shown below.

To set Hyperflash mode, set the SW1, SW2, SW3, and SW10 switches as follows:

Figure 6. SW1: HyperFlash (WS1.1).
Figure 7. SW2: HyperFlash (WS1.1).
Figure 8. SW3: HyperFlash (WS1.1).
Figure 9. SW10: HyperFlash.

To set 64-bit mode, set the SW12 switch as follows:

Figure 10. SW12: 64-bit mode (WS1.1).

If you need to use QSPI mode, or need other information about using the R-Car H3 DIP switches, see the BSP User's Guide that accompanies the Renesas R-Car H3 BSP, and the board manufacturer's documentation.

smmuman configuration

The QNX Hypervisor includes two smmuman configuration files for R-Car H3 boards:

Provided you are using one of the above board revisions, the startup script will select the appropriate configuration file (see “DMA device containment (smmuman)” in the “Using Your Hypervisor System” chapter, and smmuman in the “Utilities and Drivers Reference” chapter).