📄 guide.html.svn-base
字号:
<HTML><HEAD><TITLE>Getting started with vivi</TITLE><METANAME="GENERATOR"CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><METAhttp-equiv="Content-Type"content="text/html; charset=euc-kr"></HEAD><BODYCLASS="ARTICLE"BGCOLOR="#FFFFFF"TEXT="#000000"LINK="#0000FF"VLINK="#840084"ALINK="#0000FF"><DIVCLASS="ARTICLE"><DIVCLASS="TITLEPAGE"><H1CLASS="TITLE"><ANAME="AEN2"></A>Getting started with vivi</H1><H3CLASS="AUTHOR"><ANAME="AEN4">Janghoon Lyu</A></H3><DIVCLASS="AFFILIATION"><DIVCLASS="ADDRESS"><PCLASS="ADDRESS"> <TTCLASS="EMAIL"><<AHREF="mailto:nandy@mizi.com">nandy@mizi.com</A>></TT><br> </P></DIV></DIV><DIV><DIVALIGN="CENTER"><ANAME="AEN16"></A><P></P><P> This is a short introduction about the vivi. </P><P></P></DIV></DIV><DIVCLASS="REVHISTORY"><TABLEWIDTH="100%"BORDER="0"><TR><THALIGN="LEFT"VALIGN="TOP"COLSPAN="3"><B>Revision History</B></TH></TR><TR><TDALIGN="LEFT">Revision v0.1</TD><TDALIGN="LEFT">2002-10-21</TD><TDALIGN="LEFT">Revised by: jl</TD></TR><TR><TDALIGN="LEFT"COLSPAN="3">Initial public release. very very short descriptions. (with foolish sentences -_-;;)</TD></TR></TABLE></DIV><HR></DIV><DIVCLASS="TOC"><DL><DT><B>Table of Contents</B></DT><DT>1. <AHREF="#INTRO">Introduction</A></DT><DD><DL><DT>1.1. <AHREF="#DEFINITIONS">Definitions</A></DT></DL></DD><DT>2. <AHREF="#COMPILING">Compiling the vivi</A></DT><DD><DL><DT>2.1. <AHREF="#PREREQUIREMENTS">Pre-Requirements</A></DT><DT>2.2. <AHREF="#STRAIGHTFORWARDCOMPILING">Straight-forward compilation</A></DT><DT>2.3. <AHREF="#SA1100BASEDNORFLASH">SA-1110-Based machines with the NOR flash</A></DT><DT>2.4. <AHREF="#S3C2410BASEDNANDFLASH">S3C2410-Based machines with the NAND flash</A></DT></DL></DD><DT>3. <AHREF="#USINGVIVI">Using the vivi</A></DT><DD><DL><DT>3.1. <AHREF="#INTERFACE">Interface between an user and the vivi</A></DT><DT>3.2. <AHREF="#USERCOMMANS">Built-in user commands</A></DT><DD><DL><DT>3.2.1. <AHREF="#LOADCOMMAND"><BCLASS="EMPHASIS">load</B> command</A></DT><DT>3.2.2. <AHREF="#PARTCOMMAND"><BCLASS="EMPHASIS">part</B> command</A></DT><DT>3.2.3. <AHREF="#PARAMCOMMAND"><BCLASS="EMPHASIS">param</B> command</A></DT><DT>3.2.4. <AHREF="#BOOTCOMMAND"><BCLASS="EMPHASIS">boot</B> command</A></DT><DT>3.2.5. <AHREF="#FLASHCOMMAND"><BCLASS="EMPHASIS">flash</B> command</A></DT></DL></DD></DL></DD></DL></DIV><DIVCLASS="SECTION"><H1CLASS="SECTION"><ANAME="INTRO"></A>1. Introduction</H1><P> This document explains to you: <P></P><OLTYPE="1"><LI><P>compiling the vivi</P></LI><LI><P>interface an user and the vivi</P></LI><LI><P>avaliable user commands</P></LI></OL> </P><P> </P><DIVCLASS="SECTION"><HR><H2CLASS="SECTION"><ANAME="DEFINITIONS"></A>1.1. Definitions</H2><P> <P></P><DIVCLASS="VARIABLELIST"><DL><DT><BCLASS="EMPHASIS">vivi</B></DT><DD><P> The <BCLASS="EMPHASIS">vivi</B> is one of arm boot loaders. </P></DD><DT><BCLASS="EMPHASIS">Autoboot mode</B></DT><DD><P> The vivi has two modes. one of these is <BCLASS="EMPHASIS">autoboot</B> mode. This is a default mode. In this mode, The vivi automatically boot-up the linux kernel when a delay time is expired. </P></DD><DT><BCLASS="EMPHASIS">Prompt mode</B></DT><DD><P> One of vivi's modes is <BCLASS="EMPHASIS">prompt</B> mode. In this mode, An user is able to command to the vivi doing something. </P></DD><DT><BCLASS="EMPHASIS">Host platform</B></DT><DD><P> Generally, an engineer develop the software on the powerful destktop computer (not on the embedded machines). This descktop called host platform. </P></DD><DT><BCLASS="EMPHASIS">Target platform</B></DT><DD><P> Target platform means developemnt boards or embedded machines. </P></DD></DL></DIV> </P></DIV></DIV><DIVCLASS="SECTION"><HR><H1CLASS="SECTION"><ANAME="COMPILING"></A>2. Compiling the vivi</H1><P> This section describes how to compile the vivi. </P><DIVCLASS="SECTION"><HR><H2CLASS="SECTION"><ANAME="PREREQUIREMENTS"></A>2.1. Pre-Requirements</H2><P> Here is a list of the minimum levels of software necessary to compile the vivi. <P></P><UL><LI><P>Gnu C: 2.95.3</P></LI><LI><P>Gnu make: 3.79.1</P></LI><LI><P>binutils: 2.11.2</P></LI></UL> </P><P> And then, your host platform are installed these tools. <P></P><UL><LI><P>You have a cross-compiler and tool-chains.</P></LI><LI><P>You have a Baurne-Again shell. (<TTCLASS="FILENAME">/bin/bash</TT>) </P></LI><LI><P>You have a ncurses library. </P></LI></UL> </P></DIV><DIVCLASS="SECTION"><HR><H2CLASS="SECTION"><ANAME="STRAIGHTFORWARDCOMPILING"></A>2.2. Straight-forward compilation</H2><P> The compiliation(configuration) environment of the vivi is simlilar to the environment of the linux kernel. So, you can do <BCLASS="COMMAND">make distclean </B>, <BCLASS="COMMAND">make clean</B>, <BCLASS="COMMAND">make oldconfig</B> , <BCLASS="COMMAND">make menuconfig</B>, and <BCLASS="COMMAND">make config</B>. General compiling sequence sequence is: <P></P><OLTYPE="1"><LI><P><BCLASS="COMMAND">make distclean</B></P></LI><LI><P><BCLASS="COMMAND">make menuconfig</B></P></LI><LI><P><BCLASS="COMMAND">make</B></P></LI></OL> </P><P> Note that If you change configurations, run <BCLASS="COMMAND">make clean</B> and <BCLASS="COMMAND">make</B>. Next two sections describes compilation of two examples. </P></DIV><DIVCLASS="SECTION"><HR><H2CLASS="SECTION"><ANAME="SA1100BASEDNORFLASH"></A>2.3. SA-1110-Based machines with the NOR flash</H2><P> I will take an example about the vivi compliation. I assumed that a target platform's core block is composed like this: <P></P><UL><LI><P>CPU: SA-1110 processor</P></LI><LI><P>ROM: 32MB Intel Strata Flash (32-bit wide)</P></LI><LI><P>RAM: 32MB DRAM</P></LI></UL> These features make sense to you. Many platforms I have met is designed core block like above. For instance, KINGS, GILL, and ENDA's core block is designed like this. Therefore, you refer to <TTCLASS="FILENAME">vivi/arch/def-configs/kings</TT> , <TTCLASS="FILENAME">vivi/arch/def-configs/gill</TT>, and <TTCLASS="FILENAME">vivi/arch/def-configs/enda</TT> </P><P> If you want to compile vivi for KINGS(i.e. a configuration of a target board, alredy exist in the <TTCLASS="FILENAME">vivi/arch/def-cofnigs</TT>), just do like this: <TABLEBORDER="0"BGCOLOR="#E0E0E0"WIDTH="100%"><TR><TD><PRECLASS="SCREEN"># <BCLASS="COMMAND">make kings</B> </PRE></TD></TR></TABLE> Other machines can complie same ways. </P></DIV><DIVCLASS="SECTION"><HR><H2CLASS="SECTION"><ANAME="S3C2410BASEDNANDFLASH"></A>2.4. S3C2410-Based machines with the NAND flash</H2><P> Here, I will take an example about a S3C2410-Based machine. The SMDK-2410 (a development board by SAMSUNG) is a S3C2410-Based machine. The core block of SMDK-2410 is composed like this: <P></P><UL><LI><P>CPU: S3C2410</P></LI><LI><P>ROM: 64MB SMC (NAND Flash)</P></LI><LI><P>RAM: 64MB DRAM</P></LI></UL> A configuration for SMDK-2401 will be found at <TTCLASS="FILENAME">vivi/arch/def-configs/smdk2410</TT>. To compile for SMDK-2410, do like this: (As I described above) <TABLEBORDER="0"BGCOLOR="#E0E0E0"WIDTH="100%"><TR><TD><PRECLASS="SCREEN"># <BCLASS="COMMAND">make smdk2410</B></PRE></TD></TR></TABLE> </P></DIV></DIV><DIVCLASS="SECTION"><HR><H1CLASS="SECTION"><ANAME="USINGVIVI"></A>3. Using the vivi</H1><DIVCLASS="SECTION"><H2CLASS="SECTION"><ANAME="INTERFACE"></A>3.1. Interface between an user and the vivi</H2><P> The vivi uses the serical communication for user interface. Therefore, to connect the vivi, you 1) connect a serial cable between host paltform and target platform.⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -