📄 index.html
字号:
<html><body><title>The rrload Embedded Bootloader</title><center><h1>-- rrload --</h1></center><center><h1>Embedded Bootloader for DSPLinux</h1></center><center><h1>ver 3.8</h1></center><center><b>by RidgeRun, Inc</b></center><p><center><i>Copyright 2001</i></center><center><i>All Rights Reserved</i></center><hr WIDTH="100%"><h1>Contents</h1><UL><p>--User Manual--<LI> Section 1: <A HREF="#intro">Introduction</A><LI> Section 2: <A HREF="#objectives">Design Objectives</A><LI> Section 3: <A HREF="#features">Feature Set</A><LI> Section 4: <A HREF="#setup">Setting Things Up</A><LI> Section 5: <A HREF="#config">Persistent Configuration</A><LI> Section 6: <A HREF="#download">Downloading a New Kernel and/or Filesystem</A><LI> Section 7: <A HREF="#storing">Storing a New Kernel and/or Filesystem in Flash</A><LI> Section 7.5: <A HREF="#xip">XIP Images are a Special Case</A><LI> Section 8: <A HREF="#serialloads">A Special Note About Serial Downloads</A><LI> Section 9: <A HREF="#etherloads">A Special Note About Ethernet Downloads</A><LI> Section 10: <A HREF="#kernelargs">A Special Note About Passing A Command Line and Ethernet MAC to the Kernel</A><LI> Section 11: <A HREF="#buiding">Building the rrload Bootloader</A><LI> Section 12: <A HREF="#upgrading">Upgrading An Existing rrload Installation</A><LI> Section 13: <A HREF="#install">Installing rrload into a New Flash Chip</A><LI> Section 14: <A HREF="#customize1">Customizing rrload with New Drivers</A><LI> Section 15: <A HREF="#customize2">Customizing the Flash Partitions</A></UL><hr WIDTH="100%"><A NAME="intro"><h1>Introduction</h1></A>The rrload bootloader was developed by RidgeRun Inc,and is shipped as a component within the DSPLinux SDKdistribution. It is taylored specifically towardsallowing users to manage the loading, storing, andinvoking of a Linux kernel and root filesystem. At thetime of this writing it had been ported to at least sixTexas Instruments platforms; the C547[1|2], DSC21_EVM,DSC24_EVM, OMAP1510, OMAP710 and TI925_EVM.<p>In normal operation the bootloader resides in flash (atthe reset vector) and is the first program run on powerup, and unless intercepted, rrload will typicallytransfer control to the stored system (e.g. kernel +filesystem). Additionally, the bootloader will relocateeither the kernel and/or the filesystem to SDRAM ifnecessary prior to transferring control. This behaviorhappens automatically in response to the user havingpreviously configured rrload with a default bootcommand of "boot_auto". This is the typical commandstored along with the user's other persistentbootloader settings, which among other things, caninclude extra command line arguments the user desiresto have passed to the kernel.<p>If the bootloader is not configured with a default bootcommand, or if the boot process is intercepted, rrloadwill simply present its user interface and wait foruser input. The bootloader offers both a menu UI, aswell as a command line UI which the user may easilytoggle between. Available through the UI, is theability to download a new kernel and/or file system toeither ram or flash.<p>The bootloader supports a variety of download formatsand can accept these formats over a variety of boardI/O ports such as serial, parallel and ether. The userinterface communicates over the board's serial linewith a host terminal session such as minicom,hyperterm, etc. Holding the [Enter] key down within thehost terminal session while simultaneously applyingpower to the board will insure that any previouslystored default boot command is temporarily interceptedand instead force the bootloader to present its userinterface.<p><hr WIDTH="100%"><A NAME="objectives"><h1>Design Objectives</h1></A><UL><LI>Intended for embedded systems.<LI>Easy to build.<LI>Easy to use.<LI>Easy to modify.<LI>Small, Simple, Basic.<LI>Host based UI (minicom, hyperterm, etc).<LI>Offers core bootloader operations; not the kitchen sink.<LI>Easy to extend and portable to other platforms.<LI>Simple and well documented UI.<LI>Well documented source code.<LI>Fresh design/implementation; consistent from front to back.<LI>Self contained and releasable to Open Source Community.</UL><hr WIDTH="100%"><A NAME="features"><h1>Feature Set</h1></A><UL><LI>Menu UI as well as command line UI.<LI>UI works with standard host base terminal emulators.<LI>Can load several image formats to SDRAM including srec and rrbin (tagged binary) formats.<LI>Several I/O ports supported; serial, parallel, ether.<LI>Flash management utilities built in for component storage and retrieval<LI>User configuration settings survive power cycles (persistant params).<LI>Automatically executes a list of user stored commands at boot (default boot cmd).</UL><p><hr WIDTH="100%"><A NAME="setup"><h1>Setting Things Up</h1></A><p><b>---- If you have an C547x EVM ----</b><p>With the C547[1|2] EVM turned off, connect a serial cablebetween it and the host PC.<p>Now at the host bring up a terminal emulator such as<code>minicom</code> and associate it with theparticular host serial port you've just connected thecable to. Also use these terminal settings:<p><pre> 115200 buad 8 data bits, 1 stop bit. no start bit. no parity. no flow control Cable: Normal type (not a Null Modem type)</pre>Some jumper will have to be changed.<pre> Use all stock board jumper settings, except.... JP29 ROM size Select; moved to left-middle position. JP27 RAM/FLASH Swap ; moved to 1-2 position. JP28 FLASH WE Disable; moved to 1-2 position. JP21 Big/Little Endian; moved to 2-3 position.</pre><p>Assuming that the board has rrload contained withinon-board flash and the board switches/jumpers areenabled for boot-from-flash, then apply power to thetarget board. As the board powers up you should see therrload UI appear in the host minicom session window.The bootloader now has control of your target and iswaiting for user input.Note: If you are interested in interacting with thebootloader's UI and it is not already presented to youon a power cycle, then hold down the [Enter] key withinyour host terminal session while simultaneouslyreseting the device. This should intercept the defaultboot command and instead force the bootloader topresent its UI and allow user interaction.<p><b>---- If you have a omap1510-HelenP1 EVM ----</b><p>With the omap1510 turned off, connect a serial cablebetween it and the host PC. You may use any host serialport you desire, but on the target end you must use theboard connector identified in table below.<p>Now at the host bring up a terminal emulator such as<code>minicom</code> and associate it with theparticular host serial port you've just connected thecable to. Also use these terminal settings:<p><pre> 115200 buad 8 data bits, 1 stop bit. no start bit. no parity. no flow control Board Connector: "Modem UART" (lower connector). Cable: Null Modem type</pre>Here are the various switch settings of that dippackage which pertain to omap1510-HelenP1 rrload.<pre> Dip Switch "S2-6" on --- boot from eeprom Dip Switch "S2-6" off --- boot from flash</pre><p>Assuming that the board has rrload contained withinon-board flash and the board switches/jumpers areenabled for boot-from-flash, then apply power to thetarget board. As the board powers up you should see therrload UI appear in the host minicom session window.The bootloader now has control of your target and iswaiting for user input.Note: If you are interested in interacting with thebootloader's UI and it is not already presented to youon a power cycle, then hold down the [Enter] key withinyour host terminal session while simultaneouslyreseting the device. This should intercept the defaultboot command and instead force the bootloader topresent its UI and allow user interaction.<p><b>---- If you have a DSC21/24 EVM ----</b><p>Like the Linux kernel, the rrload bootloader uses theboard's serial port for the console. It is expectedthat a standard cable (not a NULL-Modem cable) will beconnected between the host and JP19 board connector.The terminal settings required by rrrload are the sameas those required by the DSPLinux kernel.<p><pre> 115200 baud 8 data bits 1 stop bit no start bit no parity no flow control Board Connector: JP19 Cable: Standard (not a Null Modem type)</pre><p>Assuming that the board has rrload contained withinon-board flash and the board switches and/or jumpersare enabled for boot-from-flash, then apply power tothe target board. As the board powers up you should seethe rrload UI appear in the host minicom sessionwindow. The bootloader now has control of your targetand is waiting for user input.<p>Note: If you are interested in interacting with thebootloader's UI and it is not already presented to youon a power cycle, then hold down the [Enter] key withinyour host terminal session while simultaneouslyreseting the device. This should intercept the defaultboot command and instead force the bootloader topresent its UI and allow user interaction.<p><p><b>---- If you have a TI925 EVM ----</b><p>With the TI925 turned off, connect a serial cablebetween it and the host PC. You may use any host serialport you desire, but on the target end you must use theboard connector identified in table below.<p>Now at the host bring up a terminal emulator such as<code>minicom</code> and associate it with theparticular host serial port you've just connected thecable to. Also use these terminal settings:<p><pre> 57600 buad 8 data bits, 1 stop bit. no start bit. no parity. no flow control Board Connector: "uart2" Cable: Null Modem type</pre>Here are the various switch settings of that dippackage which pertain to TI925 rrload.<pre> Dip Switch "S1-1" off --- boot from flash Dip Switch "S1-3" off --- flash write protect disabled (valid when "S1-1" off, "S1-2" off)</pre><p>Assuming that the board has rrload contained withinon-board flash and the board switches/jumpers areenabled for boot-from-flash, then apply power to thetarget board. As the board powers up you should see therrload UI appear in the host minicom session window.The bootloader now has control of your target and iswaiting for user input.Note: If you are interested in interacting with thebootloader's UI and it is not already presented to youon a power cycle, then hold down the [Enter] key withinyour host terminal session while simultaneouslyreseting the device. This should intercept the defaultboot command and instead force the bootloader topresent its UI and allow user interaction.<p><hr WIDTH="100%"><A NAME="config"><h1>Persistent Configuration</h1></A>Option 3 from the main menu will show a list of currentuser settings. These are the same settings that canbe viewed from command line mode by issuing the "set"command. If you make changes to these settings it onlyeffects the current session (ram based settings). Ifyou would like your new settings to survive power cyclesyou will have to re-flash them by first performing anerase of the params section of flash (ram copy remainsunaltered), followed by a flash store of the new paramscausing the current ram settings to be copied to flash.This can be performed with menu mode or command line mode.Here's an example showing the setting/storing of a newbootloader default boot command. In this case, we're usingthe bootloader's command line UI (as an alternative tousing the menu mode UI) to asssign the bootcmd parameter.Here we assign an empty string since no value string wassupplied on the first line:<p><pre> rrload> set bootcmd rrload> eraseflash params rrload> copy -c params -s ram -d flash -f na</pre><p>Here are the settings that rrload lets the user customizeand store persistantly.<p><UL>⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -