RFS is not extracting from MMC in Calixto board TI AM1808.

Jaymin Dabhi

Prodigy 130 points

Other Parts Discussed in Thread: AM1808, OMAP-L138, DA8XX, OMAPL138

Hi All,

I have a 'Calixto board'. TI SITARA AM1808 SoM with 128MB NAND Flash.

I flash kernel 2.6.37 Kernel uImage in NAND flash.

I want to run RFS from MMC and I inserted 4 GB MMC.

But after extracting of uImage, the board was hanged and go to search for RFS.

I post here uboot args and Kernel log where it stopped.

"U-Boot args"

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

MMC:   davinci: 0
SF: Detected SST25VF016B with page size 4096, total 2 MiB
Out:   serial
Err:   serial
ARM Clock : 300000000 Hz
DDR Clock : 150000000 Hz
Net:   Ethernet PHY: GENERIC @ 0x00
DaVinci-EMAC
Hit any key to stop autoboot: 0
U-Boot > printenv
baudrate=115200
bootargs=mem=128M console=ttyS2,115200n8 earlyprintk=ttyS2,115200n8 rw root=/dev/mmcblk0p1 rootdelay=2 rootfstype=ext2
bootcmd=mw 0x68000014 0x364200; nand read.e 0xc0700000 0x200000 0x250000;bootm 0xc0700000;
bootdelay=3
bootfile="uImage"
ethact=DaVinci-EMAC
ethaddr=0a:2b:3c:4d:a5:b6
fileaddr=C0700000
filesize=24DDE8
gatewayip=10.111.17.254
ipaddr=10.111.17.70
serverip=10.111.17.17
stderr=serial
stdin=serial
stdout=serial
ver=U-Boot 2010.12 (Feb 18 2012 - 01:03:30)

Kernel Log

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

U-Boot > boot

