• State
  • Locked Locked
  • Replies 42 replies
  • Subscribers 98 subscribers
  • Views 1592 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.

DRA756: DRA756: System files become read-only

user6252411
Intellectual 340 points
Part Number: DRA756

1、At present, our J6 project USES 8G EMMC. At present, we set the system file to read and write by default. During the process of testing switch or reading and writing to the file, the system file will become read-only.Changed to read only and can only be fixed with the repair command：fsck.ext4 –p /dev/mmcblk0p1；

2、Modify the J6 system fstab file to mount the root directory as read-only after the system is started. After repeatedly running up and down for a period of time, there will be an error when executing "fsck.ext4-p /dev/mmcblk0p1". The information is as follows：

root@dra7xx-evm:~# fsck.ext4 -p /dev/mmcblk0p1

rootfs contains a file system with errors, check forced.

rootfs: 3470/7168 files (0.0% non-contiguous), 21493/28672 blocks

What are the possible reasons for this, and how do you find them in terms of software and hardware?ERROR dmesg.txt

3、Power up and down is prone to problems, sometimes I did not power, just frequently copy and delete the file system; Sometimes the file system becomes read-only. Is the system software incompatible with EMMC? Or is there a bug somewhere else? Help give the analysis suggestion; I understand that EMMC is relatively stable, but now I find it is easy to make mistakes？

4、We use the kenel version number：Linux version 3.14.63；

5、I have learned from the EMMC supplier that this is not a problem of hardware design, but a problem of software design. What are the possible reasons?

  • 0
    TI__Mastermind 33390 points

    Hi,

    Few questions.
    - Could you share the full kernel logs when the issue happens?
    - What speed more are you operating eMMC on?
    - The kernel version is old, which SDK are you using?
    - Were there any hardware changes recently?

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、- Could you share the full kernel logs when the issue happens?

    reply：Refer to the attachment

    Fullscreen ERR0R dmesg.txt Download 
    root@dra7xx-evm:~# 
