Diff for /wikisrc/ports/sandpoint/instsynology.mdwn between versions 1.8 and 1.9

version 1.8, 2015/09/04 22:22:18 version 1.9, 2015/09/05 11:29:45
Line 187  have to be converted into regular RS232  Line 187  have to be converted into regular RS232 
 circuit. If you are not anxious using a soldering iron you find detailed  circuit. If you are not anxious using a soldering iron you find detailed
 instructions how to build such a converter here:  instructions how to build such a converter here:
   
 -   Serial adapter for 3.3V TTL  -   [Serial adapter for 3.3V TTL](http://www.netbsd.org/ports/sandpoint/ttl2rs232.html)
   
 <img src="//www.netbsd.org/images/ports/sandpoint/syno_ser_adapter.jpg" alt="Serial adapter installed" /></td>  <img src="//www.netbsd.org/images/ports/sandpoint/syno_ser_adapter.jpg" alt="Serial adapter installed" /></td>
   
Line 274  The `altboot` boot loader has to be load Line 274  The `altboot` boot loader has to be load
 started using PPCBoot / U-Boot. Usually there are three ways to invoke  started using PPCBoot / U-Boot. Usually there are three ways to invoke
 it:  it:
   
 -   loadb  -   **loadb** to load a binary file via serial line in kermit mode
     to load a binary file via serial line in  -   **tftpboot** to load a binary file over the network with TFTP protocol
     kermit  
     mode  
 -   tftpboot  
     to load a binary file over the network with TFTP protocol  
 -   start it from the flash memory  -   start it from the flash memory
   
 The last option is prefered once the installation is completed, but  The last option is prefered once the installation is completed, but
 obviously it is not possible for the first time boot. Newer firmwares  obviously it is not possible for the first time boot. Newer firmwares
 (2007) support the use of the network interface by setting the `ipaddr`  (2007) support the use of the network interface by setting the `ipaddr`
 and `serverip` environment variables with `setenv`. Once you have set up  and `serverip` environment variables with **setenv**. Once you have set up
 TFTP and DHCP ([read below](#altboot_install)) you can download  TFTP and DHCP ([read below](#altboot_install)) you can download
 `altboot` like this:  `altboot` like this:
   
Line 329  _MPC824X &gt; <strong>loadb 1000000</str Line 325  _MPC824X &gt; <strong>loadb 1000000</str
 ## Ready for binary (kermit) download ...  ## Ready for binary (kermit) download ...
 </pre>  </pre>
   
 Now quit your terminal program and launch `kermit cmdfile`. When you are  Now quit your terminal program and launch **kermit cmdfile**. When you are
 already running `kermit`, enter the command mode by typing `CTRL-\`  already running `kermit`, enter the command mode by typing `CTRL-\`
 followed by `C`. Then send `altboot.bin`. Reconnect when the transfer is  followed by `C`. Then send `altboot.bin`. Reconnect when the transfer is
 finished.  finished.
Line 465  you have to find a way to make your firm Line 461  you have to find a way to make your firm
 `altboot` and the kernel.  `altboot` and the kernel.
   
 Note that newer Synology models, especially those from 2007, may have  Note that newer Synology models, especially those from 2007, may have
 the `saveenv` command disabled. If you have one of those skip forward to  the **saveenv** command disabled. If you have one of those skip forward to
 [this](#new_firmware) section.  [this](#new_firmware) section.
   
 Old firmware (2005)  Old firmware (2005)
Line 475  When you have an old firmware you just h Line 471  When you have an old firmware you just h
 setting in PPCBoot's environment and write the `altboot.bin` binary to  setting in PPCBoot's environment and write the `altboot.bin` binary to
 any free location of the Flash ROM.  any free location of the Flash ROM.
   
 To find a suitable place on the flash you can use the `flinfo` command  To find a suitable place on the flash you can use the **flinfo** command
 and look out for empty sectors `(E)`. On my Synology box I have chosen  and look out for empty sectors `(E)`. On my Synology box I have chosen
 `0xff400000`. Replace that in all the following commands if you have  `0xff400000`. Replace that in all the following commands if you have
 chosen a different address.  chosen a different address.
Line 513  Writing to Flash... done Line 509  Writing to Flash... done
 Protected 1 sectors  Protected 1 sectors
 </pre>  </pre>
   
 The `\` is important for `setenv` not to misinterpret the `;` as the end  The `\` is important for **setenv** not to misinterpret the `;` as the end
 of the command.  of the command.
   
 New firmware (2007)  New firmware (2007)
 -------------------  -------------------
   
 Without a working `saveenv` command the only way to make your system  Without a working **saveenv** command the only way to make your system
 automatically boot NetBSD is to replace the Linux kernel on flash by  automatically boot NetBSD is to replace the Linux kernel on flash by
 `altboot.img`, which is our bootloader in PPCBoot image format, faking a  `altboot.img`, which is our bootloader in PPCBoot image format, faking a
 Linux kernel.  Linux kernel.
   
 When viewing the environment variables with `printenv` you can see that  When viewing the environment variables with **printenv** you can see that
 the `bootcmd` is calling `bootm` to load the Linux kernel. The first  the `bootcmd` is calling **bootm** to load the Linux kernel. The first
 address is the location which we have to overwrite with `altboot.img`.  address is the location which we have to overwrite with `altboot.img`.
 Here it is `0xffc00000`, which you have to replace in all the following  Here it is `0xffc00000`, which you have to replace in all the following
 commands, in case your `bootcmd` differs.  commands, in case your `bootcmd` differs.
Line 553  Protect Flash Bank # 1 Line 549  Protect Flash Bank # 1
 Optionally you may think about replacing the Linux RAM disk image at the  Optionally you may think about replacing the Linux RAM disk image at the
 second address (`0xffe00000` in the example above) by an empty PPCBoot  second address (`0xffe00000` in the example above) by an empty PPCBoot
 image, like [this](dummy.img.gz) one (do not forget to uncompress it  image, like [this](dummy.img.gz) one (do not forget to uncompress it
 with `gunzip(1)`). Or use `mkubootimage` to make your own dummy. Write  with `gunzip(1)`). Or use **mkubootimage** to make your own dummy. Write
 it to flash as shown above. This will speed up the boot process, but is  it to flash as shown above. This will speed up the boot process, but is
 not really required.  not really required.
   

Removed from v.1.8  
changed lines
  Added in v.1.9


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb