Difference between revisions of "Windows IoT Enterprise"

Revision as of 07:34, 1 June 2022

1 BSP Version
2 Released Image
3 Build Environment on Host
4 Run Docker example
5 Install Some tools
6 Getting Linux Source Code
7 Build Image - AIR-020 / EPC-R7200
8 Build Kernel - AIR-020 / EPC-R7200
9 Enter Download Mode
10 Flash Image
11 Flash DTB
12 Flash Mac Address
- 12.1 GBE in eeprom
- 12.2 Intel I210
13 Reference

BSP Version

BSP : NXP W1.0.0

Windows : W21H2

Released Image

OS Support List ( Jetpack 4.5.1 / L4T R32.5.1 )

Build Environment on Host

Currently, we adopt Docker as build environment.

You can get the latest version of advrisc/u18.04-imx8lbv1 Docker image for developing nVidia jetson projects.

Docker command:

$ docker pull advrisc/u18.04-imx8lbv1

Run Docker example

Step1 Run docker container (example)

sudo docker run -it --name jetson_linux_risc -v /home/bsp/myLinux:/home/adv/BSP:rw --privileged advrisc/u18.04-imx8lbv1:latest /bin/bash

Step2 In container, change the user. (example)

 adv@7cc0fa834366:~$ sudo chown adv:adv -R BSP

Install Some tools

$sudo apt-get install expect

Getting Linux Source Code

$ export GIT_SSL_NO_VERIFY=1

EPC-R7200

$ cd ~/BSP
$ mkdir jetson_linux_risc
$ cd jetson_linux_risc
$ git config --global user.name "Your Name"
$ git config --global user.email you@example.com
$ ../repo/repo init -u https://AIM-Linux@dev.azure.com/AIM-Linux/EPC-R7200/_git/manifests
$ ../repo/repo sync

AIR-020

$ cd ~/BSP
$ mkdir jetson_linux_risc
$ cd jetson_linux_risc
$ git config --global user.name "Your Name"
$ git config --global user.email you@example.com
$ ../repo/repo init -u https://AIM-Linux@dev.azure.com/AIM-Linux/AIR-020/_git/manifests
$ ../repo/repo sync

Build Image - AIR-020 / EPC-R7200

Build Release Image

sudo ./scripts/build_release.sh -s <SOC> -v <VERSION>
Where
"-v : Image version" 00001~99999
"-s : 186 - Jetson TX2 NX"
"   : 194 - Jetson Xavier NX"
"   : 210 - Jetson Nano"

Build Kernel - AIR-020 / EPC-R7200

sudo ./scripts/build_ota.sh -s <SOC> -v <VERSION>

Enter Download Mode

Press following button + power ON, or

EPC-R7200	AIR020
]

Enter following command in the device,

$ sudo reboot --force forced-recovery

Flash Image

Before flashing the image, power off the DUT, press recovery button and power on.

	EPC-R7200	AIR-020
Xavier NX	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -d ./kernel/dtb/tegra194-epcr7200.dtb jetson-xavier-nx-devkit-emmc mmcblk0p1 or $ sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh jetson-xavier-nx-devkit-emmc mmcblk0p1
TX2 NX	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -d ./kernel/dtb/tegra186-epcr7200.dtb jetson-xavier-nx-devkit-tx2-nx mmcblk0p1 or $ sudo ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
Nano	$ cd $TOP/Linux_for_Tegra/210/ $ sudo ./flash.sh -d ./kernel/dtb/tegra210-epcr7200.dtb jetson-nano-devkit-emmc mmcblk0p1 or $ sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1	$ cd $TOP/Linux_for_Tegra/210/ $ sudo ./flash.sh jetson-nano-devkit-emmc mmcblk0p1

Flash DTB

	EPC-R7200	AIR-020
