Tool/software: Linux
Hi,
We have an customed Am437x-gp-evm board, It is work well now with Mr. Kemal support. As the ubi filesystem in NAND is too large, it occupies almost all the NAND space, our qt-Application cann't be put into the NAND.We plan to put filesystem into RAM and config kernel menuconfig:General setup->Initial RAM filesystem and RAM disk (initramfs/initrd) support(Am437x/rootfs)Initramfs source file(s) . We get the zImage and transfer it to NAND. it cann't work, I attach the reset log in attachment.
All the images transfer to NAND are:
NAND erase.chip
1)tftpboot 0x82000000 MLO
nand write 0x82000000 NAND.SPL
nand write 0x82000000 NAND.SPL.backup1
nand write 0x82000000 NAND.SPL.backup2
nand write 0x82000000 NAND.SPL.backup3
2)tftpboot 0x82000000 u-boot.img
nand write 0x82000000 NAND.u-boot
3)tftpboot 0x82000000 zImage
(bytes transferred = 97051136)
nand write 0x82000000 NAND.kernel
(NAND write:device 0 offset 0x300000,size 0x700000 7340032 bytes written: OK)
4)tftpboot 0x82000000 am437x-gp-evm.dtb
nand write 0x82000000 NAND.u-boot-spl-os
We find the new zImage size is 97051136 bytes, but only writted 7340032 bytes to NAND.
We want to know How to modify the u-boot (written size ) and our plan is practicable. Is there any recommended way to implement RAM filesystem with remain more NAND space for application?
Best Regards!
U-Boot SPL 2018.01-00444-ge782a78ca9-dirty (Feb 16 2019 - 10:11:27) Trying to boot from NAND SPL: Please implement spl_start_uboot() for your board SPL: Direct Linux boot not active! U-Boot 2018.01-00444-ge782a78ca9-dirty (Feb 16 2019 - 10:11:27 +0800) CPU : AM437X-GP rev 1.2 Model: TI AM437x GP EVM DRAM: 1 GiB PMIC: TPS65218 NAND: 512 MiB MMC: OMAP SD/MMC: 0 Net: cpsw, usb_ether Hit any key to stop autoboot: 0 MMC: no card present MMC: no card present MMC: no card present MMC: no card present starting USB... USB0: Register 2000440 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Device 0: device type unknown ... is now current device MMC: no card present ** Bad device mmc 0 ** ** Bad device usb 0 ** Booting from nand ... NAND read: device 0 offset 0x100000, size 0x80000 524288 bytes read: OK NAND read: device 0 offset 0x300000, size 0x700000 7340032 bytes read: OK ## Flattened Device Tree blob at 88000000 Booting using the fdt blob at 0x88000000 Loading Device Tree to 8fff0000, end 8ffffe54 ... OK Starting kernel ...