root@dra7xx-evm:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.14.63 (root@ubuntu) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #80 SMP PREEMPT Tue Oct 23 02:07:32 PDT 2018
[    0.000000] CPU: ARMv7 Processor [412fc0f2] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[    0.000000] Truncating memory at 0x80000000 to fit in 32-bit physical address space
[    0.000000] Machine model: TI DRA742
[    0.000000] Reserved memory: created CMA memory pool at 0x94000000, size 80 MiB
[    0.000000] Reserved memory: initialized node ipu2_cma@95800000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x99000000, size 64 MiB
[    0.000000] Reserved memory: initialized node dsp1_cma@99000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x9d000000, size 32 MiB
[    0.000000] Reserved memory: initialized node ipu1_cma@9d000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created CMA memory pool at 0x9f000000, size 16 MiB
[    0.000000] Reserved memory: initialized node dsp2_cma@9f000000, compatible id shared-dma-pool
[    0.000000] Reserved memory: created DMA memory pool at 0xa8000000, size 32 MiB
[    0.000000] Reserved memory: initialized node cmem@A6000000, compatible id shared-dma-pool
[    0.000000] cma: CMA: reserved 24 MiB at ae000000
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 515839
[    0.000000] free_area_init_node: node 0, pgdat c097f280, node_mem_map ecf8e000
[    0.000000]   Normal zone: 1520 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 186368 pages, LIFO batch:31
[    0.000000]   HighMem zone: 2576 pages used for memmap
[    0.000000]   HighMem zone: 329471 pages, LIFO batch:31
[    0.000000] DRA752 ES2.0
[    0.000000] PERCPU: Embedded 8 pages/cpu @ecf47000 s8704 r8192 d15872 u32768
[    0.000000] pcpu-alloc: s8704 r8192 d15872 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 514319
[    0.000000] Kernel command line: console=ttyO0,115200n8 vram=16M root=/dev/mmcblk0p1 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1453752K/2063356K available (6391K kernel code, 675K rwdata, 2252K rodata, 372K init, 255K bss, 609604K reserved, 1317884K highmem)
[    0.000000] Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
    lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc08790a4   (8645 kB)
      .init : 0xc087a000 - 0xc08d7200   ( 373 kB)
      .data : 0xc08d8000 - 0xc0980f10   ( 676 kB)
       .bss : 0xc0980f1c - 0xc09c0bfc   ( 256 kB)
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] OMAP clockevent source: timer1 at 32786 Hz
[    0.000030] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 65536000000000ns
[    0.000030] OMAP clocksource: 32k_counter at 32768 Hz
[    0.000427] Architected cp15 timer(s) running at 6.14MHz (virt).
[    0.000462] sched_clock: 56 bits at 6MHz, resolution 162ns, wraps every 2794592043008ns
[    0.000470] Switching to timer-based delay loop
[    0.001472] Console: colour dummy device 80x30
[    0.001488] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[    0.001494] This ensures that you still see kernel messages. Please
[    0.001500] update your kernel commandline.
[    0.001515] Calibrating delay loop (skipped), value calculated using timer frequency.. 12.29 BogoMIPS (lpj=61475)
[    0.001528] pid_max: default: 32768 minimum: 301
[    0.001643] Security Framework initialized
[    0.001692] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.001703] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.025028] Initializing cgroup subsys net_cls
[    0.025063] CPU: Testing write buffer coherency: ok
[    0.025316] /cpus/cpu@0 missing clock-frequency property
[    0.025352] /cpus/cpu@1 missing clock-frequency property
[    0.025363] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[    0.025387] Setting up static identity map for 0x80644068 - 0x806440d8
[    0.080806] CPU1: Booted secondary processor
[    0.080835] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[    0.080964] Brought up 2 CPUs
[    0.080980] SMP: Total of 2 processors activated (24.59 BogoMIPS).
[    0.080986] CPU: All CPU(s) started in SVC mode.
[    0.081404] devtmpfs: initialized
[    0.081999] VFP support v0.3: implementor 41 architecture 4 part 30 variant f rev 0
[    0.083745] omap_hwmod: l3_main_2 using broken dt data from ocp
[    0.097346] omap_hwmod: tptc0 using broken dt data from edma-controller
[    0.097883] omap_hwmod: tptc1 using broken dt data from edma-controller
[    0.192454] omap_hwmod: dcan1: _wait_target_disable failed
[    0.291564] pinctrl core: initialized pinctrl subsystem
[    0.292304] regulator-dummy: no parameters
[    0.296652] NET: Registered protocol family 16
[    0.298451] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.300519] cpuidle: using governor ladder
[    0.300528] cpuidle: using governor menu
[    0.347327] syscon 4a002000.tisysconcore: regmap [mem 0x4a002000-0x4a0026cf] registered
[    0.347664] syscon 4a002e00.tisyscon: regmap [mem 0x4a002e00-0x4a002e7b] registered
[    0.350262] gpiochip_add: registered GPIOs 0 to 31 on device: gpio
[    0.350515] OMAP GPIO hardware version 0.1
[    0.351239] gpiochip_add: registered GPIOs 32 to 63 on device: gpio
[    0.352067] gpiochip_add: registered GPIOs 64 to 95 on device: gpio
[    0.352905] gpiochip_add: registered GPIOs 96 to 127 on device: gpio
[    0.353771] gpiochip_add: registered GPIOs 128 to 159 on device: gpio
[    0.354673] gpiochip_add: registered GPIOs 160 to 191 on device: gpio
[    0.355565] gpiochip_add: registered GPIOs 192 to 223 on device: gpio
[    0.356475] gpiochip_add: registered GPIOs 224 to 255 on device: gpio
[    0.363665] platform 40800000.dsp: assigned reserved memory node dsp1_cma@99000000
[    0.383126] No ATAGs?
[    0.383154] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.383163] hw-breakpoint: maximum watchpoint size is 8 bytes.
[    0.385917] OMAP DMA hardware revision 0.0
[    0.412112] bio: create slab <bio-0> at 0
[    0.427130] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.434160] omap-dma-engine 4a056000.dma-controller: OMAP DMA engine driver
[    0.434758] of_get_named_gpiod_flags exited with status 0
[    0.435006] evm_3v3_sd: 3300 mV 
[    0.435140] of_get_named_gpiod_flags exited with status 0
[    0.435367] evm_3v3_sd4: 3300 mV 
[    0.435482] of_get_named_gpiod_flags: can't parse gpios property of node '/fixedregulator-evm_3v3_sw[0]'
[    0.435686] evm_3v3_sw: 3300 mV 
[    0.435790] of_get_named_gpiod_flags: can't parse gpios property of node '/fixedregulator-aic_dvdd[0]'
[    0.436003] aic_dvdd: 1800 mV 
[    0.436061] aic_dvdd: supplied by evm_3v3_sw
[    0.436204] of_get_named_gpiod_flags exited with status 0
[    0.436417] vtt_fixed: 1350 mV 
[    0.439892] vgaarb: loaded
[    0.440346] i2c-core: driver [palmas] using legacy suspend method
[    0.440355] i2c-core: driver [palmas] using legacy resume method
[    0.440970] SCSI subsystem initialized
[    0.441413] libata version 3.00 loaded.
[    0.442247] usbcore: registered new interface driver usbfs
[    0.442412] usbcore: registered new interface driver hub
[    0.442596] usbcore: registered new device driver usb
[    0.444893] palmas 0-0058: IRQ missing: skipping irq request
[    0.445226] palmas 0-0058: Muxing GPIO 2e, PWM 0, LED 0
[    0.445367] prom_parse: Bad cell count for /ocp/i2c@48070000/tps659038@58
[    0.447435] smps123: 850 <--> 1500 mV at 1080 mV 
[    0.449047] smps45: 850 <--> 1500 mV at 990 mV 
[    0.450644] smps6: 850 <--> 1500 mV at 1080 mV 
[    0.453723] smps7: 850 <--> 1500 mV at 1060 mV 
[    0.455338] smps8: 850 <--> 1500 mV at 1010 mV 
[    0.456758] smps9: 1800 mV 
[    0.461247] ldo1: 1800 <--> 3300 mV at 3000 mV 
[    0.471485] ldo2: 3300 mV 
[    0.481117] ldo3: 1800 mV 
[    0.481963] LDO4: at 1800 mV 
[    0.482556] LDO5: no parameters
[    0.483154] LDO6: no parameters
[    0.483742] LDO7: no parameters
[    0.484321] LDO8: no parameters
[    0.491148] ldo9: 1050 mV 
[    0.501236] ldoln: 1800 mV 
[    0.511163] ldousb: 3300 mV 
[    0.511852] REGEN1: no parameters
[    0.512365] regen2: no parameters
[    0.512939] sysen1: no parameters
[    0.513507] sysen2: no parameters
[    0.513768] omap_i2c 48070000.i2c: bus 0 rev0.12 at 400 kHz
[    0.514239] pps_core: LinuxPPS API ver. 1 registered
[    0.514248] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.514363] PTP clock support registered
[    0.515664] omap-mailbox 48840000.mailbox: omap mailbox rev 0x400
[    0.515941] omap-mailbox 48842000.mailbox: omap mailbox rev 0x400
[    0.516773] omap-iommu 40d01000.mmu: 40d01000.mmu registered
[    0.516882] omap-iommu 40d02000.mmu: 40d02000.mmu registered
[    0.516985] omap-iommu 55082000.mmu: 55082000.mmu registered
[    0.518245] NetLabel: Initializing
[    0.518255] NetLabel:  domain hash size = 128
[    0.518262] NetLabel:  protocols = UNLABELED CIPSOv4
[    0.518313] NetLabel:  unlabeled traffic allowed by default
[    0.518808] Switched to clocksource arch_sys_counter
[    0.537976] NET: Registered protocol family 2
[    0.538679] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.538744] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[    0.538897] TCP: Hash tables configured (established 8192 bind 8192)
[    0.538941] TCP: reno registered
[    0.538954] UDP hash table entries: 512 (order: 2, 16384 bytes)
[    0.538985] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[    0.539179] NET: Registered protocol family 1
[    0.539443] RPC: Registered named UNIX socket transport module.
[    0.539453] RPC: Registered udp transport module.
[    0.539460] RPC: Registered tcp transport module.
[    0.539466] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.539476] PCI: CLS 0 bytes, default 64
[    0.540521] hw perfevents: enabled with ARMv7 Cortex-A15 PMU driver, 7 counters available
[    0.541016] yt_initio_probe
[    0.541106] gpio-105 (CPU_EN_12VCAME): gpiod_request: status -16
[    0.543940] futex hash table entries: 512 (order: 3, 32768 bytes)
[    0.634517] bounce pool size: 64 pages
[    0.634789] VFS: Disk quotas dquot_6.5.2
[    0.634897] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.635507] NFS: Registering the id_resolver key type
[    0.635541] Key type id_resolver registered
[    0.635550] Key type id_legacy registered
[    0.635582] jffs2: version 2.2. (NAND) (SUMMARY)  \xffffffc2\xffffffa9 2001-2006 Red Hat, Inc.
[    0.635762] msgmni has been set to 697
[    0.639692] alg: No test for stdrng (krng)
[    0.639876] NET: Registered protocol family 38
[    0.639904] io scheduler noop registered
[    0.639913] io scheduler deadline registered
[    0.639946] io scheduler cfq registered (default)
[    0.646139] pinctrl-single 4a003400.pinmux: 281 pins at pa fc003400 size 1124
[    0.649042] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/axi@0/pcie@51000000[0]'
[    0.684618] dra7-pcie 51000000.pcie: PCI host bridge to bus 0000:00
[    0.684633] pci_bus 0000:00: root bus resource [io  0x1000-0x10000]
[    0.684645] pci_bus 0000:00: root bus resource [mem 0x20013000-0x2fffffff]
[    0.684656] pci_bus 0000:00: No busn resource found for root bus, will use [bus 00-ff]
[    0.684694] pci 0000:00:00.0: [104c:8888] type 01 class 0x060400
[    0.684726] pci 0000:00:00.0: reg 0x10: [mem 0x00000000-0x000fffff]
[    0.684749] pci 0000:00:00.0: reg 0x14: [mem 0x00000000-0x0000ffff]
[    0.684806] pci 0000:00:00.0: supports D1
[    0.684816] pci 0000:00:00.0: PME# supported from D0 D1 D3hot
[    0.685170] PCI: bus0: Fast back to back transfers disabled
[    0.685409] PCI: bus1: Fast back to back transfers enabled
[    0.685424] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    0.685438] pci_bus 0000:00: busn_res: [bus 00-ff] end is updated to 01
[    0.685526] pci 0000:00:00.0: BAR 0: assigned [mem 0x20100000-0x201fffff]
[    0.685542] pci 0000:00:00.0: BAR 1: assigned [mem 0x20020000-0x2002ffff]
[    0.685555] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.685575] pci 0000:00:00.0: PCI bridge to [bus 01]
[    0.685591] pci_bus 0000:00: resource 4 [io  0x1000-0x10000]
[    0.685601] pci_bus 0000:00: resource 5 [mem 0x20013000-0x2fffffff]
[    0.689792] pbias_mmc_omap5: 1800 <--> 3000 mV at 3000 mV 
[    0.690548] abb_mpu: 1100 <--> 1210 mV 
[    0.690924] abb_ivahd: 1060 <--> 1250 mV 
[    0.691281] abb_dspeve: 1060 <--> 1250 mV 
[    0.691639] abb_gpu: 1060 <--> 1280 mV 
[    0.692753] Serial: 8250/16550 driver, 10 ports, IRQ sharing enabled
[    0.696683] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/serial@4806a000[0]'
[    0.697074] 4806a000.serial: ttyS0 at MMIO 0x4806a000 (irq = 299, base_baud = 3000000) is a 8250
[    1.714771] console [ttyS0] enabled
[    1.718736] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/serial@48020000[0]'
[    1.719157] 48020000.serial: ttyS2 at MMIO 0x48020000 (irq = 300, base_baud = 3000000) is a 8250
[    1.728369] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/serial@48422000[0]'
[    1.728735] 48422000.serial: ttyS7 at MMIO 0x48422000 (irq = 301, base_baud = 3000000) is a 8250
[    1.739295] omap_rng 48090000.rng: OMAP Random Number Generator ver. 20
[    1.746448] [drm] Initialized drm 1.1.0 20060810
[    1.761631] brd: module loaded
[    1.770189] loop: module loaded
[    1.773661] (hci_tty): inside hci_tty_init
[    1.778129] (hci_tty): allocated 250, 0
[    1.784385] ahci 4a140000.sata: SSS flag set, parallel bus scan disabled
[    1.791157] ahci 4a140000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
[    1.799742] ahci 4a140000.sata: flags: 64bit ncq sntf stag pm led clo only pmp pio slum part ccc apst 
[    1.810233] scsi0 : ahci_platform
[    1.814049] ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a1410ff] port 0x100 irq 334
[    1.823321] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.835806] m25p80 spi32766.0: found w25q128, expected s25fl256s1
[    1.842056] m25p80 spi32766.0: w25q128 (16384 Kbytes)
[    1.851026] libphy: Fixed MDIO Bus: probed
[    1.856457] PPP generic driver version 2.4.2
[    1.861278] usbcore: registered new interface driver asix
[    1.866842] usbcore: registered new interface driver ax88179_178a
[    1.873134] usbcore: registered new interface driver cdc_ether
[    1.879166] usbcore: registered new interface driver smsc95xx
[    1.885074] usbcore: registered new interface driver net1080
[    1.890914] usbcore: registered new interface driver cdc_subset
[    1.896996] usbcore: registered new interface driver zaurus
[    1.902785] usbcore: registered new interface driver cdc_ncm
[    1.909250] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.915807] ehci-pci: EHCI PCI platform driver
[    1.920439] ehci-omap: OMAP-EHCI Host Controller driver
[    1.926109] usbcore: registered new interface driver cdc_wdm
[    1.931977] usbcore: registered new interface driver usb-storage
[    1.938312] usbcore: registered new interface driver usbserial
[    1.944323] usbcore: registered new interface driver usbserial_generic
[    1.951028] usbserial: USB Serial support registered for generic
[    1.957195] usbcore: registered new interface driver option
[    1.962941] usbserial: USB Serial support registered for GSM modem (1-port)
[    1.971070] mousedev: PS/2 mouse device common for all mice
[    1.978958] i2c-core: driver [rtc-ds1307] using legacy suspend method
[    1.985430] i2c-core: driver [rtc-ds1307] using legacy resume method
[    1.992472] rtc rtc0: 48838000.rtcss: dev (254:0)
[    1.992496] omap_rtc 48838000.rtcss: rtc core: registered 48838000.rtcss as rtc0
[    2.000783] i2c /dev entries driver
[    2.004657] Driver for 1-wire Dallas network protocol.
[    2.010930] coproc iva_coproc: probe
[    2.014644] Adding alias for supply vdd,iva_coproc -> vdd,4a0025cc.voltdm
[    2.021482] Adding alias for supply vbb,iva_coproc -> vbb,4a0025cc.voltdm
[    2.029522] coproc iva_coproc: coproc_probe result=0
[    2.034547] coproc dsp_coproc: probe
[    2.038223] Adding alias for supply vdd,dsp_coproc -> vdd,4a0025e0.voltdm
[    2.045169] Adding alias for supply vbb,dsp_coproc -> vbb,4a0025e0.voltdm
[    2.053080] coproc dsp_coproc: coproc_probe result=0
[    2.063006] of_get_named_gpiod_flags exited with status 0
[    2.063018] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/mmc@4809c000[0]'
[    2.099063] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/mmc@480b4000[0]'
[    2.099074] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/mmc@480b4000[0]'
[    2.139031] of_get_named_gpiod_flags exited with status 0
[    2.139042] of_get_named_gpiod_flags: can't parse gpios property of node '/ocp/mmc@480d1000[0]'
[    2.168850] ata1: SATA link down (SStatus 0 SControl 300)
[    2.179483] ledtrig-cpu: registered to indicate activity on CPUs
[    2.185814] omap-aes 4b500000.aes: OMAP AES hw accel rev: 3.3
[    2.188873] mmc1: BKOPS_EN bit is not set
[    2.199037] mmc1: new high speed DDR MMC card at address 0001
[    2.205313] mmcblk0: mmc1:0001 MMC08G 7.26 GiB 
[    2.210121] mmcblk0boot0: mmc1:0001 MMC08G partition 1 4.00 MiB
[    2.216359] mmcblk0boot1: mmc1:0001 MMC08G partition 2 4.00 MiB
[    2.228191]  mmcblk0: p1 p2 p3 p4 p5 p6 p7
[    2.233683] omap-aes 4b700000.aes: OMAP AES hw accel rev: 3.3
[    2.240712] omap-des 480a5000.des: OMAP DES hw accel rev: 2.2
[    2.246501]  mmcblk0boot1: unknown partition table
[    2.252430]  mmcblk0boot0: unknown partition table
[    2.257365] alg: skcipher: setkey failed on test 5 for ecb-des-omap: flags=100
[    2.265011] alg: skcipher-ddst: setkey failed on test 5 for ecb-des-omap: flags=100
[    2.273110] alg: skcipher-ddst: setkey failed on test 5 for ecb-des-omap: flags=100
[    2.285918] omap-sham 4b101000.sham: hw accel on OMAP rev 4.3
[    2.291754] omap-sham 4b101000.sham: initialization failed.
[    2.297379] omap-sham: probe of 4b101000.sham failed with error -22
[    2.304362] usbcore: registered new interface driver usbhid
[    2.310045] usbhid: USB HID core driver
[    2.315784] extcon-usb-gpio extcon_usb1: GPIO lookup for consumer id
[    2.315796] extcon-usb-gpio extcon_usb1: using device tree for GPIO lookup
[    2.315807] of_get_named_gpiod_flags: can't parse gpios property of node '/extcon_usb1[0]'
[    2.315817] extcon-usb-gpio extcon_usb1: using lookup tables for GPIO lookup
[    2.315826] extcon-usb-gpio extcon_usb1: lookup for GPIO id failed
[    2.315836] extcon-usb-gpio extcon_usb1: GPIO lookup for consumer vbus
[    2.315845] extcon-usb-gpio extcon_usb1: using device tree for GPIO lookup
[    2.315854] of_get_named_gpiod_flags: can't parse gpios property of node '/extcon_usb1[0]'
[    2.315862] extcon-usb-gpio extcon_usb1: using lookup tables for GPIO lookup
[    2.315871] extcon-usb-gpio extcon_usb1: lookup for GPIO vbus failed
[    2.316099] extcon-usb-gpio extcon_usb1: extcon_usb1 node name: OTG
[    2.322667] extcon-usb-gpio extcon_usb2: GPIO lookup for consumer id
[    2.322678] extcon-usb-gpio extcon_usb2: using device tree for GPIO lookup
[    2.322688] of_get_named_gpiod_flags: can't parse gpios property of node '/extcon_usb2[0]'
[    2.322697] extcon-usb-gpio extcon_usb2: using lookup tables for GPIO lookup
[    2.322706] extcon-usb-gpio extcon_usb2: lookup for GPIO id failed
[    2.322716] extcon-usb-gpio extcon_usb2: GPIO lookup for consumer vbus
[    2.322724] extcon-usb-gpio extcon_usb2: using device tree for GPIO lookup
[    2.322733] of_get_named_gpiod_flags: can't parse gpios property of node '/extcon_usb2[0]'
[    2.322741] extcon-usb-gpio extcon_usb2: using lookup tables for GPIO lookup
[    2.322749] extcon-usb-gpio extcon_usb2: lookup for GPIO vbus failed
[    2.322972] extcon-usb-gpio extcon_usb2: extcon_usb1 node name: HOST
[    2.329802] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[    2.336411] ip_tables: (C) 2000-2006 Netfilter Core Team
[    2.341858] TCP: cubic registered
[    2.345189] Initializing XFRM netlink socket
[    2.349555] NET: Registered protocol family 17
[    2.354039] NET: Registered protocol family 15
[    2.358575] Bridge firewalling registered
[    2.362667] 8021q: 802.1Q VLAN Support v1.8
[    2.366912] Key type dns_resolver registered
[    2.371789] Adding alias for supply vdd,cpu0 -> vdd,4a003b20.voltdm
[    2.378088] Adding alias for supply vbb,cpu0 -> vbb,4a003b20.voltdm
[    2.385976] Power Management for TI OMAP4+ devices.
[    2.391055] ThumbEE CPU extension supported.
[    2.395349] Registering SWP/SWPB emulation handler
[    2.400172] SmartReflex Class3 initialized
[    2.405965] aic_dvdd: disabling
[    2.409147] evm_3v3_sd4: disabling
[    2.412560] evm_3v3_sd: disabling
[    2.415887] regulator-dummy: disabling
[    2.419916] dmm 4e000000.dmm: workaround for errata i878 in use
[    2.427570] dmm 4e000000.dmm: initialized all PAT entries
[    2.434672] omap_rtc 48838000.rtcss: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    2.443505] sr_init: No PMIC hook to init smartreflex
[    2.448794] sr_init: platform driver register failed for SR
[    2.468611] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[    2.498359] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[    2.505906] VFS: Mounted root (ext4 filesystem) on device 179:1.
[    2.512359] devtmpfs: mounted
[    2.731574] EXT4-fs (mmcblk0p6): recovery complete
[    2.736402] EXT4-fs (mmcblk0p6): mounted filesystem with ordered data mode. Opts: (null)
[    2.750240] EXT4-fs (mmcblk0p7): recovery complete
[    2.755061] EXT4-fs (mmcblk0p7): mounted filesystem with ordered data mode. Opts: (null)
[    2.790467] pinctrl-single 4a003400.pinmux: bad data for mux cpsw_default
[    2.797293] pinctrl-single 4a003400.pinmux: no pins entries for cpsw_default
[    2.805431] cpsw_phy_sel_probe:hzk gpio_request 51(GPIO2_19)
[    2.821427] cpsw 48484000.ethernet: Detected MACID = 88:3f:4a:7e:90:94
[    2.829085] cpsw 48484000.ethernet: cpsw: Detected MACID = 00:2c:70:ec:90:a9
[    2.884230] udevd[1077]: starting version 182
[    2.951476] EXT4-fs (mmcblk0p1): re-mounted. Opts: (null)
[    3.018839] davinci_mdio 48485000.mdio: davinci mdio revision 1.6
[    3.024970] davinci_mdio 48485000.mdio: detected phy mask fffffffe
[    3.036536] libphy: 48485000.mdio: probed
[    3.040595] davinci_mdio 48485000.mdio: phy[0]: device 48485000.mdio:00, id 0x600d8595, driver Broadcom BCM54210S
[    3.056607]  remoteproc0: 40800000.dsp is available
[    3.061603]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    3.070626]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    3.096519]  remoteproc0: registered virtio0 (type 7)
[    3.103172] can: controller area network core (rev 20120528 abi 9)
[    3.109625] NET: Registered protocol family 29
[    3.118904]  remoteproc0: powering up 40800000.dsp
[    3.124838] CAN device driver interface
[    3.129808]  remoteproc0: Booting fw image dra7-dsp1-fw.xe66, size 948568
[    3.143163] omap_hwmod: mmu0_dsp1: _wait_target_disable failed
[    3.149052] omap-iommu 40d01000.mmu: 40d01000.mmu: version 3.0
[    3.154960] omap-iommu 40d02000.mmu: 40d02000.mmu: version 3.0
[    3.162826] can: raw protocol (rev 20120528)
[    3.202243] omap_hwmod: dcan1: _wait_target_disable failed
[    3.213599] c_can_platform 4ae3c000.can: c_can_platform device registered (regs=fce3c000, irq=348)
[    3.228384] c_can_platform 48480000.can: c_can_platform device registered (regs=f04c8000, irq=349)
[    3.229685]  remoteproc0: remote processor 40800000.dsp is now up
[    3.245092] virtio_rpmsg_bus virtio0: rpmsg host is online
[    3.256096] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x36
[    3.270874] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x37
[    3.280505] virtio_rpmsg_bus virtio0: creating channel rpmsg-rpc addr 0x65
[    3.292049] rpmsg_rpc rpmsg2: probing service rpmsg-dce-dsp with src 1024 dst 101
[    3.303790] rpmsg_rpc rpmsg2: published functions = 8
[    3.306943] c_can_platform 4ae3c000.can can0: setting BTR=1c04 BRPE=0000
[    3.322964] c_can_platform 48480000.can can1: setting BTR=1c04 BRPE=0000
[    3.763748] dwc3 48890000.usb: otg: primary host xhci-hcd.0.auto registered
[    3.770760] dwc3 48890000.usb: otg: shared host xhci-hcd.0.auto registered
[    3.777664] dwc3 48890000.usb: otg: can't start till gadget registers
[    4.185274] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.191022] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1
[    4.199037] xhci-hcd xhci-hcd.1.auto: irq 424, io mem 0x488d0000
[    4.205195] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    4.212025] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.219290] usb usb1: Product: xHCI Host Controller
[    4.224187] usb usb1: Manufacturer: Linux 3.14.63 xhci-hcd
[    4.229706] usb usb1: SerialNumber: xhci-hcd.1.auto
[    4.235129] hub 1-0:1.0: USB hub found
[    4.238945] hub 1-0:1.0: 1 port detected
[    4.243120] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller
[    4.248841] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2
[    4.256672] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    4.263502] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.270768] usb usb2: Product: xHCI Host Controller
[    4.275665] usb usb2: Manufacturer: Linux 3.14.63 xhci-hcd
[    4.281180] usb usb2: SerialNumber: xhci-hcd.1.auto
[    4.286605] hub 2-0:1.0: USB hub found
[    4.290409] hub 2-0:1.0: 1 port detected
[    4.463763] random: mkfs.ext4 urandom read with 89 bits of entropy available
[    4.520289] udc 48890000.usb: registering UDC driver [g_mass_storage]
[    4.520320] Number of LUNs=8
[    4.528731] Mass Storage Function, version: 2009/09/11
[    4.539537] LUN: removable file: (no medium)
[    4.546730] Number of LUNs=1
[    4.549723] lun0: open backing file: /mnt/ramdrive/ext4-file
[    4.549735] LUN: file: /mnt/ramdrive/ext4-file
[    4.554194] Number of LUNs=1
[    4.557095] g_mass_storage gadget: adding config #1 'Linux File-Backed Storage'/bf0da39c
[    4.557166] g_mass_storage gadget: I/O thread pid: 1134
[    4.557180] g_mass_storage gadget: adding 'Mass Storage Function'/ec776e00 to config 'Linux File-Backed Storage'/bf0da39c
[    4.557199] g_mass_storage gadget: cfg 1/bf0da39c speeds: super high full
[    4.557207] g_mass_storage gadget:   interface 0 = Mass Storage Function/ec776e00
[    4.557218] g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11
[    4.564302] g_mass_storage gadget: userspace failed to provide iSerialNumber
[    4.568907] usb 1-1: new high-speed USB device number 2 using xhci-hcd
[    4.577969] g_mass_storage gadget: g_mass_storage ready
[    4.583265] dwc3 48890000.usb: otg: gadget gadget registered
[    4.588995] g_mass_storage gadget: usb_gadget_start
[    4.589015] g_mass_storage 48890000.usb: usb_gadget_udc_start
[    4.591456] g_mass_storage gadget: usb_gadget_stop
[    4.591495] g_mass_storage 48890000.usb: usb_gadget_udc_stop
[    4.591590] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.598396] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 3
[    4.608899] xhci-hcd xhci-hcd.0.auto: irq 423, io mem 0x48890000
[    4.617012] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[    4.626090] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.633533] usb usb3: Product: xHCI Host Controller
[    4.639001] usb usb3: Manufacturer: Linux 3.14.63 xhci-hcd
[    4.644520] usb usb3: SerialNumber: xhci-hcd.0.auto
[    4.651008] hub 3-0:1.0: USB hub found
[    4.654803] hub 3-0:1.0: 1 port detected
[    4.659582] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    4.667970] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 4
[    4.677404] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[    4.685641] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    4.693120] usb usb4: Product: xHCI Host Controller
[    4.698023] usb usb4: Manufacturer: Linux 3.14.63 xhci-hcd
[    4.704798] usb usb4: SerialNumber: xhci-hcd.0.auto
[    4.710650] hub 4-0:1.0: USB hub found
[    4.714444] hub 4-0:1.0: 1 port detected
[    4.729490] usb 1-1: New USB device found, idVendor=02e3, idProduct=0702
[    4.736228] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    4.744732] usb 1-1: Product: 35549
[    4.748882] usb 1-1: Manufacturer: 355
[    4.753632] usb-storage 1-1:1.0: USB Mass Storage device detected
[    4.761770] scsi1 : usb-storage 1-1:1.0
[    5.503375] net eth0: initializing cpsw version 1.15 (0)
[    5.591647] bcm54210s_config_init:hzk read1 RDB MODE_CONTROL=0x7e1c
[    5.597945] bcm54210s_config_init:hzk write RDB MODE_CONTROL=0x7e1b
[    5.608288] bcm54210s_config_init:hzk read2 RDB MODE_CONTROL=0x7f1b
[    5.616608] bcm54210s_config_init:hzk read1 RDB COPPER_MISCELLANEOUS_CONTROL=0x7167
[    5.624310] bcm54210s_config_init:hzk write RDB COPPER_MISCELLANEOUS_CONTROL=0x71e7
[    5.635847] bcm54210s_config_init:hzk read2 RDB COPPER_MISCELLANEOUS_CONTROL=0x71e7
[    5.643556] net eth0: phy found : id is : 0x600d8595
[    5.648652] cpsw_gmii_sel_dra7xx:hzk reg=3322 addr=fc002554
[    5.659925] 8021q: adding VLAN 0 to HW filter on device eth0
[    5.759327] scsi 1:0:0:0: Direct-Access     XDJA     Flash Disk       1.01 PQ: 0 ANSI: 4
[    5.775687] sd 1:0:0:0: [sda] 4294967295 512-byte logical blocks: (2.19 TB/1.99 TiB)
[    5.784730] sd 1:0:0:0: [sda] Test WP failed, assume Write Enabled
[    5.792066] sd 1:0:0:0: Attached scsi generic sg0 type 0
[    5.797564] sd 1:0:0:0: [sda] Cache data unavailable
[    5.802923] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    5.811279] sd 1:0:0:0: [sda] Test WP failed, assume Write Enabled
[    5.819265] sd 1:0:0:0: [sda] Cache data unavailable
[    5.824402] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    5.834334] random: nonblocking pool is initialized
[    5.842670]  sda: sda1
[    5.846782] sd 1:0:0:0: [sda] Test WP failed, assume Write Enabled
[    5.854963] sd 1:0:0:0: [sda] Cache data unavailable
[    5.860547] sd 1:0:0:0: [sda] Assuming drive cache: write through
[    5.868709] sd 1:0:0:0: [sda] Attached SCSI removable disk
[    7.645657] libphy: 48485000.mdio:00 - Link is Up - 1000/Full
[  612.582822] EXT4-fs error (device mmcblk0p1): __ext4_new_inode:987: comm touch: failed to insert inode 3424: doubly allocated?
[  612.595423] EXT4-fs (mmcblk0p1): Remounting filesystem read-only
    - What speed more are you operating eMMC on?

    reply：We use the system's default parameters，read speed 65MB，write speed 11MB


    3、- The kernel version is old, which SDK are you using?

    reply：How do I get the latest version of kenel, which is more changed than the version we used?


    4、 -Were there any hardware changes recently?

    reply：The hardware has not changed, but the problem persists on other projects；

    The default system file of other projects has been changed to read-only, but the following error still occurs when our project is changed to read-only:

    root@dra7xx-evm:~# fsck.ext4 -p /dev/mmcblk0p1
    rootfs contains a file system with errors, check forced.
    rootfs: 3441/7168 files (0.0% non-contiguous), 20452/28672 blocks

    5、Below is our reference schematic design：

    6、Attached is the specification that we use EMMC：8ＧＢ／MTFC8GLWDM-AIT

    eMMC_MTFC8GLWDM-AIT A_BGA153_Micron.pdf

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    List of all Linux SDK available here. Are all your projects based on Kernel 3.14?
    https://processors.wiki.ti.com/index.php/Category:Processor_SDK_Linux_Automotive

    Will get back to you on the schematics part if we see any issue.

    Could you also share your Kernel dts file?

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Thanks for your reply!

    Kernel DTS file, I'm in coordination!

    SDK is 03.04.00.03 version! 

    What might be the reason for my feedback?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    Are you using SDK version 03.04.00.03?

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33390 points

    Hi,

    Couple of comments in your schematics,

    -1-
    Why do you have the 22 ohm series resistors? The series resistors may cause signal integrity issue.

    -2-
    Could you double check the VDDI.1 connection? On our boards it's connected to GND.


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Why do you have the 22 ohm series resistors? The series resistors may cause signal integrity issue.

    reply:Signal is straight through, no series resistance.



    -2-
    Could you double check the VDDI.1 connection? On our boards it's connected to GND.

    replay:VDD1.1Just place the capacitor, there is no connection elsewhere,

    And I see in the demo that the circuit is also connected in this way.

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    The schematics you shared have 22 ohm resistors. It's not there on the board?






    Which SDK are you using?
    The kernel log you shared shows Kernel version 3.14, but you mentioned SDK version as 03.04.00.03 which is Kernel 4.4 based.


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、How do I view the SDK version number?

    2、Check there to see if EMMC enabled HS200, and if so, how to close it?Does this affect EMMC?

    3、What is the default read/write rate of EMMC in our system? Are there any protection mechanisms in the software？

    4、What is the possibility of the problem I feedback?

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、YES，Our schematic shows a 22R resistance；Here the resistance is relatively small, should not affect the software。

    2、We are checking the SDK version. Which SDK is more mature for the Kernel version of 3.14?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    1. You can look at git tree of Kernel and figure out which TI SDK you are using, If you are on kernel 3.14 look for git tags starting with glsdk-7. Based on your kernel log, you are most probably on 7.04.00.03 version.

    2. Based on log you shared you are not using HS200 mode. 

    [ 2.188873] mmc1: BKOPS_EN bit is not set
    [ 2.199037] mmc1: new high speed DDR MMC card at address 0001
    [ 2.205313] mmcblk0: mmc1:0001 MMC08G 7.26 GiB

    3. Based on the log you are using DDR50 mode.

    4. I have not seen the issue you are seeing. It could be a signal integrity issue on the board.



  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    1. Would it be possible to test without these resistors?

    2. You can try the tag glsdk-7.04.00.03.02 which has some additional fixes on top of 7.04.00.03 release (tag: glsdk-7.04.00.03)

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Thank you for your reply.

    1、Where can I check the mode Settings of EMMC?

    I have checked the specification of EMMC, which has the mode of DDR2 52M of EMMC

    2、How to test signal integrity？

    Is this problem an adaptation of the underlying driver and EMMC?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    I did not understand the question.

    Did you see my previous response? Could you test without those resistors? also try the Kernel tag I mentioned?

    Regards,
    Vishal

  • 0 in reply to user6252411
    Intellectual 340 points

    We downloaded the latest Kernel version 3.14 from the official website，SDK Version：7.04.00.03；

    We have made a comparison and found the following different places. Could you help to analyze the reasons and impacts of these changes?

    Refer to the attachment for different places：宇通精益达-J6系统文件对比.rar

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    The difference you are showing in the word document does not exist on our code base.

    Also, did you compare your code base against tag glsdk-7.04.00.03.02? This is the latest Kernel 3.14.

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    We refer to the source code from China TI technology side to get, SDK version is correct。Kernel version 3.14，SDK Version：7.04.00.03；

    The attachment is the version viewed by git command. The software found that the code we are using is newer than this one. Is the code provided by TI technology the latest? They are also downloaded from your website。

    After comparing MMC with ext4 file system, only block. C is different，

    Fullscreen iCard2文件版本对比.log Download 
    [BEGIN] 2020-4-9 15:24:29
