• State
  • Locked Locked
  • Replies 18 replies
  • Subscribers 100 subscribers
  • Views 1094 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.

TMDXEVM3358: MMC3 configuration issue

anton bauer
Prodigy 90 points

Part Number: TMDXEVM3358

Hi There,

I want to use MMC3 as SDIO interface for WiFi module.The processor SDK 05.03.00.07 is downloaded and run it on AM335x GP EVM.

Unfortunately after successful booting, I can't see MMC3 detected via dmesg. Then I go to am335x-evm.dts, do the following changes:

wlan_en_reg: fixedregulator2 {
        compatible = "regulator-fixed";
        regulator-name = "wlan-en-regulator";
        regulator-min-microvolt = <1800000>;
        regulator-max-microvolt = <1800000>;

        /* WLAN_EN GPIO for this board - Bank1, pin16 */
        gpio = <&gpio1 16 1>;      <---- change value from 0 to 1

        /* WLAN card specific delay */
        startup-delay-us = <70000>;
        /* enable-active-high; */  <---- comment out this line
  };

All the rest parts of this dts file are kept unchanged.  Following the results of dmesg | grep mmc

root@am335x-evm:~# dmesg | grep mmc
[    1.311177] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
[    1.311186] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.311220] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
[    1.311293] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.315941] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
[    1.315946] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.315955] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
[    1.315962] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
[    1.315969] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[    1.315976] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
[    1.316900] omap_hsmmc 47810000.mmc: GPIO lookup for consumer cd
[    1.316910] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
[    1.316927] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@47810000[0]'
[    1.316935] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@47810000[0]'
[    1.316940] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
[    1.316947] omap_hsmmc 47810000.mmc: lookup for GPIO cd failed
[    1.316956] omap_hsmmc 47810000.mmc: GPIO lookup for consumer wp
[    1.316961] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
[    1.316968] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@47810000[0]'
[    1.316975] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@47810000[0]'
[    1.316980] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
[    1.316986] omap_hsmmc 47810000.mmc: lookup for GPIO wp failed
[    1.645714] vmmc: supplied by vbat
[    1.670288] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
[    1.670300] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.670339] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
[    1.670420] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.675119] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
[    1.675125] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.675136] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
[    1.675144] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
[    1.675150] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[    1.675157] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
[    1.866052] mmc1: host does not support reading read-only switch, assuming write-enable
[    1.889054] mmc1: new high speed SDHC card at address aaaa
[    1.896056] mmcblk1: mmc1:aaaa SL08G 7.40 GiB
[    1.901764]  mmcblk1: p1 p2
[   29.200775] EXT4-fs (mmcblk1p2): mounting ext3 file system using the ext4 subsystem
[   30.016436] EXT4-fs (mmcblk1p2): recovery complete
[   30.081576] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[   30.322048] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

As you can see no mmc3 is detected. Running ls /sys/bus/sdio/devices, there is no any sdio device appears. What could be the reason?

Any configuration missing? The complete boot log is attached.I need your help, Thanks

Xi

Fullscreen bootlog_am335x_gp_evm.txt Download 
U-Boot 2017.01-gc68ed086bd (Nov 21 2018 - 23:37:17 +0100)

CPU  : AM335X-GP rev 2.1
Model: TI AM335x EVM
DRAM:  1 GiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env

** Unable to read "uboot.env" from mmc0:1 **
Using default environment

<ethaddr> not set. Validating first E-fuse MAC
Net:   cpsw, usb_ether
Hit any key to stop autoboot:  0
=> setenv bootfile zImage.bin
=> setenv fdtfile am335x-evm.dtb
=> setenv rootpath  /home/xfamed/ti-processor-sdk-linux-am335x-evm-05.03.00.07/targetNFS
=> setenv nfsopts 'nolock,v3,tcp,rsize=4096,wsize=4096'
=> setenv serverip 163.50.61.118
=> run netboot
Booting from network ...
link up on port 0, speed 100, full duplex
BOOTP broadcast 1
DHCP client bound to address 163.50.60.239 (5 ms)
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 163.50.61.118; our IP address is 163.50.60.239
Filename 'zImage.bin'.
Load address: 0x82000000
Loading: #################################################################
         ##############################################T ###################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################################
         278.3 KiB/s
done
Bytes transferred = 3875328 (3b2200 hex)
link up on port 0, speed 100, full duplex
Using cpsw device
TFTP from server 163.50.61.118; our IP address is 163.50.60.239
Filename 'am335x-evm.dtb'.
Load address: 0x88000000
Loading: #########
         319.3 KiB/s
