Connect to the BDI2000's CLI interface via TCP/IP on the standard telnet port 23. The telnet application is suitable for this. You should see usage information followed by the prompt:

Core#0>

Confirm correct connection with the BDI2000 with the reset halt command as follows:

Core#0> reset halt
- TARGET: processing reset request
- TARGET: BDI asserts TRST and RESET
- TARGET: BDI removes TRST
- TARGET: Bypass check 0x00000001 => 0x00000001
- TARGET: JTAG exists check passed
- Core#0: ID code is 0x05B0203F
- TARGET: All ICEBreaker access checks passed
- TARGET: BDI removes RESET
- TARGET: BDI waits for RESET inactive
- TARGET: resetting target passed
- TARGET: processing target startup ....
- TARGET: processing target startup passed
Core#0>

With the BDI2000 telnet interface, execute the following command, replacing /RBPATH with the location of the redboot_JTAG.bin file relative to the TFTP server root directory:

Core#0>load 0x20010000 /RBPATH/redboot_JTAG.bin bin
Loading /RBPATH/redboot_JTAG.bin , please wait ....
Loading program file passed
Core#0>

Run the loaded RAM RedBoot:

Core#0>go 0x20010040
Core#0>

Use the following command to initialize RedBoot's Flash Information System (FIS):

RedBoot> fis init
About to initialize [format] FLASH image system - continue (y/n)? y
*** Initialize FLASH Image System
... Unlocking from 0x60fe0000-0x60ffffff: .
... Erase from 0x60fe0000-0x60ffffff: .
... Program from 0x207e0000-0x20800000 to 0x60fe0000: .
... Locking from 0x60fe0000-0x60ffffff: .
RedBoot>

Now configure RedBoot's Flash configuration with the command:

RedBoot> fconfig -i

Remember to substitute the appropriate MAC address for this board at the appropriate step. If a BOOTP/DHCP server is not available, then IP configuration may be set manually. The default server IP address can be set to a PC that will act as a TFTP host for future RedBoot load operations, or may be left unset. The following gives an example configuration:

RedBoot> fconfig -i
Initialize non-volatile configuration - continue (y/n)? y
Run script at boot: false
Use BOOTP for network configuration: false
Gateway IP address: 192.168.7.11
Local IP address: 192.168.7.222
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.7.9
Console baud rate: 115200
DNS server IP address: 192.168.7.11
Network hardware address [MAC]: 0x00:0x23:0x31:0x37:0x00:0x4e
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Default network device: at91rm9200_eth
Update RedBoot non-volatile configuration - continue (y/n)? y
... Unlocking from 0x60fe0000-0x60ffffff: .
... Erase from 0x60fe0000-0x60ffffff: .
... Program from 0x207e0000-0x20800000 to 0x60fe0000: .
... Locking from 0x60fe0000-0x60ffffff: .
RedBoot> 

Load the RedBoot ROMRAM binary image from the TFTP server. Use the following command, replacing 111.222.333.444 with the TFTP server IP address (or domain name if a DNS server has been configured), and /RBPATH with the location of the redboot_ROMRAM.bin file relative to the TFTP server root directory:

RedBoot> load -r -b %{freememlo} -h 111.222.333.444 /RBPATH/redboot_ROMRAM.bin
Using default protocol (TFTP)
Raw file loaded 0x20030000-0x2004e91b, assumed entry at 0x20030000
RedBoot> 

Finally install the loaded image into Flash:

RedBoot> fis create RedBoot
An image named 'RedBoot' exists - continue (y/n)? y
... Erase from 0x60000000-0x6003ffff: ..
... Program from 0x20030000-0x2004e91c to 0x60000000: .
... Locking from 0x60000000-0x6003ffff: ..
... Unlocking from 0x60fe0000-0x60ffffff: .
... Erase from 0x60fe0000-0x60ffffff: .
... Program from 0x21fe0000-0x22000000 to 0x60fe0000: .
... Locking from 0x60fe0000-0x60ffffff: .
RedBoot>

It is also possible to use the fis write command to write the image into Flash, but if so, the relevant Flash blocks must also be explicitly unlocked with the command:

RedBoot> fis unlock -f 0x60000000 -l 0x30000

After a few seconds the following output should be seen on the serial line. Hit a key to stop the auto boot:

U-Boot 1.1.2 (Dec 14 2005 - 13:12:14)

U-Boot code: 21F00000 -> 21F1666C  BSS: -> 21F1AC44
RAM Configuration:
Bank #0: 20000000 32 MB
Flash: 16 MB

In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
U-Boot> 

Set up the environment of U-Boot to download the RAM RedBoot. Users with access to a TFTP server should substitute their own IP address, TFTP server address and netmask in the following commands:

U-Boot> setenv ipaddr 10.0.2.22
U-Boot> setenv serverip 10.0.1.2
U-Boot> setenv netmask 255.0.0.0
U-Boot> setenv bootfile redboot_UBOOT.bin

Download the RAM RedBoot. Users with access to a TFTP server should use the following command:

U-Boot> tftpboot 0x20040000
TFTP from server 10.0.1.2; our IP address is 10.0.2.22
Filename 'redboot_UBOOT.bin'.
Load address: 0x20040000
Loading: ########################
done
Bytes transferred = 120760 (1d7b8 hex)

Users without access to a TFTP server may use Kermit to send the file redboot_UBOOT.bin:

U-Boot> loadb 0x20040000                                                     

The downloaded RedBoot image may now be executed:

U-Boot> go 0x20040000
.+PHY: Davicom DM9161A
AT91RM9200 ETH: 100Mb
... waiting for BOOTP information
Ethernet eth0: MAC address 00:23:31:37:00:1c
IP: 10.0.2.9/255.0.0.0, Gateway: 10.0.0.3
Default server: 10.0.1.2, DNS server IP: 10.0.0.1

RedBoot(tm) bootstrap and debug environment [UBOOT]
Non-certified release, version UNKNOWN - built 18:18:48, Jun  8 2006

Platform: DNP/9200 with DNP/EVA9 (ARM9)
Copyright (C) 2000, 2001, 2002, 2003, 2004 Free Software Foundation, Inc.
Copyright (C) 2003, 2004, 2005, 2006 eCosCentric Limited

RAM: 0x20000000-0x22000000, [0x20067040-0x21fdd000] available
FLASH: 0x60000000-0x60ffffff, 128 x 0x20000 blocks
RedBoot>