• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 103 subscribers
  • Views 382 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.

TMDXIDK5718: AM5718 IDK fails to boot when configured in automatic start

Francois Charlot
Mastermind 23137 points
Part Number: TMDXIDK5718
Other Parts Discussed in Thread: AM5718, TPS659037

Hello,

My customer use the AM5718 IDK in which they have removed resistor R18 and installed it at position R931 instead so to enable automatic start. Before this modification, their software started and executed normally.

With the autostart modification, they observe that uboot executes, the device tree is loaded, but execution freezes on "Starting kernel...".

I have attached their log and dtb file (links accessible from TI only).

Their board is marked rev 1.3B, although the schematics available at the moment on ti.com are rev 1.3A.

Could you please suggest what could be wrong in my customer setup? Thank you.


Best regards,
François.

  • 0
    TI__Guru*** 131050 points

    Hi Francois,

    Can you halt at u-boot by pressing enter and give the below commands:

    env default -a
    saveenv
    boot

    Also before the modification was the board functional w.r.t booting?

    - Keerthy

  • 0 in reply to Keerthy J
    TI__Mastermind 23137 points

    Hi Keerthy,

    Thank you for replying quickly. I have asked my customer to supply the information.


    Best regards,
    François.

  • 0
    Prodigy 50 points

    Hello,

    We reinitialized the U-Boot environment as requested (env default –a ; saveenv ; boot) but it did not change the boot sequence. (We already used default environment). The log file is exactly the same (see below).

    About the question « Also before the modification was the board functional w.r.t booting?  », answer is yes.

    Please advise. Thanks.

    Emmanuel

    -------------------------------------------------------------------------------

    U-Boot SPL 2020.01-00220-g0ebed4ea7c-dirty (Jan 01 1970 - 00:00:00 +0000)

    DRA722-GP ES2.0

    no pinctrl state for default mode

    ** Unable to read file dra7-ipu1-fw.xem4 **

    Firmware loading failed

    ** Unable to read file dra7-ipu2-fw.xem4 **

    Firmware loading failed for ipu2

    Trying to boot from MMC1

    Loading Environment from FAT... no pinctrl state for default mode

    OK

     

     

    U-Boot 2020.01-00220-g0ebed4ea7c-dirty (Jan 01 1970 - 00:00:00 +0000)

     

    CPU  : DRA722-GP ES2.0

    Model: TI AM5718 IDK

    Board: AM571x IDK REV 1.3B

    DRAM:  1 GiB

    MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

    Loading Environment from FAT... OK

    Net:   eth0: ethernet@48484000

    Hit any key to stop autoboot:  0

    => env default -a

    ## Resetting to default environment

    => saveenv

    Saving Environment to FAT... OK

    => boot

    51345156 bytes read in 2271 ms (21.6 MiB/s)

    ## Loading kernel from FIT Image at 82000000 ...

       Using 'am5718-idk-safran.dtb' configuration

       Trying 'kernel@1' kernel subimage

         Description:  Linux kernel

         Type:         Kernel Image

         Compression:  uncompressed

         Data Start:   0x82000114

         Data Size:    7188992 Bytes = 6.9 MiB

         Architecture: ARM

         OS:           Linux

         Load Address: 0x80008000

         Entry Point:  0x80008000

         Hash algo:    sha256

         Hash value:   a88acb0baae9375cc1230933c537e4bf775ebce0b1b06f10d7a5798ee8b64482

       Verifying Hash Integrity ... sha256+ OK

    ## Loading ramdisk from FIT Image at 82000000 ...

       Using 'am5718-idk-safran.dtb' configuration

       Trying 'ramdisk@1' ramdisk subimage

         Description:  ramdisk image

         Type:         RAMDisk Image

         Compression:  uncompressed

         Data Start:   0x826fc4cc

         Data Size:    44018873 Bytes = 42 MiB

         Architecture: ARM

         OS:           Linux

         Load Address: unavailable

         Entry Point:  unavailable

         Hash algo:    sha256

         Hash value:   acda7a413dacbda794572456e01901c231c7a886a572c3acfb187165e1e08dd4

       Verifying Hash Integrity ... sha256+ OK

    ## Loading fdt from FIT Image at 82000000 ...

       Using 'am5718-idk-safran.dtb' configuration

       Trying 'am5718-idk-safran.dtb' fdt subimage

         Description:  Flattened Device Tree blob

         Type:         Flat Device Tree

         Compression:  uncompressed

         Data Start:   0x826db424

         Data Size:    135138 Bytes = 132 KiB

         Architecture: ARM

         Hash algo:    sha256

         Hash value:   9d39ff6ad98e29999458c3ce4b8184879a000ebf8ac8e6274ce67d6bca067cc3

       Verifying Hash Integrity ... sha256+ OK

       Booting using the fdt blob at 0x826db424

       Loading Kernel Image

       Loading Ramdisk to 8d605000, end 8ffffcb9 ... OK

       Loading Device Tree to 8d5e1000, end 8d604fe1 ... OK

     

    Starting kernel ...

  • 0 in reply to Emmanuel SIRAND-REY
    TI__Mastermind 39520 points

    I don't have the details on if this alternate mode (automatic power on) was ever tested on the EVM.  Its possible the TPS659037 is turning on before the input supply is stable.  What input supply are you using?  Is it a already-on supply, or does it turn on with the EVM?  What value of resistor are you installing in R931?

  • 0
    Prodigy 50 points

    Hello,

    We are using regular 5V power supply connected to the jack. We simply power-off/on the 5V adapter from the lab 220Vac. We exchanged the resistors R18/R931, so we assume R931 is 10kohm (value of R18 in your schematics).

    Thanks

    Emmanuel

  • +1 in reply to Emmanuel SIRAND-REY
    TI__Mastermind 39520 points

    Since the 5V input supply is also ramping, its possible the board is turning on too early (before the 5V reaches a valid value).  You can try connecting the GPIO_7 net to maybe the PMIC_RESET_IN?  This ensures the input supply is at a valid level.  Remove the resistor install at R931, and connect R931 (PMIC side of component) to U105 pin 1. 

  • 0
    Prodigy 50 points

    Hello all,

    We checked the resistors modifications that we've made.

    It appears that instead of removing R18 resistor, we have removed by mistake R854 (0 ohm) that has been placed on R931 empty pads!

    We populate again R854 (0 ohm) and moved R18 (10KR) to R931.

    Automatic start works perfectly, this time!

    I apologize for our mistake: the exchange of R18/R931 as written in your AM5718 IDK schematics is correct.

    Thanks for your support.

    Emmanuel