• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 467 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/DRA726: Micro SD issue

Michel Catudal
Genius 3825 points

Part Number: DRA726

Tool/software: Linux

Code is running out of the eMMC with kernel based on kernel linux-4.4.41+gitAUTOINC+f9f6f0db2d-gf9f6f0db2d from 3.03 SDK

Proper modification for custom DRA726 board made including added support for custom LVDS LCD and Egalax touch screen.

For test I am using the code in the SDK mentioned with a few of the unnecessary services masked.

Our customized yocto recipes are based on the automotive SDK but since weston always dies on boot I cannot use it for our first prototypes. The industrial SDK appears a lot more stable.

A number 4 Sandisk micro SD is permanently in the micro SD card. This is a proprietary database from Navionics (cost varies depending on the quantity, can be as much as $200)

During development after several crashes it is no longer recognized. I cannot do an fsck.vfat on it because it doesn't even appear on the dev directory so it cannot be mounted.

I am concerned that with our customer who has the battery disconnect "feature" this will occur. No matter how often we tell those people to use the ignition first they will use the battery disconnect to shut the system down. The PMIC has some kind of protection for itself but not for the filesystem.

Navionics requires the micro SD to be mounted rw so mounting ro is not an option.

This bring up another subject, how do we make it such that the boot partition is not mounted? Even if I put it in /etc/fstab with noauto it still gets mounted.

I am concerned that after a while it will no longer be able to boot if the same condition occurs as on the micro SD.

When we get new hardware with the QSPI connection fixed I will boot of that but in the current board that is not an option.

Michel Catudal

ACTIA Corp

  • 0
    TI__Guru*** 125430 points

    Michel Catudal said:
    During development after several crashes it is no longer recognized.

    Can the card be recognized in a Linux PC?  Can it be fixed from the PC?

    Michel Catudal said:
    I am concerned that with our customer who has the battery disconnect "feature" this will occur.

    In my opinion, if you're going to make that a feature, then you need to have a means of keeping the rail up long enough to cleanly unmount the file system.  Or perhaps another approach might be to use a file system that's more tolerant of that sort of thing.  I'm not a FS expert, so I don't have specific suggestions on that one.

  • 0
    TI__Guru*** 125430 points

    Michel Catudal said:
    This bring up another subject, how do we make it such that the boot partition is not mounted?

    That appears to be udev-related:

    • /etc/udev/rules.d/automount.rules
    • /etc/udev/scripts/mount.sh

  • 0 in reply to Brad Griffis
    Genius 3825 points
    Brad,

    I am usually able to clear the dirty flag with fsck on the PC. This is not possible on the board because it doesn't even appear as a device, thus it is not possible to do a fsck on it. The customer would not know how to do this.

    Michel