• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 639 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.

Linux/DRA75: TI OMAP Jacinto 6 eMMC host controller support for eMMC device v5.1

Vivek Pernamitta
Prodigy 170 points
Part Number: DRA75

Tool/software: Linux

HI TI Team,

We have  eMMC v5.1  device is connected to TI OMAP J6 eMMC Host controller, We see there is an file system (ext4 journal enable/disable) corruption issue with sudden power off after multiple times, When we see TRM It is mentioned that  Full compliance with MMC/eMMC command/response sets as defined in the JC64 MMC/eMMC standard specification, v4.5.

Is DRA75x (J6) is also compliance with v5.1 eMMc . We are using linux kernel v 4.4.84. Issue is observed even when  cache is enabled/disabled.

Could you please assist. Thanks in advance.

Regards,

Vivek

  • 0
    TI__Mastermind 42515 points
    Hi Vivek,

    I have forwarded your question to an expert to look at the issue, but could you attach the kernel log when the issue occurs?

    Thanks,
    Yordan
  • 0
    TI__Mastermind 33390 points

    Hi Vivek,

    When you connect v5.1 eMMC part, it should be backward compatible with v4.5 controller.

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Prodigy 170 points
    Hi Vishal and Yordan,

    This below crash is occurring at manual power off after 70~100 cycles.

    I have attached the snippet of crash log.

    [Thu Sep 20 12:30:23 2018] [ 27.259245] EXT4-fs error: 54 callbacks suppressed
    [Thu Sep 20 12:30:23 2018] [ 27.264734] EXT4-fs error (device mmcblk0p9) in ext4_free_inode:383: Corrupt filesystem
    [Thu Sep 20 12:30:23 2018] [ 27.450847] EXT4-fs error (device mmcblk0p9): ext4_ext_remove_space:2980: inode #325: comm ProfileManagerT: pblk 9269 bad header/extent: invalid magic - magic d5d9, entries 63749, max 41248(0), depth 55139(0)
    [Thu Sep 20 12:30:23 2018] [ 27.491255] EXT4-fs error (device mmcblk0p9) in ext4_ext_truncate:4669: Corrupt filesystem
    [Thu Sep 20 12:30:23 2018] [ 27.520980] EXT4-fs error (device mmcblk0p9): ext4_find_extent:910: inode #325: comm ProfileManagerT: pblk 9269 bad header/extent: invalid magic - magic d5d9, entries 63749, max 41248(0), depth 55139(0)
    [Thu Sep 20 12:30:23 2018] [ 27.560541] EXT4-fs error (device mmcblk0p9): ext4_ext_remove_space:2980: inode #325: comm ProfileManagerT: pblk 9269 bad header/extent: invalid magic - magic d5d9, entries 63749, max 41248(0), depth 55139(0)
    [Thu Sep 20 12:30:23 2018] [ 27.600433] EXT4-fs error (device mmcblk0p9) in ext4_ext_truncate:4669: Corrupt filesystem


    Thanks and Regards,
    Vivek
  • 0 in reply to Vivek Pernamitta
    TI__Mastermind 33390 points
    Hi Vivek,

    Does the boot stop or the fsck is able to repair and continue?
    Could you do the same experiment with proper shutdown and see if the behavior is seen after 70 - 100 cycles?

    If the abrupt power off is done in middle of write operation, there is a possibility of corruption.

    Regards,
    Vishal
  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33390 points
    Any update on the previous questions?
  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33390 points

    Any update on the questions asked previously?