• State Resolved
  • Locked Locked
  • Replies 49 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 781 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

SK-AM62B-P1: How and what is flashed in which part of the emmc?

SK-AM62B-P1: I wanted to flash custom images into the images using uart of the evk,which have the following components:

Suraj Singh
Intellectual 265 points
Part Number: SK-AM62B-P1
Other Parts Discussed in Thread: UNIFLASH

I wanted to flash custom images into the images of the evk,which have the following components:

  • A boot patition
    • tiboot3.bin
    • tispl.bin
    • u-boot.img
    • uboot.env
  • A ext4 partition in the user data area containing
    • Linux Kernel image
    • Linux DTB
    • Linux file system
  • 0
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/uart_uniflash$ sudo python3 uart_uniflash.py -p /dev/ttyUSB0 --cfg=/home/suraj/Downloads/uart_flash.cfg

Parsing config file ...
Parsing config file ... SUCCESS. Found 7 command(s) !!!

Executing command 1 of 7 ...
Found flash writer ... sending /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/uart_uniflash/bin/am62xx-evm/sbl_uart_uniflash_stage1.release.hs_fs.tiimage
Sent flashwriter /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/uart_uniflash/bin/am62xx-evm/sbl_uart_uniflash_stage1.release.hs_fs.tiimage of size 246687 bytes in 23.84s.                         

Executing command 2 of 7 ...
Command arguments : --file=/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/uart_uniflash/bin/am62xx-evm/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0
Sent /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/uart_uniflash/bin/am62xx-evm/sbl_uart_uniflash_stage2.release.appimage.hs_fs of size 122931 bytes in 15.11s.                                    
[STATUS] SUCCESS !!!

Executing command 3 of 7 ...
Command arguments : --file=/home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin --operation=flash --flash-offset=0x0
Sent /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin of size 295438 bytes in 31.51s.                                                                                                                      
[STATUS] SUCCESS !!!

Executing command 4 of 7 ...
Command arguments : --file=/home/suraj/Downloads/tispl.bin-am62xx-evm --operation=flash --flash-offset=0x80000
Sent /home/suraj/Downloads/tispl.bin-am62xx-evm of size 1178343 bytes in 116.58s.                                                                                                                           
[STATUS] SUCCESS !!!

Executing command 5 of 7 ...
Command arguments : --file=/home/suraj/Downloads/u-boot-am62xx-evm.img --operation=flash --flash-offset=0x280000
Sent /home/suraj/Downloads/u-boot-am62xx-evm.img of size 984939 bytes in 95.35s.                                                                                                                            
[STATUS] SUCCESS !!!

Executing command 6 of 7 ...
Command arguments : --file=/home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs/boot/Image --operation=flash --flash-offset=0x83000000
Sent /home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs/boot/Image of size 24447488 bytes in 2366.150000000001s.                                                                      
[STATUS] ERROR: Flashing failed !!!

Executing command 7 of 7 ...
Command arguments : --file=/home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs/boot/dtb/ti/k3-am625-sk.dtb --operation=flash --flash-offset=0x83080000
Sent /home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs/boot/dtb/ti/k3-am625-sk.dtb of size 61983 bytes in 8.86s.                                                                     
[STATUS] ERROR: Flashing failed !!!

All commands from config file are executed !!!

    U-Boot 2023.04-gb0d717b732 (Dec 06 2023 - 15:11:45 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM-P1 rev A
DRAM:  2 GiB
Core:  72 devices, 32 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> mmc dev 0 0
switch to partitions #0, OK
mmc0(part 0) is current device
=> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            32768           0d0c5ad5-01     0e Boot
  2     34816           31045632        0d0c5ad5-02     83
=> ls mmc 0:2
=> ls mmc 0:2 /boot
=> ls mmc 0:2 /boot/dtb/ti
=> mmc part

Partition Map for MMC device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            32768           0d0c5ad5-01     0e Boot
  2     34816           31045632        0d0c5ad5-02     83


    This are the logs , i have tried many times to flash all the images using uart uniflash script, now u-boot images are flashing but kernel and dtb images both are not flashing in logs u can see last two images are showing failed to flash please give any solution asap.

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Before discussing anything, I want to set the expectations here. I have noticed you creating multiple threads with the same issues on different occassions. This action is understandable if you do not get a response within 2 or 3 days but you have created threads within a 1 hour gap if you do not get a response like the following thread

    (+) SK-AM62B-P1: I wanted to flash custom images into the images of the evk,which have the following components - Processors forum - Processors - TI E2E support forums

    Please note the expectation is you will get a response within 24 hours of your reply. If you do not get one, please feel free to ping on the same thread. In any case, you should understand we are working with tens of issues at the same time with some issues having higher priorities. So, while we try to get back as soon as possible, at times there might be some hours delay. If you do not hear anything back from us for 24 hours, you are more than welcome to put a reminder on the thread.

    Thanks for understanding.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I understand your concern, and I apologize for any inconvenience caused by creating multiple threads for the same issue within a short timeframe. It's important to ensure efficient communication and avoid unnecessary duplication of efforts.

    In the future, if you don't receive a response within a reasonable time frame.
    Sorry once again.


    Regards,
    Suraj 

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Thanks again for understanding. Let's discuss the issue now.

    1)

    Executing command 3 of 7 ...
    Command arguments : --file=/home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin --operation=flash --flash-offset=0x0
    Sent /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin of size 295438 bytes in 31.51s.
    [STATUS] SUCCESS !!!

    You are flashing the images to OSPI. If you want to flash to eMMC, please use --operation=flash-emmc.

    2) The UART Uniflash tool cannot flash the Linux Kernel images as communicated here

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1350928/sk-am62b-p1-correct-way-to-flash-the-rootfs-into-the-emmc/5149305#5149305

    3) The Linux Kernel and DTB are itself part of the Linux EXT4 filesystem. You would need to flash the full EXT4 rootfs filesystem to boot completely from eMMC.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1350928/sk-am62b-p1-correct-way-to-flash-the-rootfs-into-the-emmc/5149160#5149160

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I want to flash to eMMC, so for that i have to use --operation=flash-emmc followed by offset value!
    As you told,     The UART Uniflash tool cannot flash the Linux Kernel images as communicated here so i would need to flash the full EXT4 rootfs filesystem to boot completely from eMMC. So how to do this! Tell me the process.


    Regards
    Suraj



  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    I would recommend to use DFU for flashing Linux Rootfs

    3.5.3. Flash via USB Device Firmware Upgrade (DFU) — Processor SDK AM62x Documentation

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I was trying before to use DFU for flashing Linux Rootfs but i could not find out those configs files for 

    Building bootloader binaries for flashing and DFU boot

    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.

    Example DFU boot binaries for TI boards are already present in bin directory. To flash custom board(s) generate the boot binaries and place them in <TI_SDK_PATH>/bin/DFU_flash/bin/<board>/<type> folder.

    Following change needs to be done in a53_defconfig file located at following path inside the SDK.

    /board-support/ti-u-boot-2023*/configs/


    so, please tell me where will i get those files


    Regards,
    Suraj 

     

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    I believe you are using TI EVM so you can skip this section. The tool already contains the DFU boot binaries for TI EVMs so you can directly jump to the flashing sections.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    Yes i am using TI EVM, 

    Preparing the Flash Configuration file

    for this  bin/${device}/${type} i went to this path and i am trying to edit the configuration file flash-files.cfg, but this file has read permission only so i can not edit this then what to do now! Whether i have to write my own configuration file to flash rootfs image!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Not sure how it is read only on your system. I check the permission in my installed SDK and find I have the write permissions

    ~/ti/psdk/am62x/09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs
