Using Hypervisor
For SDK releases that do not support dual MMC controllers, it is not possible to use a rootfs on a second MMC instance for the second guest operating system.
To use Hypervisor
1. Install Foundation SDK, ensuring that the GNU Toolchain is installed. The toolchain is installed in:
2. Ensure DHCP/NFS is set up according to the procedures in the Linux, QNX, or Android Development Guide.
3. Install Foundation SDK packwages for the operating systems, and in the SDK installation folder, run the following command:
export PDK_TOP=${PWD}
4. Define the CROSS_COMPILE variable to hold the path of the 4.9 toolchain with the following commands:
export CROSS_COMPILE=$PDK_TOP/toolchains/tegra-4.9-nv/usr/bin/aarch64-gnu-linux/aarch64-gnu-linux-
The CROSS_COMPILE variable is a prefix for the path to the correct cross-compiler toolchain binary, completed in Makefile.bind.
5. Build the uart_muxer utility:
cd <top>/drive-t186ref-foundation/tools/host/uart_muxer
make
6. Use the uart_muxer utility to create nodes.
Alternatively, use the uart_muxer.sh wrapper script to start a terminal automatically on each node with the following command:
<top>/drive-t186ref-foundation/tools/host/uart_muxer/uart_muxer.sh -g <terms> -b <msgterm> -d <console>
7. Run a terminal utility on each of the created /dev/pts/X nodes..
To flash Hypervisor with a single OS configuration
1. Prepare a foundation boot image by executing the following commands:
cd <
top>/drive-t186ref-foundation
make -f Makefile.bind BOARD=<board> PCT=linux
Where <board> is:
• For DRIVE™ PX 2 ACr (P3407): p3407-t186
• For DRIVE PX 2 ACh (P2379) Tegra A: p2379c01-t186a
• For DRIVE PX 2 ACh (P2379) Tegra B: p2379c01-t186b
2. Place the
target board into recovery mode.
3. Program the boot image and partition by running:
cd <top>/drive-t186ref-foundation/tools/host/flashtools/bootburn
./bootburn.sh -b <board>
4. Reset the target board.
