Jetson Nano eMMC partitions not show up

Robotics & Edge Computing Jetson & Embedded Systems Jetson Nano
1

Hi all,

I have faced some problems with adding extra partitions for Jetson Nano eMMC. My goal is to create two additional partition on the internal eMMC:

  • 3GB partition for log
  • 1GB partition for application resources and configuration

Im used this page:
https://docs.nvidia.com/jetson/archives/l4t-archived/l4t-325/index.html#page/Tegra%20Linux%20Driver%20Package%20Development%20Guide/part_config.html#wwp101098

Also this topic was very useful (the required changes in the p3448-0000.conf.common file was not mentioned in the previous doc):

I added the following definitions to bootloader/t210ref/cfg/flash_l4t_t210_emmc_p3448.xml:

        <partition name="FLC" type="data">
            <allocation_policy> sequential </allocation_policy>
            <filesystem_type> basic </filesystem_type>
            <size> 1073741824 </size>
            <allocation_attribute> 8 </allocation_attribute>
            <description> application resources and config </description>
        </partition>

        <partition name="LOG" type="data">
            <allocation_policy> sequential </allocation_policy>
            <filesystem_type> basic </filesystem_type>
            <size> 3221225472 </size>
            <allocation_attribute> 8 </allocation_attribute>
            <description> application logs </description>
        </partition>

and changed the ‘ROOTFSSIZE’ to 10GiB in p3448-0000.conf.common.

Im attaching my flash_l4t_t210_emmc_p3448.xml:
flash_l4t_t210_emmc_p3448.xml (18.9 KB)
and the generated flash.xml:
flash.xml (19.1 KB)

However after the board reboots the defined partitions are not visible:

:~$ sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL
NAME         FSTYPE   SIZE MOUNTPOINT                                  LABEL
loop1        vfat      16M                                             L4T-README
mmcblk0              14.7G                                             
├─mmcblk0p1  ext4      10G /                                           
├─mmcblk0p2             1M                                             
├─mmcblk0p3             6M                                             
├─mmcblk0p4            80K                                             
├─mmcblk0p5            64M                                             
├─mmcblk0p6             1M                                             
├─mmcblk0p7             6M                                             
├─mmcblk0p8            80K                                             
├─mmcblk0p9            64M                                             
├─mmcblk0p10          192K                                             
├─mmcblk0p11          256K                                             
├─mmcblk0p12           63M                                             
├─mmcblk0p13          512K                                             
├─mmcblk0p14          256K                                             
├─mmcblk0p15          256K                                             
├─mmcblk0p16          300M                                             
└─mmcblk0p17          4.2G                                             
mmcblk0boot0            4M                                             
mmcblk0boot1            4M                                             
mmcblk0rpmb             4M                                             
zram0               495.6M [SWAP]                                      
zram1               495.6M [SWAP]                                      
zram2               495.6M [SWAP]                                      
zram3               495.6M [SWAP]

There is a device named “mmcblk0p17”, but I was expecting two separate partitions. Also it is not clear how could I mount the newly created partitions in an automated way (preferably whit some configuration file which can be deployed during flashing process).

Can you help me what am I missing here?

Thanks!

Bests,
Peter