How can i verify correct root device name?

Hi,

Can you please post your SYSBOOT[15:0] pins settings? 

What hardware are you using? is it some EVM or custom board?

Thank you.

BR,

Vidin

Hi Vidin

Thanks a lot for your qucik reply.

The hardware is our custom board.

Please check the boot setting image.

The boot setting has been made sure that ti is correct by Mr Biser,

and It also could be boot correctly according to setted boot mode .

Now during linux kernel booting,It should find root=/dev/mmcblk0p2,

I  think the name of root is difference with different sd card,is it correct?

Best Regards

Qin Long

Hi Qin,

About the SYSBOOT pins what are the JP37 settings for SYSBOOT [4:0]? Actually these pins are in interest for the case.

Other thing is what is your MMCx ports connections? What do you connect to MMC0 and what device to MMC1?

On which port is the SD card connected?

Normally the first found on MMCx ports device is mounted as /dev/mmcblk0 and this is the device that boot sequence is looking for.

BR,

Vidin

Hi Vidin

JP37 is switch,so SYSBOOT [4:0] can be set 1 or 0 respectively accrording to differenct boot mode.

I'm using MMC0 connect to sd card.so  should  i correct “root=/dev/mmcblk0p2” to

"root=/dev/mmcblk0"?

I will test it with "root=/dev/mmcblk0" tomorrow.

Best Regards

Hi,

mmcblk0p2 points to the second partition of your mmc device. This should be the root file system. You cannot use root=/dev/mmcblk0 since this is not a partition. Please share how did you format your sd card.

Best regards,
Miroslav

Hi Miroslav

Thanks a lot for your reply.

I format my sd card according to follow steps.

1 refer to the url http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_create_SD_card_script

2 When run to "Select Number of Partitions", i selected [2]. it means that we use two partitions for boot and rootfs.

3 After the SD card is partitioned, i selected [n] to safely exit the script.it means that i leave the partitions empty.

4 I copy MLO,u-boot.img,uEnv.txt and uImage to boot partition

5 I copy all content of targetNFS to rootfs partition

Do you think these steps are correct?

Best Regards

Qin Long

Hi Miroslav

addtional question.

I have changed the parameter "mem=128M" to "mem=512M" in the first line of uEnv.txt.

Is it OK?

Best Regards

Qin Long

Hi all

my custom board still stopped when ran to "Waiting for root device /dev/mmcblk0p2..."

How  can i solve the problem?

Please help me.

Best Regards

Qin Long

long qin said:

I format my sd card according to follow steps.

1 refer to the url http://processors.wiki.ti.com/index.php/Sitara_Linux_SDK_create_SD_card_script

2 When run to "Select Number of Partitions", i selected [2]. it means that we use two partitions for boot and rootfs.

3 After the SD card is partitioned, i selected [n] to safely exit the script.it means that i leave the partitions empty.

4 I copy MLO,u-boot.img,uEnv.txt and uImage to boot partition

5 I copy all content of targetNFS to rootfs partition

Can you please let the create-sdcard script finish and copy the pre-built root file system to the SD card. Then you can manually copy your custom MLO, u-boot.img, uEnv.txt and uImage to the boot partition.

Best regards,
Miroslav

Hi Miroslav

Thanks a lot for your reply.

I  ran create-sdcard script again according to guide.

when run to  the step of "Choose Custom Images ",the info  is showed as follow,

###############################################################################

    Choose file path to install from

    1 ) Install pre-built images from SDK
    2 ) Enter in custom boot and rootfs file paths

################################################################################

Choose now [1/2] :

I selected 2 to enter in custom boot and rootfs file paths

those files  could be correctly copied to boot and rootfs partition respectively.

then i insert the sd card into my custom board and power on,the same thing happened.

so the problem have not been solved.

Best Regards

Qin Long

Hi Miroslav

Thanks a lot for your advice.

As you said,The problem was coused by mmc_sd_cd,

I used GPIO0_16 as mmc_sd_cd detect signal pin.

The problem have been solved.

I added two lines source code as follow,

am335x_mmc[0].nonremovable = true;

am335x_mmc[0].gpio_cd = -EINVAL;

Best Regards

Qin Long