LSDK2012 flex-installer does not split partitions

[m_kei]

We are building with LSDK2012. The flex-builder succeeded and I am trying to flush firmware, bootpartition and rootfs to the SD card. 

I am using LSDK2012's flex-installer for flush, but since flex-installer does not partition, it outputs an error when referencing /dev/sdbx. (x is the partition number)

When I used LSDK2102 previously, flex-installer did the partitioning automatically. However, LSDK2012 does not.

Do I have to prepare my own partitioned SD card for LSDK2012?
If I do it myself, which map should I follow for partitioning?

[m_kei]

The following is the error message when running flex-installer.

$ flex-installer -i auto -m lx2160ardb_rev2 -d /dev/sdb
/dev/sdb: 7 GB
The capacity of /dev/sdb is only 7 GB, using partitions: 4P=128M:2G:64M:-1
firmware_lx2160ardb_rev2_uboot_sdboot.img already exists
bootpartition_LS_arm64_lts_5.4.tgz already exists
rootfs_lsdk2012_ubuntu_main_arm64.tgz already exists
Downloaded distro images [Done]
102592+1 records in
102592+1 records out
52527324 bytes (53 MB, 50 MiB) copied, 36.4851 s, 1.4 MB/s
Program firmware_lx2160ardb_rev2_uboot_sdboot.img into /dev/sdb startblock=8 [Done]
Cleaning the existing data in /dev/sdb2
Installing bootpartition_LS_arm64_lts_5.4.tgz to /dev/sdb2, waiting ...
Install bootpartition_LS_arm64_lts_5.4.tgz in /dev/sdb2 [Done]
Installing rootfs_lsdk2012_ubuntu_main_arm64.tgz to /dev/sdb0, waiting ...
tar: /mnt/sdb0: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

We did not format the SD card, because flex-installer did the splitting and formatting for us when we had LSDK 21.02.

[yipingwang]

The capacity of /dev/sdb is only 7 GB, it recommends you to split partitions as this 4P=128M:2G:64M:-1

Please try the follow command.

$flex-installer -i auto -m lx2160ardb_rev2 4P=128M:2G:64M:-1 -d /dev/sdb

[m_kei]

I tried to flush LSDK2012 firmware, rootfs, and boot using LSDK2108 flex-installer because LSDK2012 flex-installer does not flush, but I always get an error. LSDK2012 and LSDK2108 always give a no space error, as if the partitions are different. Since we changed the SD card from 8GB to 64GB, it is not possible that the overall capacity is insufficient.

Partitioning /dev/sdc ...
Formatting partitions ...
/dev/sdc1 contains a ext4 file system labelled 'misc'
last mounted on Tue Mar 22 19:07:33 2022
/dev/sdc2 contains a ext4 file system labelled 'boot'
last mounted on /mnt/sdc2 on Tue Mar 22 19:07:34 2022
/dev/sdc3 contains a ext4 file system labelled 'data3'
last mounted on Tue Mar 22 19:07:35 2022
/dev/sdc4 contains a ext4 file system labelled 'data4'
last mounted on Tue Mar 22 19:07:36 2022
Model: USB Mass Storage Device (scsi)
Disk /dev/sdc: 61.9GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 71.3MB 138MB 67.1MB primary ext4
2 139MB 1398MB 1258MB primary ext4
3 1399MB 1533MB 134MB primary ext4
4 1534MB 61.9GB 60.4GB primary ext4

partition and format /dev/sdc [Done]
/dev/sdc1: 9161
/dev/sdc2: 9235
/dev/sdc3: 9236
51296+1 records in
51296+1 records out
52527324 bytes (53 MB, 50 MiB) copied, 18.0154 s, 2.9 MB/s
Program firmware_lx2160ardb_rev2_uboot_sdboot.img into /dev/sdc with offset 4K [Done]
Installing bootpartition_LS_arm64_lts_5.4.tgz to /dev/sdc2 ...
tar: secboot_hdrs/lx2160ardb/secboot_hdrs_xspiboot.bin: Wrote only 6144 of 10240 bytes
tar: secboot_hdrs/lx2160ardb/secboot_hdrs_sdboot.bin: Cannot write: No space left on device
tar: secboot_hdrs/lx2160ardb/hdr_dtb.out: Cannot write: No space left on device
tar: secboot_hdrs/lx2160ardb/hdr_linux.out: Cannot write: No space left on device
tar: secboot_hdrs/lx2160ardb/hdr_lx2160ardb_bs.out: Cannot write: No space left on device
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy/hdr_ls1046afrwy_bs.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy/secboot_hdrs_qspiboot.bin: Cannot open: No such file or directory
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy/secboot_hdrs_sdboot.bin: Cannot open: No such file or directory
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy/hdr_dtb.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls1046afrwy: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1046afrwy/hdr_linux.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb/hdr_ls2088ardb_bs.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb/secboot_hdrs_qspiboot.bin: Cannot open: No such file or directory
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb/secboot_hdrs_norboot.bin: Cannot open: No such file or directory
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb/hdr_dtb.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls2088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls2088ardb/hdr_linux.out: Cannot open: No such file or directory
tar: secboot_hdrs/ls1088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1088ardb: Cannot mkdir: No space left on device
tar: secboot_hdrs/ls1088ardb/secboot_hdrs_qspiboot.bin: Cannot open: No such file or directory
tar: secboot_hdrs/ls1088ardb/secboot_hdrs_sdboot.bin: Wrote only 3584 of 10240 bytes
tar: tools/perf: Wrote only 1024 of 10240 bytes
tar: vmlinuz-5.4.47: Wrote only 1536 of 10240 bytes
tar: Exiting with failure status due to previous errors

[yipingwang]

What's the output when use the following command in LSDK 21.08?

$ flex-installer -i auto -m lx2160ardb_rev2 -d /dev/sdc

[m_kei]

/dev/sdb: 7 GB
The capacity of /dev/sdb is only 7 GB, using partitions: 4P=128M:2G:64M:-1
firmware_lx2160ardb_rev2_uboot_sdboot.img already exists
bootpartition_LS_arm64_lts_5.4.tgz already exists
rootfs_lsdk2012_ubuntu_main_arm64.tgz already exists
Downloaded distro images [Done]
102592+1 records in
102592+1 records out
52527324 bytes (53 MB, 50 MiB) copied, 16.51 s, 3.2 MB/s
Program firmware_lx2160ardb_rev2_uboot_sdboot.img into /dev/sdb startblock=8 [Done]
Cleaning the existing data in /dev/sdb2
Installing bootpartition_LS_arm64_lts_5.4.tgz to /dev/sdb2, waiting ...
Install bootpartition_LS_arm64_lts_5.4.tgz in /dev/sdb2 [Done]
Installing rootfs_lsdk2012_ubuntu_main_arm64.tgz to /dev/sdb0, waiting ...
tar: /mnt/sdb0: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now

The problem will not be solved. To begin with, LSDK2012 does not perform partitioning.

Does LSDK2012 require me to create my own partitions, i.e., sdx1 to sdx4, in advance?