Update with Direct File Copy

In Direct File Copy method, developers can update the DevKit (MLSoC device) firmware by sending image files over the network and running update commands manually on the DevKit.

Note

• Starting from firmware version 1.5, developers can utilize a virtual Ethernet connection in PCIe mode to connect to the DevKit without physically altering the device setup. This enables seamless firmware updates over the existing PCIe connection.

• For developers using firmware version 1.4 or earlier in the PCIe setup, a network connection must be manually established to perform this update. This requires physically connecting the DevKit to a network in standalone mode or using the Palette-Assisted Update instead.

Warning

• For a PCIe system, you need to first update the DevKit to the desired firmware version before updating the driver on the host machine.

To proceed with a direct file copy update, ensure that your host machine has a functional network connection with the DevKit. For guidance on setting up network connections in different system architectures, refer to the following:

• Standalone Mode Network Setup

• PCIe Mode Virtual Network Setup

PrerequisitesDownload ImageUpdate The tRoot ImageUpdate The Main Image

Check if your DevKit is already running using the latest firmware release:

sima-user@sima-user-machine:~$ ssh sima@<BOARD_IP_ADDRESS> "cat /etc/build"|grep SIMA_BUILD_VERSION
sima@<BOARD_IP_ADDRESS>'s password:

SIMA_BUILD_VERSION should be 1.6.0_Palette_FW_master_B1658

If you have this version you can skip the firmware update process.

For PCIe mode, make sure you also update the PCIe host driver.