@tevet 前几天解决了，谢谢回复
C
Latest posts made by casojie
-
Reply: d1s下的overlays挂载问题，提示“No such device”posted in D1-H/D1s
@suncw 抱歉，我还是不明白，我的设备是emmc存储，mkfs.ext4 在板子上是可以正常使用的，看完后我还是不知道应该怎么做，而且我使用的是busybox-init 对应的以下fsata文件都没有
-
Reply: d1s下的overlays挂载问题，提示“No such device”posted in D1-H/D1s
@suncw 我不是很明白，根目录下是有overlay文件夹的，它应该不需要创建文件夹了吧，而我也尝试手动挂载，也是提示
root@TinaLinux:/# mount -t ext4 -o sync,data=journal /dev/by-name/rootfs_data /o verlay/ mount: mounting /dev/by-name/rootfs_data on /overlay/ failed: No such device我也尝试执行
root@TinaLinux:/# mkfs.ext4 /dev/by-name/rootfs_data mke2fs 1.46.4 (18-Aug-2021) /dev/by-name/rootfs_data contains a ext4 file system created on Thu Jan 1 08:07:28 1970 Proceed anyway? (y,N) y Discarding device blocks: done Creating filesystem with 5120 1k blocks and 1280 inodes Allocating group tables: done Writing inode tables: done Creating journal (1024 blocks): done Writing superblocks and filesystem accounting information: done仍然不行，唉
-
d1s下的overlays挂载问题，提示“No such device”posted in D1-H/D1s
D1S 无法挂载overlays，开机打印如下
Starting kernel ... [01.717][mmc]: mmc exit start [01.736][mmc]: mmc 2 exit ok mount: mounting none on /dev failed: Device or resource busy mount: mounting /dev/by-name/rootfs_data on /overlay failed: No such device Mount Failed: formating /dev/by-name/rootfs_data to ext4 ... mke2fs 1.46.4 (18-Aug-2021) mount: mounting /dev/by-name/rootfs_data on /overlay failed: No such device Didn't found ubi volume "env" Cannot open /dev/ubi0: No such file or directory Didn't found ubi volume "env-redund" Cannot open /dev/ubi0: No such file or directory mkdir: can't create directory '/overlay/upper': Read-only file system mkdir: can't create directory '/overlay/workdir': Read-only file system mount: mounting overlayfs:/overlay on /mnt failed: No such file or directory mount: mounting /proc on /mnt/proc failed: No such file or directory pivot_root: No such file or directory mount: mounting /rom/dev on /dev failed: No such file or directory mount: mounting /rom/tmp on /tmp failed: No such file or directory mount: mounting /rom/sys on /sys failed: No such file or directory mount: mounting /rom/overlay on /overlay failed: No such file or directory can't run '/etc/preinit': No such file or directory mount: mounting proc on /proc failed: Device or resource busy mount: mounting tmpfs on /run failed: No such file or directory hostname: can't open '/etc/hostname': No such file or directory ------run rc.preboot file----- mke2fs 1.46.4 (18-Aug-2021) ------run rc.modules file----- ------run rc.final file----- ifconfig: SIOCGIFFLAGS: No such device sh: write error: No such device host_chose finished! nice: can't execute '/usr/bin/story_ota_bin': No such file or directory device_chose finished!在贴吧也搜索到类似的问题，都是修改base-file里的文件，但是我是使用的busybox-init, 都找不到对应的fstat文件，感觉分区设置好像有问题，太蔡了，求大哥指点，以下pack的log
jie.cao@umr940:~/f133A/f133$ pack --==========-- PACK_CHIP sun20iw1p1 PACK_PLATFORM tina PACK_BOARD f133-evb1 PACK_KERN PACK_DEBUG uart0 PACK_SIG none PACK_SECURE none PACK_MODE normal PACK_FUNC android PACK_PROGRAMMER none PACK_TAR_IMAGE none PACK_TOPDIR /homeB/jie.cao/f133A/f133 --==========-- No kernel param, parse it from f133 copying tools file copying configs file storage_type value is 2 rm /homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition_nor.fex rm /homeB/jie.cao/f133A/f133/out/f133-evb1/image/image_nor.cfg copying boot resource copying boot file make user resource for : /homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.fex handle partition user-res no user resource partitions APP_PART_DOWNLOAD_FILE = /homeB/jie.cao/f133A/f133/out/f133-evb1/image/app.fex Need size of filesystem no data resource partitions don't build dtbo ... update_chip sboot file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sboot.bin script file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_config.bin update:unable to open sboot file script update sboot ok pack boot package GetPrivateProfileSection read to end content_count=3 LICHEE_REDUNDANT_ENV_SIZE config in BoardConfig.mk --mkenvimage create redundant env data!-- ---redundant env data size 0x20000--- packing for tina linux normal mbr count = 4 partitation file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.bin mbr_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sunxi_mbr.fex download_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/dlinfo.fex mbr size = 16384 mbr magic softw411 disk name=boot-resource disk name=env disk name=env-redund disk name=boot disk name=rootfs disk name=recovery disk name=rootfs_data this is not a partition key update_for_part_info 0 crc 0 = 9632c2e2 crc 1 = 38f93bf crc 2 = 66396619 crc 3 = f3843744 gpt_head->header_crc32 = 0xac1db3f8 GPT----part num 8--- gpt_entry: 128 gpt_header: 92 GPT:boot-resource: 12000 121f7 GPT:env : 121f8 123ef GPT:env-redund : 123f0 125e7 GPT:boot : 125e8 157e7 GPT:rootfs : 157e8 229e7 GPT:recovery : 229e8 27767 GPT:rootfs_data : 27768 29f67 GPT:UDISK : 29f68 ffffffde update gpt file ok update mbr file ok temp = 20 mbr count = 4 total_sectors = 15269888 logic_offset = 40960 partitation file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sys_partition.bin mbr_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/sunxi_mbr.fex download_name file Path=/homeB/jie.cao/f133A/f133/out/f133-evb1/image/dlinfo.fex mbr size = 16384 mbr magic softw411 disk name=boot-resource disk name=env disk name=env-redund disk name=boot disk name=rootfs disk name=recovery disk name=rootfs_data this is not a partition key update_for_part_info 0 crc 0 = 9632c2e2 crc 1 = 38f93bf crc 2 = 66396619 crc 3 = f3843744 gpt_head->header_crc32 = 0x36191a6a GPT----part num 8--- gpt_entry: 128 gpt_header: 92 GPT:boot-resource: 12000 121f7 GPT:env : 121f8 123ef GPT:env-redund : 123f0 125e7 GPT:boot : 125e8 157e7 GPT:rootfs : 157e8 229e7 GPT:recovery : 229e8 27767 GPT:rootfs_data : 27768 29f67 GPT:UDISK : 29f68 e8ffde update gpt file ok update mbr file ok ==================================== show "sys_partition_for_dragon.fex" message ------------------------------------ [mbr] mbr_size : 16384 Kbyte ------------------------------------ partition_name : boot-resource partition_size : 504 downloadfile : boot-resource.fex boot-resource.fex size : 80K byte ------------------------------------ partition_name : env partition_size : 504 downloadfile : env.fex env.fex size : 128K byte ------------------------------------ partition_name : env-redund partition_size : 504 downloadfile : env.fex env.fex size : 128K byte ------------------------------------ partition_name : boot partition_size : 12800 downloadfile : boot.fex boot.fex -> /homeB/jie.cao/f133A/f133/out/f133-evb1/boot.img boot.img size : 5.8M byte ------------------------------------ partition_name : rootfs partition_size : 53760 downloadfile : rootfs.fex rootfs.fex -> /homeB/jie.cao/f133A/f133/out/f133-evb1/rootfs.img rootfs.img size : 16M byte ------------------------------------ partition_name : recovery partition_size : 19840 ------------------------------------ partition_name : rootfs_data partition_size : 10240 ------------------------------------ /homeB/jie.cao/f133A/f133/out/host/bin/ /homeB/jie.cao/f133A/f133/out/f133-evb1/image Begin Parse sys_partion.fex Add partion boot-resource.fex BOOT-RESOURCE_FEX Add partion very boot-resource.fex BOOT-RESOURCE_FEX FilePath: boot-resource.fex FileLength=14000Add partion env.fex ENV_FEX000000000 Add partion very env.fex ENV_FEX000000000 FilePath: env.fex FileLength=20000Add partion env.fex ENV_FEX000000000 Add partion very env.fex ENV_FEX000000000 FilePath: env.fex FileLength=20000Add partion boot.fex BOOT_FEX00000000 Add partion very boot.fex BOOT_FEX00000000 FilePath: boot.fex FileLength=5b4800Add partion rootfs.fex ROOTFS_FEX000000 Add partion very rootfs.fex ROOTFS_FEX000000 FilePath: rootfs.fex FileLength=fc0000BuildImg 0 Dragon execute image.cfg SUCCESS ! ----------image is for nand/emmc---------- ----------image is at---------- -
F133A烧录时大概率卡住失败posted in D1-H/D1s
背景：开始时使用F133B芯片，编译了镜像烧录，几乎没怎么遇到烧录失败的情况
现在做了一款新的PCB板子，贴的是F133A芯片，就大概率出现卡0%，卡10%，卡55%，卡70%，但也有大约10%的概率成功，据之前有个大哥说，代码软件层面上不用区分F133A和F133B，但是同样的镜像对F133B和F133A烧录情况不一致（当然PCB的电路也不一样），现在就不知道是我代码编译出的镜像有问题，还是后面的F133A电路硬件上有问题，请大佬指点，烧录卡住时的打印如下
10%tfs 5, d200, 8000 recovery 6, 4d80, 8000 rootfs_data 7, 2800, 8000 UDISK 8, 0, 0 [09.637]erase all part start need erase flash: 18 [09.643][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.678][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0x1c ms [09.685]read item0 copy0 [09.687]Item0 (Map) magic is bad [09.690]the secure storage item0 copy0 magic is bad [09.695]Item0 (Map) magic is bad [09.698]the secure storage item0 copy1 magic is bad [09.702]Item0 (Map) magic is bad [09.705]the secure storage map is empty [09.710]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.727]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init卡50%
common1(partition3) need it, here is a weak func total part: 9 mbr 0, 8000, 8000 boot-resource 1, 1f8, 8000 env 2, 1f8, 8000 env-redund 3, 1f8, 8000 boot 4, 3200, 8000 rootfs 5, d200, 8000 recovery 6, 4d80, 8000 rootfs_data 7, 2800, 8000 UDISK 8, 0, 0 [09.491]erase all part start need erase flash: 18 [09.497][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.513][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms [09.520]read item0 copy0 [09.522]Item0 (Map) magic is bad [09.525]the secure storage item0 copy0 magic is bad [09.530]Item0 (Map) magic is bad [09.533]the secure storage item0 copy1 magic is bad [09.537]Item0 (Map) magic is bad [09.540]the secure storage map is empty [09.545]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.562]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000 FEX_CMD_fes_verify_value 0xe6f75b5c FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0xa0bf6d78 FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0xa0bf6d78卡79%
DISK 8, 0, 0 [09.584]erase all part start need erase flash: 18 [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms [09.613]read item0 copy0 [09.615]Item0 (Map) magic is bad [09.618]the secure storage item0 copy0 magic is bad [09.623]Item0 (Map) magic is bad [09.626]the secure storage item0 copy1 magic is bad [09.630]Item0 (Map) magic is bad [09.633]the secure storage map is empty [09.638]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.655]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000 FEX_CMD_fes_verify_value 0xe6f75b5c FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000 FEX_CMD_fes_verify_value 0xd668265a -
Reply: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1posted in D1-H/D1s
@yteraa 也有卡10%的
common1(partition3) need it, here is a weak func total part: 9 mbr 0, 8000, 8000 boot-resource 1, 1f8, 8000 env 2, 1f8, 8000 env-redund 3, 1f8, 8000 boot 4, 3200, 8000 rootfs 5, 100000, 8000 recovery 6, 4d80, 8000 rootfs_data 7, 2800, 8000 UDISK 8, 0, 0 [09.694]erase all part start need erase flash: 18 [09.700][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.719][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xd ms [09.725]read item0 copy0 [09.728]Item0 (Map) magic is bad [09.731]the secure storage item0 copy0 magic is bad [09.736]Item0 (Map) magic is bad [09.738]the secure storage item0 copy1 magic is bad [09.743]Item0 (Map) magic is bad [09.746]the secure storage map is empty [09.751]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.768]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init -
Reply: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1posted in D1-H/D1s
@yteraa 也就是说，在编译时，都无需关心是A还是B是吗，现在遇到一个问题，原先的开发板F133B烧录正常，而同样的镜像到F133A大概率失败（也可能成功10%），F133A是我们做的另一款板子，现在不知道问题出在硬件上，还是镜像上
卡55%```bash common1(partition3) need it, here is a weak func total part: 9 mbr 0, 8000, 8000 boot-resource 1, 1f8, 8000 env 2, 1f8, 8000 env-redund 3, 1f8, 8000 boot 4, 3200, 8000 rootfs 5, 100000, 8000 recovery 6, 4d80, 8000 rootfs_data 7, 2800, 8000 UDISK 8, 0, 0 [09.584]erase all part start need erase flash: 18 [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms [09.613]read item0 copy0 [09.615]Item0 (Map) magic is bad [09.618]the secure storage item0 copy0 magic is bad [09.623]Item0 (Map) magic is bad [09.626]the secure storage item0 copy1 magic is bad [09.630]Item0 (Map) magic is bad [09.633]the secure storage map is empty [09.638]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.655]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000 FEX_CMD_fes_verify_value 0xe6f75b5c FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000 FEX_CMD_fes_verify_value 0xd668265a也有卡79%的
[09.584]erase all part start need erase flash: 18 [09.590][mmc]: erase from: 0, to: 7634943, cnt: 7634944, erase_group: 1024 [09.606][mmc]: sunxi_mmc_do_send_cmd_common: cmd 38 wait rsp busy 0xa ms [09.613]read item0 copy0 [09.615]Item0 (Map) magic is bad [09.618]the secure storage item0 copy0 magic is bad [09.623]Item0 (Map) magic is bad [09.626]the secure storage item0 copy1 magic is bad [09.630]Item0 (Map) magic is bad [09.633]the secure storage map is empty [09.638]erase secure storage: 0 ok SUNXI_EFEX_MBR_TAG mbr size = 0x10000 write primary GPT success write Backup GPT success [09.655]update partition map FEX_CMD_fes_verify_status FEX_CMD_fes_verify last err=0 ******Has init FEX_CMD_fes_verify_value, start 0x8000, size high 0x0:low 0x14000 FEX_CMD_fes_verify_value 0xe6f75b5c FEX_CMD_fes_verify_value, start 0x81f8, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x83f0, size high 0x0:low 0x20000 FEX_CMD_fes_verify_value 0x882de1bc FEX_CMD_fes_verify_value, start 0x85e8, size high 0x0:low 0x5fc000 FEX_CMD_fes_verify_value 0xd668265a -
Reply: 哪吒开发板D1编译报错Cannot find lib ld-linux-riscv64-lp64.so.1posted in D1-H/D1s
@whycan 抱歉，我在论坛和资料网站上没有找到相关的芯片区别表，F133就是D1-S是吗，F133还区分F133-A/B我是F133B
而且D1-H和D1-S（F133A/B）都是公用一份SDK的话，如果我想编译F133B
1. d1-h_nezha_min-tina
2. d1-h_nezha-tina
3. d1s_nezha-tina
下面我就该选择3是吗 SDK上我不用区分A与B吗？