done
Bytes transferred = 41244 (a11c hex)
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8fff2000, end 8ffff11b ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.14.79-ge669d52447 (xfamed@VM64-200G) (gcc version 7.2.1 20171011 (Linaro GCC 7.2-2017.11)) #2 PREEMPT Wed Mar 11 11:38:52 CET 2020
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: TI AM335x EVM
[    0.000000] Memory policy: Data cache writeback
[    0.000000] efi: Getting EFI parameters from FDT:
[    0.000000] efi: UEFI not found.
[    0.000000] cma: Reserved 48 MiB at 0xbd000000
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (sgx neon)
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260416
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/nfs nfsroot=163.50.61.118:/home/xfamed/ti-processor-sdk-linux-am335x-evm-05.03.00.07/targetNFS,nolock,v3,tcp,rsize=4096,wsize=4096 rw ip=dhcp
[    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: 976296K/1048576K available (8192K kernel code, 319K rwdata, 2488K rodata, 1024K init, 267K bss, 23128K reserved, 49152K cma-reserved, 212992K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0900000   (9184 kB)
[    0.000000]       .init : 0xc0c00000 - 0xc0d00000   (1024 kB)
[    0.000000]       .data : 0xc0d00000 - 0xc0d4ff40   ( 320 kB)
[    0.000000]        .bss : 0xc0d4ff40 - 0xc0d92c94   ( 268 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Tasks RCU enabled.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000016] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000035] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000046] OMAP clocksource: timer1 at 24000000 Hz
[    0.000212] timer_probe: no matching timers found
[    0.000417] Console: colour dummy device 80x30
[    0.000444] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[    0.000450] This ensures that you still see kernel messages. Please
[    0.000455] update your kernel commandline.
[    0.000487] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
[    0.089201] pid_max: default: 32768 minimum: 301
[    0.089384] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.089402] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.090168] CPU: Testing write buffer coherency: ok
[    0.090237] CPU0: Spectre v2: using BPIALL workaround
[    0.090913] Setting up static identity map for 0x80100000 - 0x80100060
[    0.091055] Hierarchical SRCU implementation.
[    0.091370] EFI services will not be available.
[    0.092666] devtmpfs: initialized
[    0.100317] random: get_random_u32 called from bucket_table_alloc+0x8c/0x1ac with crng_init=0
[    0.100766] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.101068] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.101088] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.104607] pinctrl core: initialized pinctrl subsystem
[    0.105323] DMI not present or invalid.
[    0.105741] NET: Registered protocol family 16
[    0.107790] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.121123] omap_hwmod: debugss: _wait_target_disable failed
[    0.173378] cpuidle: using governor ladder
[    0.173409] cpuidle: using governor menu
[    0.177421] OMAP GPIO hardware version 0.1
[    0.185393] omap-gpmc 50000000.gpmc: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/nandflash_pins_s0, deferring probe
[    0.188091] No ATAGs?
[    0.188104] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.200458] edma 49000000.edma: TI EDMA DMA engine driver
[    0.204403] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe
[    0.204467] omap_i2c 4802a000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c1_pins, deferring probe
[    0.204602] media: Linux media interface: v0.10
[    0.204640] Linux video capture interface: v2.00
[    0.204739] pps_core: LinuxPPS API ver. 1 registered
[    0.204747] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.204768] PTP clock support registered
[    0.204800] EDAC MC: Ver: 3.0.0
[    0.205190] dmi: Firmware registration failed.
[    0.205577] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.205914] Advanced Linux Sound Architecture Driver Initialized.
[    0.207073] clocksource: Switched to clocksource timer1
[    0.214582] NET: Registered protocol family 2
[    0.215304] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    0.215378] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.215445] TCP: Hash tables configured (established 8192 bind 8192)
[    0.215580] UDP hash table entries: 512 (order: 1, 8192 bytes)
[    0.215604] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[    0.215764] NET: Registered protocol family 1
[    0.216203] RPC: Registered named UNIX socket transport module.
[    0.216218] RPC: Registered udp transport module.
[    0.216225] RPC: Registered tcp transport module.
[    0.216231] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.217345] hw perfevents: no interrupt-affinity property for /pmu, guessing.
[    0.217475] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.218925] workingset: timestamp_bits=14 max_order=18 bucket_order=4
[    0.222739] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.223554] NFS: Registering the id_resolver key type
[    0.223601] Key type id_resolver registered
[    0.223608] Key type id_legacy registered
[    0.223651] ntfs: driver 2.1.32 [Flags: R/O].
[    0.225587] bounce: pool size: 64 pages
[    0.225688] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[    0.225700] io scheduler noop registered
[    0.225708] io scheduler deadline registered
[    0.225896] io scheduler cfq registered (default)
[    0.225906] io scheduler mq-deadline registered
[    0.225912] io scheduler kyber registered
[    0.227312] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.230436] pwm-backlight backlight: backlight supply power not found, using dummy regulator
[    0.274524] Serial: 8250/16550 driver, 10 ports, IRQ sharing disabled
[    0.277654] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, base_baud = 3000000) is a 8250
[    0.945568] console [ttyS0] enabled
[    0.950161] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 31, base_baud = 3000000) is a 8250
[    0.960805] omap_rng 48310000.rng: Random Number Generator ver. 20
[    0.968782] panel panel: found backlight
[    0.973028] OF: graph: no port node found in /ocp/lcdc@4830e000
[    0.979338] OF: graph: no port node found in /ocp/lcdc@4830e000
[    0.985773] OF: graph: no port node found in /ocp/lcdc@4830e000
[    0.991784] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    0.998437] [drm] No driver support for vblank timestamp query.
[    1.047142] Console: switching to colour frame buffer device 100x30
[    1.069473] tilcdc 4830e000.lcdc: fb0:  frame buffer device
[    1.075617] [drm] Initialized tilcdc 1.0.0 20121205 for 4830e000.lcdc on minor 0
[    1.094531] brd: module loaded
[    1.104474] loop: module loaded
[    1.110232] libphy: Fixed MDIO Bus: probed
[    1.187126] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6, bus freq 1000000
[    1.194837] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    1.202240] libphy: 4a101000.mdio: probed
[    1.206308] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver Atheros 8031 ethernet
[    1.216562] cpsw 4a100000.ethernet: Detected MACID = 98:5d:ad:34:30:39
[    1.223399] cpsw 4a100000.ethernet: initialized cpsw ale version 1.4
[    1.229883] cpsw 4a100000.ethernet: ALE Table size 1024
[    1.235189] cpsw 4a100000.ethernet: cpts: overflow check period 500 (jiffies)
[    1.243796] i2c /dev entries driver
[    1.247867] IR NEC protocol handler initialized
[    1.252422] IR RC5(x/sz) protocol handler initialized
[    1.257559] IR RC6 protocol handler initialized
[    1.262106] IR JVC protocol handler initialized
[    1.266651] IR Sony protocol handler initialized
[    1.271302] IR SANYO protocol handler initialized
[    1.276024] IR Sharp protocol handler initialized
[    1.280756] IR MCE Keyboard/mouse protocol handler initialized
[    1.286615] IR XMP protocol handler initialized
[    1.292689] cpuidle: enable-method property 'ti,am3352' found operations
[    1.299850] sdhci: Secure Digital Host Controller Interface driver
[    1.306086] sdhci: Copyright(c) Pierre Ossman
[    1.311293] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.467415] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.477131] ledtrig-cpu: registered to indicate activity on CPUs
[    1.488037] NET: Registered protocol family 10
[    1.493845] Segment Routing with IPv6
[    1.497812] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    1.505537] NET: Registered protocol family 17
[    1.510414] Key type dns_resolver registered
[    1.514934] omap_voltage_late_init: Voltage driver support not added
[    1.526874] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    1.532272] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[    1.540121] nand: No NAND device found
[    1.543942] omap2-nand 8000000.nand: scan failed, may be bus-width mismatch
[    1.577320] tps65910 0-002d: No interrupt support, no core IRQ
[    1.585023] vrtc: supplied by vbat
[    1.592173] vio: supplied by vbat
[    1.596942] vdd1: supplied by vbat
[    1.601498] random: fast init done
[    1.605485] vdd2: supplied by vbat
[    1.612124] vdig1: supplied by vbat
[    1.616931] vdig2: supplied by vbat
[    1.621761] vpll: supplied by vbat
[    1.626481] vdac: supplied by vbat
[    1.631191] vaux1: supplied by vbat
[    1.635940] vaux2: supplied by vbat
[    1.640834] vaux33: supplied by vbat
[    1.645714] vmmc: supplied by vbat
[    1.650445] vbb: supplied by vbat
[    1.654869] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    1.662523] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 100 kHz
[    1.670420] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.730369] input: volume_keys0 as /devices/platform/volume_keys0/input/input0
[    1.742448] hctosys: unable to open rtc device (rtc0)
[    1.764106] net eth0: initializing cpsw version 1.12 (0)
[    1.866052] mmc1: host does not support reading read-only switch, assuming write-enable
[    1.875929] Atheros 8031 ethernet 4a101000.mdio:00: attached PHY driver [Atheros 8031 ethernet] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)
[    1.889054] mmc1: new high speed SDHC card at address aaaa
[    1.896056] mmcblk1: mmc1:aaaa SL08G 7.40 GiB
[    1.901764]  mmcblk1: p1 p2
[    1.911983] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[    4.009098] cpsw 4a100000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[    4.017353] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[    4.047126] Sending DHCP requests ., OK
[    4.091151] IP-Config: Got DHCP answer from 163.50.61.252, my address is 163.50.60.239
[    4.099715] IP-Config: Complete:
[    4.102973]      device=eth0, hwaddr=98:5d:ad:34:30:39, ipaddr=163.50.60.239, mask=255.255.254.0, gw=163.50.61.254
[    4.113502]      host=163.50.60.239, domain=meed.co.murata.local, nis-domain=(none)
[    4.121537]      bootserver=0.0.0.0, rootserver=163.50.61.118, rootpath=     nameserver0=163.50.61.16, nameserver1=163.50.67.7
[    4.133602] lis3_reg: disabling
[    4.136769] wlan-en-regulator: disabling
[    4.141064] ALSA device list:
[    4.144047]   No soundcards found.
[    4.192863] VFS: Mounted root (nfs filesystem) on device 0:15.
[    4.201921] devtmpfs: mounted
[    4.206996] Freeing unused kernel memory: 1024K
[    5.138818] systemd[1]: System time before build time, advancing clock.
[    5.277710] systemd[1]: systemd 234 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid)
[    5.299919] systemd[1]: Detected architecture arm.

