Hi Mr. Nelson,
I made some progress,
mdev was auto-mounting /dev/mmcblk0* partitions, i changed following line
in the mdev.conf file.
*#mmcblk[0-9]p+[0-9]* root:root 660 */etc/mdev/mount.sh $MDEV*
*mmcblk[0-9]p+[0-9]* root:root 660 *
But i don't understand why auto-mounting was creating proble
Hi Mr. Nelson,
Problem in short
I changed partitioning command but with help,
Here is my sfdisk commad,
#Partition
drive
sfdisk --force --in-order --Linux ${DRIVE} -uM
<<-__EOF__
1,32,C,*
On Fri, Apr 24, 2015 at 11:22 AM, Ankur Tank wrote:
> Problem in short:
> eMMC partition's device files are not visible in /dev/ directory after
> partitiong using "sfdisk"
> HI ,
>
> I have put log of script here, any suggestions,
>
> + partition_emmc /dev/mmcblk0
> + DRIVE=/dev/mmcblk0
> + HEADS
Problem in short:
*eMMC partition's device files are not visible in /dev/ directory after
partitiong using "sfdisk"*
HI ,
I have put log of script here, any suggestions,
+ partition_emmc /dev/mmcblk0
+ DRIVE=/dev/mmcblk0
+ HEADS=255
+ SECTOR_SIZE=512
+ SECTORS_PER_TRACK=63
*+ dd if=/dev/zer
Oh that was the problem..I was referring JDEC spec and all :)
Thank you very much for reply Mr. Nelson,
7 Partition problem solved :)
Let me know if you have any suggestions for other problems.
One more questions,
# blkid
/dev/mmcblk0p2: LABEL="rootfs" UUID="3bb8e52f-1434-4e04-9d76-a50d75380c39"
On Wed, Apr 22, 2015 at 9:25 PM, Ankur Tank wrote:
> I am writing firmware(MLO,u-boot.img, uImage(ver 3.12), dtb, rootfs.tar.gz)
> programming script for
> am335x based custom board which is based on Beaglebone black.
> Rootfile system is to be put onto the eMMC.
> Firmware programming script run
I am writing firmware(MLO,u-boot.img, uImage(ver 3.12), dtb, rootfs.tar.gz)
programming script for
am335x based custom board which is based on Beaglebone black.
Rootfile system is to be put onto the eMMC.
Firmware programming script runs as the one of the init script from
the nfsroot folder
