• State Resolved
  • Replies 85 replies
  • Answers 3 answers
  • Subscribers 98 subscribers
  • Views 1191 views
  • Users 0 members are here
Support feedback
Options
Options
Related

AM625: AM62x Secure Boot Stuck at "Starting Keywriting" — VPP Hardware Toggle Issue

Kapil Vyas
Prodigy 20 points
Part Number: AM625

Tool/software:

Hello TI Support Team,

I am implementing secure boot on a custom AM62x-based board using dummy keys (HS‑FS variant) based on TI’s AM62x secure boot guide. I have followed all documentation steps, including:

  • Generating tiboot3.bin (with embedded certificate) via gen_keywr_cert.sh.

  • Flashing the OTP keywriter/SBL (tiboot3.bin) via DFU as described in the official guide.

  • Monitoring UART output during secure key provisioning.
    Upon flashing, the console output halts at:
    "Starting Keywriting"

    However, it never proceeds to:

    Starting Keywriting
    Enabled VPP
    keys Certificate found: ...
    Keywriter Debug Response: 0x0
    Success Programming Keys
    My Question:
    1) Is the hardware-level presence and assertion of the 1.8 V VPP rail on MSP_8 strictly required, even when using dummy keys, for the secure boot keywriting process to proceed? Or is there any software-based mechanism or alternative configuration that allows keywriting to continue without hardware VPP?

    Regards,
    Kapil
  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    This is again not the correct certificate as the md5sum differs from the md5sum you shared in your previous response

    ❯ md5sum 2860.final_certificate.bin.txt
c3d93114b0694851d8fa52b19b27b41e  2860.final_certificate.bin.txt
❯ openssl asn1parse -in 2860.final_certificate.bin.txt -inform DER
    0:d=0  hl=4 l=1664 cons: SEQUENCE
    4:d=1  hl=4 l=1128 cons: SEQUENCE
    8:d=2  hl=2 l=   3 cons: cont [ 0 ]
   10:d=3  hl=2 l=   1 prim: INTEGER           :02
   13:d=2  hl=2 l=  20 prim: INTEGER           :4663719957B7DFE07CC2683B47296DF403D0E62A
   35:d=2  hl=2 l=  13 cons: SEQUENCE
   37:d=3  hl=2 l=   9 prim: OBJECT            :sha512WithRSAEncryption
Error in encoding
133043991890816:error:0D07209B:asn1 encoding routines:ASN1_get_object:too long:crypto/asn1/asn1_lib.c:91:

    I am not sure what is going on.

    Please generate the certificate, run those md5sum & openssl commands, and share the same certificate to me for cross verifying. In fact, please share the generated certificate and the built keywriter binary as well (tiboot3.bin).

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    we regenrate final_certificate.bin file 

    $ ./gen_keywr_cert.sh -t tifek/ti_fek_public.pem --msv 0xC0FFE -b-def --bmek-def -s-def --smek-def --keycnt 2 --keyrev 1
# Using MSV[19:0]: 0x000C0FFE
INFO: Using default BMPK for programming
INFO: Using default BMEK for programming
INFO: Using default SMPK for programming
INFO: Using default SMEK for programming
# Using Key Count: 0x00000003
# Using Key Rev: 0x00000001
Generating Dual signed certificate!!
GEN: AES256 key generated, since not provided
# encrypt aes256 key with tifek public part
# encrypt SMPK-priv signed aes256 key(hash) with tifek public part
# encrypt smpk-pub hash using aes256 key
writing RSA key
# encrypt smek (sym key) using aes256 key
# encrypt BMPK-priv signed aes256 key(hash) with tifek public part
# encrypt bmpk-pub hash using aes256 key
writing RSA key
# encrypt bmek (sym key) using aes256 key
1668	secondary_cert.bin
5383	primary_cert.bin
7051	../../x509cert/final_certificate.bin
# SHA512 Hashes of keys are stored in verify_hash.csv for reference..

    This is the md5sum terminal output

    $ md5sum -b  final_certificate.bin