Welcome to Arago 2018.10!

[    5.346598] systemd[1]: Set hostname to <am335x-evm>.
[    6.891365] random: crng init done
[    6.939238] systemd[1]: /lib/systemd/system/gadget-init.service:15: Unknown lvalue 'ExecStopPre' in section 'Service'
[    7.870345] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    7.909467] systemd[1]: Listening on Network Service Netlink Socket.
[  OK  ] Listening on Network Service Netlink Socket.
[    7.948045] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[  OK  ] Started Forward Password Requests to Wall Directory Watch.
[    7.988372] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    8.018027] systemd[1]: Reached target Remote File Systems.
[  OK  ] Reached target Remote File Systems.
[    8.047529] systemd[1]: Reached target Swap.
[  OK  ] Reached target Swap.
[  OK  ] Created slice User and Session Slice.
[  OK  ] Started Dispatch Password Requests to Console Directory Watch.
[  OK  ] Reached target Paths.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Syslog Socket.
[  OK  ] Listening on Process Core Dump Socket.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
[  OK  ] Created slice System Slice.
         Starting Create list of required st…ce nodes for the current kernel...
         Mounting Kernel Debug File System...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Journal Service...
         Starting Load Kernel Modules...
         Mounting Temporary Directory (/tmp)...
[  OK  ] Reached target Slices.
         [    8.860261] cryptodev: loading out-of-tree module taints kernel.
Starting Remount Root and Kernel File Systems...
[    8.896042] cryptodev: driver 1.9 loaded.
         Mounting POSIX Message Queue File System...
[  OK  ] Created slice system-getty.slice.
[  OK  ] Mounted Kernel Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[    9.040266] usbcore: registered new interface driver usbfs
[  OK  ] Mounted Temporary Directory (/tmp).
[    9.063015] usbcore: registered new interface driver hub
[    9.092829] usbcore: registered new device driver usb
[  OK  ] Started Create list of required sta…vice nodes for the current kernel.
[    9.152384] usbcore: registered new interface driver usbserial
[    9.215334] usbcore: registered new interface driver ftdi_sio
[    9.255328] usbserial: USB Serial support registered for FTDI USB Serial Device
[  OK  ] Started Remount Root and Kernel File Systems.
         Starting udev Coldplug all Devices...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Started Journal Service.
[  OK  ] Started Load Kernel Modules.
         Starting Apply Kernel Variables...
         Mounting Kernel Configuration File System...
         Starting Flush Journal to Persistent Storage...
[  OK  ] Mounted Kernel Configuration File System.
[  OK  ] Started Apply Kernel Variables.
[    9.875340] systemd-journald[63]: Received request to flush runtime journal from PID 1
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Flush Journal to Persistent Storage.
[  OK  ] Reached target Local File Systems (Pre).
         Mounting /var/volatile...
         Mounting /media/ram...
         Starting udev Kernel Device Manager...
[  OK  ] Mounted /var/volatile.
[  OK  ] Mounted /media/ram.
         Starting Load/Save Random Seed...
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Network Time Synchronization...
         Starting Update UTMP about System Boot/Shutdown...
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on RPCbind Server Activation Socket.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
         Starting Docker Socket for the API.
[  OK  ] Listening on dropbear.socket.
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started Daily rotation of log files.
         Starting Network Service...
[  OK  ] Started Daily Cleanup of Temporary Directories.
[   12.698090] input: matrix_keypad0 as /devices/platform/matrix_keypad0/input/input1
[  OK  ] Reached target Timers.
[FAILED] Failed to listen on Docker Socket for the API.
See 'systemctl status docker.socket' for details.
[DEPEND] Dependency failed for Docker Application Container Engine.
[   13.017797] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[   13.049984] omap_rtc 44e3e000.rtc: registered as rtc0
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Created slice system-systemd\x2dbacklight.slice.
         Starting Load/Save Screen Backlight…ightness of backlight:backlight...
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Login Service...
[  OK  ] Started System Logging Service.
[  OK  ] Reached target Containers.
[  OK  ] Started D-Bus System Message Bus.
[   14.662405] tlv320aic3x-codec 1-001b: Too high supply voltage(s) AVDD: 3300000, DVDD: 5000000
[  OK  ] Started Periodic Command Scheduler.
[  OK  ] Started Kernel Logging Service.
         Starting Avahi mDNS/DNS-SD Stack...
[  OK  ] Started Job spooling tools.
         Starting RPC Bind Service...
         Starting uim-sysfs.service...
[  OK  ] Started Hardware RNG Entropy Gatherer Daemon.
         Starting Print notice about GPLv3 packages...
[  OK  ] Started Load/Save Screen Backlight Brightness of backlight:backlight.
[  OK  ] Started Login Service.
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
[  OK  ] Started Redis In-Memory Data Store.
         Starting Enable and configure wl18xx bluetooth stack...
         Starting Lightning Fast Webserver With Light System Requirements...
         Starting Permit User Sessions...
         Starting DNS forwarder and DHCP server...
         Starting Simple Network Management Protocol (SNMP) Daemon....
         Starting Wait for Network to be Configured...
         Starting Network Name Resolution...
