If the IDU is not booting and it is necessary to reload the IDU firmware without the current firmware running, it can be loaded through the boot loader as follows. This process assumes a direct connection between a PC and the IDU with both Ethernet and serial console access.
- Download/prep tftp server on your computer
- Download firmware from support portal or ftp dropbox.
- Configure the IP address of the laptop to be 192.168.100.1 (or match the IDU IP address to your existing config).
- Set tftp server to use that folder or put giga files in the tftp server folder.
- Connect Ethernet and serial cable to laptop and Giga. (Serial settings: 115200, 8, n, 1, xon/xoff.)
- Reboot or power cycle the Giga IDU.
- From the console port connection (i.e. hyperterm, putty or SecureCRT), intercept the bootup process by pressing any key multiple times. (For example, spacebar multiple times or ctrl+c)
- The above will take the system to the bootloader u-boot> (which is =>)
- Check ip settings using printenv command. Either match the setup there or change with setenv. The example below sets the IDU to 192.168.100.1 and the laptop/server to 192.168.100.180. The laptop must be configured to use this address or the IDU configured to match the range of the laptop.
- Set the IP address of the IDU to 192.168.100.100 (or match your existing subnet as necessary)
u-boot> Setenv ipaddr 192.168.100.1
- Set the subnet mask:
u-boot> Setenv netmask 255.255.255.0
- Set the IP address of the TFTP server:
u-boot> Setenv serverip 192.168.100.180
- Check settings with printenv
- Check with ping 192.168.100.180 that you can communicate with the tftp server from the IDU.
u-boot> ping 192.168.100.180
- Download the OS and FW images from a TFTP Server (i.e. tftpd32 or Solarwind running on a Windows PC) to the target RAM:
u-boot> tftp 100000 idu_os_v243.bin u-boot> tftp 800000 idu_fw_v243.binYou will see the status of the transfer. If you do not, something is not right in the IP settings.
- Run the sytem:
u-boot> bootm 100000 800000
- After the system comes up normally, login and go to config mode to upgrade the system normally. You must do a full upgrade of all of the images as the steps above were just temporary.
Don't forget to use two step process for other IDU if you're upgrading from 1.x to 2.x.
For a screen shot example of this process, please see Apex instructions to load firmware via console.