❯ /bin/ls -l flash-files.cfg
-rw-r--r-- 1 p-shivhare p-shivhare 2399 Apr 23 12:52 flash-files.cfg

    Anyway, if it is really read only, you can create a new config file and accordingly give its path to the dfu_flash.py script.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    As you told to create a new config file and accordingly give its path to the dfu_flash.py script, but that also not possible because dfu_flash.py has no permission to write only has read permission so now what to do! Is there any way to change the permission?
    I checked in my colleague system, there also same has no permission to write anything, give any solution.


    Regards,
    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Can you share the `ls -l` output from the DFU_flash directory as shown

    ~/ti/psdk/am62x/09.02.01.09/bin/DFU_flash
❯ /bin/ls -l
total 32
drwxr-xr-x 2 p-shivhare p-shivhare 4096 Mar 23 23:32 benchmark
drwxr-xr-x 4 p-shivhare p-shivhare 4096 Mar 23 23:33 bin
-rw-r--r-- 1 p-shivhare p-shivhare 3965 Mar 23 23:32 dfu_flash.py
-rw-r--r-- 1 p-shivhare p-shivhare 3043 Mar 23 23:32 LICENSE
-rw-r--r-- 1 p-shivhare p-shivhare 9446 Mar 23 23:32 README.md
drwxr-xr-x 2 p-shivhare p-shivhare 4096 Mar 23 23:32 src

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ ls -l
total 32
drwxr-xr-x 2 60898 1373 4096 Mar 23 23:32 benchmark
drwxr-xr-x 4 60898 1373 4096 Mar 23 23:33 bin
-rw-r--r-- 1 60898 1373 3965 Mar 23 23:32 dfu_flash.py
-rw-r--r-- 1 60898 1373 3043 Mar 23 23:32 LICENSE
-rw-r--r-- 1 60898 1373 9446 Mar 23 23:32 README.md
suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$


    This is the output:-

    Regards,
    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    I think you have installed the SDK in /opt directory where you will need root access to create and edit files. So, you can use sudo to edit the flash config file. And you would also need to use sudo with dfu_flash.py script.

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    Now i can edit so in flash-files.cfg this file i edited but output is given below!

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d /dev/ttyUSB0 -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
2024-04-23 15:57:09 INFO: Starting the flashing tool
2024-04-23 15:57:09 INFO: Validating the requirements before flashing...
2024-04-23 15:57:09 ERROR: The device path {/dev/ttyUSB0/hsfs} does not exist!!!



    Regards,
    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    The -d argument takes the device name for which you are performing the DFU flashing procedure. The flash script will automatically detect the DFU port and start the flashing procedure.

    The following command should work for you

    sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

     # Path to the DFU boot images
    dfu_tiboot3 = "/home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin"
    dfu_tispl   = "/home/suraj/Downloads/tispl.bin-am62xx-evm"
    dfu_uboot   = "/home/suraj/Downloads/u-boot-am62xx-evm.img"


    I have included the path of images in dfu_flash.py so, my rootfs image that path also should i include in this python script?
    And uart also we have to connect or not that i have a doubt!
    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
[sudo] password for suraj: 
2024-04-23 17:08:56 INFO: Starting the flashing tool
2024-04-23 17:08:56 INFO: Validating the requirements before flashing...
2024-04-23 17:08:56 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-23 17:08:56 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-23 17:08:56 INFO: Found 3 flash images
<<DFU_FLASH_CONF
----------------------- ------------------------------------------------- ------- -------- ----- ----------
                    Alt Path                                                 Size   Offset Media Attributes