[  OK  ] Started RPC Bind Service.
[  OK  ] Started Permit User Sessions.
[  OK  ] Started Getty on tty1.
[  OK  ] Started Serial Getty on ttyS0.
[FAILED] Failed to start DNS forwarder and DHCP server.
See 'systemctl status dnsmasq.service' for details.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Lightning Fast Webserver With Light System Requirements.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started NFS status monitor for NFSv2/3 locking..
[   19.323281] omap-sham 53100000.sham: hw accel on OMAP rev 4.3
[   19.800628] omap-aes 53500000.aes: OMAP AES hw accel rev: 3.2
[  OK  ] Started Enable and configure wl18xx bluetooth stack.
[   20.135579] omap-aes 53500000.aes: will run requests pump with realtime priority
[  OK  ] Started Simple Network Management Protocol (SNMP) Daemon..
[   20.521714] [drm] Initialized pvr 1.14.3699939 20110701 for 56000000.sgx on minor 1
[  OK  ] Started uim-sysfs.service.
         Starting rc.pvr.service...
[   21.572071] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[   21.592072] remoteproc remoteproc0: wkup_m3 is available
[   21.884312] remoteproc remoteproc0: powering up wkup_m3
[   21.968928] remoteproc remoteproc0: Booting fw image am335x-pm-firmware.elf, size 224628
[   21.993296] remoteproc remoteproc0: remote processor wkup_m3 is now up
[   21.993324] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x192
[   22.039495] PM: bootloader does not support rtc-only!
[   22.093012] PVR_K: UM DDK-(3699939) and KM DDK-(3699939) match. [ OK ]

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am335x-evm ttyS0

Arago 2018.10 am335x-evm ttyS0

am335x-evm login: [   23.376399] asoc-simple-card sound: tlv320aic3x-hifi <-> 4803c000.mcasp mapping ok
[   23.634342] asoc-simple-card sound: ASoC: no DMI vendor name!
[   29.200775] EXT4-fs (mmcblk1p2): mounting ext3 file system using the ext4 subsystem
[   30.016436] EXT4-fs (mmcblk1p2): recovery complete
[   30.081576] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[   30.322048] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   37.201634] NET: Registered protocol family 15
[   38.443553] Initializing XFRM netlink socket
[   46.607850] input: ti-tsc as /devices/platform/ocp/44e0d000.tscadc/44e0d000.tscadc:tsc/input/input2
[   47.019614] am335x-phy-driver 47401300.usb-phy: 47401300.usb-phy supply vcc not found, using dummy regulator
[   47.842854] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[   48.127692] musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
[   48.607604] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   48.733750] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   48.827001] usb usb1: Product: MUSB HDRC host driver
[   49.050335] usb usb1: Manufacturer: Linux 4.14.79-ge669d52447 musb-hcd
[   49.366167] usb usb1: SerialNumber: musb-hdrc.0
[   49.841792] hub 1-0:1.0: USB hub found
[   49.964278] hub 1-0:1.0: 1 port detected
[   50.146413] pruss 4a300000.pruss: creating PRU cores and other child platform devices
[   50.409443] am335x-phy-driver 47401b00.usb-phy: 47401b00.usb-phy supply vcc not found, using dummy regulator
[   50.762390] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[   50.807646] musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
[   51.060200] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[   51.315568] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   51.367002] usb usb2: Product: MUSB HDRC host driver
[   51.375225] usb usb2: Manufacturer: Linux 4.14.79-ge669d52447 musb-hcd
[   51.384502] usb usb2: SerialNumber: musb-hdrc.1
[   51.393965] hub 2-0:1.0: USB hub found
[   51.402985] hub 2-0:1.0: 1 port detected
[   51.922097] remoteproc remoteproc1: 4a334000.pru is available
[   51.932253] pru-rproc 4a334000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
[   52.016137] remoteproc remoteproc2: 4a338000.pru is available
[   52.147528] pru-rproc 4a338000.pru: PRU rproc node /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
***************************************************************
***************************************************************
NOTICE: This file system contains the following GPLv3 packages:
        autoconf
        bash-dev
        bash
        binutils
        cifs-utils
        cpio
        cpp-symlinks
        cpp
        dnsmasq
        dosfstools
        elfutils
        findutils
        g++-symlinks
        g++
        gawk
        gcc-symlinks
        gcc
        gdb
        gdbserver
        gettext
        glmark2
        gstreamer1.0-libav
        gzip
        hidapi
        libdw1
        libelf1
        libgdbm-compat4
        libgdbm-dev
        libgdbm4
        libgettextlib
        libgettextsrc
        libgmp10
        libidn11
        libmavconn
        libmpc3
        libmpfr4
        libreadline-dev
        libreadline7
        libunistring2
        m4-dev
        m4
        make
        mavlink
        mavros-extras
        mavros-msgs
        mavros
        nettle
        python3-pycairo
        rsync
        socketcan-interface
        which

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution.  This can be done using
the opkg remove command.  i.e.:
    opkg remove <package>
Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you
      will be notified of the dependent packages.  You should
      use the --force-removal-of-dependent-packages option to
      also remove the dependent packages as well
***************************************************************
***************************************************************

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am335x-evm ttyS0

Arago 2018.10 am335x-evm ttyS0

