Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 210 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.

AM623: AM623 deferred issue

Rio Chan
Genius 14000 points
Part Number: AM623

Tool/software:

Champs:

How to resolve those 3 deferred  issues in the SDK10.07?

[ 21.852116] platform fa00000.mmc: deferred probe pending
[ 21.857490] platform regulator-3: deferred probe pending
[ 21.862805] platform 2b300050.target-module: deferred probe pending

BR Rio

  • 0
    TI__Guru 61997 points

    Hi Rio,

    this happens on a perfector "healthy" / normal Kernel boot. If certain dependencies for a given driver are not in place at time of probe the Kernel will try to probe this module again later, that's called deferred probe. Only if the "deferred probe" fails several times this will result in an error with a given driver/module.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Genius 14000 points

    Hi AD:

    Yes, I know, but I dont know how to resolve this 1 by 1...:(.

    I already tried everything.

    9.2 SDK wont give me those errors.

    BR Rio

  • 0 in reply to Rio Chan
    TI__Guru 61997 points

    Hi Rio,

    as per email discussion, please share a complete(!) boot log of booting your SDK v10-based image on the custom HW Including U-Boot and everything. Then, also provide the output of `ls -al /lib/modules/*`.

    Also, we need to stick to using either E2E (preferred) or email to discuss this (and other) concerns; otherwise it becomes confusing and creates too much overhead.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Genius 14000 points

    Hi AD:

    I forced the SD card working as Legacy mode by setting this, now, the problem is resolved.

    BR Rio


    sdhci1: mmc@fa00000 {
    compatible = "ti,am62-sdhci";
    reg = <0x00 0x0fa00000 0x00 0x1000>, <0x00 0x0fa08000 0x00 0x400>;
    interrupts = <GIC_SPI 83 IRQ_TYPE_LEVEL_HIGH>;
    power-domains = <&k3_pds 58 TI_SCI_PD_EXCLUSIVE>;
    clocks = <&k3_clks 58 5>, <&k3_clks 58 6>;
    clock-names = "clk_ahb", "clk_xin";
    /*bus-width = <4>;* Rio Fix Delta*/
    bus-width = <1>;
    ti,clkbuf-sel = <0x7>;
    ti,otap-del-sel-legacy = <0x8>;
    /*ti,otap-del-sel-sd-hs = <0x0>;*/
    /*ti,otap-del-sel-sdr12 = <0x0>;*/
    /*ti,otap-del-sel-sdr25 = <0x0>;*/
    /*ti,otap-del-sel-sdr50 = <0x8>;*/
    /*ti,otap-del-sel-sdr104 = <0x7>;*/
    /*ti,otap-del-sel-ddr50 = <0x4>;*/
    ti,itap-del-sel-legacy = <0xa>;
    /*ti,itap-del-sel-sd-hs = <0x1>;*/
    /*ti,itap-del-sel-sdr12 = <0xa>;*/
    /*ti,itap-del-sel-sdr25 = <0x1>;*/
    status = "disabled";

  • 0 in reply to Rio Chan
    TI__Guru 61997 points

    Hi Rio,

    Rio Chan said:
    I forced the SD card working as Legacy mode by setting this, now, the problem is resolved.

    I'm glad you found a workaround to get this to boot; however it should not be needed. As per separate email discussion there have been MMC-tuning related changes in SDK v10.0 that might be causing a regression here; something we need to urgently investigate and fix, if needed.

    Let's leave this E2E thread open so we can document any findings for knowledge sharing purposes.

    Regards, Andreas