Xavier NX	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -r -k kernel-dtb xavier-nx-epcr7200 mmcblk0p1	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit-emmc mmcblk0p1
TX2 NX	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -r -k kernel-dtb tx2-nx-epcr7200 mmcblk0p1	$ cd $TOP/Linux_for_Tegra/186/ $ sudo ./flash.sh -r -k kernel-dtb jetson-xavier-nx-devkit-tx2-nx mmcblk0p1
Nano	$ cd $TOP/Linux_for_Tegra/210/ $ sudo ./flash.sh -r -k DTB nano-epcr7200 mmcblk0p1	$ cd $TOP/Linux_for_Tegra/210/ $ sudo ./flash.sh -r -k kernel-dtb jetson-nano-devkit-emmc mmcblk0p1

Flash Mac Address

GBE in eeprom

$ sudo ./eeprom $SOC $mac_address

Where SOC

  186 : TX2-NX
  194 : XavierNX
  210 : Nano

Intel I210

$ sudo -s
$ BDF=`lspci | grep 210 | awk '{print $1}'`
$ setpci -s $BDF COMMAND=0007

Get NIC

$./EepromAccessTool

Flash I210 address with mac_address = D4E5F6123456 ( If mac address = D4:E5:F6:12:34:56 )

$ ./EepromAccessTool -nic=<NIC> -f=Dev_Start_I210_Copper_NOMNG_8Mb_A2_3.25_0.03.hex -mac=$mac_address

Cold reboot the device.

Reference

Boot Device

In CBoot, there is bootable menu,

[0002.262] I> Using default boot order
[0002.265] I> boot-dev-order :-
[0002.268] I> 1.sd
[0002.270] I> 2.usb
[0002.272] I> 3.nvme
[0002.274] I> 4.emmc
[0002.276] I> 5.net
[0002.277] I> Hit any key to stop autoboot:     4       3       2       1

Change the boot order, you may type

$ setvar boot-order emmc, sd, usb, net

or

$ setvar boot-order emmc

And boot the system

$ boot

For example, there are two of bootable devices - NVME SSD and EMMC If the NVME SSD was plugged-in, the system will always boot NVME SSD.

Boot to Rootfs in external storage

Make Rootfs

1.Check the external drive’s device name (e.g. NVME : /dev/nvmeXn1, U-Disk : /dev/sdX): The <search_keyword> will be NVME : nvme and U-Disk : sd

$ lsblk -d -p | grep <search_keyword> | cut -d\  -f 1

Note that there must be two spaces after the ‑d\.

2.Create a new GPT:

$ sudo parted /dev/<device> mklabel gpt

Where <device> is the device name that your host computer assigns to the external drive. For example, if the host computer assigns the NVMe drive device name nvme0n1, the command is:

$ sudo parted /dev/nvme0n1 mklabel gpt

3.Add the APP partition:

$ sudo parted /dev/<device> mkpart APP 0GB <size>

Where <size> is the size of the partition. It must be at least 16 GB. It may be larger if the external drive has enough space. For example, if <device> is nvme0n1 and the partition is to contain 16 GB, enter:

$ sudo parted /dev/nvme0n1 mkpart APP 0GB 16GB

The NVME device name of the APP partition <DPART> is then <nvmeXn1>p1.
The U-Disk device name of the APP partition <DPART> is then <sdX>1.

4.Format APP as an ext4 partition and mount it.

$ sudo mkfs.ext4 /dev/<DPART>
$ sudo mount /dev/<DPART> /mnt

You may format APP as ext2 or ext3, but ext4 is strongly recommended because it is faster, more compact, and more reliable.

5.Connect the Jetson device to a host computer and put it into recovery mode, then enter the following commands to generate the rootfs without flashing the device:

$ cd Linux_for_Tegra/
$ sudo BOOTDEV=<DPART> ./flash.sh --no-flash <board> <DPART>
$ sudo mkdir tmp_system
$ sudo mount bootloader/system.img.raw ./tmp_system
$ sudo rsync -axHAWX --numeric-ids --info=progress2 --exclude=/proc ./tmp_system/ /mnt

Where <DPART> is the device name that the Jetson device will assign to APP.