----------------------- ------------------------------------------------- ------- -------- ----- ----------
tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin  295438      0x0 EMMC  raw,1,-   
                  tispl /home/suraj/Downloads/tispl.bin-am62xx-evm        1178343  0x80000 EMMC  raw,1,-   
      u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img        984939 0x280000 EMMC  raw,1,-   
----------------------- ------------------------------------------------- ------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-23 17:08:56 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- --------------------------------------------------------------------------------------------- -------
       Alt Path                                                                                             Size
---------- --------------------------------------------------------------------------------------------- -------
bootloader /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin                                              295438
 tispl.bin /home/suraj/Downloads/tispl.bin-am62xx-evm                                                    1178343
u-boot.img /home/suraj/Downloads/u-boot-am62xx-evm.img                                                    984939
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt     174
---------- --------------------------------------------------------------------------------------------- -------
DFU_BOOT_CONF


    This is the output when i am giving this above command:-


    Regards,
    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    You must not change anything in the source code. The dfu_tiboot3, dfu_tispl, dfu_uboot variable stores of the paths of the U-Boot images available in the bin/am62xx-evm/hsfs. These images are used to boot to U-Boot via DFU.

    The only change you need to do is the paths to your images in the flash-files.cfg. So, please revert back the changes in the source code and try the flashing procedure again.

    Also, please make sure you have put the board in DFU bootmode. If you run the following command and see similar output before running the dfu_flash.py script, it means the DFU device is connected and the dfu_flash.py script should be able to detect it.

    ~/ti/psdk/am62x/09.02.01.09/bin/DFU_flash
❯ sudo dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0451:6165] ver=0200, devnum=41, cfg=1, intf=0, path="1-3.4", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=41, cfg=1, intf=0, path="1-3.4", alt=0, name="bootloader", serial="01.00.00.00"

    Please refer the sample logs of dfu_flash.py script

    2023-08-29 17:13:21 INFO: Starting the flashing tool
2023-08-29 17:13:21 INFO: Validating the requirements before flashing...
2023-08-29 17:13:21 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2023-08-29 17:13:21 INFO: Parsing the flash configuration file {C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\flash-files.cfg}...
2023-08-29 17:13:21 INFO: Found 4 flash images
<<DFU_FLASH_CONF
------- -------------------------------------- --------- -------- -----
    Alt Path                                        Size   Offset Media
------- -------------------------------------- --------- -------- -----
tiboot3 bin\am62xx-evm\hsfs\images\tiboot3.bin    332430      0x0 EMMC
  tispl bin\am62xx-evm\hsfs\images\tispl.bin      961988  0x80000 EMMC
 u-boot bin\am62xx-evm\hsfs\images\u-boot.img     897880 0x280000 EMMC
 rootfs bin\am62xx-evm\hsfs\images\rootfs.img  475078656      0x0 EMMC
------- -------------------------------------- --------- -------- -----
DFU_FLASH_CONF
2023-08-29 17:13:21 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- -------------------------------------------------------- ------
       Alt Path                                                       Size
---------- -------------------------------------------------------- ------
bootloader C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\tiboot3.bin 333163
 tispl.bin C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\tispl.bin   960044
u-boot.img C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\u-boot.img  894876
  uEnv.txt C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\uEnv.txt       174
---------- -------------------------------------------------------- ------
DFU_BOOT_CONF
2023-08-29 17:13:21 INFO: Number of USB DFU devices detected: 1
2023-08-29 17:13:21 INFO: Starting flashing for 1 identified devices
2023-08-29 17:13:21 INFO: Spawning 1 parallel processes
2023-08-29 17:13:23 INFO:           1-3.2 Sent! C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\tiboot3.bin
2023-08-29 17:13:25 INFO:           1-3.2 Sent! C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\tispl.bin
2023-08-29 17:13:28 INFO:           1-3.2 Sent! C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\u-boot.img
2023-08-29 17:13:33 INFO:           1-3.2 Sent! C:\ti\uboot-flash-writer\bin\am62xx-evm\hsfs\uEnv.txt
2023-08-29 17:13:35 INFO:           1-3.2 Sent! bin\am62xx-evm\hsfs\images\tiboot3.bin
2023-08-29 17:13:36 INFO:           1-3.2 Sent! bin\am62xx-evm\hsfs\images\tispl.bin
2023-08-29 17:13:38 INFO:           1-3.2 Sent! bin\am62xx-evm\hsfs\images\u-boot.img
2023-08-29 17:15:08 INFO:           1-3.2 Sent! bin\am62xx-evm\hsfs\images\rootfs.img
2023-08-29 17:15:08 INFO:           1-3.2 Flashing Successful...
2023-08-29 17:15:08 INFO: Flashed 1 out of 1 identified devices successfully...
2023-08-29 17:15:11 INFO: Exiting!!!

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
2024-04-23 17:40:57 INFO: Starting the flashing tool
2024-04-23 17:40:57 INFO: Validating the requirements before flashing...
2024-04-23 17:40:57 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-23 17:40:57 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-23 17:40:57 INFO: Found 4 flash images
<<DFU_FLASH_CONF
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
                      Alt Path                                                                                  Size   Offset Media Attributes
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
  tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin                                   295438      0x0 EMMC  raw,1,-   
                    tispl /home/suraj/Downloads/tispl.bin-am62xx-evm                                         1178343  0x80000 EMMC  raw,1,-   
        u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img                                         984939 0x280000 EMMC  raw,1,-   
agl-demo-platform-am62xx- /home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs.tar.gz 1034191331      0x0 EMMC  part,0,1  
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-23 17:40:57 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- ------------------------------------------------------------------------------------------------ ------
       Alt Path                                                                                               Size
