Dear F&S,
we purchased the armstone A5 Starter Kit. I've created a rootfs image using buildroot and tried to load it following the guide Vibrid Linux First Steps starting at section 4.4 Load and Save Root File System. Unfortunately
command ubi create rootfs fails. What did I miss? Here is my log:
Code
- armStoneA5 # tftp rootfs.ubifs
- Using FEC1 device
- TFTP from server 192.168.101.42; our IP address is 192.168.101.30
- Filename 'rootfs.ubifs'.
- Load address: 0x80800000
- Loading: TX timeout
- TX timeout
- TX not ready
- TX timeout
- TX not ready
- TX timeout
- ARP Retry count exceeded; starting again
- Using FEC0 device
- TFTP from server 192.168.101.42; our IP address is 192.168.101.30
- Filename 'rootfs.ubifs'.
- Load address: 0x80800000
- Loading: #####################...###########
- done
- Bytes transferred = 30062592 (0x1cab800)
- armStoneA5 # ubi part TargetFS
- Creating 1 MTD partitions on "nand0":
- 0x000000800000-0x000008000000 : "mtd=6"
- UBI: attaching mtd1 to ubi0
- UBI: physical eraseblock size: 131072 bytes (128 KiB)
- UBI: logical eraseblock size: 129024 bytes
- UBI: smallest flash I/O unit: 2048
- UBI: sub-page size: 512
- UBI: VID header offset: 512 (aligned 512)
- UBI: data offset: 2048
- UBI: attached mtd1 to ubi0
- UBI: MTD device name: "mtd=6"
- UBI: MTD device size: 120 MiB
- UBI: number of good PEBs: 960
- UBI: number of bad PEBs: 0
- UBI: max. allowed volumes: 128
- UBI: wear-leveling threshold: 4096
- UBI: number of internal volumes: 1
- UBI: number of user volumes: 1
- UBI: available PEBs: 0
- UBI: total number of reserved PEBs: 960
- UBI: number of PEBs reserved for bad PEB handling: 9
- UBI: max/mean erase counter: 4/1
- armStoneA5 # ubi create rootfs
- No size specified -> Using max size (0)
- No space left in UBI device!
- verify_mkvol_req failed 12