NAND read: device 0 offset 0x200000, size 0x250000
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
2424832 bytes read: OK
## Booting kernel from Legacy Image at c0700000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2416040 Bytes = 2.3 MiB
   Load Address: c0008000
   Entry Point: c0008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (root@DTP148) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-67) ) #15 PREEMPT Thu Sep 3 12:51:56 IST 2015
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: DaVinci DA850/OMAP-L138/AM18x EVM
Memory policy: ECC disabled, Data cache writeback
DaVinci da850/omap-l138/am18x variant 0x1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
Kernel command line: mem=128M console=ttyS2,115200n8 earlyprintk=ttyS2,115200n8 rw root=/dev/mmcblk0p1 rootdelay=2 rootfstype=2
PID hash table entries: 512 (order: -1, 2048 bytes)
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 128MB = 128MB total
Memory: 124824k/124824k available, 6248k reserved, 0K highmem
Virtual kernel memory layout:
    vector : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xff000000 - 0xffe00000   ( 14 MB)
    vmalloc : 0xc8800000 - 0xfea00000   ( 866 MB)
    lowmem : 0xc0000000 - 0xc8000000   ( 128 MB)
    modules : 0xbf000000 - 0xc0000000   ( 16 MB)
      .init : 0xc0008000 - 0xc0030000   ( 160 kB)
      .text : 0xc0030000 - 0xc049f000   (4540 kB)
      .data : 0xc04a0000 - 0xc04d53e0   ( 213 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptable hierarchical RCU implementation.
        RCU-based detection of stalled CPUs is disabled.
        Verbose stalled-CPUs detection is disabled.
NR_IRQS:245
Console: colour dummy device 80x30
Calibrating delay loop... 149.50 BogoMIPS (lpj=747520)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
DaVinci: 144 gpio irqs
NET: Registered protocol family 16
No entry for the specified index
calixto_evm_init: lcdcntl mux setup failed: -19
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c-gpio i2c-gpio.1: using pins 20 (SDA) and 21 (SCL)
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource timer0_1
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 3, 32768 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
EMAC: RMII PHY configured, MII PHY will not be functional
msgmni has been set to 243
alg: No test for stdrng (krng)
io scheduler noop registered (default)
da8xx_lcdc da8xx_lcdc.0: GLCD: Found Tianma_TM035KDH03 panel
Console: switching to colour frame buffer device 40x30
Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x1c42000 (irq = 25) is a AR7
serial8250.0: ttyS1 at MMIO 0x1d0c000 (irq = 53) is a AR7
serial8250.0: ttyS2 at MMIO 0x1d0d000 (irq = 61) is a AR7
console [ttyS2] enabled
brd: module loaded
ONFI flash detected
NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix ��)
Creating 2 MTD partitions on "davinci_nand.1":
0x000000020000-0x000000820000 : "kernel"
0x000000820000-0x000008000000 : "filesystem"
davinci_nand davinci_nand.1: controller rev. 2.5
spi_davinci spi_davinci.1: DMA: supported
spi_davinci spi_davinci.1: DMA: RX channel: 18, TX channel: 19, event queue: 0
m25p80 spi1.0: found sst25vf016b, expected m25p80
m25p80 spi1.0: sst25vf016b (2048 Kbytes)
Creating 4 MTD partitions on "m25p80":
0x000000000000-0x000000010000 : "UBL"
0x000000010000-0x000000090000 : "U-Boot"
0x000000090000-0x0000000a0000 : "U-Boot-Env"
0x0000001f0000-0x000000200000 : "MAC-Address"
Read MAC addr from SPI Flash: ff:ff:ff:ff:ff:ff
spi_davinci spi_davinci.1: Controller at 0xfef0e000
davinci_mdio davinci_mdio.0: davinci mdio revision 1.5
davinci_mdio davinci_mdio.0: detected phy mask fffffffe
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver SMSC LAN8710/LAN8720
console [netcon0] enabled
netconsole: network logging started
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci ohci.0: DA8xx OHCI
ohci ohci.0: new USB bus registered, assigned bus number 1
Waiting for USB PHY clock good...
ohci ohci.0: irq 59, io mem 0x01e25000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: DA8xx OHCI
usb usb1: Manufacturer: Linux 2.6.37 ohci_hcd
usb usb1: SerialNumber: ohci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
omap_rtc: RTC power up reset detected
i2c /dev entries driver
Linux video capture interface: v2.00
watchdog watchdog: heartbeat 60 sec
cpuidle: using governor ladder
cpuidle: using governor menu
davinci_mmc: probe of davinci_mmc.0 failed with error -16
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
asoc: tlv320aic3x-hifi <-> davinci-mcasp.0 mapping ok
ALSA device list:
#0: DA850/OMAP-L138 EVM
nf_conntrack version 0.5.0 (1950 buckets, 7800 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
TCP cubic registered
NET: Registered protocol family 17
davinci_emac_probe: using random MAC addr: 6a:44:22:41:f2:50
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
Waiting 2sec before mounting root device...
Root-NFS: no NFS server address
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
Backtrace:
[<c0034718>] (dump_backtrace+0x0/0x114) from [<c0386870>] (dump_stack+0x18/0x1c)
r6:00008000 r5:c7815000 r4:c04d5990 r3:00000000
[<c0386858>] (dump_stack+0x0/0x1c) from [<c03868ec>] (panic+0x78/0x1a4)
[<c0386874>] (panic+0x0/0x1a4) from [<c0008fb0>] (mount_block_root+0x1d8/0x218)
r3:00000030 r2:00000000 r1:c7829f58 r0:c0431c7c
[<c0008dd8>] (mount_block_root+0x0/0x218) from [<c000909c>] (mount_root+0xac/0xd0)
r8:00000000 r7:00000013 r6:c004799c r5:c00272c1 r4:00200000
[<c0008ff0>] (mount_root+0x0/0xd0) from [<c0009230>] (prepare_namespace+0x170/0x1c8)
r4:c04d5444
[<c00090c0>] (prepare_namespace+0x0/0x1c8) from [<c00084b8>] (kernel_init+0x114/0x154)
r5:c00083a4 r4:c04d53e0
[<c00083a4>] (kernel_init+0x0/0x154) from [<c004799c>] (do_exit+0x0/0x6d4)
r4:00000000 r3:00000000

I am not sure about this, but the problem is in few last lines which I marked as red color.

Was this error related to MMC partition related?

Are my u-boot arguments wrong, specially 'bootargs'?

Please give a solution about this error.

over 8 years ago

0 Prabhakar Lad over 8 years ago

Guru 11260 points

Hi,

Is the board booting from SD card itself (uboot is present in SD card) ?
when you formatted the SD card was it ext2 type ?

How many partitions do you have in your SD card ? 1/2/3 ? and in which partition is your rootfile system extracted ?
If it is say partition 2, then it should be root=/dev/mmcblk0p2

Refer [1] to create a SD card.

[1] processors.wiki.ti.com/.../OMAP-L138_Preparing_SD_Card_for_Boot

Cheers,
--Prabhakar Lad

0 Titusrathinaraj Stalin over 8 years ago

TI__Guru** 116100 points

Hi Jaymin,

VFS: Cannot open root device "mmcblk0p1" or unknown-block(2,0)
Please append a correct "root=" boot option; here are the available partitions:

In my opinion, I didn't see any MMC card detect logs, you should get log for SD card detection from kernel with partition information(p1,p2 etc.,).
So, please check the MMC initalization.
Also you are getting some MMC error.

davinci_mmc: probe of davinci_mmc.0 failed with error -16

0 Jaymin Dabhi over 8 years ago in reply to Prabhakar Lad

Prodigy 130 points

Hi Prabhakar,

Thank you for quick response and thanks for the link.

Is the board booting from SD card itself (uboot is present in SD card) ?
when you formatted the SD card was it ext2 type ?

The uboot is on NAND flash.

Kernel uImage is also on NAND flash.

I have to boot up my board so for that reason I need to port Kernel in NAND and then after RFS.

Kernel uImage which I already flashed in NAND but for RFS first I want to use MMC and then after I will flash it on NAND. (That's what I planned!!).

So, only RFS is present only on SD card.

when you formatted the SD card was it ext2 type ?

YES, I formatted SD card with ext2 type FS and copy RFS using 'dd' command.

How many partitions do you have in your SD card ? 1/2/3 ? and in which partition is your rootfile system extracted ?
If it is say partition 2, then it should be root=/dev/mmcblk0p2

I have only one partition on the SD card with RFS only.

Actually, I am confusing that 'root' parameter.

If I have only one partition on the SD card with RFS only then what will be the value of 'root' parameter?

Is it /dev/mmcblk0p2 or /dev/mmcblk0p1?

And one more thing is that, whether is there any special configurations or settings needed for 'boot from SD card'?

Please let me know your suggestions and comments.

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hi Stalin,

Thanking you for suggestions.

What would be the possible reasons of the MMC initialization failure?
Is it related to boot args parameter? Is uboot taking it incorrectly?
OR
Is it occurring, because I have only one partition on the SD card with RFS only? I mean, Is it necessary to make two partitions on SD card and put FS on second partition? Is this the only way/method?(Just assuming!)

Please let me know your comments about this.

0 Prabhakar Lad over 8 years ago in reply to Jaymin Dabhi

Guru 11260 points

Hello,

In case you are booting from NAND and you have only one partition then the bootargs are correct. The only reason now it is failing because the mmc driver is failing when you are kernel is coming up, that is the reason rootfs is failing to mount.

You need to debug why mmc driver is failing, fixing it will probably fix the rootfs mounting problem

Im not aware of calixto board, but it might have boot switch which will load the uboot from SD card instead of NAND.

Cheers,

--Prabhakar Lad

0 Titusrathinaraj Stalin over 8 years ago in reply to Jaymin Dabhi

TI__Guru** 116100 points

Hi Jaymin,
Are you using EVM board or custom board ?
If EVM, have you tried with pre-built (default) boot binaries ?
Since it has support for all peripherals by default right ?

If custom, what is the hw difference on SD peripheral ?
Modified the SD card initialization for your custom board if any ?

0 Jaymin Dabhi over 8 years ago in reply to Prabhakar Lad

Prodigy 130 points

Hello Prabhakar,

Greeting of the day.

Thanks a lot for your reply.

YES, there is four switch on my carrier board.

Details is as below:

SW1 - BOOT4 - PULL DOWN (with R58 shown as below)

SW2 - BOOT 3 - PULL UP (with R48 shown as below)

SW3 - BOOT 2 - PULL UP (with R49 shown as below)

SW4 - BOOT 1 - PULL DOWN (with R55 shown as below)

and BOOT 0, BOOT 7, BOOT 6 and BOOT 5 are PULL DOWN.

As per Calixto manual it is a SPI Uboot Loading configuration.

Switches connections

So, Is it correct configuration of switches to load RFS from SD card.?

Now, apart from this scenario Is there any setting which I need to enable in Kernel(mean to say at the time of 'make menuconfig' and 'kernel compilation') for the MMC driver to configure it properly?

Also, I have examined a couple of things in kernel log and boot args, but I am new to this board so I don't know whether it's correct or not? Please clarify it.

1. In Kernel log:

Root-NFS: no NFS server address

What it means by NFS server address?

Is this point out any NAND flash related issue?

One more thing is that, whether I need to load RFS in my NAND? Is the only way to mounting RFS on board apart from SD card?

2. In uboot args:

bootcmd=mw 0x68000014 0x364200; nand read.e 0xc0700000 0x200000 0x250000;bootm 0xc0700000;

Is uboot instructing to read RFS from NAND? If this is YES, then how to change it to 'SD' card?

Let me know about it.

Inform me if you want any more details from me regarding this problem.

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hi Titusrathinaraj,

Thanking you for you answer.

I have custom board(carrier board + SOM TI AM1808)

Link: http://www.calixto.co.in/products_soms.html

I have pre built boot configurations.

In that configuration board boots from NAND flash with pre-install uboot. Uboot installed already.

Then after I flashed uImage into NAND and also Kernel extracting successfully(not completely) as seen in my 1st Kernel log.

But now I want to mount RFS to bring up boot completely.

So, for now RFS is not mounting from SD card.

In custom hardware on carrier board there is switches, detail as below:

SW1 - BOOT4 - PULL DOWN

SW2 - BOOT 3 - PULL UP

SW3 - BOOT 2 - PULL UP

SW4 - BOOT 1 - PULL DOWN

and BOOT 0, BOOT 7, BOOT 6 and BOOT 5 are PULL DOWN.

BOOT 0 to BOOT 7 are pins of AM1808.

I didn't get you at 'what is the hardware difference on SD peripheral?'
Would you please elaborate it?

Please let me know about this .

0 Titusrathinaraj Stalin over 8 years ago in reply to Jaymin Dabhi

TI__Guru** 116100 points

Hi Jaymin,
So you are using EVM board with default binaries, so no more doubts on SD card hw.
Please refer to the EVM user guide for SD card operation.
You have to check that why THE SD card is failing even you use the default binary.
I don't have calixto board and no experience with that board, but SDI,LogicPD and TI's LCDK boards.

Do one things, boot the board with filesystem from NAND or NFS then insert the SD card and see, able to detect or not.

Able to detect the SD card in u-boot ?

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hello Titusrathinaraj,

Thank you for the quick response.

I referred the user manual of the Calixto board for the procedure and currently following the procedure, but I am new to this Calixto and TI AM1808, there is slow progress.

There is no RFS on NAND flash.
Actually, the board came with only uboot in NAND flash.
I flashed only uImage in NAND using 'TFTP' as below:

uboot > tftp c0700000 uImage_kernel_2_ 6_37

It flashed successfully, but Kernel stop to extracting at the time of RFS mount.

NOW,
---------
I examined one more thing that I founded one of built Kernel 'uImage' from the database of 'completed work'. It's name was 'uImage_mmc_ready'.

Let me explain a whole scenario/condition. Hope you will find some helpful information/points for the solution and it will be more helpful to understanding the main reason behind this issue.

For better understanding I am abbreviate names as:
1) uImage - which I flashed in NAND already. It was compiled by myself which some new configuration setting and I have whole Kernel tarball of it. I did only 2 changes related to serial-to-usb driver related in 'make menuconfig', load '.config' file name as 'calixto_ecb_defconfig' which was given by Calixto and compiled uImage. No other changes.

2) uImage_mmc - which I founded on old database. I haven't 'ANY' details about this uImage nor any tarball. I have only uImage, that's all.