---------- ------------------------------------------------------------------------------------------------ ------
bootloader /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin 333163
 tispl.bin /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin   960044
u-boot.img /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img  894876
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt       209
---------- ------------------------------------------------------------------------------------------------ ------
DFU_BOOT_CONF
    Dear Prashant,

    I revert back the changes in the source code and again i am flashing the images output is given above, so this process will take lot of time that i want to know because already more than 15 minutes has taken still not completed! So is it correct no!

    Regards,

    Suraj 

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    The dfu_flash.py script is unable to detect any DFU devices connected and so stuck after logging DFU_BOOT_CONF.

    Prashant Shivhare said:
    Also, please make sure you have put the board in DFU bootmode. If you run the following command and see similar output before running the dfu_flash.py script, it means the DFU device is connected and the dfu_flash.py script should be able to detect it.

    Have you confirmed this before running the dfu_flash.py script?

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I did not plug in the uart console and how do i confirm that the DFU device is connected and the dfu_flash.py script should be able to detect it.
    Please tell me the commands to check this.

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Do you see the same output on running dfu-util -l on your host machine?

    ~/ti/psdk/am62x/09.02.01.09/bin/DFU_flash
❯ sudo dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0451:6165] ver=0200, devnum=41, cfg=1, intf=0, path="1-3.4", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=41, cfg=1, intf=0, path="1-3.4", alt=0, name="bootloader", serial="01.00.00.00"

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo dfu-util -l
[sudo] password for suraj: 
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Found DFU: [0bda:5800] ver=0001, devnum=6, cfg=1, intf=0, path="1-3", alt=0, name="Camera DFU Device", serial="200901010001"


    Dear Prashant,

    This is the output:-

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    The output suggests you do not have the board connected in DFU bootmode. Did you change the bootmode settings on your board to DFU bootmode?

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
[sudo] password for suraj: 
2024-04-23 18:43:55 INFO: Starting the flashing tool
2024-04-23 18:43:55 INFO: Validating the requirements before flashing...
2024-04-23 18:43:55 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-23 18:43:55 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-23 18:43:55 INFO: Found 4 flash images
<<DFU_FLASH_CONF
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
                      Alt Path                                                                                  Size   Offset Media Attributes
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
  tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin                                   295438      0x0 EMMC  raw,1,-   
                    tispl /home/suraj/Downloads/tispl.bin-am62xx-evm                                         1178343  0x80000 EMMC  raw,1,-   
        u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img                                         984939 0x280000 EMMC  raw,1,-   
agl-demo-platform-am62xx- /home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs.tar.gz 1034191331      0x0 EMMC  part,0,1  
------------------------- ------------------------------------------------------------------------------- ---------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-23 18:43:55 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- ------------------------------------------------------------------------------------------------ ------
       Alt Path                                                                                               Size
---------- ------------------------------------------------------------------------------------------------ ------
bootloader /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin 333163
 tispl.bin /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin   960044
u-boot.img /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img  894876
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt       209
---------- ------------------------------------------------------------------------------------------------ ------
DFU_BOOT_CONF
2024-04-23 18:43:55 INFO: Number of USB DFU devices detected: 1
2024-04-23 18:43:55 INFO: Starting flashing for 1 identified devices
2024-04-23 18:43:55 INFO: Spawning 1 parallel processes
2024-04-23 18:43:57 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin
2024-04-23 18:44:00 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin
2024-04-23 18:44:03 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img
2024-04-23 18:44:07 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt
2024-04-23 18:44:09 INFO:             1-2 Sent! /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin
2024-04-23 18:44:11 INFO:             1-2 Sent! /home/suraj/Downloads/tispl.bin-am62xx-evm
2024-04-23 18:44:12 INFO:             1-2 Sent! /home/suraj/Downloads/u-boot-am62xx-evm.img
2024-04-23 18:44:21 ERROR:             1-2 Error! /home/suraj/Downloads/agl-demo-platform-am62xx-evm-20240416145915.rootfs.tar.gz
<<DFU_ERROR_LOGS
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #3 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 4096
Copying data from PC to DFU device
Download	[                         ]   1%     14778368 bytes failed!
state(10) = dfuERROR, status(14) = Something went wrong, but the device does not know what it was

dfu-util: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!

