EMMC extra partition for firmware update in apalis-imx6

Hi @jaski.tx ,

i want to create one extra partition on emmc to store my firmware for update.

so what change need to be done for that in u-boot side??

i’m able to create 3rd partition after modifying update.sh script , but not able to copy any file system ( rootfs ) in that area.

check below snippet from u-boot :

Apalis iMX6 # mmc part

Partition Map for MMC device 0 – Partition Type: DOS

Part Start Sector Num Sectors UUID Type

1 8192 32768 91735e44-01 0c

2 40960 3502071 91735e44-02 83

3 3543050 3583990 91735e44-03 83

Apalis iMX6 # ls mmc 0:1
5831200 zimage
50365 imx6q-apalis-eval.dtb

2 file(s), 0 dir(s)

Apalis iMX6 # ls mmc 0:2

   1024 .
   1024 ..
  12288 lost+found
   3072 bin
   1024 boot
   1024 dev
   3072 etc
   1024 home
   3072 lib
   1024 media
   1024 mnt
   1024 proc
   1024 run
   3072 sbin
   1024 sys
   1024 tmp
   1024 usr
   1024 var

Apalis iMX6 # ls mmc 0:3

Failed to mount ext2 filesystem…

** Unrecognized filesystem type **

Apalis iMX6 #

please suggest what is the issue here ? what more modification made to copy data on that partition ??

I checked many person asked question like that and you posted solution for changes , but i’ did not get the correct solution for that. could you provide files with changes??

example : Imx6 extra partition - Toradex Community

https://www.toradex.com/community/questions/8008/partitioning-of-emmc-for-ab-deployment-support.html

more colibri-imx6_bin/mbr.bin file created after running update.sh script. this file will call on every run setupdate and run update command . so it will create new partition table every time??

Please explain me about this…

check attachment : link text

regards,

nikunj patel

Hi,

after login in to system , using mkfs.ext4 utility i’m able to format the partition and copy the data in to it.

so , what is the issue from u-boot side ? Not able to mount system and copy data ??

Hi @jaski.tx ,

I want to create 5 partition in emmc .

1. U-boot(Zimage + dtb)
2. rootfs
3. recovery
4. config_data
5. log_data

As we know that we can create only 4 primary partition.

So , i will create 1 to 3 as primary partition and created 1 extended partition in which i will create 4 and 5th partition as logical.

while flashing sd-card means while running update.sh script i’ll able to see partition table as below:

[upload|QFdjnv+ECabO/IoM36YRBQa2WEU=]

this is done correctly as i’m expecting .

while when i’m flashing entire module ( apalis-imx6 ) , i’m not able to get correct partition table.

See partition table on apalis-imx6 module :

[upload|PSXz3rQvZlJlkMO72tafj8eQ7Ow=]

So what is the issue here?? why it is showing error bad MBR sector signature 0x0000 ??

please help me on that.

Check attach script . link text

Regards,
nikunj patel

Rather than using MBR with extended partitions to overcome the limitation of max. 4 primary partitions I would suggest to use the more recent GPT partitioning scheme which is supported in U-Boot as well. Note that while U-Boot supports reading such partitions it does NOT really support creating them. In our legacy update scripts we kinda cheat by pre-generating binary MBR resp. file system images on the development workstation to overcome this limitation. However, nowadays using the Toradex Easy Installer would be the preferred way to go about the initial deployment of such systems.