• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 100 subscribers
  • Views 767 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.

am3358 clock problem

xiaolong zhong
Prodigy 210 points

Other Parts Discussed in Thread: TPS65217

Hi, all

    I designed a customer board with DDR3 of k4b2g1646e-bck0, but I got a warning from the kernel log :

clock: Could not find fieldval 0 for clock dpll_core_m6_ck

    Is it just a warning or something was wrong ?

Best Regards

  • 0
    TI__Guru**** 393215 points

    Hi,

    What software are you using? Could you attach a log file?

  • 0 in reply to Biser Gatchev-XID
    Prodigy 210 points

        Hi, Biser

        I use ti-sdk-am335x-evm-06.00.00.00, My board is copy from beaglebone black, and I use TPS65217. the log info is:

    [ 0.000000] Linux version 3.2.0 (root@Vm-ubuntu) (gcc version 4.7.3 20130226 (prerelease) Fri Mar 21 17:23:15 CST 2014
    [ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
    [ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
    [ 0.000000] Machine: am335xevm
    [ 0.000000] Memory policy: ECC disabled, Data cache writeback
    [ 0.000000] AM335X ES1.0 (sgx neon )
    [ 0.000000] ---------------------------------------------[ cut here ]----------------------------------------------
    [ 0.000000] WARNING: at arch/arm/mach-omap2/clkt_clksel.c:194 omap2_clksel_recalc+0xc8/0x134()
    [ 0.000000] clock: Could not find fieldval 0 for clock dpll_core_m6_ck parent dpll_core_x2_ck
    [ 0.000000] Modules linked in:
    [ 0.000000] Backtrace:
    [ 0.000000] [<c0017dbc>] (dump_backtrace+0x0/0x10c) from [<c04113d4>] (dump_stack+0x18/0x1c)
    [ 0.000000] r6:c0030b28 r5:00000009 r4:c05d1e78 r3:c05f308c
    [ 0.000000] [<c04113bc>] (dump_stack+0x0/0x1c) from [<c003e610>] (warn_slowpath_common+0x54/0x6c)
    [ 0.000000] [<c003e5bc>] (warn_slowpath_common+0x0/0x6c) from [<c003e6cc>] (warn_slowpath_fmt+0x38/0x40)
    [ 0.000000] r8:80000200 r7:c064eaa4 r6:00000000 r5:c05e4c38 r4:00000000
    [ 0.000000] r3:00000009
    [ 0.000000] [<c003e694>] (warn_slowpath_fmt+0x0/0x40) from [<c0030b28>] (omap2_clksel_recalc+0xc8/0x134)
    [ 0.000000] r3:00000000 r2:c04fe938
    [ 0.000000] [<c0030a60>] (omap2_clksel_recalc+0x0/0x134) from [<c0034ba0>] (propagate_rate+0x34/0x54)
    [ 0.000000] r6:c064eadc r5:c05e4b38 r4:c05e4c38
    [ 0.000000] [<c0034b6c>] (propagate_rate+0x0/0x54) from [<c0034bac>] (propagate_rate+0x40/0x54)
        It since that I get the same problem as the forum: http://e2e.ti.com/support/arm/sitara_arm/f/791/t/305535.aspx.
    but I didn't mark the pmic init (am33xx_spl_board_init).
     
    Best Regards
  • 0 in reply to Biser Gatchev-XID
    Prodigy 210 points

    Hi, Biser

        Thanks for your help, The problem have been solved.

        Since my board is designed with TPS65217, and we do not use the EEPROM. I skip the funtion of read_eeprom() and initialize header.config with SKU#01, So the function of am33xx_spl_board_init consider my board to be SK and init TP65910.