guide.html.svn-base

vivi源代码

    2) already have a serial communication program like the minicom. 3) properly make 
    the vivi binary to support a UART port when you configure the vivi.
    </P
><P
>    If all of above is ok, you can see messages on the screen printed by the vivi.
    For example, below messages catched from the SMDK-2410
    <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>VIVI version 0.1.4 ([e-mail]) (gcc version 2.95.2 20000516 (release) 
[Rebel.com]) #0.1.4 荐 10岿 16 16:19:11 KST 2002
MMU table base address = 0x33DFC000
Succeed memory mapping.
NAND device: Manufacture ID: 0xec, Chip ID: 0x75 (Samsung KM29U256T)
Found saved vivi parameters.
Press Return to start the LINUX now, any other key for vivi </PRE
></TD
></TR
></TABLE
>
    </P
><P
>    See the last line on the screen. (As I mentioned section 1.1) the vivi has 
    two mode: an autoboot mode and a prompt mode. The vivi wait for a key input.
    If an user want to enter the prompt mode, press andy key (except Enter key).
    And then you can see the "vivi&#62;" prompt. Otherwise, the vivi try boot the
    linux kernel after waiting a few seconds or minutes.
    </P
></DIV
><DIV
CLASS="SECTION"
><HR><H2
CLASS="SECTION"
><A
NAME="USERCOMMANS"
></A
>3.2. Built-in user commands</H2
><P
>    This is not full-described built-in user comamnd. But following commands is 
    enough to use the vivi (as far as I know).
    </P
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="LOADCOMMAND"
></A
>3.2.1. <B
CLASS="EMPHASIS"
>load</B
> command</H3
><P
>      A load command is loading binaries to the flash or the ram.
      </P
><P
>      Usage:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>load &#60;media_type&#62; [ &#60;partname&#62; | &#60;addr&#62; &#60;size&#62; ] &#60;x|y|z&#62;</PRE
></TD
></TR
></TABLE
>
      <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>&#60;media_type&#62;</DT
><DD
><P
>          This argument is where to load.  Availabe values are 
          <B
CLASS="EMPHASIS"
>flash</B
> and <B
CLASS="EMPHASIS"
>ram</B
>.
          </P
