hi,

Please refer to git link below

https://git.ti.com/cgit/processor-sdk/uboot-flash-writer/

Readme Below

Regards

Anshu

U-Boot Flash Writer

U-Boot Flash Writer is a tool used to flash binaries to the on-chip flash memory. This application note provides instructions on how to use U-boot flash writer script for flashing on AM62x. Flash writer script will use DFU to boot the board and then flash the binaries to flash memory. Script also supports flashing multiple EVMs via DFU one by one.

Requirements

• AM62x EVM / AM64x EVM
• Linux Development PC that can access serial console.
• u-boot_flashwriter.sh script and uEnv.txt files packaged inside AM62x Processer SDK Installer.
• Type C USB cable
• dfu-util installed on Linux host.
• USB hub to connect multiple boards (Optional)
• UART to read the logs from the EVM (Optional)

Important files

• Download and install AM62x/AM64x Processer SDK Installer from here.am62x am64x.

• u-boot_flashwriter.sh script for flashing via DFU is located at following path inside the SDK.

• For more info please refer to sdk docs. am62x am64x.

• The text files for setting up environment variables in U-Boot for DFU flash are located at following path inside the SDK.

Requirements on Host PC

dfu-util software package provides Device firmware update (DFU) USB programmer, you can install in your Linux PC by running the commands given below on the terminal.

Building bootloader binaries for DFU

• For flashing and using the script we need to override the bootcmd command to receive the environment variable text file after DFU boot and flash the binaries/images.
• Following change needs to be done to am62x_evm_a53_defconfig/am64x_evm_a53_defconfig file located at following path inside the SDK.

• Add or update the CONFIG_BOOTCOMMAND

• It will enable script to send uEnv.txt file, import the environment variables from the uEnv.txt file and run user_commands after DFU boot. The user_commands variable is defined in the uEnv.txt file and the value assigned will be based on the on what flashing memory.
• If you have saved environment variables in your board (or saved during earlier boot), u-boot takes the environment variables (saved during earlier boot) which will override the bootcmd which will cause the flashing to fail. To make u-boot not to take the saved environment variables you can do following changes in am62x_evm_a53_defconfig or am64x_evm_a53_defconfig.

• For DFU boot you need to build the bootloader images using “am62x_evm_r5_usbdfu_defconfig”. no change is needed in case of am64x. Following change is needed in Rules.make file present in the top level of SDK.

• Now generate the bootloader images for DFU boot using top-level makefile by running following commands on the terminal from the top-level of the SDK.

Making changes in the environment variable text file for flashing

• It is used to set environment variables in U-Boot for flashing.
• It assigns a set of U-Boot commands to variable user_commands. Ex. for DFU transfer to eMMC following commands are assigned to variable user_commands.

• The user_commands variable defined in the text file contains the commands to setup environment variables in U-Boot for DFU transfer.
• You can also add your own U-Boot commands but make sure to not to remove the existing commands.

Export path to files

• Before starting the actual script, you need to export the path of DFU boot binaries, path to uEnv.txt and path to the actual binaries which will be flashed to the board. You can define them in a bash script and then call the u-boot_flashwriter.sh script from your script.
• Assign the path of bootloader binaries for flashing and DFU boot (as created in previous section) to variables as shown below. Not defining these variables or providing wrong path will throw an error.

• Assign the path of environment variable text file to below variable and export. The environment variable path will depend on the memory you want to flash. Not defining this variable or providing wrong path will throw an error. You can make your own uEnv.txt file using the uEnv.txt files packaged in SDK ( /bin/DFU_flash/am62xx-evm/ ) as an example.

• Assign the path of the files you want to flash in the given variables and export them. It is not mandatory to assign all the below variables with a path. Script will skip flashing files for which corresponding variable is undefined.

• The script will use the same files/binaries for all boards connected while flashing. If you want to flash different files/binaries, then you will need to run the script again with their respective paths.

Flashing the files

• The script u-boot_flashwriter.sh takes 2 arguments - Flash memory and Device.
• Run u-boot_flashwriter.sh to use the flash writer on Linux host with suitable arguments. All of the examples below assume that you are running commands from the top-level of the SDK.

Flashing to eMMC

• eMMC needs to be partitioned (2 partitions) before running the script. A reset is required for the partition table to be visible. Otherwise, you will get an error during flashing.
• The eMMC device typically ships without any partition table We make use of the GPT support in U-Boot to write a GPT partition table to eMMC. In this case we need to use the uuidgen program on the host to create the UUIDs used for the disk and each partition.
• Enter below commands in Linux host to generate uuid

• Flash default wic image to SD Card. Boot the board using the SD Card. Press any key to enter the U-Boot prompt. Enter following commands in U-Boot prompt.

• After the eMMC is partitioned, you can now flash to eMMC without error. (After doing all the pre-steps as mentioned in previous sections)
• Use uEnv_dfu_emmc.txt as environment variable file for flashing. Give the path of this file to variable UENV_TXT. All the example environment variables text files are packaged SDK (/bin/DFU_flash/am62xx-evm/) (/bin/DFU_flash/am64xx-evm/)
• Run following command in Linux host from the top level of SDK.

Flash to SD card

• SD Card needs to be partitioned before running the script. A reset is required for the partition table to be visible. Otherwise, you will get an error during flashing.
• For this purpose, the Processor SDK Linux AM62x, AM64x package includes a script in the /bin directory named create-sdcard.sh. Connect your SD Card to your host PC then run the script from the top level of SDK.

• After the SD Card is partitioned, you can now flash to SD Card without error. (After doing all the pre-steps as mentioned in previous sections).
• Insert the SD Card on the SD Card slot on the board.
• Use uEnv_dfu_sdcard.txt as environment variable text file for flashing. Give the path of this file to variable UENV_TXT. All the example environment variables text files are packaged SDK (/bin/DFU_flash/am62xx-evm/) or (/bin/DFU_flash/am64xx-evm/)
• Run following command in Linux host from the top level of SDK.

Flash to OSPI NOR

• Use uEnv_dfu_ospi-nor.txt as environment variable file for flashing. Give the path of this file to variable UENV_TXT. All the example environment variables text files are packaged SDK (/bin/DFU_flash/am62xx-evm/).
• Do all the pre-steps as mentioned in previous sections for flashing.
• Run following command in Linux host from the top level of SDK.

Flashing multiple devices via USB Device Firmware Upgrade (DFU)

• The script supports flashing multiple EVMs via DFU one by one. The steps for flashing for multiple devices is same as single device. User needs to connect all the boards to the host PC in DFU boot mode.
• Script checks for existing DFU device(s) connected. It will detect the devices connected to your host(in DFU mode), boot the board, flash the files, detach the device and repeat the same steps for other devices. After flashing the initial set of device(s), it will then wait for new device(s) for next iteration of flashing.
• If a new device is connected to host pc while the script is flashing to the connected devices or while the script is waiting for new devices, the script will detect the device and then flash to that device. You can exit the script by pressing Ctrl C.