689992a645b1185d42d1ff29fcce0015 *final_certificate.bin

    This is the openssl command terminal output

    $ openssl asn1parse -in final_certificate.bin -inform DER
    0:d=0  hl=4 l=1664 cons: SEQUENCE          
    4:d=1  hl=4 l=1128 cons: SEQUENCE          
    8:d=2  hl=2 l=   3 cons: cont [ 0 ]        
   10:d=3  hl=2 l=   1 prim: INTEGER           :02
   13:d=2  hl=2 l=  20 prim: INTEGER           :542CE09F3418A456448717DB05C2C8C14DFF2786
   35:d=2  hl=2 l=  13 cons: SEQUENCE          
   37:d=3  hl=2 l=   9 prim: OBJECT            :sha512WithRSAEncryption
   48:d=3  hl=2 l=   0 prim: NULL              
   50:d=2  hl=3 l= 191 cons: SEQUENCE          
   53:d=3  hl=2 l=  11 cons: SET               
   55:d=4  hl=2 l=   9 cons: SEQUENCE          
   57:d=5  hl=2 l=   3 prim: OBJECT            :countryName
   62:d=5  hl=2 l=   2 prim: PRINTABLESTRING   :oR
   66:d=3  hl=2 l=  11 cons: SET               
   68:d=4  hl=2 l=   9 cons: SEQUENCE          
   70:d=5  hl=2 l=   3 prim: OBJECT            :stateOrProvinceName
   75:d=5  hl=2 l=   2 prim: UTF8STRING        :rx
   79:d=3  hl=2 l=  22 cons: SET               
   81:d=4  hl=2 l=  20 cons: SEQUENCE          
   83:d=5  hl=2 l=   3 prim: OBJECT            :localityName
   88:d=5  hl=2 l=  13 prim: UTF8STRING        :gQE843yQV0sag
  103:d=3  hl=2 l=  43 cons: SET               
  105:d=4  hl=2 l=  41 cons: SEQUENCE          
  107:d=5  hl=2 l=   3 prim: OBJECT            :organizationName
  112:d=5  hl=2 l=  34 prim: UTF8STRING        :dqhGYAQ2Y4gFfCq0t1yABCYxex9eAxt71f
  148:d=3  hl=2 l=  17 cons: SET               
  150:d=4  hl=2 l=  15 cons: SEQUENCE          
  152:d=5  hl=2 l=   3 prim: OBJECT            :organizationalUnitName
  157:d=5  hl=2 l=   8 prim: UTF8STRING        :a87RB35W
  167:d=3  hl=2 l=  24 cons: SET               
  169:d=4  hl=2 l=  22 cons: SEQUENCE          
  171:d=5  hl=2 l=   3 prim: OBJECT            :commonName
  176:d=5  hl=2 l=  15 prim: UTF8STRING        :x0FSqGTPWbGpuiV
  193:d=3  hl=2 l=  49 cons: SET               
  195:d=4  hl=2 l=  47 cons: SEQUENCE          
  197:d=5  hl=2 l=   9 prim: OBJECT            :emailAddress
  208:d=5  hl=2 l=  34 prim: IA5STRING         :kFp5uGcgWXxcfxi@vsHs9C9qQWGrBs.com
  244:d=2  hl=2 l=  30 cons: SEQUENCE          
  246:d=3  hl=2 l=  13 prim: UTCTIME           :250818135242Z
  261:d=3  hl=2 l=  13 prim: UTCTIME           :250917135242Z
  276:d=2  hl=3 l= 191 cons: SEQUENCE          
  279:d=3  hl=2 l=  11 cons: SET               
  281:d=4  hl=2 l=   9 cons: SEQUENCE          
  283:d=5  hl=2 l=   3 prim: OBJECT            :countryName
  288:d=5  hl=2 l=   2 prim: PRINTABLESTRING   :oR
  292:d=3  hl=2 l=  11 cons: SET               
  294:d=4  hl=2 l=   9 cons: SEQUENCE          
  296:d=5  hl=2 l=   3 prim: OBJECT            :stateOrProvinceName
  301:d=5  hl=2 l=   2 prim: UTF8STRING        :rx
  305:d=3  hl=2 l=  22 cons: SET               
  307:d=4  hl=2 l=  20 cons: SEQUENCE          
  309:d=5  hl=2 l=   3 prim: OBJECT            :localityName
  314:d=5  hl=2 l=  13 prim: UTF8STRING        :gQE843yQV0sag
  329:d=3  hl=2 l=  43 cons: SET               
  331:d=4  hl=2 l=  41 cons: SEQUENCE          
  333:d=5  hl=2 l=   3 prim: OBJECT            :organizationName
  338:d=5  hl=2 l=  34 prim: UTF8STRING        :dqhGYAQ2Y4gFfCq0t1yABCYxex9eAxt71f
  374:d=3  hl=2 l=  17 cons: SET               
  376:d=4  hl=2 l=  15 cons: SEQUENCE          
  378:d=5  hl=2 l=   3 prim: OBJECT            :organizationalUnitName
  383:d=5  hl=2 l=   8 prim: UTF8STRING        :a87RB35W
  393:d=3  hl=2 l=  24 cons: SET               
  395:d=4  hl=2 l=  22 cons: SEQUENCE          
  397:d=5  hl=2 l=   3 prim: OBJECT            :commonName
  402:d=5  hl=2 l=  15 prim: UTF8STRING        :x0FSqGTPWbGpuiV
  419:d=3  hl=2 l=  49 cons: SET               
  421:d=4  hl=2 l=  47 cons: SEQUENCE          
  423:d=5  hl=2 l=   9 prim: OBJECT            :emailAddress
  434:d=5  hl=2 l=  34 prim: IA5STRING         :kFp5uGcgWXxcfxi@vsHs9C9qQWGrBs.com
  470:d=2  hl=4 l= 546 cons: SEQUENCE          
  474:d=3  hl=2 l=  13 cons: SEQUENCE          
  476:d=4  hl=2 l=   9 prim: OBJECT            :rsaEncryption
  487:d=4  hl=2 l=   0 prim: NULL              
  489:d=3  hl=4 l= 527 prim: BIT STRING        
 1020:d=2  hl=2 l= 114 cons: cont [ 3 ]        
 1022:d=3  hl=2 l= 112 cons: SEQUENCE          
 1024:d=4  hl=2 l=  12 cons: SEQUENCE          
 1026:d=5  hl=2 l=   3 prim: OBJECT            :X509v3 Basic Constraints
 1031:d=5  hl=2 l=   5 prim: OCTET STRING      [HEX DUMP]:30030101FF
 1038:d=4  hl=2 l=  96 cons: SEQUENCE          
 1040:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.34
 1051:d=5  hl=2 l=  83 prim: OCTET STRING      [HEX DUMP]:3051060960864801650304020304407C5EBAB71944C51EA737CAF93B26295B20F54FE6E5A191B4F8FDF5CE39293D1CDCF3CE600D6D08A384F44F96FF97E98076081B93465FF392779986EF5289828302021507
 1136:d=1  hl=2 l=  13 cons: SEQUENCE          
 1138:d=2  hl=2 l=   9 prim: OBJECT            :sha512WithRSAEncryption
 1149:d=2  hl=2 l=   0 prim: NULL              
 1151:d=1  hl=4 l= 513 prim: BIT STRING        
 1668:d=0  hl=4 l=5379 cons: SEQUENCE          
 1672:d=1  hl=4 l=4843 cons: SEQUENCE          
 1676:d=2  hl=2 l=   3 cons: cont [ 0 ]        
 1678:d=3  hl=2 l=   1 prim: INTEGER           :02
 1681:d=2  hl=2 l=  20 prim: INTEGER           :7B6A018CB5B1AB5F23EEDE76F75896FB953CAF56
 1703:d=2  hl=2 l=  13 cons: SEQUENCE          
 1705:d=3  hl=2 l=   9 prim: OBJECT            :sha512WithRSAEncryption
 1716:d=3  hl=2 l=   0 prim: NULL              
 1718:d=2  hl=3 l= 191 cons: SEQUENCE          
 1721:d=3  hl=2 l=  11 cons: SET               
 1723:d=4  hl=2 l=   9 cons: SEQUENCE          
 1725:d=5  hl=2 l=   3 prim: OBJECT            :countryName
 1730:d=5  hl=2 l=   2 prim: PRINTABLESTRING   :oR
 1734:d=3  hl=2 l=  11 cons: SET               
 1736:d=4  hl=2 l=   9 cons: SEQUENCE          
 1738:d=5  hl=2 l=   3 prim: OBJECT            :stateOrProvinceName
 1743:d=5  hl=2 l=   2 prim: UTF8STRING        :rx
 1747:d=3  hl=2 l=  22 cons: SET               
 1749:d=4  hl=2 l=  20 cons: SEQUENCE          
 1751:d=5  hl=2 l=   3 prim: OBJECT            :localityName
 1756:d=5  hl=2 l=  13 prim: UTF8STRING        :gQE843yQV0sag
 1771:d=3  hl=2 l=  43 cons: SET               
 1773:d=4  hl=2 l=  41 cons: SEQUENCE          
 1775:d=5  hl=2 l=   3 prim: OBJECT            :organizationName
 1780:d=5  hl=2 l=  34 prim: UTF8STRING        :dqhGYAQ2Y4gFfCq0t1yABCYxex9eAxt71f
 1816:d=3  hl=2 l=  17 cons: SET               
 1818:d=4  hl=2 l=  15 cons: SEQUENCE          
 1820:d=5  hl=2 l=   3 prim: OBJECT            :organizationalUnitName
 1825:d=5  hl=2 l=   8 prim: UTF8STRING        :a87RB35W
 1835:d=3  hl=2 l=  24 cons: SET               
 1837:d=4  hl=2 l=  22 cons: SEQUENCE          
 1839:d=5  hl=2 l=   3 prim: OBJECT            :commonName
 1844:d=5  hl=2 l=  15 prim: UTF8STRING        :x0FSqGTPWbGpuiV
 1861:d=3  hl=2 l=  49 cons: SET               
 1863:d=4  hl=2 l=  47 cons: SEQUENCE          
 1865:d=5  hl=2 l=   9 prim: OBJECT            :emailAddress
 1876:d=5  hl=2 l=  34 prim: IA5STRING         :kFp5uGcgWXxcfxi@vsHs9C9qQWGrBs.com
 1912:d=2  hl=2 l=  30 cons: SEQUENCE          
 1914:d=3  hl=2 l=  13 prim: UTCTIME           :250818135242Z
 1929:d=3  hl=2 l=  13 prim: UTCTIME           :250917135242Z
 1944:d=2  hl=3 l= 191 cons: SEQUENCE          
 1947:d=3  hl=2 l=  11 cons: SET               
 1949:d=4  hl=2 l=   9 cons: SEQUENCE          
 1951:d=5  hl=2 l=   3 prim: OBJECT            :countryName
 1956:d=5  hl=2 l=   2 prim: PRINTABLESTRING   :oR
 1960:d=3  hl=2 l=  11 cons: SET               
 1962:d=4  hl=2 l=   9 cons: SEQUENCE          
 1964:d=5  hl=2 l=   3 prim: OBJECT            :stateOrProvinceName
 1969:d=5  hl=2 l=   2 prim: UTF8STRING        :rx
 1973:d=3  hl=2 l=  22 cons: SET               
 1975:d=4  hl=2 l=  20 cons: SEQUENCE          
 1977:d=5  hl=2 l=   3 prim: OBJECT            :localityName
 1982:d=5  hl=2 l=  13 prim: UTF8STRING        :gQE843yQV0sag
 1997:d=3  hl=2 l=  43 cons: SET               
 1999:d=4  hl=2 l=  41 cons: SEQUENCE          
 2001:d=5  hl=2 l=   3 prim: OBJECT            :organizationName
 2006:d=5  hl=2 l=  34 prim: UTF8STRING        :dqhGYAQ2Y4gFfCq0t1yABCYxex9eAxt71f
 2042:d=3  hl=2 l=  17 cons: SET               
 2044:d=4  hl=2 l=  15 cons: SEQUENCE          
 2046:d=5  hl=2 l=   3 prim: OBJECT            :organizationalUnitName
 2051:d=5  hl=2 l=   8 prim: UTF8STRING        :a87RB35W
 2061:d=3  hl=2 l=  24 cons: SET               
 2063:d=4  hl=2 l=  22 cons: SEQUENCE          
 2065:d=5  hl=2 l=   3 prim: OBJECT            :commonName
 2070:d=5  hl=2 l=  15 prim: UTF8STRING        :x0FSqGTPWbGpuiV
 2087:d=3  hl=2 l=  49 cons: SET               
 2089:d=4  hl=2 l=  47 cons: SEQUENCE          
 2091:d=5  hl=2 l=   9 prim: OBJECT            :emailAddress
 2102:d=5  hl=2 l=  34 prim: IA5STRING         :kFp5uGcgWXxcfxi@vsHs9C9qQWGrBs.com
 2138:d=2  hl=4 l= 546 cons: SEQUENCE          
 2142:d=3  hl=2 l=  13 cons: SEQUENCE          
 2144:d=4  hl=2 l=   9 prim: OBJECT            :rsaEncryption
 2155:d=4  hl=2 l=   0 prim: NULL              
 2157:d=3  hl=4 l= 527 prim: BIT STRING        
 2688:d=2  hl=4 l=3827 cons: cont [ 3 ]        
 2692:d=3  hl=4 l=3823 cons: SEQUENCE          
 2696:d=4  hl=2 l=  12 cons: SEQUENCE          
 2698:d=5  hl=2 l=   3 prim: OBJECT            :X509v3 Basic Constraints
 2703:d=5  hl=2 l=   5 prim: OCTET STRING      [HEX DUMP]:30030101FF
 2710:d=4  hl=4 l= 539 cons: SEQUENCE          
 2714:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.64
 2725:d=5  hl=4 l= 524 prim: OCTET STRING      [HEX DUMP]:30820208048202007DDD9A48FF7F56D7EEAB2D824DB082F48D913D517928857BE4D390ABD99FF1EDD7737DCE9C3E22A9AB634534D3198EE5DB2B26F0F67365A38F315C7FB3297B0A75EC840896842D96477A52BD9DF7E3632B692464F8E4A0DDA577A7516020DA64ECB7A6F48A044B950DCD0EEDD1D98FCCB1608504B9526C1EC9A01E8ABE1E3085800EDBDD75ECFC94846F8E66E37B81DAB16418C9E1CED8FFE85960C384A87E7962DE4EA55A2458D51CFDB148BEF60672F14B330F0F49223299C7AB4C328DD8234785112D99121A675E9BAFC2D52F04303819024C0AECBF17BD3E1FA2DDD853C51E84E2DF40D9827DB7E900F71EB96D97331ECA294E5EF4601BEF41267DC8D2986AD1A509A8783FE7A990A05069691171AA4048027C6482AFCB0E3C8EF92D5ECF4C566A9D7A6927688615345B38EF0E65611EFAAFB2D024D67854516AA4CBC6A176D5D48B1865748B4CFBCBACBE45EB548DBA7D1D52D2C3F9055F25F39819C2B0351BD968A477896828C61B22C79F30EE74E9AC3EB1343522BECF6E1A91B7A673DBAA1016BF26C0C680F23D2209C794E9015A28A397ACB1D611EBE601BAE1B1EA7BF5B45D2BBB8DF98811DD3310D8B4E4A49E51F551C32B9CF118D1355B7E3E45199BEF44935B3909E9E13DE902A5BD9A19DDDC70E0660D58F48B770815E86474D8A59AD88C0C3941F12D739321AEFD1F9405C2C27E130D0C03012415BF118B2D02020200
 3253:d=4  hl=4 l=1051 cons: SEQUENCE          
 3257:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.65
 3268:d=5  hl=4 l=1036 prim: OCTET STRING      [HEX DUMP]:308204080482040087FE2F294FC96E3FAC685D4562E04F179C940AC06029BF4FD41EB67E832F17808631BEF503B0BED75A3A528000D3E459E5EEB7AC7214D70487A7A23AF4F61AD6A41C9616FE5277A7A73FFBA1EECB389889658696C5972A3D64CC5D33256DCDA312CC97D36189865D6A7E93373F682BCD76A3CB84B0E84D3B02D98F62F58C4277843F5AD385AED0BE25AB655F2BACE6A4387CE7111E7C98FD40C2FB066F2F68E4A796AB50B62EF303807330C6A0CB31CD089997BEC79A77CA5BC1A698308AD7B6E0CBE0A01B78F537B88D9A529BCCC3BBD9F9F4CFFB805F18CDE557EDE8F96CF14BCA2D30E6649D2A66663EFCC38CB62E1BC4877CEB88109D2978D75AB1A274CE8A70FC70F6CFB1F3A61DC7ACF5FBC0EDD01D9219E5EAAAFF10FA427B63CD415CE5C08833D5F29950FEBC9472EA894D55A5F56BAF5C286C1C4B204C8E0D8A89D1A46FF2B91EF77A33A5D7AB6EB61C35BD51D9F7C41293FBC68317DCE67853D44D67885FB9DCD70A2042929691BFE885B0215062F5C65C3D4342953BC5B7A34EA86BBC8AF07ABDDA11596B93B6A77CE0B4D1F541EE03E7F6B9DBD593665A6E0707B5738321DAE293BED7D45CE1A2DA91E06A9F6F6DF7C65015996CD829D3F11C4A0E7E0E0E6325B79743309C16C4FD426EFF4F3B31BD3C41C0C78CAE58DC89C4E803D32ADB7C4281587BBC38180819FF0E96D2D7BD7981A4B78393F5C605C5C5853DF7970B929D40339B8B735DA669A1B968FD7C1BF050AB573A1FB99C1D305E663CDA2A5F0C2BE7578681C0B53B6C45567A695E4618EAF2FD0A5FC99C2FE3CE5A929DA82A663E0F9CB988AA3A52BA2BF748FBF6F1BD86E39D468DDE411195397E9AB72F8F4643E636B87F3D95B6A05A54450772F25088B5DADBEE7065E9E648160216ABDEF9B4078E60DD15D906C87731E1AC77F148FC35C2B732EA47708E1FC27582DC8D11B7BC30BB882744CABBDD06826762C7280A0EA4453C9752CE8FD1A031C1D5E1453624D68948094D0237CD61EC8FF6745DA73B6B2A5A90532587A10594A13FF2847B567A7C0BB3C295A24AED5A9329144C3221299FEDEE91F735983A538AB0012A154E05689B7B575F801BD3D8A8CCB761A3559A70BAE2A70D4E6941325A4F2ACD19522FF90BBD245FE59A6D0C5109F1307E51AAD5803E0CA3292FA6D5C4B13BDFC1046A7FD698602657830C2B6C08D948832BBE91AFEDD0FF2CA5C54137A4A878247854C0F80A7BE98041B2172B8DF2FE0EAEC0042BC5A64E0336D8F624C5777A23E00C5F65343652384478A5AA5BD053823B0D541DF80718EBACA6E472723700DCC103638B0DE8C4328FEAE28A94E16F945BC4568600208D3B15EBA2A186F9B2ABC7ACA929903EE6562DF36A79C5FE27523680D0A41515CF41BDF9D7E1B5D039371B6898CC4D5164EC5A666879DDA0E934DB3596E2F87F19B79E6A02020400
 4308:d=4  hl=4 l=1051 cons: SEQUENCE          
 4312:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.66
 4323:d=5  hl=4 l=1036 prim: OCTET STRING      [HEX DUMP]:30820408048204000614A8B67DB60E8E702BD846152F73B07866F2F36BD8C3991E570E96E0B05D4BAF5296423381FE0AE09FB9548627F7582C0DDCD16A097FEF91F2DAEFCD01EECA4912BD7857548DA6E7FB793EFA8BE92DB904109EF45326DC434EEB2FDC75BE5FAC3BFC0C96A7F72BD463CB5F61900E3C7196FACF34AE40BD773D1C28076D57D2ABAC33D068E04E8AB9E3997F617CB2154437D310C78F3B1B060C0B001E4A4FACA9A21FB8E81A7F7172C56CD9DE2E9BE11477EAE23A72C81A658A15A7E28D9D542D265D33C09DDAAC0E1DA5E6B64C7C9C314EB945C931B60D5189791C9087D8A4F9E3019118154386A5408585911DFD1231078F39C86B81C84CE78F719E9F479770D5E42915E33E20A20291C17D0DCD84A8485FD755F2126A104B8D590A9A02CC7B2E4AEDF2663CA1D348EBB19EB7965B20A8669CE0080296754847A9AD2052C20CAF3A37C864502C8F5E4C3BBE7DDD5AA1029461428AC04AF36209C2AA59F03554A8C196BA0650F68A1BBA3D2BF1F4A9D03D318CC7C0C904FB0711CB0FF1F93F9784E4085C961D07534BE827168C72043E5EFF15750FBAEA63C21DF11166C95A9404C9930AD22A3B31C8A528FA5FF7BEA0C620650FBA2014B5F82E16AEA91C9009F9AE7B346433EB063B9440C072FE0C7B40809F7BF5E3FE11261AAFA1F57757B3BE83A329D99D1D44012B6AAEF5B84F4E720BF1ED68A8187B25BAE163D6D0747F04A6AD0BC8616C75F4AEE782AB842BEEBB00C81CFFDD2BE8701DEC39316C4FC03BF22E4E6D4D7133736F529438C5B26E3A1D4A0FE4F95F41748D7165BC152E2B9CDA69DA97B8F7B6ED5470EBE673A16587AE94FBE0AFA9DD7294BC63B9BB577E1C8FE3221EF9BD48F5467FFE8D83EE323BDCB1956378717F0BE78028C692DC0E4DCFF9A497EB25A24510B806F607F3244034B95C4609B5E5C7E61EE7AC064213D88EF5595E7E34849B4032D8F2956DF008C186E991A70D1687ED2D59BCA5D96DEB1A72465DF3700C7E9597520EA6E44411B4B860643C3188F343AB0BB42A102174B3F06E5468FA14C4C011384A863474042FD20AD107185C06921CA7470AE2E8B2745B7BF6D40B038ECEC80560ED5BB6A4C5CB24176707876C8FB51C2B95EF52A46BC7D14ED466B1DA28BF18929A92225C7815CEE5C24F4F93F9E5983C96CD9F7FF942E18139CEC288C7A1BB4A1CB2A89F0C7FFB3EDC0E39DBA0F38B608A3432576B283C2DED1FAAFAE070F91E84F05D193D7ECBB81CB11A8C478C746D849A5EA704BAED57CA5B6BABDCDF7D55D12C3E760D6E1FDCF1F894937F14690A6B3A2214D8279CE88731ED31E0ADC3B6FA6EDE6EEFA1C9DAF9CEC5AD8B7032DD8B72FCD6B4FA0209450D7C85D4C926F8571B803DFAA1DA2BF39CB7E65E74D94D4F9AF6ECCEC6DECB5950334174AC126372499C6560E89780C4D0931D45230C9C3C1402020400
 5363:d=4  hl=3 l= 177 cons: SEQUENCE          
 5366:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.67
 5377:d=5  hl=3 l= 163 prim: OCTET STRING      [HEX DUMP]:3081A004603343CC7D7FDE2C78BB9CBDC1F9B398C9743E1CA14512E84A00A9445AF598111BE190D0A569A343BB211F88685F092097D1A6B8D814633B01796663DA54CAF42757BFC22593D812389EC4C18F64FB03EE8FE40E58D496FD9FF3D6031119E796310410263DC569E6C1BC594C0B1B2B2E6C21EC0420ECE1ABC5B40A002FFEEBA37D4F819EFEB4B105FCA592C471F916FC40F8E27377020160020500A5A5A55A
 5543:d=4  hl=3 l= 145 cons: SEQUENCE          
 5546:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.68
 5557:d=5  hl=3 l= 131 prim: OCTET STRING      [HEX DUMP]:30818004409A7497A3DD6DDDD6FA39E22EAB262895A4E26C2F5ABF5150689B3574BD1DB60B956D1266A3BF5A39D110347D8E8A57408229C31548D3578DCAE38833B0DD6766041087C61B414E8D404713A9543058C4921C04204C89456A80F5507A81366F4FF29801E210679C4B67B4FB682FFC13CC9706C03A020140020500A5A5A55A
 5691:d=4  hl=2 l=  26 cons: SEQUENCE          
 5693:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.69
 5704:d=5  hl=2 l=  13 prim: OCTET STRING      [HEX DUMP]:300B04020000020500A5A5A5A5
 5719:d=4  hl=3 l= 177 cons: SEQUENCE          
 5722:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.70
 5733:d=5  hl=3 l= 163 prim: OCTET STRING      [HEX DUMP]:3081A0046040B1D972294FB832B526EFF9708E1A98BAC91F014198CB2F84C03B5667BB0BB8E4BDD24742258ED33DA9EE933394D7F9B4F5001B16D4E79B91FEE6ADC746D75A1EF6B6A680E233D33ADEA9DA39C92804C50A31293F56FC7ADFF84909722F348D0410EED36D0BC216657DA346FB2692B7459B04200AC83FEC07D3CAC63D190B5104854D0B07F3E714DD0C08808C289A79E5BE9121020160020500A5A5A55A
 5899:d=4  hl=3 l= 145 cons: SEQUENCE          
 5902:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.71
 5913:d=5  hl=3 l= 131 prim: OCTET STRING      [HEX DUMP]:30818004406B26C3F5985B1E945A554BD004EC538E6DA28AA7D137B113A888AD6046F06E5BE766AFD00EBF00AA4588A5659DD30BBB50306A515B7603B323BDEE4D925EDAC204106C0C9374510CC8CFEB4761DB74BA1E600420EBFDFCA8C98E3D39D80C0E74D3CB2EC0CBAF2CB399085C1F864BDD112E828943020140020500A5A5A55A
 6047:d=4  hl=2 l=  25 cons: SEQUENCE          
 6049:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.72
 6060:d=5  hl=2 l=  12 prim: OCTET STRING      [HEX DUMP]:300A040100020500A5A5A5A5
 6074:d=4  hl=3 l= 231 cons: SEQUENCE          
 6077:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.73
 6088:d=5  hl=3 l= 217 prim: OCTET STRING      [HEX DUMP]:3081D6048180000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000004100000000000000000000000000000000004200000000000000000000000000000000000000000000000000000000000000000041000000000000000000000000000000000020100020100020500A5A5A5A5
 6308:d=4  hl=2 l=  28 cons: SEQUENCE          
 6310:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.74
 6321:d=5  hl=2 l=  15 prim: OCTET STRING      [HEX DUMP]:300D040400000001020500A5A5A55A
 6338:d=4  hl=2 l=  28 cons: SEQUENCE          
 6340:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.76
 6351:d=5  hl=2 l=  15 prim: OCTET STRING      [HEX DUMP]:300D0404000C0FFE020500A5A5A55A
 6368:d=4  hl=2 l=  28 cons: SEQUENCE          
 6370:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.77
 6381:d=5  hl=2 l=  15 prim: OCTET STRING      [HEX DUMP]:300D040400000003020500A5A5A55A
 6398:d=4  hl=2 l=  30 cons: SEQUENCE          
 6400:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.78
 6411:d=5  hl=2 l=  17 prim: OCTET STRING      [HEX DUMP]:300F0406000000000000020500A5A5A5A5
 6430:d=4  hl=2 l=  30 cons: SEQUENCE          
 6432:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.79
 6443:d=5  hl=2 l=  17 prim: OCTET STRING      [HEX DUMP]:300F0406000000000000020500A5A5A5A5
 6462:d=4  hl=2 l=  32 cons: SEQUENCE          
 6464:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.80
 6475:d=5  hl=2 l=  19 prim: OCTET STRING      [HEX DUMP]:301104080000000000000000020500A5A5A5A5
 6496:d=4  hl=2 l=  21 cons: SEQUENCE          
 6498:d=5  hl=2 l=   9 prim: OBJECT            :1.3.6.1.4.1.294.1.81
 6509:d=5  hl=2 l=   8 prim: OCTET STRING      [HEX DUMP]:3006040400000200
 6519:d=1  hl=2 l=  13 cons: SEQUENCE          
 6521:d=2  hl=2 l=   9 prim: OBJECT            :sha512WithRSAEncryption
 6532:d=2  hl=2 l=   0 prim: NULL              
 6534:d=1  hl=4 l= 513 prim: BIT STRING

    and this are the generated certificate and the built keywriter binary (tiboot3.bin).
    tiboot3+final_certificate.zip

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    Now, the certificate looks good.

    Is it still not working? Please share the logs including the TIFS ones.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    After flashing ti-boot3.bin, we observed the following output on the R5 UART console:

    Starting Keywriting
    Enabled VPP
    keys Certificate found: 0x43c16f00
    Keywriter Debug Response: 0x0
    Success Programming Keys

    This seems to confirm that the keywriting step was successful using dummy keys.

    Issue:
    After this, we powered off the SoC, changed the boot mode switch, and powered the board back on. However, we are not seeing any UART output from the SoC at this stage.

    Questions:

    1. Is this the expected behavior immediately after programming dummy keys?

    2. What should be the next step after this keywriting step to proceed with the secure boot flow using dummy keys?

    3. At this point, what output is expected on the UART
  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points
    Kapil Vyas said:
    What should be the next step after this keywriting step to proceed with the secure boot flow using dummy keys?

    You would need to flash the HSSE images.

    If you are booting SPL from SD card then you would need to replace the `tiboot3.bin` with `tiboot3-am62x-hs-evm.bin`.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    Thank you for the clarification.

    We are not using SD card boot; instead, we are using DFU (dfu-util) to flash images to the target storage .

    Could you please confirm:

    1.Whether it's correct to flash the tiboot3-am62x-hs-evm.bin (signed with dummy keys) via DFU using dfu-util?

    2.What is the correct flash offset or DFU alt setting to use when flashing this HS-SE signed SPL via DFU?

    3.Are there any other bootloader components (e.g., u-boot.img, tispl.bin) that also need to be signed with dummy keys and flashed accordingly?

    We want to ensure the entire boot chain is signed and flashed properly now that the keywriting step has succeeded.

    Thanks and looking forward to your guidance.

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    Please continue with the flow you have for flashing and booting the device. The only change required is flashing the HSSE tiboot3.bin instead of the HSFS one at the same offset. The `tispl.bin` and `u-boot.img` are already signed with the dummy keys.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    After flashing tiboot3-am62x-hs-evm.bin this is the R5 terminal output we got :-

    U-Boot SPL 2023.04 (Aug 25 2025 - 15:25:36 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

    we use "sudo dfu-util -c 1 -i 0 -a bootloader -D <path_to_tiboot3.bin>" this command to flash tiboot3-am62x-hs-evm.bin & this is terminal output we get :-

    $ sudo dfu-util -c 1 -i 0 -a bootloader -D /home/renu/my_boot/tiboot3.bin 
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: Invalid DFU suffix signature
dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
Opening DFU capable USB device...
ID 0451:6165
Run-time device DFU version 0110
Claiming USB DFU Interface...
Setting Alternate Setting #0 ...
Determining device status: state = dfuIDLE, status = 0
dfuIDLE, continuing
DFU mode device DFU version 0110
Device returned transfer size 512
Copying data from PC to DFU device
Download	[=========================] 100%       294274 bytes
Download done.
state(6) = dfuMANIFEST-SYNC, status(0) = No error condition is present
state(2) = dfuIDLE, status(0) = No error condition is present
Done!

     

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    Could you please explain the steps you have been following to boot the HSFS device till now? If you did have a working setup then all that's required is using the HSSE tiboot3.bin instead of the HSFS one.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello, 

    1. As requested, here are the steps we followed to boot the device in HS-FS mode.

    # FOR FLASHING BOOTLOADER 

sudo dfu-util -R -a bootloader -D bootloader.bin
sudo dfu-util -R -a tispl.bin -D tispl.bin
sudo dfu-util -R -a u-boot.img -D u-boot.img

stop autoboot, enter below commands -

setenv dfu_alt_info ${dfu_alt_info_emmc}
dfu 0 mmc 0

# FOR FLASHING FILESYSTEM USE BELOW COMMANDS

sudo dfu-util -a tiboot3.bin.raw -D tiboot3-raw.bin
sudo dfu-util -a tispl.bin.raw -D tispl.bin
sudo dfu-util -a u-boot.img.raw -D u-boot.img

sudo dfu-util -a rootfs -D /PATH/TO/EXT4

enter ctrl-C and enter below commands -
mmc partconf 0 1 1 1
mmc bootbus 0 2 0 0

change the switch mode and set the environment

setenv mmcdev 0
setenv bootpart 0
saveenv

            2.yes we have working setup. and we only flash the HSSE tiboot3.bin.

    also attaching the HSSE tiboot3.bin file 

    5826.tiboot3.zip  

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points 

    # FOR FLASHING BOOTLOADER 

sudo dfu-util -R -a bootloader -D bootloader.bin

    How do you generate this "bootloader.bin"? In those steps, all you need is to use the corresponding HSSE images for the "bootloader.bin" and "tiboot3-raw.bin".

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Regarding the bootloader.bin,

    • The one i have been using so far was a GP image.
    • This steps i followed to generate it:

    Defcofig for tiboot3.bin :

make ARCH=arm CROSS_COMPILE=/home/renu/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf- am62x_evm_r5_usbdfu_defconfig O=/home/renu/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/build/out/r5

build tiboot3.bin : dfu-usb

make ARCH=arm CROSS_COMPILE=/home/renu/arm-gnu-toolchain-11.3.rel1-x86_64-arm-none-linux-gnueabihf/bin/arm-none-linux-gnueabihf- O=/home/renu/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/build/out/r5/ BINMAN_INDIRS=/home/renu/ti-processor-sdk-linux-am62xx-evm-09.00.00.03/board-support/prebuilt-images/am62xx-evm/

     

    my question is :- For moving to HSSE, do i need to regenrate a new bootloader.bin specifically for HSSE(using the HSSE signing process) or can i continue using the GP generated bootloader.bin together with the HSSE tiboot3.bin?

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    The build automatically generates "tiboot3.bin" for all the device types (GP, HSFS, HSSE) so you just need to pick the HSSE one. More specifically, after your build completes, you need to pick the "board-support/u-boot-build/r5/tiboot3-am62x-hs-evm.bin" binary.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Thank you for the clarification. I understand now that the build process already generates all tiboot3 variants, including the HSSE one. for HSSE boot , i should specifically use: "board-support/u-boot-build/r5/tiboot3-am62x-hs-evm.bin" binary.

    please confirm if my existing bootloader.bin also needs to be rebuilt/signed specifically for HSSE, or if only replacing tiboot3.bin with the HSSE version is sufficient for boot.

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points
    Kapil Vyas said:
    please confirm if my existing bootloader.bin also needs to be rebuilt/signed specifically for HSSE

    There is no file generated in the build by the name "bootloader.bin". You might have just renamed sometime the "tiboot3.bin" to "bootloader.bin".

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    we flashed the HSSE tiboot3-am62x-hs-evm.bin from this path : "board-support/u-boot-build/r5/tiboot3-am62x-hs-evm.bin"

    and on the terminal i see the following output:

    Terminal ready

U-Boot SPL 2023.04 (Aug 25 2025 - 15:25:36 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

    From my understanding this idicates that tiboot3 was successfully executed and SYSFW was loaded, but it is not finding the next stage bootloader.

    could you please confirm:

    1. Does this log confirm that the HSSE tiboot3 was successfully flashed and executed?
    2. for the next steps, should i flash the HSSE version "board-support/u-boot-build/a53/ tispl.bin and u-boot".
  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    I believe you are not exactly following the working HSFS setup. The R5 SPL (tiboot3.bin) is built separately for DFU and eMMC support. You would have separately generated these when you were working with HSFS. The same you just need to do for HSSE.

    In any case, the point is you need to build the R5 SPL separately for booting from DFU and eMMC.

    software-dl.ti.com/.../UG-General-Info.html

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    I've successfully provisioned the device and now I see the device is now in HS-SE mode.

    SoC:   AM62X SR1.0 HS-SE
Model: Texas Instruments AM625 SK

    this two output lines after flashing the u-boot from this i verify the device state.

    However, I'm currently facing an issue when trying to verify the device type (SoC ID) over UART.

    As per the documentation, after setting the appropriate boot mode switches (e.g., UART mode), I expect to see Boot ROM output (SoC ID, etc.) on the terminal. But I’m not seeing any output at all on the UART terminal — it stays completely blank.

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points
    Kapil Vyas said:
    As per the documentation, after setting the appropriate boot mode switches (e.g., UART mode),

    Please make sure you have set the bootmode pins correctly for the UART bootmode.

    And what is the output of the following commands run from the A53 U-Boot?

    => mw 0x43000030 0x3b 0x1;reset;

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    I attempted to boot the board using DFU mode as follows

    $sudo dfu-util -c 1 -i 0 -a bootloader -D /home/ti/board-support/u-boot-build/r5/tiboot3-am62x-hs-evm.bin
$sudo dfu-util -R -a tispl.bin -D tispl.bin
$sudo dfu-util -R -a u-boot.img -D u-boot.img

    Here is the output I received from these commands

    Terminal ready

U-Boot SPL 2023.04 (Aug 28 2025 - 11:48:42 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
Trying to boot from DFU
##########################################################DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed
Authentication passed
Loading Environment from nowhere... OK
init_env from device 10 not supported!
Authentication passed
Authentication passed
Starting ATF on ARM64 core...

NOTICE:  BL31: v2.9(release):v2.9.0-614-gd7a7135d32-dirty
NOTICE:  BL31: Built : 09:34:15, Aug 24 2023

U-Boot SPL 2023.04 (Aug 28 2025 - 12:07:43 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (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 DFU
####DOWNLOAD ... OK
Ctrl+C to exit ...
Authentication passed
Authentication passed


U-Boot 2023.04 (Aug 28 2025 - 12:07:43 +0530)

SoC:   AM62X SR1.0 HS-SE
Model: Texas Instruments AM625 SK
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed -1
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
EEPROM not available at 80, trying to read at 81
Reading on-board EEPROM at 0x51 failed -1
Net:   Could not get PHY for ethernet@8000000port@1: addr 0
am65_cpsw_nuss_port ethernet@8000000port@1: phy_connect() failed
No ethernet found.

Hit any key to stop autoboot:  0 
=> 
=> setenv dfu_alt_info ${dfu_alt_info_emmc}
=> dfu 0 mmc 0
generic_phy_get_bulk : no phys property

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    I don't see those commands. You are just running dfu commands.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points 

    Hit any key to stop autoboot:  0 
=> mw 0x43000030 0x3b 0x1;reset;
resetting ...
02000000011a0000616d3632780000000000000048535345010001000100010002a6000001000200d68ecb2c055dff11ade95bd927e837d2a53bc23b0a2800cebce4f106bcf309df2213912d77a157a8b7c2df40672a06a918034aa4c7d603e462481475225d49b81f6002b07cd9b0b7c47d9ca8d1aae57b8e8784a12f636b2b760d7d98a18f189760dfd0f23e2b0cb10ec7edc7c6edac3d9bdfefe0eddc3fff7fe9ad875195527d74b24aed316cea6820016d5ff184fbcf2fedcff26f288a6108d9c320a0e784a0CCCCCCCCCCCC

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    This shows that the warm reset to UART bootmode is working and you got the SoC ID dump from the ROM.

    Kapil Vyas said:
    As per the documentation, after setting the appropriate boot mode switches (e.g., UART mode),

    So, this must be caused by the incorrect settings for the UART bootmode. Please rectify those and then you should see expected output.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    Facing a boot failure after flashing the bootloader components to eMMC.

    1.Booted the board in USB DFU mode and flashed to RAM using

    sudo dfu-util -R -a bootloader -D tiboot3-am62x-hs-evm.bin
sudo dfu-util -R -a tispl.bin -D tispl.bin
sudo dfu-util -R -a u-boot.img -D u-boot.img

    2. Stopped at U-Boot prompt and executed:

    setenv dfu_alt_info ${dfu_alt_info_emmc}
dfu 0 mmc 0

    3.Then, I flashed to eMMC using:

    sudo dfu-util -a tiboot3.bin.raw -D tiboot3-am62x-hs-evm.bin
sudo dfu-util -a tispl.bin.raw -D tispl.bin
sudo dfu-util -a u-boot.img.raw -D u-boot.img

    4.In U-Boot, I configured the eMMC boot settings:

    mmc partconf 0 1 1 1
mmc bootbus 0 2 0 0

    Then I powered off the board, changed the boot mode switches to eMMC boot, and powered it back on.

     Issue:

    After reboot, I consistently get the following error:

    U-Boot SPL 2023.04 (Aug 28 2025 - 11:48:42 +0530)
SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.8--v09.01.08 (Kool Koala)')
SPL initial stack usage: 13384 bytes
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###

  • 0 in reply to Prashant Shivhare
    TI__Guru 70871 points
    Prashant Shivhare said:
    In any case, the point is you need to build the R5 SPL separately for booting from DFU and eMMC.

    Again, you need to have separate tiboot3.bin for booting from DFU and eMMC.

    e2e.ti.com/.../5980741

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,
    We generated  separate tiboot3.bin for booting from DFU and eMMC
    Booted the board in USB DFU mode and flashed to RAM using:
    sudo dfu-util -R -a bootloader -D tiboot3-am62x-hs-evm.bin
    sudo dfu-util -R -a tispl.bin -D tispl.bin
    sudo dfu-util -R -a u-boot.img -D u-boot.img

    Stopped at U-Boot prompt and executed:
    setenv dfu_alt_info ${dfu_alt_info_emmc}
    dfu 0 mmc 0

    Couldn't find part #1 on mmc device #0
DFU entities configuration failed!
(partition table does not match dfu_alt_info?)
dfu - Device Firmware Upgrade

Usage:
dfu <USB_controller> [<interface> <dev>] [list]
  - device firmware upgrade via <USB_controller>
    on device <dev>, attached to interface
    <interface>
    [list] - list available alt settings

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points
    Kapil Vyas said:
    2. Stopped at U-Boot prompt and executed:

    In your second last response, it was working but not now. So, you must have changed something. Do you recall doing something?

    Please share the output of the following commands

    => printenv dfu_alt_info_emmc
=> mmc dev 0
=> mmc part

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    => printenv dfu_alt_info_emmc
dfu_alt_info_emmc=rawemmc raw 0 0x800000 mmcpart 1; rootfs part 0 1; tiboot3.bin.raw raw 0x0 0x400 mmcpart 1; tispl.bin.raw raw 0x400 0x1000 mmcpart 1; u-boot.img.raw raw 0x1400 0x2000 mmcpart 1; u-env.raw raw 0x3400 0x100 mmcpart 1; sysfw.itb.raw raw 0x3600 0x800 mmcpart 1
=> mmc dev 0
switch to partitions #0, OK
mmc0(part 0) is current device
=> mmc part
## Unknown partition table type 0

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    There is no partition table in the eMMC. Since, the command was working, you have likely erased the partition table unknowingly. Please partition the eMMC again following the steps you must have followed in the past for the same.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    eMMC partition was successfully created.

    I'm encountering an issue while flashing the rootfs.

    mmc part shows that partition 1 exists and is ~15 GB.

    • It's a custom generated ext4 image ,

    • Size is around 8.6GB

    Isuue:

    When attempting to flash the rootfs image via DFU, I receive the following error:

    dfu-util: File size is too big: Success

  • +1 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,

    • The U-Boot command mmc part shows a valid GPT partition with a single rootfs partition (rootfs1), starting at LBA 0x22 and ending at 0x1da3fde, approximately 15.95 GB in size.

    • The rootfs image size is about 8.6 GB, well within the partition boundaries.

    • My dfu_alt_info_emmc environment variable is configured to use the rootfs partition via rootfs part 0 1.

    • After upgrading to the latest dfu-util version, the previous error "File size is too big: Success" no longer appears.

    • However, I am encountering a error during DFU flashing:

      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/

libusb version 1.0.25 (11696)
dfu-util: Cannot allocate memory of size 0 bytes

    • U-Boot recognizes the partition, but the DFU process seems to fail with this allocation error

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points
    Kapil Vyas said:
    However, I am encountering a error during DFU flashing:

    The "dfu-util" tool is not owned by TI. It's an open source tool so any issues with it should be discussed on its specific forum. I can only suggest to try flashing a smaller size rootfs just to see if the "dfu-util" just fails for big file sizes.

  • 0 in reply to Prashant Shivhare
    Prodigy 20 points

    Hello,
    The ext4 filesystem flashing issue has been resolved — the ext4 gets flashed properly now. However, after this fix, The device boots successfully once, then reboots again. After 2-3 automatic reboots, the terminal output hangs midway during boot, and the system becomes unresponsive.

  • 0 in reply to Kapil Vyas
    TI__Guru 70871 points

    Please create new thread for this issue.