3) RFS - which I have RFS tarball which was taken from 'Calixto google code' website. I haven't in depth details about it.

4)uboot - Came with board already.

Please interpret necessary details as per above information in the below description.
--------------------------------------------------------------------------------------------------------------------
1. I have 'uboot' in NAND flash. - boot successfully.
2. I flashed 'uImage' in NAND flash. - extract successfully, but stop at the time of 'RFS' mounts.
=> At that time my boot args was,
uboot > setenv bootcmd "mw 0x68000014 0x364200; nand read.e 0xc0700000 0x200000 0x250000;bootm 0xc0700000"
uboot > setenv bootargs "mem=128M console=ttyS2,115200n8 earlyprintk=ttyS2,115200n8 rw root=/dev/mmcblk0p1 rootdelay=2 rootfstype=ext2"
Which was same as described by Calixto.
3. I copied 'RFS' in SD card with only ONE partition and tried to mount RFS from SD card, but Kernel stopped to extracting at the time of mount it.
----------
NEXT - thought to do one experiment with another method.
----------
4. Followed boot-able SD card creation steps from Calixto manual.
5. Copied 'RFS' in a 2nd partition of SD card.
6. Copied 'uImage' into 1st partition.
7. Inserted SD card, but same thing happened again, Kernel stopped at the time of 'RFS' mount.
=> At that time my boot args was,
uboot > setenv bootcmd "mw 0x68000014 0x364200; nand read.e 0xc0700000 0x200000 0x250000;bootm 0xc0700000"
uboot > setenv bootargs "mem=128M console=ttyS2,115200n8 earlyprintk=ttyS2,115200n8 rw root=/dev/mmcblk0p2 rootdelay=2 rootfstype=ext2"
[I changed the root=/dev/mmcblk0p1 to root=/dev/mmcblk0p2]
8. Now, copied the 'uImage_mmc' into 1st partition. copied the 'uImage_mmc' into 1st partition.
9. Inserted SD card, but same thing happened again, Kernel stopped at the time of 'RFS' mount.
=> At that time my boot args was,
uboot > setenv bootcmd "mw 0x68000014 0x364200; nand read.e 0xc0700000 0x200000 0x250000;bootm 0xc0700000"
uboot > setenv bootargs "mem=128M console=ttyS2,115200n8 earlyprintk=ttyS2,115200n8 rw root=/dev/mmcblk0p2 rootdelay=2 rootfstype=ext2"
-------------------------
NEW - Imporatant
-------------------------
10. Copied the 'uImage_mmc' into 1st partition. copied the 'uImage_mmc' into 1st partition.
11. Inserted SD card and Kernel extract from SD card, then after 'RFS' also mounted successfully and I get shell prompt of 'ARAGO PROJECT' which my FS was.
=> At that time my boot args was,
uboot > setenv bootargs 'mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off'
uboot > setenv bootcmd 'mmc rescan 0;fatload mmc 0 0xc0700000 uImage; bootm c0700000;'
[I found that argument from link 'http://processors.wiki.ti.com/index.php/OMAP-L138_Preparing_SD_Card_for_Boot' which was mentioned by 'Prabhakar Lad' in same post related to this issue.]