6.Unmount the external drive and disconnect it from the host computer:

$ sudo umount /mnt
$ sudo umount ./tmp_system

7.Plug the external drive into the target device and power on.

reference : nVidia

Set up boot menu for multi-rootfs

During system boot to u-boot, it will check the file /boot/extlinux/extlinux.conf to select one of rootfs.
The following example added NVME and SD card for candidate. the default rootfs will be primary. You may choose one of option in console termianl or default if there was no any selection.
Modify the root path to the <DPART> for every external storage

TIMEOUT 30
DEFAULT primary

MENU TITLE L4T boot options

LABEL primary
      MENU LABEL primary kernel
      LINUX /boot/Image
      INITRD /boot/initrd
      FDT /boot/tegra194-epcr7200.dtb
      APPEND ${cbootargs} quiet root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

LABEL sdcard
      MENU LABEL Boot from SD Card
      LINUX /boot/Image
      INITRD /boot/initrd
      FDT /boot/tegra194-epcr7200.dtb
      APPEND ${cbootargs} quiet root=/dev/sda1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

LABEL UIO-4040
      MENU LABEL Boot from UIO-4040
      LINUX /boot/Image
      INITRD /boot/initrd
      FDT /boot/tegra194-epcr7200.dtb
      APPEND ${cbootargs} quiet root=/dev/sda1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0

Calculate GPIO value from pin number

AIR-020-nVidia_GPIO.docx

Device PID VID

Open a terminal window on your host and enter the command lsusb.
The Jetson module is in Force Recovery mode if you see this message:

Bus <bbb> Device <ddd>: ID 0955: <nnnn> Nvidia Corp.

Where:

•<bbb> is any three-digit number
•<ddd> is any three-digit number
•<nnnn> is a four-digit number that represents the type of Jetson module:

Simultaneous flashing to multiple target devices.

Create MFI

$ sudo BOARDID=<boardid> BOARDSKU=<boardsku> FAB=<fab> BOARDREV=<boardrev> FUSELEVEL=fuselevel_production ./nvmassflashgen.sh <BOARD> <DEV_PART>

ex : Create a MFI tarball for a TX2 board.

$ cd Linux_for_Tegra 
$ sudo BOARDID=3636 BOARDSKU=0001 FAB=100 BOARDREV=B.0 FUSELEVEL=fuselevel_production ./nvmassflashgen.sh jetson-xavier-nx-devkit-tx2-nx mmcblk0p1

The tarball mfi_<BOARD>.tbz2 will be created in the Linux_for_Tegra/

Flash this tarball to device

1.Download mfi_jetson-xavier-nx-devkit-emmc.tbz2 to each flashing hosts.
2.Untar mfi_<BOARD>.tbz2.

$ tar xvjf mfi_mfi_<BOARD>.tbz2
$ cd mfi_jetson-xavier-nx-devkit-emmc

3. Connect Jetson boards(jetson-xavier-nx-devkit-emmc only) and put them in RCM mode.

$ ./nvmflash.sh

@@ Line 1: / Line 1: @@
-== Linux BSP Version ==
-Ubuntu 18.04
+== BSP Version ==
-Kernel 4.9.201
+BSP : NXP W1.0.0
+Windows :&nbsp;W21H2
+<div id="gtx-trans" style="position: absolute; left: -7px; top: 45px;"><div class="gtx-trans-icon">&nbsp;</div> </div>
 == Released Image ==

Difference between revisions of "Windows IoT Enterprise"

Revision as of 07:34, 1 June 2022

Contents

BSP Version

Released Image

Build Environment on Host

Run Docker example

Install Some tools

Getting Linux Source Code

Build Image - AIR-020 / EPC-R7200

Build Kernel - AIR-020 / EPC-R7200

Enter Download Mode

Flash Image

Flash DTB

Flash Mac Address

GBE in eeprom

Intel I210

Reference

Navigation menu

Personal tools

Namespaces

Variants

Views

More

Search

Navigation

Tools