![]() |
Tegra Linux Driver Package Developers' Guide September 4, 2012 R16 Release |
•
|
A kernel image (zImage). L4T does contain a kernel image (zImage), and you can also download and rebuild from source.
|
•
|
Boot loader. This can be Fastboot or U-Boot. Flashing on Tegra 3 series (code-named Cardhu) and Tegra 2 series (code-named Ventana) developer boards requires a boot loader. This boot loader can be either the Fastboot utility or U-Boot, both of which are included in this release.
|
•
|
A rootfs device which can be an SD card, a USB hard disk, or USB stick formatted to EXT3. It is also possible to use the target device’s internal memory, or your Linux Host PC hard-drive through NFS.
|
•
|
(Cardhu) A USB Micro-B plug to USB Std A female cable to plug into the board’s recovery port.
|
•
|
•
|
•
|
Internal eMMC
|
•
|
<release_num> is the branch number of the release, such as R16.
|
•
|
<version_num> is the revision number of the build such as 1.0 for the first build.
|
•
|
•
|
You have a device specified above in the “Boot Options” topic (formatted to EXT3). (It can also be a memory card with a USB adapter.)
|
•
|
•
|
Modified: /etc/{init/ssh.conf, X11/Xwrapper.conf, resolve.conf}
|
•
|
Deleted: /etc/ssh/ssh_host_*
|
•
|
•
|
1.
|
2.
|
Extract the compressed file as follows:
|
•
|
•
|
Extract the sample file system to the rootfs directory with this command:
|
3.
|
Run the apply_binaries.sh script to copy the NVIDIA user space libraries into the target file system:
|
•
|
•
|
Examine the resulting file /var/log/Xorg.0.log, which will contain something like the following:
|
4.
|
Optionally load any additional packages as shown in the Installing Additional Packages topic in this guide.
|
5.
|
Load the target file system that you have generated onto the first partition of a device (either a USB stick, an SD card, or a USB hard drive) and attach that device to the target board. Alternatively, you can use the flash.sh script to flash the root filesystem to the internal eMMC. In this case proceed with the following steps, and then and follow the internal eMMC instructions.
|
6.
|
•
|
2.
|
If your device is not formatted as Ext3, enter the following command to format it with an Ext3 file system:
|
3.
|
If needed, mount your device with the following command:
|
4.
|
Copy the file system. If LDK_ROOTFS_DIR is set, execute these commands:
|
•
|
2.
|
Download the NVIDIA Tegra Linux driver release and the additional support packages (for example the codec's package) from the nvidia.com links with wget. For example, to download the last (not the latest) release do the following:
|
•
|
3.
|
Extract the release. For more information, see Extracting Tegra Linux Driver Package in this section.
|
6.
|
Run the apply_binaries.sh script to install the NVIDIA drivers onto your target board. For more information, see Setting Up the Root File System in this section.
|
7.
|
(Optional) Change your X driver ABI as a variable passed into apply_binaries. For more information, see Setting Up the Root File System in this section.
|
8.
|
For the codecs, or other additional packages, extract the files, being sure to extract them to your root '/' directory. For more information, see Installing Additional Packages in this section.
|
•
|
<target_device> is either cardhu or ventana.
|
•
|
<size_in_bytes> is the desired size for the partition.
|
•
|
<rootdev> is the rootfs partition’s internal memory, for example mmcblk0p1.
|
•
|
restricted_codecs.tbz2, which is included in the <target_board>_Tegra-Linux-codecs-<version>_<release_type>.tbz2
|
•
|
wifi.tbz2 file
|
1.
|
3.
|
Unmount the device with this command:
|
•
|
•
|
1.
|
2.
|
Turn on networking by executing:
|
3.
|
•
|
You must have an Ethernet connection on the target, as well.
|
1.
|
2.
|
•
|
•
|
After adding the entry, restart using the following command:
|
3.
|
4.
|
6.
|
(Optional) If the Ubuntu firewall blocks NFS root access, it must be disabled depending upon your configuration. You can do so with the following command:
|
7.
|
If there are issues performing the NFS boot, to separately verify everything on the ‘host’ machine is configured properly, you can perform the following step on a booted target board through USB/SD/internal eMMC. It should be possible to mount the host NFS root point on the target device:
|
•
|
Enter the following command:
|
•
|
/bootloader—boot loader plus flashing tools (NvFlash, CFG, BCTs, etc.)
|
•
|
•
|
/rootfs—the root file system that you download
|
•
|
1.
|
Put the target board into reset/recovery mode. Do so by first powering on the board and then holding the recovery button, and then pressing the reset button as described in the Quick Start guide for the board.
|
2.
|
Run the flash.sh script that is in the top level directory of this release. The script must be supplied with the target board code name (cardhu or ventana) for the root file system:
|
•
|
If the root file system will be on a USB disk, execute the script as follows:
|
•
|
If the root file system will be on an SD card, execute the script as follows:
|
Is one of following:
|
||
Skip building and reuse existing system.ing
|
||
Specifies the kernel command line. Warning: Each option in this kernel command-line gets higher precedence over the same option from fastboot. In case of NFS booting, this script adds NFS booting related arguments, if the -i option is omitted.
|
||
Specifies the kernel command line as-provided by the user and passes it to fastboot.
|
||
•
|
•
|
1.
|
•
|
You have downloaded the kernel source code.
|
•
|
<crossbin> is the prefix applied to form the path to the tool chain for cross compilation, e.g., gcc. For a CodeSourcery tool chain, it will look something like:
|
•
|
<outdir> is the desired destination for the compiled kernel.
|
2.
|
3.
|
Execute the following commands to build the kernel:
|
5.
|
Copy the kernel zImage over the one present in the ‘kernel’ directory of the release.
|
6.
|
Archive the kernel modules created in step 4 using the tar command and the filename that is used for the kernel modules tar file in the same kernel directory of the release. When both of those tar files are present, you can follow the instructions provided in this document to flash and load your newly built kernel.
|
1.
|
2.
|
Manually create the sym-links in the target root file-system for /usr/lib/libEGL.so.1 and /usr/lib/libGLESv2.so.2.
|
Copyright © 2011-2012 by NVIDIA Corporation. All rights reserved. |
PG_06076-R16 Revised: 30 Aug 2012 |