Texas Instruments TMS320DM357 DVEVM v2.05 manual Updating/Restoring the Bootloaders

Page 57

Updating/Restoring the Bootloaders

A.5 Updating/Restoring the Bootloaders

The DM357 EVM board contains 2 GB of NAND flash memory. During the boot process 64 MB of NAND is used. After booting, 2 GB are used for the file system.

When the EVM board is reset, the ROM bootloader (RBL) executes, initializing the board and then loading a small program called UBL (User Bootloader) from NAND flash memory into internal memory for execution. UBL in turn loads the U-Boot bootloader program from NAND flash memory. The U-Boot bootloader is responsible for loading and starting the Linux kernel.

Therefore, there are two bootloader images that need to be stored in the EVM's NAND flash memory: UBL and U-Boot. This section describes how to flash UBL and U-Boot in case these images are corrupted or need to be updated.

If the U-Boot image is intact in the EVM flash memory, you can use it to update itself. If working U-Boot (or UBL) images are not present in flash, you will need to restore these images using Code Composer Studio (CCStudio) and an emulator. The subsections that follow explain both of these procedures.

You can find UBL, U-Boot, and the NAND programmer pre-built binaries in your DVSDK installation. The location for these is typically the

/home/<useracct>/dvsdk_#_#/PSP_#_#_#_#/bin/dm357 directory. Alternatively, the source code for the Bootloader components can be found in the /home/<useracct>/dvsdk_#_#/PSP_#_#_#_#/board_utilities directory.

For further information about upgrading and flashing, see the TI DaVinci

Technology Developers Wiki at http://wiki.davincidsp.com.

A.5.1 Updating U-Boot Using U-Boot

If the U-Boot image is intact in the EVM flash memory, you can use it to update itself by following these steps:

1)After aborting the automatic boot sequence, assign an IP address to the EVM board using one of these methods:

■If you are on a standalone network or using a network cross cable to your workstation, you can assign a static IP address to the EVM as follows:

EVM # setenv ipaddr <static IP address>

Additional Procedures

A-9

Page 56 Page 58
Image 57
Page 56 Page 58
Contents TMS320DM357 Dvevm Getting Started Guide Important Notice Evaluation BOARD/KIT Important Notice FCC Warning About This Guide PrefaceTrademarks Contents Contents Dvevm Overview What’s in this Kit? DM357 What’s on the Board?What’s Next? EVM Hardware Setup Setting Up the Hardware Audio In P3 Audio Out P5 Composite Video Out J8 Uart P6 Connecting to a Console Window Running the Demonstration Software Starting the Standalone Demos Default Boot ConfigurationStarting the Standalone Demos Starting the Standalone Demos Running the Standalone Demos Shutting Down the Demos About the Encode Demo About the Encode + Decode DemoIR Remote Buttons for Encode Demo IR Remote Buttons for Decode Demo About the Decode DemoRunning the Demos from the Command Line Running the Network Demo Page Dvevm Software Setup Software Overview Command Prompts in This Guide Software Components ApplicationPreparing to Install Installing the Target Linux Software Installing the SoftwareInstalling the Dvsdk Software Exporting a Shared File System for Target Access Installing the A/V Demo FilesSwitch user to root on the host Linux workstation EVM # setenv nfshost ip address of nfs host Testing the Shared File SystemInstalling the Software Writing a Simple Program and Running it on the EVM Setting Up the Build/Development EnvironmentBuilding a New Linux Kernel Compile the kernel using the following commandRebuilding the Dvevm Software for the Target Building with DSPLink EVM # setenv serverip tftp server ip address Booting the New Linux KernelUsing the Digital Video Test Bench Dvtb Page Additional Procedures Ntsc Changing the Video Input/Output MethodsPutting Demo Applications in the Third-Party Menu File filename.tar.gz You should see the following output Setting Up a Tftp Server Booting from Flash Using Board’s Nand Flash File System Alternate Boot MethodsBooting from Flash Using NFS File System Booting via Tftp Using Board’s Nand Flash File SystemBooting via Tftp Using NFS File System Updating U-Boot Using U-Boot Updating/Restoring the BootloadersTo assign a dynamic address, use the following Updating/Restoring the Bootloaders Updating the Kernel Restoring the Nand FlashRestoring the Nand Flash Using NFS Restoring the Nand Flash Using RAM Disk and a 2 GB SD Card EVM # tar xf /mnt/mmc/dm357flashimage####.tar EVM # cd Page NFS IndexIndex--2 Index--3 Spectrum Digital, Inc 511458-0001B
Top Page Image Contents