• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 6015 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[FAQ] [AM6XX]: How to check if device type is HS-SE, HS-FS or GP?

Vaibhav Kumar
Guru 56354 points

Part Number: PROCESSOR-SDK-AM62A
Other Parts Discussed in Thread: PROCESSOR-SDK-AM62X, PROCESSOR-SDK-AM64X

Hi, 

There is a concern around figuring out if the device in use is HS-SE, HS-FS or GP.

The above factor plays a vital role in selecting the image for SBL programming.

Lets have a look at one of the ways by which you can figure out the device type.

Thanks,

Vaibhav

  • +1
    TI__Guru 56354 points

    Here's a simple explanation which will help you figure out the device type.

    During the step of Flash SOC Initialization Binary you must have seen some values on UART COM port as shown in the image below.


    Follow the steps here:

    • Copy all the data content before character “C” and save it to a file called data.txt

    • Download the python script by clicking here

    • Once you have the python script and the data.txt in the same folder, simply run the command python uart_boot_socid.py data.txt

    • Now you will be able to figure out by reading the value of Device Type

    Have a look at a sample output by running the script shown in the image below.

  • 0 in reply to Vaibhav Kumar
    TI__Guru* 82011 points

    The device type can be checked using USB DFU bootmode as well with the following steps

    1) Put the board in the USB DFU bootmode and run the following command

    ❯ 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=18, cfg=1, intf=0, path="1-5.1.2", alt=1, name="SocId", serial="01.00.00.00"
Found DFU: [0451:6165] ver=0200, devnum=18, cfg=1, intf=0, path="1-5.1.2", alt=0, name="bootloader", serial="01.00.00.00"

    2) Fetch the data with the following command

    ❯ dfu-util -a SocId -U socid.bin
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/

Opening DFU capable USB device...
Device ID 0451:6165
Device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Interface #1 ...
Determining device status...
DFU state(2) = dfuIDLE, status(0) = No error condition is present
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from DFU device to PC
Upload  [=========================] 100%          200 bytes
Upload done.
Received a total of 200 bytes

    3) Convert the data to the hex and run the script from the above response

    ❯ xxd -p -c 1000 socid.bin > socid.txt
❯ python3 7080.uart_boot_socid.py socid.txt
-----------------------
SoC ID Header Info:
-----------------------
NumBlocks            : [2]
-----------------------
SoC ID Public ROM Info:
-----------------------
SubBlockId           :
SubBlockSize         :
DeviceName           : am62px
DeviceType           : HSFS
DMSC ROM Version     : [0, 1, 0, 0]
R5 ROM Version       : [0, 1, 0, 0]
-----------------------
SoC ID Secure ROM Info:
-----------------------
Sec SubBlockId       : 2
Sec SubBlockSize     : 166
Sec Prime            : 0
Sec Key Revision     : 0
Sec Key Count        : 0
Sec TI MPK Hash      : ade976fcfd18ebf60229bee902edcec6d5fd07d1b2101101198c7ff4f552a9436bda045679d54baa04a1cb85d16fffe0f21e32f7f341c769534d7a560364a908
Sec Cust MPK Hash    : ad0bc40b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Sec Unique ID        : 26d580c8f62a17ab0222bd7a07ad21c2bc3e37af017dd500b478d7a40b615097