am335x-evm login: root
root@am335x-evm:~#
root@am335x-evm:~# dmesg | grep mmc
[    1.311177] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
[    1.311186] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.311220] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
[    1.311293] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.315941] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
[    1.315946] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.315955] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
[    1.315962] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
[    1.315969] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[    1.315976] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
[    1.316900] omap_hsmmc 47810000.mmc: GPIO lookup for consumer cd
[    1.316910] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
[    1.316927] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@47810000[0]'
[    1.316935] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@47810000[0]'
[    1.316940] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
[    1.316947] omap_hsmmc 47810000.mmc: lookup for GPIO cd failed
[    1.316956] omap_hsmmc 47810000.mmc: GPIO lookup for consumer wp
[    1.316961] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
[    1.316968] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@47810000[0]'
[    1.316975] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@47810000[0]'
[    1.316980] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
[    1.316986] omap_hsmmc 47810000.mmc: lookup for GPIO wp failed
[    1.645714] vmmc: supplied by vbat
[    1.670288] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
[    1.670300] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.670339] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
[    1.670420] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.675119] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
[    1.675125] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
[    1.675136] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
[    1.675144] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
[    1.675150] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
[    1.675157] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
[    1.866052] mmc1: host does not support reading read-only switch, assuming write-enable
[    1.889054] mmc1: new high speed SDHC card at address aaaa
[    1.896056] mmcblk1: mmc1:aaaa SL08G 7.40 GiB
[    1.901764]  mmcblk1: p1 p2
[   29.200775] EXT4-fs (mmcblk1p2): mounting ext3 file system using the ext4 subsystem
[   30.016436] EXT4-fs (mmcblk1p2): recovery complete
[   30.081576] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
[   30.322048] FAT-fs (mmcblk1p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

  • 0
    TI__Mastermind 30746 points

    Hello,

    I'm sorry, the best person to respond to this is out of the office for a couple of days. We will get you a response early next week.

    Thank you.

  • 0
    Expert 1110 points

    hiii,

    i am not expert

    but  mmcX: new high speed SDIO card at address 0001
    message is not present in your boot log

    if mmc3 configure successfully you will get message something like above.

    may be it helps

    if it is possible please share your .dts file and dtsi file

    and verify your sdio pin not used by any other pins

  • 0 in reply to RAJU KUMARKHANIYA
    TI__Guru 70372 points

    Raju,

    RAJU KUMARKHANIYA said:
    but  mmcX: new high speed SDIO card at address 0001
    message is not present in your boot log

    many thanks for adding your suggestions here!

    Anton,

    you can also look at the "BeagleBone Black Wireless" project, it has an SDIO-based wifi connected to MMC3, you should be able to model after that.

    https://git.ti.com/cgit/processor-sdk/processor-sdk-linux/tree/arch/arm/boot/dts/am335x-boneblack-wireless.dts?h=processor-sdk-linux-4.19.y

    Regards, Andreas

  • 0 in reply to RAJU KUMARKHANIYA
    Prodigy 90 points

    Hi Raju, Andreas,

    I was also wondering why I can't see any message about mmc3 in the boot log file as you described:

      mmcX: new high speed SDIO card at address 0001

    I just take the am335x-evm.dts from the sdk (05.03.00.07) and do small change in the mmc3 configuration part, nothing else.

    So I expected that at least I shoul be able to see the mmc3 interface, but unfortunately it is not the case.

    enclosed the am335x-evm.dts and am33xx.dtsi files which are used for bringup the am335x GP EVM.

    Best Regards

    Anton

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Anton,

    I cannot access the files you attached ("Unfortunately, the page you've requested no longer exists. Please use the search form above to locate the information you're interested in.").

    However did you follow the thread that Raju pointed to in detail? 

    anton bauer said:
    The processor SDK 05.03.00.07 is downloaded and run it on AM335x GP EVM.

    Also can you use our current v6.01 processor SDK?

    And why are you changing pin settings from the default when you are using the  AM335x GP EVM?

    Can you look at the SDIO signals connected to the WiFi module with a logic analyzer to see if there is any activity? (CLK and CMD signals).

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Hi Andreas,

    thanks for the advise. Would you please tell me which clock frquency is used for MMC3? I can't find the value in dts file.

    And where can I configure the MMC3 clock frequency?

    Thanks

    Anton

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Anton,

    anton bauer said:
    Would you please tell me which clock frquency is used for MMC3? I can't find the value in dts file.

    It is usually negotiated between the host controller and the MMC/SDIO device during probe depending on mutual capabilities (there is a way to turn on debug prints in the Kernel via CONFIG to get more verbose into), unless set specifically...

    anton bauer said:
    And where can I configure the MMC3 clock frequency?

    Just add something like max-frequency = <2500000>; to the respective device tree node, see here for an example: https://git.ti.com/cgit/processor-sdk/processor-sdk-linux/tree/arch/arm/boot/dts/dra7.dtsi?h=processor-sdk-linux-4.19.y#n1157

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Andreas,

    I insert a MMC card (8GB)) into MMC3 slot (bottom of daughter board), the bootable MMC card is in the MMC1 slot (bottom of base board). Profile 1 is chosen. The image is from TI SDK 05.03.00.07. After scuccessful boot I still can't see the MMC3 recoginzed in the boot log. Following I list the dmesg | grep mmc messages. 

    Would you please do me a favour,  just put a MMC card into the MMC3 slot on your EVM to see if you can see the MMC3 slot recognized using SDK 05.03.00.07 ?  Maybe I missed some settings, so if you can

    do the reference booting it would be very helpful for me. Thank you

    -----------------------------------------------------------------------------------------

    root@am335x-evm:~# dmesg | grep mmc
    [    1.289612] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.289622] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.289647] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.289757] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.294501] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.294506] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.294515] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.294521] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.294526] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.294534] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
    [    1.295358] omap_hsmmc 481d8000.mmc: GPIO lookup for consumer cd
    [    1.295366] omap_hsmmc 481d8000.mmc: using device tree for GPIO lookup
    [    1.295374] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@481d8000[0]'
    [    1.295380] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@481d8000[0]'
    [    1.295385] omap_hsmmc 481d8000.mmc: using lookup tables for GPIO lookup
    [    1.295390] omap_hsmmc 481d8000.mmc: lookup for GPIO cd failed
    [    1.295398] omap_hsmmc 481d8000.mmc: GPIO lookup for consumer wp
    [    1.295402] omap_hsmmc 481d8000.mmc: using device tree for GPIO lookup
    [    1.295408] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@481d8000[0]'
    [    1.295413] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@481d8000[0]'
    [    1.295417] omap_hsmmc 481d8000.mmc: using lookup tables for GPIO lookup
    [    1.295422] omap_hsmmc 481d8000.mmc: lookup for GPIO wp failed
    [    1.642244] vmmc: supplied by vbat
    [    1.665215] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.665224] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.665251] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.665324] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.669971] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.669976] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.669982] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.669988] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.669993] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.670000] omap_hsmmc 48060000.mmc: lookup for GPIO wp failed
    [    1.724213] pinctrl-single 44e10800.pinmux: pin PIN0 already requested by 50000000.gpmc; cannot claim for 481d8000.mmc
    [    1.735054] pinctrl-single 44e10800.pinmux: pin-0 (481d8000.mmc) status -22
    [    1.742050] pinctrl-single 44e10800.pinmux: could not request pin 0 (PIN0) from group pinmux_mmc2_pins  on device pinctrl-single
    [    1.753686] omap_hsmmc 481d8000.mmc: Error applying setting, reverse things back
    [    1.761142] omap_hsmmc: probe of 481d8000.mmc failed with error -22
    [    1.901857] mmc0: host does not support reading read-only switch, assuming write-enable
    [    1.912946] mmc0: new high speed SDHC card at address aaaa
    [    1.919270] mmcblk0: mmc0:aaaa SL08G 7.40 GiB
    [    1.925572]  mmcblk0: p1 p2
    [    6.275153] EXT4-fs (mmcblk0p2): recovery complete
    [    6.281674] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
    [    7.992410] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
    [   15.394290] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
    [   21.536417] LUN: removable read only file: /dev/mmcblk0p1
    root@am335x-evm:~#

    ----------------------------------------------------------------------------------------

    Anton

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Hi Anton,

    on the AM335x GP EVM the 3rd MMC interface of the AM335x (a.k.a 'mmc2') is muxed between a connector for a wireless interface, and the extra SD card slot on the daughterboard. The default shipping configuration of the EVM is such that mmc2 is routed to the wireless interface connector as the SEL input of the mux chip (U28) is getting pulled high.

    Can you confirm the logic level on your SEL input, and move the resistor over to position R516 if needed?

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    TI__Guru 70372 points

    Hi Anton,

    I had a closer look at the AM335x GP EVM daughter board schematic and actually switching the MMC2_SDIO_SEL signal as I suggested earlier won't help routing the MMC2 (the device's 3rd MMC interface) signals all the way to the daughtercard SD interface, which itself only supports MMC1 (the device's 2nd MMC interface). This being said I cannot use the EVM to test MMC2 functionality via a second SD card as you had suggested, as MMC2 is only exposed through the COM connector on the main board.

    Unfortunately I currently don't have access to a WiLink COM module that I could try plugging into the COM connector on the main board so we need to find another way to get your setup to work.

    Can you go back to our current Linux SDK (v6.01) and use this as-is (without any modifications to any files, including DTS files), and report back with the boot log? https://software-dl.ti.com/processor-sdk-linux/esd/AM335X/latest/index_FDS.html

    Why were you modifying the DTS files as you reported initially?

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Hi Andreas,

    I downlaoded SDK 06.01.00.08 as you recommended and create the SDCARD using the prebuilt image. Then I booted the GP EVM throught the created SDCARD im MMC1 (the device's 2nd MMC interface).

    Still I can't find the mmc2 (the device's 3rd MMC interface), see below the log:

    --------------------------------------------------------------------------------------------------------

    root@am335x-evm:~# uname -a
    Linux am335x-evm 4.19.59-g5f8c1c6121 #1 PREEMPT Sat Oct 19 17:17:25 UTC 2019 armv7l GNU/Linux


    root@am335x-evm:~# dmesg | grep mmc
    [    1.267526] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.267535] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.267575] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.276481] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.281138] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.281144] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.281159] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.281171] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.281180] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.281186] omap_hsmmc 48060000.mmc: No GPIO consumer wp found
    [    1.282146] omap_hsmmc 47810000.mmc: GPIO lookup for consumer cd
    [    1.282155] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
    [    1.282177] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@47810000[0]'
    [    1.282190] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@47810000[0]'
    [    1.282198] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
    [    1.282205] omap_hsmmc 47810000.mmc: No GPIO consumer cd found
    [    1.282213] omap_hsmmc 47810000.mmc: GPIO lookup for consumer wp
    [    1.282218] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
    [    1.282230] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@47810000[0]'
    [    1.282242] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@47810000[0]'
    [    1.282248] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
    [    1.282254] omap_hsmmc 47810000.mmc: No GPIO consumer wp found
    [    1.282637] omap_hsmmc 47810000.mmc: Linked as a consumer to regulator.3
    [    1.581123] vmmc: supplied by vbat
    [    1.622091] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.622101] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.622144] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.631171] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.635841] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.635847] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.635864] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.635876] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.635885] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.635892] omap_hsmmc 48060000.mmc: No GPIO consumer wp found
    [    1.636398] omap_hsmmc 48060000.mmc: Linked as a consumer to regulator.18
    [    1.764323] mmc1: host does not support reading read-only switch, assuming write-enable
    [    1.775473] mmc1: new high speed SDHC card at address aaaa
    [    1.783298] mmcblk1: mmc1:aaaa SL08G 7.40 GiB
    [    1.790000]  mmcblk1: p1 p2
    [    1.810618] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
    [    3.509388] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
    root@am335x-evm:~#

    --------------------------------------------------------------------------------------------------------

    I modified the dts file because I can't find the mmc2 (the device 3rd interface), so I try to set WLAN_EN_GPIO to 1 as below and hope I can then find the mmc2.

    /* WLAN_EN GPIO for this board - Bank1, pin16 */
    gpio = <&gpio1 16 1>;      <---- change value from 0 to 1

    Questions:

    1. It seems the mmc2 (the device 3rd interface) is not accessable as default.  How can I configure the GP EVM so that the mmc2 (the device 3rd interface) is accessable?

    2. Where can I find the schematic of the GP EVM board, specially for the COM connector?

    Thanks

    Anton

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Hi Andreas,

    I downloaded the SDK 06.01.00.08 as you recommanded and created a SD boot card (inserted it later into MMC1, the device 2nd MMC interface) with prebuilt image using the script

    ~/ti-processor-sdk-linux-am335x-evm-06.01.00.08/bin/create-sdcard.sh

    But still I can't find the MMC2 (the device 3rd MMC inerface) after successful booting from MMC1(the debvice 2nd MMC interface), following the log messages:

    ---------------------------------------------------------------------------------------------------------------------------------------------------------

    root@am335x-evm:~# uname -a
    Linux am335x-evm 4.19.59-g5f8c1c6121 #1 PREEMPT Sat Oct 19 17:17:25 UTC 2019 armv7l GNU/Linux
    root@am335x-evm:~#
    root@am335x-evm:~# dmesg | grep mmc
    [    1.267543] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.267552] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.267593] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.276498] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.281153] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.281159] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.281177] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.281189] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.281197] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.281204] omap_hsmmc 48060000.mmc: No GPIO consumer wp found
    [    1.282172] omap_hsmmc 47810000.mmc: GPIO lookup for consumer cd
    [    1.282182] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
    [    1.282204] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/ocp/mmc@47810000[0]'
    [    1.282218] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/ocp/mmc@47810000[0]'
    [    1.282225] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
    [    1.282232] omap_hsmmc 47810000.mmc: No GPIO consumer cd found
    [    1.282240] omap_hsmmc 47810000.mmc: GPIO lookup for consumer wp
    [    1.282245] omap_hsmmc 47810000.mmc: using device tree for GPIO lookup
    [    1.282257] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@47810000[0]'
    [    1.282269] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@47810000[0]'
    [    1.282275] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
    [    1.282281] omap_hsmmc 47810000.mmc: No GPIO consumer wp found
    [    1.282667] omap_hsmmc 47810000.mmc: Linked as a consumer to regulator.3
    [    1.581279] vmmc: supplied by vbat
    [    1.622190] omap_hsmmc 48060000.mmc: GPIO lookup for consumer cd
    [    1.622200] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.622244] of_get_named_gpiod_flags: parsed 'cd-gpios' property of node '/ocp/mmc@48060000[0]' - status (0)
    [    1.631273] omap_hsmmc 48060000.mmc: Got CD GPIO
    [    1.635941] omap_hsmmc 48060000.mmc: GPIO lookup for consumer wp
    [    1.635946] omap_hsmmc 48060000.mmc: using device tree for GPIO lookup
    [    1.635965] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/mmc@48060000[0]'
    [    1.635978] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/mmc@48060000[0]'
    [    1.635987] omap_hsmmc 48060000.mmc: using lookup tables for GPIO lookup
    [    1.635995] omap_hsmmc 48060000.mmc: No GPIO consumer wp found
    [    1.636601] omap_hsmmc 48060000.mmc: Linked as a consumer to regulator.18
    [    1.765221] mmc1: host does not support reading read-only switch, assuming write-enable
    [    1.776524] mmc1: new high speed SDHC card at address aaaa
    [    1.784635] mmcblk1: mmc1:aaaa SL08G 7.40 GiB
    [    1.791580]  mmcblk1: p1 p2
    [    1.946989] EXT4-fs (mmcblk1p2): recovery complete
    [    1.953566] EXT4-fs (mmcblk1p2): mounted filesystem with ordered data mode. Opts: (null)
    [    4.120625] EXT4-fs (mmcblk1p2): re-mounted. Opts: (null)
    root@am335x-evm:~#

    ---------------------------------------------------------------------------------------------------------------------------------------------------------

    I modified the dts file previously, because I thought setting the wlan enable gpio pin to high could be the solution to see the MMC2 (device 3rd MMC interface), but it doesn't help.

    So it seems that the MMC2 (the device 3rd MMC interface) is not activated as default.  My questions are:

    1. How to activate the MMC2 (the device 3rd MMC interface) so that I can access it without using the COM connector ?

    2. Where can I get the schematic of the am335x GP EVM, especially for the COM connector?

    Thank you in advance

    Anton

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Hi Anton,

    anton bauer said:
    So it seems that the MMC2 (the device 3rd MMC interface) is not activated as default

    The MMC interface peripheral module is active, as per "omap_hsmmc 47810000.mmc" entries in your log, corresponding to the base address of that module.

    anton bauer said:
    1. How to activate the MMC2 (the device 3rd MMC interface) so that I can access it without using the COM connector ?

    Can you use a digital scope to see if you get any activity on the COM_SDIO_CLK==MMC2_CLK and COM_SDIO_CMD==MMC2_CMD signals on the COM connector during Kernel startup? That would mean the Kernel is trying to probe the interface.

    If so, what wireless module do you have? We may need to check that the correct driver is available in the Kernel.

    anton bauer said:
    2. Where can I get the schematic of the am335x GP EVM, especially for the COM connector?

    The GP EVM base board schematics are available in the product folder at http://www.ti.com/tool/TMDXEVM3358. Look for "ARM MPU AM335x EVM Base Board 15x15 Package Schematic" (TI document # sprr164) under "Design Files". It has PDF versions of the schematics in it.

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Hi Andreas,

    I measured the MMC2_CLK (at R485) and MMC2_CMD (at R486), but no any signal can be observed during the whole boot up process.

    Addtionally I also measured the DC voltage, at R485 the voltage is Zero and at R486, R487, R488, R489, R490 it is as expected 1.8V.  Following the picture showing where I did the measurement

    Question 1: What could be the reason that no MMC2_CLK signal on the COM connector?  Would you please check it on your side if you have the same results?

    In the file am335x_evm_gpdaughterboard_3h0001_bottomassembly_rev1_1A.pdf, I see the MMC2 (the 3rd device MMC interface) as the following

    Question 2: Why here in the PCB layout of the daughter board bootom side it is SDMMC1, not MMC2?  Just a name mismatching?

    Best Regards

    Anton

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    In the file am335x_evm_gpdaughterboard_3h0001_bottomassembly_rev1_1A.pdf, I see the MMC2 (the 3rd device MMC interface) as the following

    Question 2: Why here in the PCB layout of the daughter board bootom side it is SDMMC1, not MMC2?  Just a name mismatching?

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Anton,

    anton bauer said:
    Question 1: What could be the reason that no MMC2_CLK signal on the COM connector?  Would you please check it on your side if you have the same results?

    I just tried it, using an unmodified Linux SDK image from the AM335x Linux SDK v06.01.00.08 as created with the included SD card creation script, and I can see a 400kHz clock on MMC2_CLK from the host driver's probe attempts, see attached screenshot, measured via R485 using a logic analyzer. The reason there is no associated output in the Kernel message log is that the MMC commands that are sent go unanswered, hence the device driver never gets to the stage trying to match SDIO vendor and device IDs (after which an actual WiFi driver would get probed for example).

    I also enabled additional debug prints in the omap_hsmmc driver, and saw various CMDx getting issued, which corresponds with the CLK signal activity that was observed. For example...

    [    1.232307] omap_hsmmc 47810000.mmc: using lookup tables for GPIO lookup
