• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 120 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

PROCESSOR-SDK-AM335X: emmc_part

Manu kumar
Intellectual 480 points
Part Number: PROCESSOR-SDK-AM335X

Tool/software:

Hi , Liu, ,

We observed that emmc_part.dump file as below works fine in TISDK 8.2, for creating emmc partition using "sfdisk /dev/mmcblk1 < emmc_part.dump"

label: dos
device: /dev/sdb
unit: sectors

/dev/sdb1 : start=       48195, size=      143360, type=c, bootable
/dev/sdb2 : start=      191555, size=     2097152, type=83
/dev/sdb3 : start=     2288807, size=     2097152, type=83
/dev/sdb4 : start=     4385965, size=     3145728, type=5
/dev/sdb5 : start=     4385970, size=      102400, type=c
/dev/sdb6 : start=     4488450, size=     2936012, type=83

the same partition is not working in TISDK 9.1.. so we changed partitions as below,

label: dos
device: /dev/sdb
unit: sectors

/dev/sdb1 : start= 48195, size= 143360, type=c, bootable
/dev/sdb2 : start= 191555, size= 2097152, type=83
/dev/sdb3 : start= 2288807, size= 2097152, type=83
/dev/sdb4 : start= 4385965, size= 3019603, type=5
/dev/sdb5 : start= 4385970, size= 100357, type=c
/dev/sdb6 : start= 4488450, size= 2915150, type=83

May i know why this behavior i am curious about it Slight smile
  • 0
    TI__Guru**** 150911 points

    Hi Manu,

    I see the difference between the 2 partitions is the sdb6 size, is my understanding correct?

    Manu kumar said:
    the same partition is not working in TISDK 9.1..

    Can you please provide the details what is not working?

  • 0 in reply to Bin Liu
    Intellectual 480 points

    Yes, this is the change it was expecting to modify the partition..

    thing which is not working is.. in 1st scenario is sfdisk was not able to partition with the command "sfdisk /dev/mmcblk1 < emmc_part.dump"

    Also i observed that sfdisk was not part of in built package.. we add in the "util-linux " in our package.. 

  • 0 in reply to Manu kumar
    TI__Guru**** 150911 points
    Manu kumar said:
    Also i observed that sfdisk was not part of in built package.. we add in the "util-linux " in our package.. 

    Is the util-linux package version different on your SDK8.2 and 9.1 builds? I am wondering it is because of the changes in util-linux package.

  • 0 in reply to Bin Liu
    Intellectual 480 points

    TISDK 8.2:

    root@am335x-evm:~# utmpdump.util-linux -V
    utmpdump.util-linux from util-linux 2.37.4

    TISDK 9..1:

    root@am335x-evm:~# utmpdump.util-linux -V
    utmpdump.util-linux from util-linux 2.35.1

  • 0 in reply to Manu kumar
    TI__Guru**** 150911 points

    I am wondering why the util-linux version in 9.1 is older than that in 8.2? Is it a human error?

    Manu kumar said:
    Also i observed that sfdisk was not part of in built package.. we add in the "util-linux " in our package.. 

    I see sfdisk is provided in the default rootfs image in the SDK9.1:

    root@am335x-evm:~# which sfdisk
    /usr/sbin/sfdisk
    root@am335x-evm:~# sfdisk --version
    sfdisk from util-linux 2.37.4
    root@am335x-evm:~# utmpdump.util-linux -V
    utmpdump.util-linux from util-linux 2.37.4

  • 0 in reply to Bin Liu
    Intellectual 480 points

    Sorry its my bad.. yep its a human error, 

    TISDK 8.2:

    root@am335x-evm:~# utmpdump.util-linux -V
    utmpdump.util-linux from util-linux 2.35.1

    TISDK  9.1:

    root@am335x-evm:~# utmpdump.util-linux -V
    utmpdump.util-linux from util-linux 2.37.4

    you are seeing because i have added util-linux pacakage.. else it will not be present as default

  • 0 in reply to Manu kumar
    TI__Guru**** 150911 points

    Sorry Manu, we won't be able to provide much support on the util-linux package. It is a open source project and TI is not involved. You might want to check its source code to see the changes between 2.35.1 to 2.37.4.