Copyright © Speakerbus Technology Ltd. All Rights Reserved.
This readme contains important information about this release.
Notes:
The preferred method of upgrading iD712 is to use the upgrader process described in the following sub-sections. These methods will
automatically upgrade the application software and also the bootloader and kernel if they have changed; it will not install
the pre-built v1 firmware package or remove the package if already present.
If it is not possible to apply the upgrade using the method above, for example if no existing application software
is installed and running, or when upgrading from 'SE712' versions such as 1.000.1.0 or when the pre-built v1 firmware package
is also required, then please follow the full installation instructions below.
From version 2.600.1.0 and later, upgrade from an SFTP server would also be available. Please either follow SFTP Upgrader Instructions, or TFTP Upgrader Instructions.
1. Copy the following file into a suitable directory accessible by the TFTP server; for upgrades from v1.xxx.x.x firmware this directory must be 'upgraders/' for upgrades from v2.xxx.x.x this sub-directory is optional.
1. Copy the following file into the indicated directory below the root of your TFTP server.
2. If the iD712 is currently connected to i cms, then i manager can be used to start the firmware download and upgrade. Alternatively enter the command below on the engineering console, where X.X.X.X is the IP address of the TFTP server. Note that it will take several minutes to download the encrypted tar file and complete the upgrade.
1. Copy the following file into a suitable directory accessible by the SFTP server (eg SFTP_Root) for upgraders from v2.600.1.0 or later.
2. If the iD712 is currently connected to i cms, then i manager can be used to start the firmware download and upgrade. Alternatively enter the command below on the engineering console, where X.X.X.X is the IP address of the SFTP server. Note that it will take several minutes to download the encrypted tar file and complete the upgrade.
From version 2.700.1.0, <SFTP-user-password> will be requested in response to the following command line:
Before version 2.700.1.0, <SFTP-user-password> is included in the command line:
The new version of firmware can be confirmed via the iD712 Device Information - Show Version menu, i manager deskstations view, or by executing GetVer.sh on the engineering console.
The new version of U-boot can be confirmed by examining the engineering console output during boot up, if applicable.
Note that this process will automatically take a backup of the unit's local configuration settings and restore most settings
after the upgrade is complete, but a full default configuration will always be applied automatically when upgrading from version 1 software.
Acoustic profile DSP settings will always be set to their defaults. XML configuration files will always be replaced by empty ones
except for the call register, but full XML files will be automatically downloaded from i cms later.
When upgrading from version 2.0 software, the following settings will also be set to their defaults :
When upgrading from version 2.0 or 2.1 software, the following setting will also be set to its default :
Additionally, the following CM variables are defaulted during an upgrade when the old software version (being upgraded) is below v2.520.x.x:
If a default configuration of all settings is required, then this must be separately applied from the engineering console, except when upgrading from version 1 software.
If it is not possible to upgrade a unit using the steps above, then follow this full installation procedure to individually update all the SPI and NAND Flash components on the unit. The components that may be upgraded are the bootloader (U-boot), the Linux kernel, the complete uClinux filesystem and pre-built v1 (1.000.5.0) firmware package. This is a complete upgrade and any configuration stored on the unit will be lost; after the upgrade the unit will have a blank configuration. These installation instructions assume you have an iD712 with a bootloader previously installed and a serial cable attached to the iD712.
1. Copy the following files into the indicated directories below the root of your TFTP server.
2. Connect the RS232 serial cable to the iD712 using a suitable RS232 converter. Use a terminal emulator program configured for 38400 baud, 8-bit, no parity, 1 stop bit, no flow control.
3. Connect the iD712 to an Ethernet LAN with Power-over-Ethernet, a DHCP server and access to the TFTP server, using the Ethernet RJ45 socket on the iD712. In the terminal emulator, enter a Space or Return to stop iD712 U-Boot booting uClinux.
4. Use the iD712 U-Boot 'printenv' command to check the current settings and change the value of tftp_server to match the IP address of the TFTP server, if necessary, using the command below with the appropriate IP address.
5. Check if the correct file names are set for ubootfile, vmImagefile and nandfile to match the filenames and directories in step 1 above. If necessary use the commands below with the appropriate filename.
If desired, save the new settings with the command :
6. Check that iD712 can access the TFTP server with the commands:
The ping command should report a message similar to "Operating at 100M full duplex mode, host 10.12.1.58 is alive"
7. Execute the following commands to perform the required upgrades. Note that these commands execute silently and may take a while to complete:-
8. If the program updates have been installed without any errors, then reset the board with the following command:
Note that after a reboot there is a short delay while uClinux generates SSH keys before the UI starts up and normal operation is possible.
These keys are only generated the first time uClinux runs after replacing the JFFS2 file system. When monitoring the console output, the unit reports something like:-
Generating Dropbear SSH RSA host key
Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa
...
Generating Dropbear SSH ECDSA host key
Generating 256 bit ed25519 key, this may take a while...
Public key portion is:
ssh-ed25519
...
at which point it should be possible to access the unit via an SSH program.
Back
to the Index