></DD
><DT
>[ &#60;partname&#62; ] or [ &#60;addr&#62; &#60;size&#62; ]</DT
><DD
><P
>          This arguement determines location where to load a binary.
          If you want to use pre-defined mtd partiton informations, just type
          a partition name. Otherwise you specify an address and a size.
          </P
></DD
><DT
>&#60;x|y|z&#62;</DT
><DD
><P
>          This arguement determines the file transfer protocol. I shy that the 
          vivi only supprot xmodem curruntly. So, Available value is "x".
          </P
></DD
></DL
></DIV
>
      </P
><P
>      For exampe, you load zImage to flash memroy.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi &#62; <B
CLASS="COMMAND"
>load flash kernel x</B
></PRE
></TD
></TR
></TABLE
>
      or you specify an address and a size.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi &#62; <B
CLASS="COMMAND"
>load flash 0x80000 0xc0000 x</B
></PRE
></TD
></TR
></TABLE
>
      </P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="PARTCOMMAND"
></A
>3.2.2. <B
CLASS="EMPHASIS"
>part</B
> command</H3
><P
>      The vivi has mtd partiton informations for the vivi. This informatin not 
      related to mtd partition informations of mtd device drivers. The vivi uses
      partition informations when load a binary, boot the linux kernel, erase
      flash memroy, etc...
      </P
><P
>      Avalilable commands are:
      </P
><P
>      Display mtd partition informations.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>part show</PRE
></TD
></TR
></TABLE
>
      </P
><P
>      Add a new mtd partition.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>part add &#60;name&#62; &#60;offset&#62; &#60;size&#62; &#60;flag&#62;</PRE
></TD
></TR
></TABLE
>
      <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>&#60;name&#62;</DT
><DD
><P
>          is name of a new mtd partiton.
          </P
></DD
><DT
>&#60;offset&#62;</DT
><DD
><P
>          is offset in the mtd device.
          </P
></DD
><DT
>&#60;size&#62;</DT
><DD
><P
>          is a size of a mtd parition.
          </P
></DD
><DT
>&#60;flag&#62;</DT
><DD
><P
>          is flags of a mtd parition. Available valuse are <B
CLASS="EMPHASIS"
>JFFS2</B
>,
          <B
CLASS="EMPHASIS"
>LOCKED</B
>, and <B
CLASS="EMPHASIS"
>BONFS</B
>.
          </P
></DD
></DL
></DIV
>
      </P
><P
>      Delete a mtd partiton.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>part del &#60;partname&#62;</PRE
></TD
></TR
></TABLE
>
      </P
><P
>      Reset mtd partitions to default values.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>part reset</PRE
></TD
></TR
></TABLE
>
      </P
><P
>      Save paramter valuse and mtd parition informations to flash permanently.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>part save</PRE
></TD
></TR
></TABLE
>
      </P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="PARAMCOMMAND"
></A
>3.2.3. <B
CLASS="EMPHASIS"
>param</B
> command</H3
><P
>      The vivi has some parameter values. For example, the "<B
CLASS="EMPHASIS"
>boot_delay
      </B
>" paramter determines how long wait keystroek when the vivi 
      is in the autoboot mode. I'm sorry that this feature is in progress. So
      all listed parameter is not available. 
      </P
><P
>      Here, I give several tips for you.
      </P
><P
>      If you change the "linxu command line",
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>param set linux_cmd_line "you wish.."</B
></PRE
></TD
></TR
></TABLE
>
      </P
><P
>      If you want to see paramters,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>param show</B
></PRE
></TD
></TR
></TABLE
>
      </P
><P
>      If you want to wait a long time when recevie file via xmodem,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>param set xmodem_initial_timeout 3000000</B
></PRE
></TD
></TR
></TABLE
>

      </P
><P
>      If you want to boot imediately when a hardware reset,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>param set boot_delay 100000</B
></PRE
></TD
></TR
></TABLE
>
      </P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="BOOTCOMMAND"
></A
>3.2.4. <B
CLASS="EMPHASIS"
>boot</B
> command</H3
><P
>      A boot command is boot the linux kernel which is stored in the flash memroy
      or ram.
      Usage:
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>boot &#60;media_type&#62; [ &#60;partname&#62; | &#60;addr&#62; &#60;size&#62; ]</PRE
></TD
></TR
></TABLE
>
      <P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>&#60;media_type&#62;</DT
><DD
><P
>          This argument is where to store the linux kernel image.
          Availabe values are <B
CLASS="EMPHASIS"
>ram</B
>, <B
CLASS="EMPHASIS"
>nor</B
> and
          <B
CLASS="EMPHASIS"
>smc</B
>.
          </P
></DD
><DT
>[ &#60;partname&#62; ] or [ &#60;addr&#62; &#60;size&#62; ]</DT
><DD
><P
>          This arguement determines location where to store the linux kernel.
          If you want to use pre-defined mtd partiton information, just type
          a partition name. Otherwise you shuld specify an address and a size.
          </P
></DD
></DL
></DIV
>
      </P
><P
>      Note that all argument is optional. If you omit all argument (just type
      <B
CLASS="COMMAND"
>boot</B
>), all arguments is parsing from pre-defined mtd parititon
      information called "<B
CLASS="EMPHASIS"
>kernel</B
>"
      For example,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>boot</B
></PRE
></TD
></TR
></TABLE
>
      the vivi read the linux kernel binary from the "kernel" mtd parititons.
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; <B
CLASS="COMMAND"
>boot nor 0x80000</B
></PRE
></TD
></TR
></TABLE
>
      the vivi read the linux kernel binary form the nor flash memory. the offset is
      0x80000 and the size is default value (0xc0000).
      </P
><P
>      Ocassionally, you want to test the kernel on the ram (not store kernel 
      to flash). you can do it on the vivi
      On the SA-1110 based machine,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; load ram 0xc0008000 x
vivi&#62; boot ram</PRE
></TD
></TR
></TABLE
>
      On the S3C2410 based machine,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; load ram 0x30008000 x
vivi&#62; boot ram</PRE
></TD
></TR
></TABLE
>
      On the PXA-240 based machine,
      <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>vivi&#62; load ram 0xA0008000 x
vivi&#62; boot ram</PRE
></TD
></TR
></TABLE
>
      the vivi boot the linux kernel from the ram.
      </P
></DIV
><DIV
CLASS="SECTION"
><HR><H3
CLASS="SECTION"
><A
NAME="FLASHCOMMAND"
></A
>3.2.5. <B
CLASS="EMPHASIS"
>flash</B
> command</H3
><P
>    A <B
CLASS="EMPHASIS"
>flash</B
> comamnd manages the flash memory.
    If you want to erase flash memory,
    <TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="SCREEN"
>flash erase [ &#60;partname&#62; | &#60;offset&#62; &#60;size&#62; ]</PRE
></TD
></TR
></TABLE
>
    </P
></DIV
></DIV
></DIV
></DIV
></BODY
></HTML
>