[    1.232312] omap_hsmmc 47810000.mmc: No GPIO consumer wp found
[    1.232462] omap_hsmmc 47810000.mmc: context is restored: restore count 1
[    1.232468] omap_hsmmc 47810000.mmc: enabled
[    1.232668] omap_hsmmc 47810000.mmc: Linked as a consumer to regulator.3
[    1.239506] omap_hsmmc 47810000.mmc: unable to get vmmc_aux regulator -19
[    1.239517] omap_hsmmc 47810000.mmc: unable to get pbias regulator -19
[    1.322764] omap_hsmmc 47810000.mmc: Set clock to 0Hz
[    1.335293] omap_hsmmc 47810000.mmc: Set clock to 400000Hz
[    1.348083] omap_hsmmc 47810000.mmc: mmc0: CMD52, argument 0x00000c00
[    1.348389] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.354095] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.354206] omap_hsmmc 47810000.mmc: mmc0: CMD52, argument 0x80000c08
[    1.354541] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.354610] omap_hsmmc 47810000.mmc: Set clock to 400000Hz
[    1.355130] ledtrig-cpu: registered to indicate activity on CPUs
[    1.361212] omap_hsmmc 47810000.mmc: mmc0: CMD0, argument 0x00000000
[    1.361371] omap_hsmmc 47810000.mmc: IRQ Status is 1
[    1.362785] omap_hsmmc 47810000.mmc: Set clock to 400000Hz
[    1.364249] omap_hsmmc 47810000.mmc: mmc0: CMD8, argument 0x000000aa
[    1.364594] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.364675] omap_hsmmc 47810000.mmc: mmc0: CMD5, argument 0x00000000
[    1.365010] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.365081] omap_hsmmc 47810000.mmc: mmc0: CMD5, argument 0x00000000
[    1.365416] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.365480] omap_hsmmc 47810000.mmc: mmc0: CMD5, argument 0x00000000
[    1.365817] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.365964] omap_hsmmc 47810000.mmc: mmc0: CMD5, argument 0x00000000
[    1.366297] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.367472] NET: Registered protocol family 10
[    1.372662] omap_hsmmc 47810000.mmc: mmc0: CMD55, argument 0x00000000
[    1.373006] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.373077] omap_hsmmc 47810000.mmc: mmc0: CMD55, argument 0x00000000
[    1.373410] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.373488] omap_hsmmc 47810000.mmc: mmc0: CMD55, argument 0x00000000
[    1.373657] Segment Routing with IPv6
[    1.377355] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.377417] omap_hsmmc 47810000.mmc: mmc0: CMD55, argument 0x00000000
[    1.377507] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[    1.383458] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.383573] omap_hsmmc 47810000.mmc: Set clock to 400000Hz
[    1.383588] omap_hsmmc 47810000.mmc: mmc0: CMD1, argument 0x00000000
[    1.383921] omap_hsmmc 47810000.mmc: IRQ Status is 18000
[    1.384001] omap_hsmmc 47810000.mmc: Set clock to 0Hz

    anton bauer said:

    In the file am335x_evm_gpdaughterboard_3h0001_bottomassembly_rev1_1A.pdf, I see the MMC2 (the 3rd device MMC interface) as the following

    Question 2: Why here in the PCB layout of the daughter board bootom side it is SDMMC1, not MMC2?  Just a name mismatching?

    Yes unfortunately those names get easily confused. Generally speaking the AM335x GP EVM design is not very easy to follow and understand in my opinion, not only are there different boards stacked together they also all have their own schematic/design archives, using different signal names, plus there is a CPLD involved managing and routing various logic signals making things more complex than they need to be. If you are looking for SDIO-based WiFi connectivity one of the wireless BeagleBones might be a better starting point.

    Anyways if you want to use the AM335x GP EVM I think you need to figure out why you don't see any activity on the CLK signal during boot. Can you check the MUX chip configuration I pointed out earlier? Can you try to measure the CLK signal closer to the actual AM335x device pin (before the MUX chip for example).

    Also I had asked earlier, what WiFi/SDIO module are you trying to use?

    Regards, Andreas

  • 0 in reply to Andreas Dannenberg
    Prodigy 90 points

    Hi Andreas,

    thanks for the confirmation. I will check it as you suggested.

    - Would you please also tell me how did you enable additional debug prints in the omap_hsmmc driver? I also want to enable it so that I can see more log messages

    - Which profile is selected on your test?

    For your question I want to try with Murata 1MW module, but failed already on the first step

    Best Regards

    Xi

  • 0 in reply to anton bauer
    TI__Guru 70372 points

    Xi,

    anton bauer said:
    - Would you please also tell me how did you enable additional debug prints in the omap_hsmmc driver? I also want to enable it so that I can see more log messages

    There are different ways to do MMC debug printing (you can google that topic if you are interested) but I wanted something that works right away during Kernel boot so I just activated/modified existing debug code in a quick and dirty way to show activity around the 3rd MMC interface as follows:

    adannenb@beast:~/git/linux (ti-linux-4.19.y-dev)
