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.

AM62A7: ❗︎ MMC1 error printing

Part Number: AM62A7

Tool/software:sdk806 sdk902

When booting from the SD card, there is a high probability that mmc1 will have an error printing. What is the reason for this

[    1.455017] mmcblk0boot1: mmc0:0001 AGUF4R partition 2 31.9 MiB
[    1.464022] mmc1: CQHCI version 5.10
[    1.465132] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[    1.465814] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[    1.465821] debugfs: Directory 'pd:182' with parent 'pm_genpd' already present!
[    1.467343] mmcblk0rpmb: mmc0:0001 AGUF4R partition 3 4.00 MiB, chardev (237:0)
[    1.468129] ALSA device list:
[    1.468133]   No soundcards found.
[    1.509526] mmc1: SDHCI controller on fa00000.mmc [fa00000.mmc] using ADMA 64-bit
[    1.512989]  mmcblk0: p1 p2 p3
[    1.524972] Waiting for root device PARTUUID=b96f8d92-02...
[    1.574775] mmc1: Got data interrupt 0x00200000 even though no data operation was in progress.
[    1.583373] mmc1: sdhci: ============ SDHCI REGISTER DUMP ===========
[    1.589798] mmc1: sdhci: Sys addr:  0x00000000 | Version:  0x00001004
[    1.596222] mmc1: sdhci: Blk size:  0x00007040 | Blk cnt:  0x00000001
[    1.602646] mmc1: sdhci: Argument:  0x00000000 | Trn mode: 0x00000013
[    1.609069] mmc1: sdhci: Present:   0x01ff0000 | Host ctl: 0x0000001f
[    1.615493] mmc1: sdhci: Power:     0x0000000f | Blk gap:  0x00000080
[    1.621916] mmc1: sdhci: Wake-up:   0x00000000 | Clock:    0x00000007
[    1.628339] mmc1: sdhci: Timeout:   0x00000000 | Int stat: 0x00000000
[    1.634763] mmc1: sdhci: Int enab:  0x03ff008b | Sig enab: 0x03ff008b
[    1.641186] mmc1: sdhci: ACmd stat: 0x00000000 | Slot int: 0x00000000
[    1.647610] mmc1: sdhci: Caps:      0x3de8c801 | Caps_1:   0x18002407
[    1.654033] mmc1: sdhci: Cmd:       0x0000133a | Max curr: 0x00000000
[    1.660457] mmc1: sdhci: Resp[0]:   0x00000000 | Resp[1]:  0x00eddf7f
[    1.666880] mmc1: sdhci: Resp[2]:   0x325b5900 | Resp[3]:  0x00400e00
[    1.673303] mmc1: sdhci: Host ctl2: 0x0000000b
[    1.677733] mmc1: sdhci: ADMA Err:  0x00000000 | ADMA Ptr: 0x0000000880fec200
[    1.684849] mmc1: sdhci: ============================================
[    1.695868] mmc1: new ultra high speed SDR104 SDHC card at address 5048
[    1.703000] mmcblk1: mmc1:5048 SD32G 29.7 GiB 
[    1.709189]  mmcblk1: p1 p2
[    1.877715] EXT4-fs (mmcblk1p2): 1 orphan inode deleted
[    1.882974] EXT4-fs (mmcblk1p2): recovery complete
[    1.896745] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[    1.904900] VFS: Mounted root (ext4 filesystem) on device 179:98

  • This seems to be caused by the opening of 1.8V. Turning off 1.8V does not result in this printing, but the enumeration speed cannot reach sdr104 and can only be in hs mode

    May I ask how to remove this print in sdr 104 mode

    The interrupt mask is SDHCI-INT-DATA_cRC


    @@ -772,6 +772,7 @@ &sdhci1 {
            pinctrl-0 = <&main_mmc1_pins_default>;
            ti,driver-strength-ohm = <50>;
            disable-wp;
    +       no-1-8-v;
     };
    

    [ 1.586829] mmc1: new high speed SDHC card at address 5048
    [ 1.592797] mmcblk1: mmc1:5048 SD32G 29.7 GiB
    [ 1.599406] mmcblk1: p1 p2

  • Hello,

    I have taken note of the query. Please allow me sometime to go through the findings and get back to you.

    Thanks for your patience!!

  • hello:

    Please help evaluate whether this is a problem and if it does not affect it, does it mean that I can handle it this way? Add a refund earlier below

    	pr_err("%s: Got data interrupt 0x%08x even though no data operation was in progress-zyk.result:0x%08x\n",
    		       mmc_hostname(host->mmc), (unsigned)intmask,(intmask&SDHCI_INT_DATA_CRC));
    		sdhci_dumpregs(host);

    add this.

    if (intmask & SDHCI_INT_DATA_CRC)
    {
    return;
    }

  • Have you received a reply yet

  • Hello,

    Apologies for the delay in response.

    Could you please clarify the following questions to evaulate the issue better?

    • Do you see the issue with different SD card brands?
    • The Processor SDK version you are using & the Linux Kernel version?
    • Does the Kernel or the MMC driver become unresponsive after the error?
    • What is the probability of this issue occuring?

    Regards,

    Prashant