de15ffbb6f c22b04c9c6c436fbc14f6c812643a7cf64ebcd18 -stat
usage: git diff [<options>] [<commit> [<commit>]] [--] [<path>...]
de15ffbb6f c22b04c9c6c436fbc14f6c812643a7cf64ebcd18 --stat
 .gitignore                                            |    1 -
 Makefile                                              |    2 +-
 arch/arm/boot/dts/Makefile                            |    2 -
 arch/arm/boot/dts/dra7-evm-infoadas.dts               |   86 --
 arch/arm/boot/dts/dra7-evm.dts                        |   42 +-
 arch/arm/boot/dts/dra7.dtsi                           |   12 +-
 arch/arm/boot/dts/dra72-evm-infoadas.dts              |   70 --
 arch/arm/boot/dts/dra72-evm-vision.dts                |   38 +-
 arch/arm/boot/dts/dra72-evm.dts                       |   49 +-
 arch/arm/boot/dts/dra75x-icard2-upgrade.dts           | 1200 -------------------
 arch/arm/boot/dts/dra75x-icard2.dts                   | 1524 ------------------------
 arch/arm/configs/dra75x_icard2_defconfig              | 4517 ------------------------------------------------------------------------
 arch/arm/configs/omap2plus_defconfig                  | 4274 +-------------------------------------------------------------------
 arch/arm/mach-omap2/Makefile                          |    3 -
 arch/arm/mach-omap2/board-initio.c                    |  204 ----
 arch/arm/mach-omap2/omap_hwmod_7xx_data.c             |   15 +-
 drivers/extcon/extcon-usb-gpio.c                      |   31 +-
 drivers/gpu/drm/omapdrm/omap_drv.c                    |   43 +-
 drivers/gpu/drm/omapdrm/omap_drv.h                    |    4 -
 drivers/gpu/drm/omapdrm/omap_gem.c                    |   64 --
 drivers/hid/hid-ids.h                                 |    3 -
 drivers/hid/usbhid/hid-quirks.c                       |    1 -
 drivers/media/Kconfig                                 |   14 -
 drivers/media/Makefile                                |    3 -
 drivers/media/device_control.c                        |  415 -------
 drivers/media/device_control.h                        |   38 -
 drivers/media/i2c/Kconfig                             |   10 -
 drivers/media/i2c/Makefile                            |    2 -
 drivers/media/i2c/nvp6124.c                           |  443 -------
 drivers/media/i2c/nvp6124.h                           |  370 ------
 drivers/media/i2c/nvp6124_fpd3.c                      | 2096 ---------------------------------
 drivers/media/i2c/ov1063x.c                           |  146 ---
 drivers/media/pwm_beep.c                              |  292 -----
 drivers/mmc/card/block.c                              |   22 -
 drivers/mtd/devices/m25p80.c                          |   21 +-
 drivers/net/ethernet/ti/cpsw-phy-sel.c                |    6 +-
 drivers/net/usb/qmi_wwan.c                            |    2 +-
 drivers/spi/Kconfig                                   |   13 -
 drivers/spi/Makefile                                  |    1 -
 drivers/spi/mcu_spi.c                                 |  522 ---------
 drivers/spi/mcu_spi.h                                 |   30 -
 drivers/spi/spi-atmel.c                               |    3 +-
 drivers/spi/spi-ti-qspi.c                             |  143 +--
 drivers/spi/spi.c                                     |    2 +-
 drivers/usb/serial/option.c                           |   18 +-
 drivers/usb/serial/qcserial.c                         |    2 +-
 drivers/usb/serial/usb_wwan.c                         |   13 -
 drivers/video/fbdev/omap2/displays-new/Kconfig        |    7 -
 drivers/video/fbdev/omap2/displays-new/Makefile       |    1 -
 drivers/video/fbdev/omap2/displays-new/panel-ch7026.c |  625 ----------
 fs/proc/root.c                                        |   32 -
 include/asm-generic/vmlinux.lds.h                     |    8 +-
 include/dt-bindings/pinctrl/dra.h                     |    4 +-
 include/linux/init.h                                  |    5 -
 include/uapi/drm/omap_drm.h                           |   12 +-
 include/uapi/linux/major.h                            |    6 -
 init/do_mounts.c                                      |    9 -
 init/main.c                                           |   66 +-
 sound/soc/codecs/Kconfig                              |    8 +-
 sound/soc/codecs/Makefile                             |    2 -
 sound/soc/codecs/nvp6124-codec.c                      |  180 ---
 sound/soc/codecs/tlv320aic3x.c                        |   95 --
 sound/soc/davinci/Kconfig                             |   13 -
 sound/soc/davinci/Makefile                            |   11 +-
 sound/soc/davinci/davinci-evm.c                       |   30 +-
 sound/soc/davinci/yt-davinci-mcasp.c                  | 2056 ---------------------------------
 sound/soc/davinci/yt-record-card0.c                   |  220 ----
 sound/soc/davinci/yt-record-card1.c                   |  220 ----
 68 files changed, 133 insertions(+), 20289 deletions(-)
