I'm trying to install (flash) linux os into k2L EVM.(v1.0.3.0)
I'm using following processor sdk pakage, ti-processor-sdk-linux-k2l-evm-03.00.00.04-Linux-x86-Install.bin (at software-dl.ti.com/.../index_FDS.html)
I followed following steps
u-boot# env default -a
u-boot# setenv ipaddr 10.100.1.10
u-boot# setenv serverip 10.100.1.40
u-boot# setenv tftp_root processor_sdk
u-boot# run get_ubi_net
u-boot# run burn_ubi
u-boot# setenv boot ubi
u-boot# saveenv
u-boot# reset
but when it is booting it gives me following:
K2L EVM # reset
resetting ...
U-Boot SPL 2013.01 (Aug 05 2014 - 12:55:40)
SF: Detected N25Q128A with page size 64 KiB, total 16 MiB
U-Boot 2013.01 (Aug 05 2014 - 12:55:40)
I2C: ready
DRAM: 2 GiB
Reseting entire DDR3 memory to 0 ...
DRAM: 2 GiB
NAND: 2048 MiB
Net: K2L_EMAC0, K2L_EMAC1, K2L_EMAC2, K2L_EMAC3
Hit any key to stop autoboot: 0
Creating 1 MTD partitions on "nand0":
0x000000180000-0x000080000000 : "mtd=2"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size: 262144 bytes (256 KiB)
UBI: logical eraseblock size: 253952 bytes
UBI: smallest flash I/O unit: 4096
UBI: VID header offset: 4096 (aligned 4096)
UBI: data offset: 8192
UBI: volume 0 ("boot") re-sized from 1549 to 8097 LEBs
UBI: attached mtd1 to ubi0
UBI: MTD device name: "mtd=2"
UBI: MTD device size: 2046 MiB
UBI: number of good PEBs: 8182
UBI: number of bad PEBs: 4
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: 8182
UBI: number of PEBs reserved for bad PEB handling: 81
UBI: max/mean erase counter: 1/0
UBIFS: mounted UBI device 0, volume 0, name "boot"
UBIFS: mounted read-only
UBIFS: file system size: 2053709824 bytes (2005576 KiB, 1958 MiB, 8087 LEBs)
UBIFS: journal size: 9404416 bytes (9184 KiB, 8 MiB, 38 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: zlib
UBIFS: reserved for root: 0 bytes (0 KiB)
securedb.key.bin not found!
ubifsload - load file from an UBIFS filesystem
Usage:
ubifsload <addr> <filename> [bytes]
- load file 'filename' to address 'addr'
1) why it gives an error "securedb.key.bin not found! "?
this error occurs when executing; ubifsload ${addr_secdb_key} securedb.key.bin;
where addr_secdb_key =0xc000000 (these are defined as "env")
(init_ubi=run set_fs_none args_all args_ubi; ubi part ubifs; ubifsmount boot;ubifsload ${addr_secdb_key} securedb.key.bin;)
2) Is there anything wrong with this procedure?
