2. 1
Product names mentioned in this document are trademarks of their respective manufacturers and are used here only
for identiďŹcation purposes.
Š Copyright 2001-2007, Jungo Ltd. All Rights Reserved.
Information in this document is subject to change without notice. The software described in this document is
furnished under a license agreement. The software may be used, copied or distributed only in accordance with that
agreement. No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or
any means, electronically or mechanically, including photocopying and recording for any purpose without the written
permission of Jungo Ltd.
This document is available for download at:
http://www.jungo.com/openrg/manuals.html#4.1
DOC-INST-419-3-2007
March, 2007
Jungo Intellectual Property
4. What You Need to Get Started
1
This guide will help you to quickly load an OpenRG image to your Intel IXP425-based development plat-
form. To do so, you must have the following:
⢠An OpenRG image. Obtain the image in one of the following ways:
â You can download a pre-built image for your chosen platform from
http://www.jungo.com/openrg/download_v41.html.
â You can download and install the OpenRG Software Development Kit (SDK) from
http://www.jungo.com/openrg/download_v41.html. After installing the SDK and compiling an
image, the created openrg.img and openrg.rmt ďŹles can be found under the rg/build subdirec-
tory.
⢠An Intel IXDPG425 (Monte Jade) or IXP425 (Coyote) board.
⢠An installed bootloader.
⢠A PC with a network interface card.
⢠Network and serial cables (one of each).
⢠A terminal application, e.g. Minicom (Linux), HyperTerminal (Windows).
Jungo Intellectual Property
5. Physical Connection
2
The following images present the Intel IXP425-based boards, detailing their relevant components. Please
review them prior to installation.
Jungo Intellectual Property
6. 2.1 Monte Jade Board 5
2.1 Monte Jade Board
Figure 2.1: Monte Jade Board
Jungo Intellectual Property
7. 2.1 Monte Jade Board 6
The following image presents the connected board:
Figure 2.2: Connected Monte Jade Board
Jungo Intellectual Property
9. 2.3 Supported Cards 8
The following image presents the connected board:
Figure 2.4: Connected Coyote Board
2.3 Supported Cards
⢠IEEE 802.11b/g 54M MiniPCI 54M Ralink RT2560 Wireless LAN card â supported by OpenRG on
Coyote and Monte Jade boards (see ďŹgure 2.5).
Figure 2.5: Ralink Card
⢠ST MicroElectronics Mt. Ararat ADSL2+ ATM card â supported by OpenRG on Monte Jade boards
(see ďŹgure 2.6).
Jungo Intellectual Property
10. 2.4 Connecting the Boards 9
Figure 2.6: Mt. Ararat Card
2.4 Connecting the Boards
1. Connect the board to a power output. Make sure to connect each board to its correct power output,
according to the following table:
Board Voltage Current
Monte 12V DC 2.5A
Jade
Coyote 12V DC 1.5A
2. Connect the boardâs WAN socket to the PCâs network card. ConďŹgure the cardâs IP address with
192.168.1.10.
3. Connect the âUART0â serial port to your PC using a serial cable. For all platforms, the terminal appli-
cation should be conďŹgured to the following settings:
⢠Speed: 115200
⢠Data bits: 8
⢠Parity: None
⢠Stop bits: 1
⢠HW Flow Control: None
⢠SW Flow Control: None
In order to conďŹgure these settings on Minicom, follow these instructions:
(a) On your console screen, run âMinicom -sâ.
(b) Select âSerial port setupâ.
(c) Change the relevant settings.
(d) Select âSave setup as dďŹâ.
4. Switch the board on.
Jungo Intellectual Property
11. Setting up RGLoader
3
RGLoader must be up and running on your board in order to burn an OpenRG image.
3.1 Replacing RedBoot with RGLoader
Note: If RGLoader is already installed on your board, skip this section. If you are using a Monte Jade
image, starting from OpenRG version 4.1, you need to update to a new RGLoader (refer to section 3.3).
If you are using a RedBoot version that supports the on-board Ethernet MACs, connect one of the switch
ports to your PC using a cross Ethernet cable. Otherwise connect the EEPRO100 Ethernet PCI card.
3.1.1 Network Setup
1. If this is the ďŹrst time RedBoot is run on the board, you must perform an initialization by executing:
Redboot> fis init -f
The initialization process may take about 2 minutes.
2. Reboot the board.
3. The RedBoot greeting will appear on the serial modem console screen. When RedBoot comes up,
press âCTRL-Câ to prevent it from loading an existing image.
4. Set up an appropriate network conďŹguration by executing:
Redboot> fconfig
Note: If the below conďŹguration options are not shown, use the
fconďŹg -i option to erase the old Redboot conďŹguration.
The following conďŹguration options will appear:
(a) Type âFALSEâ on the run script at boot option.
(b) Type âFALSEâ on the BOOTP option type in order to be able to set the local and remote IPs.
Jungo Intellectual Property
12. 3.1 Replacing RedBoot with RGLoader 11
(c) Specify the IP of the computer connected with the boardâs LAN in âGateway IPâ (suggested
192.168.1.10).
(d) Specify the boardâs LAN IP address in âLocal IPâ (suggested 192.168.1.1).
(e) Specify the local mask settings in âLocal IP address maskâ (suggested 255.255.255.0).
(f) Specify the TFTP server host IP in âDefault server IPâ (suggested 192.168.1.10 - same as the Gate-
way IP).
(g) Leave the following entries in âDefault Network Deviceâ with their default settings (press âEn-
terâ):
⢠Baud rate
⢠DNS server IP
⢠GDB connection port
⢠Force console for special debug messages
⢠Network debug at boot time
(h) Specify npe eth0 as the default network device.
(i) Leave the MAC addresses as they are (press âEnterâ).
(j) Type âyâ to apply the conďŹguration changes.
(k) Reboot the board.
5. If RedBoot comes up with a notice that the network card has not been found, reboot the board until it
ďŹnds it.
3.1.2 Uploading RGLoader to RAM
1. ConďŹgure your PCâs IP address to 192.168.1.10 (or the IP you chose as the default server IP).
2. Make sure you have a working TFTP server on your PC. Note that the Windows TFTP server requires
to set up a TFTP directory.
3. Download the appropriate RAM RGLoader image ďŹle to your PC:
⢠Monte Jade
http://www.jungo.com/openrg/download/ixdpg425_ram_rgloader.img
⢠Coyote
http://www.jungo.com/openrg/download/coyote_ram_rgloader.img
4. Place the image to be burnt in the TFTP server directory, usually the /tftpboot directory on the PC (or
any directory with which you set the server). Make sure the directory has reading permissions for all
users.
5. Load the RAM RGLoader image into the memory, by executing:
Redboot> load r <platform>_ram_rgloader.img b 0x20000
6. Run the RGLoader, by executing:
Redboot> go 0x20000
3.1.3 Burning a Complete Image
1. Download the appropriate OpenRG image ďŹle to your PC:
⢠Monte Jade
http://www.jungo.com/openrg/download/ixdpg425_opensmb_flash_41.img
Jungo Intellectual Property
13. 3.2 Compiling the RGLoader 12
⢠Coyote
http://www.jungo.com/openrg/download/coyote_opensmb_flash_41.img
2. Place the image to be burnt in the TFTP server directory, usually the /tftpboot directory on the PC (or
any directory with which you set the server). Make sure the directory has reading permissions for all
users.
3. In order to release the Flash memory and allow burning a new boot loader, execute:
OpenRG Boot> unlock 0x0 0x800000
4. After RGLoader is up, execute the following command to burn the new image:
OpenRG Boot> load -u tftp://<TFTP Server IP>/<Image-Name> -r 0
<TFTP Server IP> should be replaced with the hostâs IP address on which your TFTP Server is in-
stalled. <Image-Name> should be replaced with the ďŹle you have just downloaded.
Wait for the âDownload completed successfullyâ message on the serial console, indicating that the
download process has completed.
Note: If you encounter the following error message âNo route found by OpenRG to ip <TFTP Server
IP>â â disregard it.
5. Reboot the board.
3.2 Compiling the RGLoader
1. Change the directory to where you installed the OpenRG development tree, for example:
$ cd Ë/rg.4_0_11/rg
2. Execute the following command to conďŹgure and build the development tree:
make config DIST=RGLOADER_<platform-specific distribution> LIC=<license file path> && make
The platform-speciďŹc distribution is according to the board you choose:
⢠Coyote â âDIST=RGLOADER COYOTEâ
⢠Monte Jade â âDIST=RGLOADER MONTEJADEâ
The license is provided with your distribution.
3. The compilation process will produce rgloader.img. You can ďŹnd the image under the OpenRG devel-
opment tree directory, under the build.RGLOADER <platform-speciďŹc distribution> subdirectory
(i.e. rg.4 0 11/rg/build.RGLOADER COYOTE/).
3.3 Updating to a New RGLoader Version
Note: Monte Jade images, starting from OpenRG version 4.1, require a new RGLoader, compiled from the
SDK, before loading the new OpenRG image. You can download the SDK from
http://www.jungo.com/openrg/download_v41.html.
Use your old RGLoader in order to burn the new version of the supplied RGLoader.
1. Download the new RGLoader into the boardâs memory from the PC by executing:
OpenRG boot> load -u tftp://192.168.1.10/rgloader.img
Jungo Intellectual Property
14. 3.3 Updating to a New RGLoader Version 13
2. Reboot the board and make sure the RGLoader is running. You will see the Kernel extraction (âLinux..........â)
repeating itself, press the âESCâ key on the second extraction and make sure you get an RGLoader
prompt (OpenRG boot>).
3. Burn the new RGLoader into section 0 by executing:
OpenRG boot> load -u tftp://192.168.1.10/rgloader.img -s 0
Wait until a âDownload completed successfullyâ message appears.
Jungo Intellectual Property
15. Burning an Image using RGLoader
4
You can burn OpenRG to the Flash using one of two methods:
⢠Burning a full Flash image (refer to section 4.1). The whole Flash is burnt using a single image
(ďŹash.img). Refer to the âBuilding a Complete Flash Imageâ section in the OpenRG Programmerâs
Guide.
⢠Burn OpenRG using several component images â openrg.img, located in rg/build and rg factory,
located in rg/build/pkg/main (refer to section 4.2).
4.1 Burning a Full Flash Image using RGLoader
1. Turn on the board. The RGLoader greeting will appear on the serial modem console screen. When
RGLoader comes up press âESCâ to stop it from loading an existing image.
2. ConďŹgure your PCâs IP address to 192.168.1.10. The LAN IP address is 192.168.1.1.
3. Make sure you have a working TFTP server on your PC. Note that the Windows TFTP server requires
to set up a TFTP directory.
4. Place the image to be burnt (ďŹash.img) in the TFTP server directory, usually /tftpboot (or any directory
with which you set the server) on the PC.
5. Download the new image into the boardâs ďŹash from the PC, by executing:
OpenRG boot> load -u tftp://192.168.1.10/flash.img -r 0
Wait until a âDownload completed successfullyâ message appears. Note that the process takes a few
minutes.
6. Hard reset the board and allow RGLoader to load the OpenRG image.
Note: It is important to hard reset the board and not call the ârebootâ command because it might
corrupt the new burnt image by overwriting it with current OpenRG conďŹguration.
Jungo Intellectual Property
16. 4.2 Burning the Image and the Factory Settings Using RGLoader 15
4.2 Burning the Image and the Factory Settings Using RGLoader
In order to separately burn an OpenRG image and the factory settings, you must have openrg.img (located
in rg/build) and rg factory (located in rg/build/pkg/main). If you do, proceed directly to the burning
process (section 4.2.2). Otherwise compile an image ďŹrst, following the instructions in the next section
(4.2.1).
4.2.1 Compiling an Image
1. Change the directory to where you installed the OpenRG development tree, for example:
$ cd Ë/rg.4_0_11/rg
2. Execute the following command to automatically conďŹgure the development tree:
make config DIST=<platform-specific distribution> LIC=<license file path>
The platform-speciďŹc distribution is according to the board you choose. The license is provided with
your distribution.
3. To build the image ďŹles, execute:
make
4. The compilation process will produce openrg.img, which is a binary that can be downloaded and
burnt using the OpenRG âloadâ CLI command. You can ďŹnd the image under the OpenRG develop-
ment tree directory, under the build subdirectory (i.e. rg.4 0 11/rg/build). The factory settings can be
found under rg.4 0 11/rg/build/pkg/main/rg factory.
4.2.2 The Burning Process
1. Turn on the board. The RGLoader greeting will appear on the serial modem console screen. When
RGLoader comes up press âESCâ to stop it from loading an existing image.
2. ConďŹgure your PCâs IP address to 192.168.1.10. The LAN IP address is 192.168.1.1.
3. Make sure you have a working TFTP server on your PC. Note that the Windows TFTP server requires
to set up a TFTP directory.
4. Place the image to be burnt (openrg.img) in the TFTP server directory, usually the /tftpboot directory
(or any directory with which you set the server) on the PC.
5. Download the new image into the boardâs memory from the PC, by executing:
OpenRG boot> load -u tftp://192.168.1.10/openrg.img
Wait until a âDownload completed successfullyâ message appears. Note that the process takes a few
minutes.
6. Verify that the new image has been created, by executing:
OpenRG boot> flash_layout
In the IMAGE section details, verify that the counter is higher than the counter of the second IMAGE
section.
7. Copy the factory settings ďŹle (rg factory) to the TFTP directory.
8. Identify the proper factory settings section by executing âďŹash layoutâ and locating the section type
FACTORY. Then execute:
OpenRG boot> load -u tftp://192.168.1.10/rg_factory -s <factory section>
9. Verify that the factory settings section has been initialized, by executing âďŹash layoutâ.
10. Hard reset the board and allow RGLoader to load the OpenRG image.
Jungo Intellectual Property
17. Troubleshooting
5
5.1 I Receive a TFTP Error
If you receive the following TFTP error when you try to burn the Flash with an OpenRG image:
OpenRG boot> TFTP Error. Bad 0ACK response
1. Disable the ânegotiationâ option in your TFTP setup.
2. Verify the Flash image ďŹle has READ permission.
5.2 The ST ATM Card on my Board is not Working
If your ST MicroElectronics Mt. Ararat ADSL2+ ATM card is not working after loading the OpenRG image,
make sure you are using an ATM image:
1. If you compiled an image from the SDK, the speciďŹed distribution in the âmake conďŹgâ command
should be MONTEJADE ATM:
make config DIST=MONTEJADE_ATM LIC=<license file path>
2. If you downloaded a pre-built image from http://www.jungo.com/openrg/download_v41.html, the
downloaded image should be the Monte Jade OpenRG ATM image.
5.3 The Monte Jade ATM Image is Stuck after Soft Reboot
When executing reboot from the CLI, if your image is stuck after the ATM card is up, perform a hard reset.
This is a known issue of ST, the Monte Jade ATM can only be hard reset.
5.4 I was Asked for the Factory Settings File
After burning an image, the boot process may stop to ask for the factory settings ďŹle. The factory settings
can be found under /rg/build/pkg/main/rg factory. Please refer to section 4.2.
Jungo Intellectual Property
18. 5.5 OpenRG Halts in RGLoader instead of Running Image 17
5.5 OpenRG Halts in RGLoader instead of Running Image
In the case where after burning an image from RGLoader, you reboot, and OpenRG halts in RGLoader
instead of running the image you have just loaded, you should restore the defaults in the RGLoader.
The reason for this is a problem in consistency of the counters of each section on the Flash.
Jungo Intellectual Property