From above 11 points I concluded one thing that there is no issue with MMC hardware.
'uImage_mmc' extracted successfully and mounted 'RFS' without any problem, it means that there is some changes in 'uImage' (which I made with ready-made ''calixto_ecb_defconfig' file and flashed into NAND flash) and 'uImage_mmc'.

But, the main problem is that I haven't any kind of source code or Kernel tarball of that image(uImage_mmc). Because of that I can't explore it to examine the changes.

Now, I have source code/Kernel tarball of 'uImage' only. Which I can compile it again with the changes.

So, there should be some changed related to MMC/SD card related in 'uImage_mmc' for that reason board booted up with this image and mounted 'RFS'. Otherwise 'RFS' was same in both cases, with 'uImage' and 'uImage_mmc'.

Changes were only -> boot args and Kernel image.
As per my understanding of uboot's args,
In the 1st type of args it was going to check into NAND and on 2nd type of args it was going to check into MMC.

So, as you point of understanding,
What is the main reason for this issue? Is it boot args or Kernel configuration or both?

How can I enable/set MMC related setting in Kernel(in 'make menuconfig')? only this change I can do so my 'uImage' will go to check into the MMC for 'RFS'.

Is there any other reasons/possibilities/assumptions or important things related to this problem?

Please let me know about your thinking and answers about this.
It will very much clear my doubts and solve the issue.
I think that I am very near the exact solution about the problem.

By the way, How can I check the SD card detection in uboot?
(Your question: Able to detect the SD card in u-boot ?)

Hope this information will give clear visibility about the problem.

Please let me know about solutions/views.

[Pardon for such a very long message]

0 Titusrathinaraj Stalin over 8 years ago in reply to Jaymin Dabhi

TI__Guru** 116100 points

Hi Jaymin,

Sorry for the delayed response on this.

So, as you point of understanding,
What is the main reason for this issue? Is it boot args or Kernel configuration or both?

Its purely related to kernel configuration only.

How can I enable/set MMC related setting in Kernel(in 'make menuconfig')? only this change I can do so my 'uImage' will go to check into the MMC for 'RFS'.

Please make sure that you have enabled the davinci MMC support via make menuconfig.
Ex:
make menuconfig
---> drivers
---> SD/MMC

Also please refer to the following TI wiki page.

processors.wiki.ti.com/.../Building_PSP_Components_for_OMAP-L1x_on_v3.x_Kernel

Is there any other reasons/possibilities/assumptions or important things related to this problem?

Other than enabling MMC driver, you may need to modify/enable the MMC support in board file.

By looking into kernel bootup log, it shows that you have enabled MMC driver support, so surely it may need some modification in board file, say MMC pinmuxing,MMC card detect etc.,
Please refer to the OMAPL138 LCDK board file for reference and modify it for your board with checking both schematics of LCDK & Calixto board.

BOARD FILE LOCATION:
arch/arm/mach-davinci/<check for Calixto board file>

BOARD FILE LOCATION for OMAPL138 LCDK board:
arch/arm/mach-davinci/board-omapl138-lcdk.c

By the way, How can I check the SD card detection in uboot?
(Your question: Able to detect the SD card in u-boot ?)

There is a command to initialize the MMC and to list the contents of SD card (FAT)
For that you have to enable MMC support in u-boot code.
CONFIG_MMC
CONFIG_DAVINCI_MMC

u-boot Commands:
i) mmc init or mmc rescan
ii) fatls mmc 0 1