DFU_ERROR_LOGS
2024-04-23 18:44:21 INFO: Flashed 0 out of 1 identified devices successfully...
^C2024-04-23 18:45:50 INFO: Exiting!!!
    Dear Prashant,

    This is the logs, rootfs image got failed to flash whether offset value we need give different or remain same in flash-files.cfg!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    That's looking good. At least the tool is up and running successfully and could flash the U-Boot images successfully.

    Regarding the rootfs, you would need to partition the eMMC first. Have you already done this?

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    No partition i did not completed yet!

    Regards,
    Suraj

  • 0 in reply to Suraj Singh
    Intellectual 265 points 

    U-Boot 2023.04-g7d05009917 (Feb 01 2024 - 15:06:40 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM-P1 rev A
DRAM:  2 GiB
Core:  72 devices, 32 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> printenv partitions
partitions=name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
=> setenv uuid_gpt_disk ...4a36a0a4-fbce-4e58-aa47-2465759314b1...
=> setenv uuid_gpt_rootfs ...8ce658e3-d81f-40e2-85c0-23bac0a9f73d...
=> mmc list
mmc@fa10000: 0
mmc@fa00000: 1
=> gpt write mmc 0 ${partitions}
Writing GPT: Wrong uuid format for partition 0
Partition list incomplete
error!

    Dear Prashant,

    I tried for partitioning the emmc but its showing error, i have attached logs regarding partition can you check once!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    You would need to remove the dots from the "setenv uuid_gpt_*" commands. Attached are the sample partition logs

    => printenv partitions
partitions=name=rootfs,start=0,size=-,uuid=${uuid_gpt_rootfs}
=> setenv uuid_gpt_rootfs c4a7af12-62d7-434f-a3ef-20cb951104e6
=> gpt write mmc 0 $partitions
Writing GPT: success!
=> reset
resetting ...

    Please note after partitioning successfully, you cannot directly flash the compressed (.tar.gz) rootfs filesystem. This needs to be converted into a EXT4 filesystem which needs to be flashed.

    Please refer to the following reference instructions where you would need to modify the number passed to seek as per your uncompressed filesystem size.

    $ dd if=/dev/null of=rootfs.ext4 bs=1M seek=300
$ mkfs.ext4 -F rootfs.ext4
$ mkdir mnt_fs
$ sudo mount -t ext4 rootfs.ext4 mnt_fs
$ cd mnt_fs
$ sudo tar xvf ../tisdk-base-image-am62xx-evm.tar.xz
$ cd ..
$ sudo umount mnt_fs

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    ./etc/ssl/certs/E-Tugra_Certification_Authority.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/E-Tugra_Certification_Authority.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Trusted_Root_G4.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Trusted_Root_G4.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_High_Assurance_EV_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_High_Assurance_EV_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Global_Root_G3.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G3.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Global_Root_G2.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Global_Root_G2.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Global_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Global_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Assured_ID_Root_G3.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_G3.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Assured_ID_Root_G2.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_G2.crt’: No space left on device
tar: ./etc/ssl/certs/DigiCert_Assured_ID_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/DigiCert_Assured_ID_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/D-TRUST_Root_Class_3_CA_2_EV_2009.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/D-TRUST_Root_Class_3_CA_2_EV_2009.crt’: No space left on device
tar: ./etc/ssl/certs/D-TRUST_Root_Class_3_CA_2_2009.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/D-TRUST_Root_Class_3_CA_2_2009.crt’: No space left on device
tar: ./etc/ssl/certs/Cybertrust_Global_Root.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Cybertrust_Global_Root.crt’: No space left on device
tar: ./etc/ssl/certs/Comodo_AAA_Services_root.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Comodo_AAA_Services_root.crt’: No space left on device
tar: ./etc/ssl/certs/Certum_Trusted_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Certum_Trusted_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/Certum_Trusted_Network_CA_2.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Certum_Trusted_Network_CA_2.crt’: No space left on device
tar: ./etc/ssl/certs/Certum_Trusted_Network_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Certum_Trusted_Network_CA.crt’: No space left on device
tar: ./etc/ssl/certs/Certum_EC-384_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Certum_EC-384_CA.crt’: No space left on device
tar: ./etc/ssl/certs/Certigna_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Certigna_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/COMODO_RSA_Certification_Authority.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/COMODO_RSA_Certification_Authority.crt’: No space left on device
tar: ./etc/ssl/certs/COMODO_ECC_Certification_Authority.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/COMODO_ECC_Certification_Authority.crt’: No space left on device
tar: ./etc/ssl/certs/COMODO_Certification_Authority.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/COMODO_Certification_Authority.crt’: No space left on device
tar: ./etc/ssl/certs/CA_Disig_Root_R2.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/CA_Disig_Root_R2.crt’: No space left on device
tar: ./etc/ssl/certs/Buypass_Class_3_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Buypass_Class_3_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/Buypass_Class_2_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Buypass_Class_2_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/Baltimore_CyberTrust_Root.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Baltimore_CyberTrust_Root.crt’: No space left on device
tar: ./etc/ssl/certs/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Autoridad_de_Certificacion_Firmaprofesional_CIF_A62634068.crt’: No space left on device
tar: ./etc/ssl/certs/Atos_TrustedRoot_2011.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Atos_TrustedRoot_2011.crt’: No space left on device
tar: ./etc/ssl/certs/Amazon_Root_CA_4.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Amazon_Root_CA_4.crt’: No space left on device
tar: ./etc/ssl/certs/Amazon_Root_CA_3.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Amazon_Root_CA_3.crt’: No space left on device
tar: ./etc/ssl/certs/Amazon_Root_CA_2.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Amazon_Root_CA_2.crt’: No space left on device
tar: ./etc/ssl/certs/Amazon_Root_CA_1.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Amazon_Root_CA_1.crt’: No space left on device
tar: ./etc/ssl/certs/AffirmTrust_Premium_ECC.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AffirmTrust_Premium_ECC.crt’: No space left on device
tar: ./etc/ssl/certs/AffirmTrust_Premium.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AffirmTrust_Premium.crt’: No space left on device
tar: ./etc/ssl/certs/AffirmTrust_Networking.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AffirmTrust_Networking.crt’: No space left on device
tar: ./etc/ssl/certs/AffirmTrust_Commercial.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AffirmTrust_Commercial.crt’: No space left on device
tar: ./etc/ssl/certs/Actalis_Authentication_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/Actalis_Authentication_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/ANF_Secure_Server_Root_CA.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/ANF_Secure_Server_Root_CA.crt’: No space left on device
tar: ./etc/ssl/certs/AC_RAIZ_FNMT-RCM_SERVIDORES_SEGUROS.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AC_RAIZ_FNMT-RCM_SERVIDORES_SEGUROS.crt’: No space left on device
tar: ./etc/ssl/certs/AC_RAIZ_FNMT-RCM.pem: Cannot create symlink to ‘../../../usr/share/ca-certificates/mozilla/AC_RAIZ_FNMT-RCM.crt’: No space left on device
tar: ./etc/fonts/conf.d/65-fonts-persian.conf: Cannot create symlink to ‘../../../usr/share/fontconfig/conf.avail/65-fonts-persian.conf’: No space left on device
tar: ./etc/fonts/conf.d/30-metric-aliases.conf: Cannot create symlink to ‘../../../usr/share/fontconfig/conf.avail/30-metric-aliases.conf’: No space left on device
tar: ./etc/fonts/conf.d/20-unhint-small-vera.conf: Cannot create symlink to ‘../../../usr/share/fontconfig/conf.avail/20-unhint-small-vera.conf’: No space left on device
tar: ./etc/fonts/conf.d/10-scale-bitmap-fonts.conf: Cannot create symlink to ‘../../../usr/share/fontconfig/conf.avail/10-scale-bitmap-fonts.conf’: No space left on device
tar: ./etc/fonts/conf.d/10-hinting-slight.conf: Cannot create symlink to ‘../../../usr/share/fontconfig/conf.avail/10-hinting-slight.conf’: No space left on device

    Dear Prashant,

    After giving "sudo tar xvf ../tisdk-base-image-am62xx-evm.tar.xz" this command giving this output. What i am missing the steps!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    Intellectual 265 points

    Dear Prashant,

    File is converted into a EXT4 filesystem which needs to be flashed. Now, i need to change anything, anywhere or directly i can flash the files!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    If the EXT4 filesystem is created successfully, then you are good to go. You would only need to uncomment the rootfs line and update the path

    Looking at the size of your compressed (.tar.gz) rootfs ~1GB, I believe the EXT4 filesystem size would be around ~8GB so the flashing might take 10-15 minutes. You can keep the UART console open to see the flashing progress.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    You told to update the path! Which path i need to change! Should i plug in uart console!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Suraj Singh said:
    You told to update the path!

    I meant update the --file value to your EXT4 rootfs path.

    Suraj Singh said:
    Should i plug in uart console!

    You can open the UART console to see the flashing logs.

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    In flash-files.cfg you told to uncomment the rootfs line, that i did now you are telling to update the path means in dfu_flash.py i need update the the path! Please clarify.

        # Path to the DFU boot images
    dfu_tiboot3 = DEVICE_PATH / "tiboot3.bin"
    dfu_tispl   = DEVICE_PATH / "tispl.bin"
    dfu_uboot   = DEVICE_PATH / "u-boot.img"

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    I did not say anywhere to update the path in the source code. I mean the following

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear prashant,

    still not flashed how much time it will take! my rootfs.ext4 file size is 2.7gb.

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points
    Suraj Singh said:
    still not flashed how much time it will take! my rootfs.ext4 file size is 2.7gb.

    Can you share the captured UART console logs?

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
2024-04-24 17:57:49 INFO: Starting the flashing tool
2024-04-24 17:57:49 INFO: Validating the requirements before flashing...
2024-04-24 17:57:49 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-24 17:57:49 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-24 17:57:49 INFO: Found 3 flash images
<<DFU_FLASH_CONF
----------------------- ------------------------------------------------- ------- -------- ----- ----------
                    Alt Path                                                 Size   Offset Media Attributes
----------------------- ------------------------------------------------- ------- -------- ----- ----------
tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin  295438      0x0 EMMC  raw,1,-   
                  tispl /home/suraj/Downloads/tispl.bin-am62xx-evm        1178343  0x80000 EMMC  raw,1,-   
      u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img        984939 0x280000 EMMC  raw,1,-   
----------------------- ------------------------------------------------- ------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-24 17:57:49 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- ------------------------------------------------------------------------------------------------ ------
       Alt Path                                                                                               Size
---------- ------------------------------------------------------------------------------------------------ ------
bootloader /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin 333163
 tispl.bin /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin   960044
u-boot.img /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img  894876
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt       174
---------- ------------------------------------------------------------------------------------------------ ------
DFU_BOOT_CONF
2024-04-24 17:57:49 INFO: Number of USB DFU devices detected: 1
2024-04-24 17:57:49 INFO: Starting flashing for 1 identified devices
2024-04-24 17:57:49 INFO: Spawning 1 parallel processes
2024-04-24 17:57:51 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin
2024-04-24 17:57:54 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin
2024-04-24 17:57:57 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img
2024-04-24 17:58:01 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt
2024-04-24 17:58:03 INFO:             1-2 Sent! /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin
2024-04-24 17:58:05 INFO:             1-2 Sent! /home/suraj/Downloads/tispl.bin-am62xx-evm
2024-04-24 17:58:06 INFO:             1-2 Sent! /home/suraj/Downloads/u-boot-am62xx-evm.img
2024-04-24 17:58:06 INFO:             1-2 Flashing Successful...
2024-04-24 17:58:06 INFO: Flashed 1 out of 1 identified devices successfully...
    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points 

    <<DFU_FLASH_CONF
----------------------- ------------------------------------------------- ------- -------- ----- ----------
                    Alt Path                                                 Size   Offset Media Attributes
----------------------- ------------------------------------------------- ------- -------- ----- ----------
tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin  295438      0x0 EMMC  raw,1,-   
                  tispl /home/suraj/Downloads/tispl.bin-am62xx-evm        1178343  0x80000 EMMC  raw,1,-   
      u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img        984939 0x280000 EMMC  raw,1,-   
----------------------- ------------------------------------------------- ------- -------- ----- ----------
DFU_FLASH_CONF

    You should see in the logs that you are not flashing the rootfs. The flashing was successful for the three U-Boot images uncommented in the flash-files.cfg. If you want to flash rootfs then include the rootfs config line as well.

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    For flashing the rootfs image which image i have to include that new generated rootfs.ext4 right.But it showing error.

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
2024-04-24 18:10:58 INFO: Starting the flashing tool
2024-04-24 18:10:58 INFO: Validating the requirements before flashing...
2024-04-24 18:10:58 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-24 18:10:58 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-24 18:10:58 INFO: Found 4 flash images
<<DFU_FLASH_CONF
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
                    Alt Path                                                    Size   Offset Media Attributes
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin     295438      0x0 EMMC  raw,1,-   
                  tispl /home/suraj/Downloads/tispl.bin-am62xx-evm           1178343  0x80000 EMMC  raw,1,-   
      u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img           984939 0x280000 EMMC  raw,1,-   
                 rootfs /home/suraj/Downloads/rootfs.ext4                 2684354560      0x0 EMMC  part,0,1  
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-24 18:10:58 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- ------------------------------------------------------------------------------------------------ ------
       Alt Path                                                                                               Size
---------- ------------------------------------------------------------------------------------------------ ------
bootloader /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin 333163
 tispl.bin /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin   960044
u-boot.img /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img  894876
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt       190
---------- ------------------------------------------------------------------------------------------------ ------
DFU_BOOT_CONF
2024-04-24 18:10:58 INFO: Number of USB DFU devices detected: 1
2024-04-24 18:10:58 INFO: Starting flashing for 1 identified devices
2024-04-24 18:10:58 INFO: Spawning 1 parallel processes
2024-04-24 18:10:59 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin
2024-04-24 18:11:02 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin
2024-04-24 18:11:06 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img
2024-04-24 18:11:10 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt
2024-04-24 18:11:12 INFO:             1-2 Sent! /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin
2024-04-24 18:11:13 INFO:             1-2 Sent! /home/suraj/Downloads/tispl.bin-am62xx-evm
2024-04-24 18:11:14 INFO:             1-2 Sent! /home/suraj/Downloads/u-boot-am62xx-evm.img
2024-04-24 18:11:14 ERROR:             1-2 Error! /home/suraj/Downloads/rootfs.ext4
<<DFU_ERROR_LOGS
dfu-util 0.9

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2016 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/


dfu-util: File size is too big: Success

DFU_ERROR_LOGS
2024-04-24 18:11:14 INFO: Flashed 0 out of 1 identified devices successfully...
     

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    Can you please use the dfu-util v0.11? The pre-built binaries are available here: https://dfu-util.sourceforge.net/releases/dfu-util-0.11-binaries.tar.xz

    After downloading & extracting, you will find the Linux dfu-util binary in linux-amd64 folder as shown

    ~/dfu-util-0.11-binaries/linux-amd64
❯ /bin/ls -l dfu-util
-rwxr-xr-x 1 p-shivhare p-shivhare 217592 Sep  6  2021 dfu-util

~/dfu-util-0.11-binaries/linux-amd64
❯ ./dfu-util -l
dfu-util 0.11

Copyright 2005-2009 Weston Schmidt, Harald Welte and OpenMoko Inc.
Copyright 2010-2021 Tormod Volden and Stefan Schmidt
This program is Free Software and has ABSOLUTELY NO WARRANTY
Please report bugs to http://sourceforge.net/p/dfu-util/tickets/

    You can then update the DFU_UTIL_PATH in "src/constants.py" file to the downloaded dfu-util so that the script picks the downloaded one

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I updated the DFU_UTIL_PATH in "src/constants.py" file but while flashing it si showing error.

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
Traceback (most recent call last):
  File "/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/dfu_flash.py", line 8, in <module>
    from src.flash import dfu_main
  File "/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/src/flash.py", line 8, in <module>
    from src.constants import DFU_UTIL_PATH, DFU_SOCID_REG_EXP, BIN_DIR_PATH
  File "/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/src/constants.py", line 28
    DFU_UTIL_PATH = /home/suraj/Downloads/dfu-util-0.11-binaries
                    ^
SyntaxError: invalid syntax

    # Directory containing different binaries
BIN_DIR_PATH = PROJECT_DIR_PATH / "bin"

# Path of the dfu-util
DFU_UTIL_PATH =home/suraj/Downloads/dfu-util-0.11-binaries

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    DFU_UTIL_PATH =home/suraj/Downloads/dfu-util-0.11-binaries

    This needs to be DFU_UTIL_PATH = "home/suraj/Downloads/dfu-util-0.11-binaries/linux-amd64/dfu-util"

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points 

    suraj@suraj-HP-Laptop-15s-fr2xxx:/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash$ sudo python3 dfu_flash.py -d am62xx-evm -t hsfs -c /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg
[sudo] password for suraj: 
2024-04-25 10:18:52 INFO: Starting the flashing tool
2024-04-25 10:18:52 INFO: Validating the requirements before flashing...
2024-04-25 10:18:52 INFO: Validated the CLI arguments and the paths to the DFU boot binaries
2024-04-25 10:18:52 INFO: Parsing the flash configuration file {/opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/flash-files.cfg}...
2024-04-25 10:18:52 INFO: Found 4 flash images
<<DFU_FLASH_CONF
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
                    Alt Path                                                    Size   Offset Media Attributes
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
tiboot3-am62x-hs-fs-evm /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin     295438      0x0 EMMC  raw,1,-   
                  tispl /home/suraj/Downloads/tispl.bin-am62xx-evm           1178343  0x80000 EMMC  raw,1,-   
      u-boot-am62xx-evm /home/suraj/Downloads/u-boot-am62xx-evm.img           984939 0x280000 EMMC  raw,1,-   
                 rootfs /home/suraj/Downloads/rootfs.ext4                 2684354560      0x0 EMMC  part,0,1  
----------------------- ------------------------------------------------- ---------- -------- ----- ----------
DFU_FLASH_CONF
2024-04-25 10:18:52 INFO: Found 4 boot images
<<DFU_BOOT_CONF
---------- ------------------------------------------------------------------------------------------------ ------
       Alt Path                                                                                               Size
---------- ------------------------------------------------------------------------------------------------ ------
bootloader /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin 333163
 tispl.bin /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin   960044
u-boot.img /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img  894876
  uEnv.txt /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt       190
---------- ------------------------------------------------------------------------------------------------ ------
DFU_BOOT_CONF
2024-04-25 10:18:52 INFO: Number of USB DFU devices detected: 1
2024-04-25 10:18:52 INFO: Starting flashing for 1 identified devices
2024-04-25 10:18:52 INFO: Spawning 1 parallel processes
2024-04-25 10:18:53 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tiboot3.bin
2024-04-25 10:18:56 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/tispl.bin
2024-04-25 10:19:00 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/u-boot.img
2024-04-25 10:19:04 INFO:             1-2 Sent! /opt/ti-processor-sdk-linux-am62xx-evm-09.02.01.09/bin/DFU_flash/bin/am62xx-evm/hsfs/uEnv.txt
2024-04-25 10:19:06 INFO:             1-2 Sent! /home/suraj/Downloads/tiboot3-am62x-hs-fs-evm.bin
2024-04-25 10:19:07 INFO:             1-2 Sent! /home/suraj/Downloads/tispl.bin-am62xx-evm
2024-04-25 10:19:08 INFO:             1-2 Sent! /home/suraj/Downloads/u-boot-am62xx-evm.img
2024-04-25 10:32:08 INFO:             1-2 Sent! /home/suraj/Downloads/rootfs.ext4
2024-04-25 10:32:08 INFO:             1-2 Flashing Successful...
2024-04-25 10:32:08 INFO: Flashed 1 out of 1 identified devices successfully...
    Dear Prashant,

    Here only its stopped more than half an hour so whether flashing is happening or how long it will take any idea!

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    Hi Suraj,

    2024-04-25 10:32:08 INFO: 1-2 Flashing Successful...
    2024-04-25 10:32:08 INFO: Flashed 1 out of 1 identified devices successfully...

    This means the flashing is successful. The script is just waiting for next set of devices to be flashed. You can press "Ctrl +C" to terminate the script execution.

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    After flashing i changed the boot mode to emmc mode and i was trying to boot but its not booting, i attached logs and also i changed the environment setup but still not booting!

    U-Boot SPL 2023.04-g7d05009917 (Feb 01 2024 - 15:06:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.1--v09.02.01 (Kool Koala)')
SPL initial stack usage: 13416 bytes
Trying to boot from MMC1
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.10.0(release):v2.10.0-367-g00f1ec6b87-dirty
NOTICE:  BL31: Built : 15:06:40, Feb  1 2024

U-Boot SPL 2023.04-g7d05009917 (Feb 01 2024 - 15:06:40 +0000)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.2.1--v09.02.01 (Kool Koala)')
SPL initial stack usage: 1856 bytes
MMC: no card present
** Bad device specification mmc 1 **
Couldn't find partition mmc 1:1
Error: could not access storage.
Trying to boot from MMC1
Authentication passed
Authentication passed


U-Boot 2023.04-g7d05009917 (Feb 01 2024 - 15:06:40 +0000)

SoC:   AM62X SR1.0 HS-FS
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Board: AM62B-SKEVM-P1 rev A
DRAM:  2 GiB
Core:  72 devices, 32 uclasses, devicetree: separate
MMC:   mmc@fa10000: 0, mmc@fa00000: 1
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@8000000port@1
Hit any key to stop autoboot:  0 
=> setenv mmcdev 0
=> setenv bootpart 0:2
=> boot
switch to partitions #0, OK
mmc0(part 0) is current device
SD/MMC found on device 0
Failed to load 'boot.scr'
Can't set block device
** Invalid partition 2 **
## Error: "main_cpsw0_qsgmii_phyinit" not defined
** Invalid partition 2 **
Couldn't find partition mmc 0:2
Can't set block device
** Invalid partition 2 **
Couldn't find partition mmc 0:2
Can't set block device
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
Bad Linux ARM64 Image magic!
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
MMC: no card present
No EFI system partition
No EFI system partition
Failed to persist EFI variables
BootOrder not defined
EFI boot manager: Cannot load any image
MMC: no card present
starting USB...
Bus usb@31100000: generic_phy_get_bulk : no phys property
Register 1000840 NbrPorts 1
Starting the controller
USB XHCI 1.10
scanning bus usb@31100000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
ethernet@8000000port@1 Waiting for PHY auto negotiation to complete......... TIMEOUT !
am65_cpsw_nuss_port ethernet@8000000port@1: phy_startup failed
am65_cpsw_nuss_port ethernet@8000000port@1: am65_cpsw_start end error
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-1c-63-49-22-4f-13

    Regards,

    Suraj

  • 0 in reply to Suraj Singh
    TI__Guru 50351 points

    => setenv mmcdev 0
    => setenv bootpart 0:2
    => boot

    You have flashed Linux in 1st partition. So, you would need to use

    => setenv mmcdev 0
=> setenv bootpart 0:1
=> boot

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Hello Prashant,

    I wanted to reach out and say a big thank you for your help on the TI Forum. Your assistance has been incredibly helpful, and I'm grateful for your expertise and willingness to share it.

    Your contributions make a real difference in the community, and I wanted to express my appreciation for the time and effort you put into helping others like me. Your knowledge and support are invaluable, and I'm thankful to have you as part of the forum.

    Thanks again for all your help. It's truly appreciated!

    Best regards,
    Suraj