huizk@ubuntu:~/iCard2_sdk/sdk_develop/vsdk0210-system/ti_components/os_tools/linux/kernel/omap$ 

[END] 2020-4-9 15:25:05

    What does this difference do? How do we troubleshoot the code?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    -1-

    The 3.14 maintenance code base is tag glsdk-7.04.00.03.02 from git tree http://git.omapzoom.org/?p=kernel/omap.git;a=summary
    It's difficult for me to comment on your code base based on git stats log you attached in last response.





    -2-

    The block.c code difference is not seen in our code base.
    http://git.omapzoom.org/?p=kernel/omap.git;a=blob;f=drivers/mmc/card/block.c;hb=glsdk-7.04.00.03.02


    -3-

    Can you try the test with those 22 ohm resistors removed from the board?


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Thank you for your reply！

    We use Kernel version 3.14，SDK Version：7.04.00.03；

    Later, we found that our code was equipped with ADAS function, but we turned off the ADAS function, not pure Linux, and the code should be visionSDK.

    I will  try the test with those 22 ohm resistors removed from the board.

    Please help to see the difference between our code and vsdk2.10. Which version of VSDK is corresponding to the latest 3.14?

  • 0 in reply to user6252411
    Intellectual 340 points

    Please help me check the original default program of J6, CLK clock frequency configured by EMMC part; What is the read/write rate of the data?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    At boot time the Kernel log will show the eMMC enumeration and speed mode. Below snippet from your previous log you shared.

    [ 2.188873] mmc1: BKOPS_EN bit is not set
    [ 2.199037] mmc1: new high speed DDR MMC card at address 0001
    [ 2.205313] mmcblk0: mmc1:0001 MMC08G 7.26 GiB
    [ 2.210121] mmcblk0boot0: mmc1:0001 MMC08G partition 1 4.00 MiB
    [ 2.216359] mmcblk0boot1: mmc1:0001 MMC08G partition 2 4.00 MiB
    [ 2.228191] mmcblk0: p1 p2 p3 p4 p5 p6 p7


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    TI__Mastermind 33390 points

    Any update on the test without the resistors connected to data lines?

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、We deleted the 22R resistance, did the experiment, still can appear, and there should be no relation; I want to know where the software can change the read/write rate of EMMC?

    2、Currently, the CLK clock frequency of EMMC tested is 48M, the read rate is 11M/s, and the write rate is 65M/s. According to the software, it is mmc-ddr-1_8v. How can we modify the mode of EMMC from the agent, such as changing SDR or DDR? Could you please provide detailed explanation?

  • 0 in reply to user6252411
    Intellectual 340 points

    Currently, the CLK clock frequency of EMMC tested is 48M, the write rate is 11M/s, and the read rate is 65M/s. According to the software, it is mmc-ddr-1_8v. How can we modify the mode of EMMC from the agent, such as changing SDR or DDR? Could you please provide detailed explanation?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    Yes, according to your kernel log, eMMC is enumerated in High Speed mode and matches the 48MHz clock value.
    In kernel 3.14, mmc-ddr-1_8v property in dts indicates that i eMMC high-speed DDR mode(1.8V I/O) is supported.

    You can try deleting that property and try adding one of the below properties to try lower speed modes.
    sd-uhs-sdr12 --> SD UHS SDR12 speed is supported
    sd-uhs-sdr25 --> SD UHS SDR25 speed is supported


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Yes，I looked at the original code, as if it was not configured by default; Mmc-ddr-1_8v is also not available, I also deleted this part, the test found that the default state clock frequency CLK is still 48M, the write rate is not changed to 11MB/s, the read rate is changed to 40MB/s, where is the change affected?

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    Our code compares the demo differences and finds that there are differences here; The software is commented out, the write rate doesn't change, the CLK rate doesn't change; I'm just reading at a rate of 65M/s to 40MB/s.

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    Could you also try removing the pinctrl-* entries and test?
    Keep only below and check the behavior.

    pinctrl-names = "default";
    pinctrl-0 = <&mmc2_pins_default>;

    Please note that Kernel 3.14 is very old kernel and supporting this is difficult.

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    At present, our software system file has been changed to read only by default in boot, and the machine experiment is frequently switched on and off. Execute the following command: fsck.ext4-p /dev/mmcblk0p1, and still report the following error: "rootfs contains a file system with errors, check null."

    What could be the cause of this? Normally to read only, read the system file is not written action, how can there be an error?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Did this setup have no errors when it was booted first time with read only configuration?

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、This setting in the boot changed to read only, repeatedly on and off the machine; Running the detection command after some time of operation will still find errors. The modifications are as follows:

    2、We currently use the SDK version glsdk7.04.03. How do we dispose the roofs as read-only？

    3、We are now following the following modification, EMMC will still report an error：

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    You can use 'mount' command to confirm if the file system is mounted as readonly.

    Adding 'ro' flag in kernel bootargs mounts the root device partition as read-only. If there are other partitions that needs to be marked as read-only, that gets done via /etc/fstab file.

    ro    [KNL] Mount root device read-only on boot


    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    We now default to read-only system files；The machine was then switched on and off frequently；

    Then run for a while to execute the following command：

    1、command：fsck.ext4 –p /dev/mmcblk0p1

    This error occurs when executing -p:rootfs contains a file system with errors, check forced

    2、If you do -f"fsck.ext4 –f /dev/mmcblk0p1” first, then -p, you do it for a few days and you don't find anything unusual；

    What's the difference between these two instructions“fsck.ext4 –p”and“fsck.ext4 –f”？

    3、If we want to determine whether there are any errors in the system files of EMMC, how to operate? Is the current inspection method reasonable?

    4、“rootfs contains a file system with errors, check forced”，

    What does this error mean and how do we get to the actual error?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    From the man page of fsck.ext4 below are the meanings of the option.

    -f --> Force checking even if filesystem is marked clean
    -p --> Automatic repair

    Let me check and get back on what this error means "rootfs contains a file system with errors, check forced"

    In your testing, do you do orderly shutdown? or just power cycle the board?

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、Please help to confirm the meaning of this error instruction： "rootfs contains a file system with errors, check forced"

    2、In my test；we orderly shutdown，Frequent switching of input power；

    3、In our tests, we found that -f was used first, then -p was used, and no errors were found. Just executing -p makes an error. What's the difference?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Hi,

    I did not understand point #2. Do you do "shutdown" command or just disconnect the power?
    There were some more pointers provided here regarding this and graceful shutdown -- https://e2e.ti.com/support/processors/f/791/t/869862

    Other than what's mentioned from the manual page of fsck tool, I don't know the difference between the two options.

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    The system file is read-write by default, and becomes read-only after problems occur. We have added the repair command " fsck.ext4 -p  " /etc/init.d/lee_checkroot.sh；When it starts, it will go back to detect and fix the problem automatically. And sometimes it can't be fixed.

    The instructions must be entered manually:

    root@dra7xx-evm:~# fsck.ext4 -p /dev/mmcblk0p1 rootfs: Superblock last write time (Mon Jun 8 14:41:07 2020, now = Thu Feb 27 15:57:04 2020) is in the future. rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options)

    root@dra7xx-evm:~# fsck.ext4 -f /dev/mmcblk0p1 e2fsck 1.42.9 (28-Dec-2013) Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Unattached inode 3749 Connect to /lost+found<y>? no Unattached zero-length inode 3750. Clear<y>? no Unattached inode 3750

    Why can't it be fixed automatically? What does manual repair mean here? What's the difference between the two repair commands? What is the cause of this system file error?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    Kernel will convert a filesystem to read only if there are too many errors from the block driver.
    We don't know the difference between those 2 options of fsck other than what's mentioned in the tool manual page.

    Also, do you have the IODELAY settings for MMC in your kernel dts?

    Regards,
    Vishal

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、Our EMMC is using the default setting without change. Where is the IODELAY setting you said to check?

    2、We will copy the abnormal system image file to another good machine, good machine execution fsck.ext4-p /-f can still report the error; But look at the system file, the original read-only mirror file can be read and write; Why is the read/write permission changed after copying, but the error remains.

    3、What causes this, what causes the system to become read-only, how do you troubleshoot for errors?

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    -1-
    The IODELAY settings are provided through dts file for MMC.
    According to log the card is enumerated in high speed mode and there are no iodelay settings needed for this mode.

    Could you still share the mmc node from dts file?

    -2-
    Not sure about this one. 

    -3-
    Linux Kernel will convert a filesystem to read only if there are too many errors from the block driver.
    The log "Remounting filesystem read-only" is coming from file fs/ext4/super.c

  • 0 in reply to Vishal Mahaveer
    Intellectual 340 points

    1、We loaded the autorun repair command at system startup time: # fsck.ext4-fy /dev/mmcblk0p1；

    When performing the -f check, the following error still occurs:

    root@dra7xx-evm:~# fsck.ext4 -f /dev/mmcblk0p1 e2fsck 1.42.9 (28-Dec-2013)

    Pass 1: Checking inodes, blocks, and sizes

    Pass 2: Checking directory structure

    Pass 3: Checking directory connectivity

    Pass 4: Checking reference counts

    Pass 5: Checking group summary information

    Free blocks count wrong (6214, counted=6588). Fix<y>? no

    Free inodes count wrong (3352, counted=3666). Fix<y>? no

    rootfs: 3816/7168 files (0.1% non-contiguous), 22458/28672 blocks

    root@dra7xx-evm:~# root@dra7xx-evm:~#

    2、What do these two mistakes mean?

    Free blocks count wrong (6214, counted=6588). Fix<y>? no

    Free inodes count wrong (3352, counted=3666). Fix<y>? no

  • 0 in reply to user6252411
    TI__Mastermind 33390 points

    I don't know the meanings of those errors.

    Are you running fsck on mounted file system?
    There is a note in man page of fsck tool saying this is not safe to run fsck on mounted file system.

    Also, do you unmount file system every time you power off the board?