Please let me know if any further help required.

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hi Titusrathinaraj,

Same here, sorry for delayed.
Thank you for the reply.

I thought same that there is totally Kernel related issues and now after your reply it has been confirmed.
YES, I have enabled the MMC support in Kernel.

So, as you suggest I will do the following task.
I will check the board file of my Calixto board with reference of board file of OMAPL138 LCDK board for MMC driver and its configuration related.

As concern to u-boot, I can't modify its source code, but I think that MMC support has enabled already in u-boot code.
Also, I will check both commands as you suggest.
[ i) mmc init or mmc rescan and ii) fatls mmc 0 1 ]

I will try my best to complete as early as possible.
I will put output here for your reference.

Sure, I will inform for further help.
Thanks for that.

0 Titusrathinaraj Stalin over 8 years ago in reply to Jaymin Dabhi

TI__Guru** 116100 points

Hi Jaymin,
Thanks.
Also please check the schematics of LCDK board and your Calixto board on MMC section like CARD DETECT pin, DATA pins etc., while comparing the board file.

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hi Titusrathinaraj,,

Sure, I will check that also MMC related section.
I download schematic files from below link. Please confirm that, Is this correct? or Is there other link?

link : www.ti.com/.../tmdslcdk138

0 Titusrathinaraj Stalin over 8 years ago in reply to Jaymin Dabhi

TI__Guru** 116100 points

Hi Jaymin,
Yes you can use & refer the LCDK board schematics.
www.ti.com/.../tmdslcdk138

0 Jaymin Dabhi over 8 years ago in reply to Titusrathinaraj Stalin

Prodigy 130 points

Hi Titusrathinaraj,

Thanks for reference. It will help me.

I will check and inform here about updates and issue if any.

Processors

Processors forum

RFS is not extracting from MMC in Calixto board TI AM1808.