$ git show drivers/mmc/host/omap_hsmmc.c
commit 76bca21a00f5a68f37fcb05c085949c9ca57dc0f (HEAD -> ti-linux-4.19.y-dev)
Author: Andreas Dannenberg <dannenberg@ti.com>
Date:   Wed Apr 8 17:10:02 2020 -0500

    Add debug prints for SDIO WiFi Debug

diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
index 0135693afa15..1e2e9efb7259 100644
--- a/drivers/mmc/host/omap_hsmmc.c
+++ b/drivers/mmc/host/omap_hsmmc.c
@@ -15,6 +15,9 @@
  * kind, whether express or implied.
  */
 
+#define DEBUG
+#define VERBOSE_DEBUG
+
 #include <linux/module.h>
 #include <linux/init.h>
 #include <linux/kernel.h>
@@ -596,7 +599,8 @@ static void omap_hsmmc_set_clock(struct omap_hsmmc_host *host)
        unsigned long timeout;
        unsigned long clkdiv;
 
-       dev_vdbg(mmc_dev(host->mmc), "Set clock to %uHz\n", ios->clock);
+       if (strcmp(dev_name(mmc_dev(host->mmc)), "47810000.mmc") == 0)
+               dev_vdbg(mmc_dev(host->mmc), "Set clock to %uHz\n", ios->clock);
 
        omap_hsmmc_stop_clock(host);
 
