• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 625 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.

AM3352: rebooting after 'Starting kernel....' message

Sung-IL
Mastermind 31050 points
Part Number: AM3352


Dear Champs,

In my customer's custom board, they faced their system reboot continually after changing device(AM3352BZCZD80 => AM3352BZCZA100)

They did not change PLL settings and other SWs yet after replacing device to AM3352BZCZA100, and their log is as below.

===============================================

……

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

   Using 'config-1' configuration

   Trying 'fdt-1' fdt subimage

     Description:  Flattened Device Tree blob

     Created:      2020-09-09   1:18:59 UTC

     Type:         Flat Device Tree

     Compression:  uncompressed

     Data Start:   0x885505c0

     Data Size:    35757 Bytes = 34.9 KiB

     Architecture: ARM

   Verifying Hash Integrity ... OK

   Booting using the fdt blob at 0x885505c0

   Loading Kernel Image ... OK

   Loading Ramdisk to 8c400000, end 90000000 ... OK

   Loading Device Tree to 8c3f4000, end 8c3ffbac ... OK

 

Starting kernel ...

=============================================

When they tried to debug it after connecting JTAG, they found it was suspended in 'Calibrate_delay( )' function. 

Could you please let me know your opinion where they should check in this case?

They checked and tried to have DDR3 memory test, but could not find any issue in their DDR3 memory test.

Their SW is  Linux PSDK 6.03, and there was no issue in their custom board with AM3352BZCZD80 .

Thanks and Best Regards,

SI.

  • 0
    TI__Guru 70490 points

    Hi SI, 

    AM3352BZCZD80 (800MHz)

    AM3352BZCZA100 (1GHz) 

    Depending on the max speed detected in SPL code via calling am335x_get_efuse_mpu_max_freq(),

    - DPLL_MPU parameters are setup via calling get_dpll_mpu_params()

    - VDD_MPU, VDD_CORE are setup via calling scale_vcores() to configure PMIC

    Specifically VDD_MPU operating on Nitro OPP in order to supporting 1GHz speed needs to be met according to VDD_MPU (Nitro OPP) specified in AM335x datasheet.

    1. Have we measured VDD_MPU?

    2. Additionally for testing purpose only, rebuild SPL/uboot by skipping max speed detection from reading efuse, instead hard coding to always return “MPUPLL_M_800” in am335x_get_efuse_mpu_max_freq(). 

    Best,

    -Hong

  • 0 in reply to Hong Guan64
    TI__Mastermind 31050 points

    Hi Hong,

    This issue was resolved.

    I found the VDD_MPU is only 1.1V while I checked your question, and this issue was resolved after using 1.325V from datasheet.

    Thanks and Best Regards,

    SI.