Changes between Version 14 and Version 15 of Internal/OpenFlow/QuantaSetup

Timestamp:

Mar 2, 2011, 7:34:43 PM (14 years ago)

Author:

akoshibe

Comment:

—

Internal/OpenFlow/QuantaSetup

@@ -21 +21 @@
 [[BR]] 
 === 1.2 Prerequisites === 
+The things listed here are mostly for connecting to the switch via serial. The actual steps are covered [#uboot later on]. 
+
  * A PC running some *nix with a serial port
- * null modem cable  
+ * RS232 to RJ45 null cable (a Cisco flat cable actually works)  
  * packages on PC: ckermit, openssh  
 
@@ -46 +48 @@
 }}}
 
-As seen in the above "screenshot", XorPlus will be automatically loaded after 10 seconds, giving you the standard switch CLI. !XorPlus is a full-fledged switch configuration interface; Documentation for using XorPlus can be downloaded from the [http://www.pica8.org/documents/user-guide Pica8 website].
-
-The second choice, "!OpenFlow", gives you an outdated version of the Indigo interface, the "pure OpenFlow" switch firmware. The interface is essentially a standard Linux shell, plus !OpenFlow facilities such as `of-bcm-cli`.  
-
-The last choice, "System shell", lets you access the base system using the ash shell. This last mode is useful if you need to access the cf card contents (e.g. to try different versions of firmware without erasing stuff/dealing with flashing the switch).
-
+As seen in the above "screenshot", !XorPlus will be automatically loaded after 10 seconds, giving you the standard switch CLI. !XorPlus is a full-fledged switch configuration interface; Documentation for using !XorPlus can be downloaded from the [http://www.pica8.org/documents/user-guide Pica8 website].
+
+The second choice, "!OpenFlow", gives you an outdated version of the Indigo interface, the "pure !OpenFlow" switch firmware. The interface is essentially a standard Linux shell, plus !OpenFlow facilities such as `of-bcm-cli`.  
+
+The last choice, "System shell", lets you access the base system using the ash shell. This last mode is useful if you need to access the cf card to test out a new image, or to check configuration scripts for !XorPlus or !OpenFlow.
 
 === 2.2 The flash image ===
@@ -73 +74 @@
 There isn't much I can tell you about this interface, except that option [1 ] doesn't do anything, [7 ] reboots the switch, and [8 ] might be unsafe to do on a hard, inclined surface^1^. 
 
-=== 2.3 u-boot ===
+=== 2.3 u-boot === #uboot
 u-boot is the second-stage boot loader that comes with the switch. It has enough smarts to allow you to flash the switch and inspect/configure various boot options, and in the case of !OpenFlow, set parameters that the switch will use to connect to the controller.   
 
@@ -153 +154 @@
 Each entry is a line of the form [variable name]=[parameters]. the parameters can be a combination of u-boot commands and other variables in a way similar to a simple shell script.  
 
+The general case for these variables can be summarized as follows:
+
+ * syntax is `[name]=[parameters]`, where [parameter] is some string
+ * `$[name]` returns the value of the separately defined variable, [name]
+ * semicolon (;) delimits individual commands  
+
 For example, note the first two entries in the "screen shot" above:
 {{{
@@ -158 +165 @@
 <entry 2> cfcard_bootcmd=setenv bootargs root=/dev/ram console=ttyS0,$baudrate; ext2load ide 0:1 0x1000000 /uImage;ext2load ide 0:1 0x2000000/uInitrd2m;ext2load ide 0:1 0x400000 /LB9A.dtb;bootm 1000000 2000000 400000
 }}}   
-they were part of the `run` commands mentioned earlier. The parameters to these variables create another variable called "bootargs" using command `setenv`. What follows are the parameters for this new variable: 
+they were part of the `run` commands mentioned earlier. The parameters to these variables create another variable called "bootargs" using command `setenv`. What follows are the parameters for this new variable (which are also environment variables): 
+
  * `root=/dev/ram` - probably specifies where the root filesystem should be loaded^2^
- * `console=ttyS0` - set console 
- * `$baudrate` - use the parameters specified in the variable "baudrate" 
-The parameters that follow the semicolon after `$baudrate` differ a bit for the two variables. For the cfcard entry the `ext2load` cammands specifies where to fetch the kernel, ramdisk, and device tree files from, and finally issues the command `bootm` to load the image.  
-
+ * `console=ttyS0` - set output to /dev/ttyS0 
+ * `$baudrate` - use the parameters specified in the variable "baudrate," which we can see above is set to 115200 (baud)
+
+The parameters that follow the semicolon after `$baudrate` differ a bit for the two variables. For the cfcard_bootcmd entry the `ext2load` commands specifies where to fetch the kernel, ramdisk, and device tree files from, respectively. The specific syntax for each `ext2load` command is: 
+
+ `ext2load [interface] [memory address]`
+
+What is really important here are the memory location values. For the cf card, the values should be:
+ * 0x1000000 for kernel image
+ * 0x2000000 for filesystem
+ * 0x400000 for the device tree 
+
+The same follows for the flash image, with ffd00000, ff00000, and ffee0000 being the address locations where the kernel, ramdisk, and device tree files always begin, respectively. The current version of u-boot has some tools for inspecting flash memory. These will be discussed in the [#ts troubleshooting section].      
+
+Both script variables end with the `bootm` command, which loads the program files from the memory locations given by `ext2load` in the cf card or implied in the flash.   
+
+=== 3.2 modifying the environment variables list ===
+`setenv` allows you to modify and create environment variables. In general:
+
+ * `setenv [name]`, where [name] is new, creates a new variable with that name. 
+ * `setenv [name]`, where [name] already exists, wipes out its previous parameters. 
+ * `setenv [name] [parameters]` sets parameters for the variable [name].  
+ 
+''Long parameters.'' For variables with whitespaces in its parameters (e.g. "script variables" like flash_bootcmd), the parameters have to be surrounded by single quotes to let u-boot know that everything is part of a single script. For example, to create and configure the variable dn_boot, we'd type this at the command line:
+
+{{{
+setenv dn_boot 'dhcp; nfs ff000000 $nfsip:$rootpath/uInitrd2m; setenv bootargs root=/dev/ram console=ttyS0,$baudrate DEV_ADDR=$ipaddr ETH0_IP=$ipaddr $extra_boot_args rw; bootm ffd00000 ff000000 ffee0000'
+}}}  
+
+Note the single quotes before `dhcp` and after `ffee0000`. Another important thing about long parameters is that they cannot contain newlines; The whole command must be typed in a single line.    
+
+=== 3.3 Some important variables ===
+
+=== 3.4 troubleshooting === #ts
 
 == IV OpenFlow Switching == #IV