AM625: AM625: Android SDK Flashing Instruction ValueError

Alan Wen

Prodigy 70 points

Part Number: AM625

Tool/software:

Host: Ubuntu 22.04 (python3.10.x)

Board: SK-AM625 EVM

I have been working on SK-AM625 EVK board on Android SDK 09_02_00 and I tried to build the SDK myself from

1.3. Flashing Instruction — Processor SDK AM62x Documentation

I got a erro message ValueError: The device has no langid (permission issue, no string descriptors supported or device error) while running snagrecover on host using binaries built locally.

Starting recovery of am625 board
Installing firmware tiboot3
Searching for partition id...
Downloading file...
Done
Done installing firmware tiboot3
Installing firmware tispl
Searching for partition id...
Traceback (most recent call last):
  File "/home/user/.local/bin/snagrecover", line 8, in <module>
    sys.exit(cli())
  File "/home/user/.local/lib/python3.10/site-packages/snagrecover/cli.py", line 147, in cli
    am62x_recovery()
  File "/home/user/.local/lib/python3.10/site-packages/snagrecover/recoveries/am62x.py", line 22, in main
    run_firmware(dev, "tispl")
  File "/home/user/.local/lib/python3.10/site-packages/snagrecover/firmware/firmware.py", line 110, in run_firmware
    am62x_run(port, fw_name, fw_blob)
  File "/home/user/.local/lib/python3.10/site-packages/snagrecover/firmware/firmware.py", line 70, in am62x_run
    partid = dfu.search_partid(dev, partname)
  File "/home/user/.local/lib/python3.10/site-packages/snagrecover/protocols/dfu.py", line 36, in search_partid
    desc = usb.util.get_string(dev, intf.iInterface)
  File "/home/user/.local/lib/python3.10/site-packages/usb/util.py", line 313, in get_string
    raise ValueError("The device has no langid"
ValueError: The device has no langid (permission issue, no string descriptors supported or device error)

But the DFU intruction works on the pre-built binaries from SDK download page with the command below:

cd AM62x_09.02.00_emmc
snagrecover -s am625 -f ./am62x-sk-evm.yaml

BTW, in eMMC flashing instructions step 4. running snagrecover for host & step 7. run flashall.sh, I could not find the path of the binaries directories as out/target/product/am62x.

I found the am62x-sk-evm.yaml from $WORK_DIR/ti-aosp-14/device/ti/am62x/config/dfu, is there any configuration I should setup before Build Instructions ?

I'm not familiar with the binman code and thus do not understand the nature of the problem. Maybe you guys could help me out ?

Thanks in advance !

6 months ago

0 Mattijs Korpershoek 6 months ago

TI__Intellectual 1495 points

Hi Alan,

Do you have any logs from serial console on the device side ?

It looks like the first upload via snagrecover (of tiboot3.bin) was sucessfull, and then tispl failed to be loaded.
This can mean that tiboot3.bin crashed/failed to start DFU mode.

If it crashes, you won't see any logs. Crashing can happen if the wrong tiboot3 has been taken (GP vs HS-FS).

It's also possible that your own rebuild bootloaders don't have DFU support.
DFU support is enabled via a different defconfig for tiboot3. Instead of using am62x_evm_r5_defconfig, we use am62x_evm_r5_usbdfu_defconfig

This is needed because tiboot3 has space constraints.

So, if we modify the instructions from https://software-dl.ti.com/processor-sdk-android/esd/AM62X/09_02_00/docs/android/Overview_Building_the_SDK.html#android-build-bootloaders a bit to include the DFU-enabled configurations:

3. Build tiboot3.bin:

$ cd ${YOUR_PATH}/ti-bootloader-aosp/ti-u-boot/
$ make ARCH=arm am62x_evm_r5_usbdfu_defconfig
$ make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabihf- \
       BINMAN_INDIRS=${YOUR_PATH}/ti-bootloader-aosp/ti-linux-firmware

The documentation is not great about this, we will consider updating it in the future.

Hope that helps,
Mattijs

0 Alan Wen 6 months ago in reply to Mattijs Korpershoek

Prodigy 70 points

I've tried to link the tiboot3.bin to tiboot3-am62x-gp-evm.bin and it works.

But there are more problems about flashall.sh command the instruction used, it seems to `userdata.img` & `super.img` & `boot.img` etc., I'm not sure that the command in the flashing binaries instructions is totally correct.

And as I mention before, I can't find the out/target/product/am62x directory, maybe there is still something wrong with the instrcutions, please help.

Thanks.

0 Mattijs Korpershoek 6 months ago in reply to Alan Wen

TI__Intellectual 1495 points

Hi Alan,

Can you please share the exact steps you have performed to run `flashall.sh` ?

`flashall.sh` is designed to run from a build output folder (such as out/target/product/am62x)

Did you follow the build instructions to rebuild Android from:
https://software-dl.ti.com/processor-sdk-android/esd/AM62X/09_02_00/docs/android/Overview_Building_the_SDK.html#android-file-system

Especially, can you confirm you rebuild the Android File System following:
https://software-dl.ti.com/processor-sdk-android/esd/AM62X/09_02_00/docs/android/Overview_Building_the_SDK.html#android-build-aosp

If so, please share the commands you have done and the console output of your build commands.

0 Alan Wen 6 months ago in reply to Mattijs Korpershoek

Prodigy 70 points

I did follow the building instructions step by step and still can't find the output folder named out/target/product/am62x on my PC.

Each step was built successfully with a #### build completed successfully #### comment in the end.

As I finished the 1.2.3.3 Android File System instructions with lunch am62x-userdebug, the out directory at ${YOUR_PATH}/ti-aosp-14/out/ only had those data as below.

Do you have any idea about the output folder being created by which command or step ?

And where I found the flashall.sh is at here

And some console output as below:

Thanks.

0 Mattijs Korpershoek 6 months ago in reply to Alan Wen

TI__Intellectual 1495 points

Hello, can you please post a console output after running the "m" command from:

cd ${YOUR_PATH}/ti-aosp-14
$ source build/envsetup.sh
$ lunch <BUILD_TARGET>
$ m

0 Alan Wen 6 months ago in reply to Mattijs Korpershoek

Prodigy 70 points

It seems to be crashed at the last task: analyzing Android.bp files and generating ninja file at out/soong/build.ninja

While calling the `m` command to make file, there is a message about using threads `If you run into segfaults or other errors, try reducing your -j value.`

Is it correct to use the argument as `m -j <value>` ?

I didn't see the threads usage reducing after calling this command. Please help.

Thanks.

0 Mattijs Korpershoek 6 months ago in reply to Alan Wen

TI__Intellectual 1495 points

Hi Alan,

According to the documentation:
https://software-dl.ti.com/processor-sdk-android/esd/AM62X/09_02_00/docs/android/Overview_Building_the_SDK.html#build-pc-setup

Build PC setup states to follow:
https://source.android.com/setup/build/requirements

Which, in section https://source.android.com/docs/setup/start/requirements#hardware-requirements says:

> A minimum of 64 GB of RAM. Google uses 72-core machines with 64 GB of RAM to build Android

If it crashes during "Analyzing Android.bp files", it uses crashes with an Out Of Memory error.

How many RAM does your build PC has?

If you have less than 64GB of RAM, please consider upgrading your machine to following the hardware requirements for building Android.

Processors

Processors forum

AM625: AM625: Android SDK Flashing Instruction ValueError