@@ -848,8 +852,9 @@ omap_hsmmc_start_command(struct omap_hsmmc_host *host, struct mmc_command *cmd,
 {
        int cmdreg = 0, resptype = 0, cmdtype = 0;
 
-       dev_vdbg(mmc_dev(host->mmc), "%s: CMD%d, argument 0x%08x\n",
-               mmc_hostname(host->mmc), cmd->opcode, cmd->arg);
+       if (strcmp(dev_name(mmc_dev(host->mmc)), "47810000.mmc") == 0)
+               dev_vdbg(mmc_dev(host->mmc), "%s: CMD%d, argument 0x%08x\n",
+                               mmc_hostname(host->mmc), cmd->opcode, cmd->arg);
        host->cmd = cmd;
 
        omap_hsmmc_enable_irq(host, cmd);
@@ -1041,7 +1046,8 @@ static void omap_hsmmc_dbg_report_irq(struct omap_hsmmc_host *host, u32 status)
                        buf += len;
                }
 
-       dev_vdbg(mmc_dev(host->mmc), "%s\n", res);
+       if (strcmp(dev_name(mmc_dev(host->mmc)), "47810000.mmc") == 0)
+               dev_vdbg(mmc_dev(host->mmc), "%s\n", res);
 }
 #else
 static inline void omap_hsmmc_dbg_report_irq(struct omap_hsmmc_host *host,
@@ -1110,7 +1116,8 @@ static void omap_hsmmc_do_irq(struct omap_hsmmc_host *host, int status)
        int error = 0;
 
        data = host->data;
-       dev_vdbg(mmc_dev(host->mmc), "IRQ Status is %x\n", status);
+       if (strcmp(dev_name(mmc_dev(host->mmc)), "47810000.mmc") == 0)
+               dev_vdbg(mmc_dev(host->mmc), "IRQ Status is %x\n", status);
 
        if (status & ERR_EN) {
                omap_hsmmc_dbg_report_irq(host, status);

    Note that the above dev_vdbg prints usually emit into the Kernel log you need to retrieve via 'dmesg' command, and will not print straight through to the console (depending on your console loglevel). But you can change these statements if you like to something like dev_err() to make them always print.

    anton bauer said:
    - Which profile is selected on your test?

    I've selected profile 0 (all DIP switches of SW8 turned to "OFF" position -> towards the LCD) but I don't think that matters. The signals related to MMC2 are solely managed on the main board, and are not routed through the daughtercard back to the COM connector.

    Regards, Andreas