Texas Instruments OMAP35 DVEVM Series Getting Started Manual page 48

Hide thumbs Also See for OMAP35 DVEVM Series:
Table of Contents

Advertisement

Document
OMAP35x DVEVM Getting Started Guide
Document Number
SPRUFZ7
setenv rf_ub          run rf_unlock\; run rf_blank_ram\; run rf_er_uboot\; run rf_get_uboot\; run 
rf_wr_uboot 
setenv rf_kn          run rf_unlock\; run rf_blank_ram\; run rf_er_kernel\; run rf_get_kernel\; run 
rf_wr_kernel 
setenv rf_rd          run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_ramdisk\; run 
rf_wr_ramdisk 
setenv rf_min_rd      run rf_unlock\; run rf_blank_ram\; run rf_er_ramdisk\; run rf_get_min_rd\; run 
rf_wr_ramdisk 
setenv rf_fs          run rf_unlock\; run rf_blank_ram\; run rf_er_fs\; run rf_get_fs\; run rf_wr_fs 
setenv rf_all_rd      run rf_xl\; run rf_ub\; run rf_kn\; run rf_rd 
setenv rf_all_min_rd  run rf_xl\; run rf_ub\; run rf_kn\; run rf_min_rd 
setenv rf_all_fs      run rf_xl\; run rf_ub\; run rf_kn\; run rf_fs 
printenv 
echo done  
echo Make sure to set MAC address 
If you need to re-flash the target file systems that contains the demos that come along with the
OMAP3530 DVSDK, or your own target file systems, refer section Flashing the Pre-built/rebuilt
NAND Flash File System
For HyperTerm use Transfer / Send Text File ...
o
For TeraTerm use File / Send file ...
o
For minicom use the paste file command (Ctrl-A Y)
o
6. Run the reflash command sequence
OMAP3EVM # run rf_all_fs (for jffs file‐system) 
OMAP3EVM # run rf_all_rd (for ramdisk) 
(Individual components can be reflashed by using commands like rf_ub, rf_kn, etc)
Note: For reflashing choices for Micron nand please select the commands which are marked by
_new.(For example 'rf_all_fs_new' for using JFFS filesystem and 'rf_all_rd_new' for using full
ramdisk).
Note: Ramdisk should be used for Micron boards as JFFS produces warnings and very long boot
times.
Note: If the flashed rootfs.jffs2 or the NFS setup uses the target file system which is present in the
CD , or uses the NFS setup, which has demos that have dependency on the CMEM module, then the
bootargs within the initenv-xxx.txt scripts need to be modified as follows. The changes are reflected in
bold.
The bootargs for DVSDK releases from 3.00.00.36 up to and including 3.00.01.42 are as given
below
setenv bootargs_rd     mem=88M console=ttyS0,115200n8 root=/dev/ram0 initrd=0x81600000,16M 
ramdisk_size=40960 omapfb.rotate=1 omapfb.rotate_type=1 omap_vout.vid1_static_vrfb_alloc=y 
Rev
Date
48
3.0
Sept 23, 2009

Advertisement

Table of Contents
loading

Table of Contents