Lines Matching refs:to

5 how to setup network booting and then optionally use this support to flash
9   1. You have to enable generic SPL configuration options (see
12 CONFIG_SPL_LIBCOMMON_SUPPORT in your board configuration file to build
13 SPL with support for booting over the network. Also you have to enable
16 If you want SPL to use some Vendor Class Identifier (VCI) you can set
19  2. Define CONFIG_BOOTCOMMAND for your board to load and run debrick
30     You will need u-boot.img and spl/u-boot.bin images to perform
31 network boot. Copy them to u-boot-restore.img and
32 u-boot-spl-restore.bin respectively to distinguish this version
37    - Install DHCP server and setup it to listen on the interface you
38 chose to connect to the board (usually configured in
43 to use. IMPORTANT! Both RBL and SPL use the image filename provided
46 image -- u-boot-restore.img). So you have to configure DHCP server to
47 provide different image filenames to RBL and SPL (and possibly another
48 one to main U-Boot). This can be done by checking Vendor Class
49 Identifier (VCI) set by BOOTP client (RBL sets VCI to "DM814x ROM v1.0"
52    - If you plan to use TFTP server on another machine you have to set
53 server-name option to point to it.
55 used to connect to the board is eth0, and it has address 192.168.8.1:
74      Install TFTP server and put image files to it's root directory
79   1. Write debrick script. You will need to write a script that will
80 be executed after network boot to perform actual rescue actions. You
81 can use usual U-Boot commands from this script: tftp to load additional
82 files, nand erase/nand write to erase/write the NAND flash.
90   3. Copy debrick.scr to TFTP root directory. You also need to copy
91 there all the files your script tries to load via TFTP. Example script
92 loads u-boot.img and MLO. You have to create these files doing regular
93 (not restore_flash) build and copy them to tftpboot directory.