I'm using MYS-6ULY2-256N2. I built a mys6ull14x14 image, loaded it into the board. Boot won't go further the line "Normal boot", waiting for input. Here's a log:
U-Boot 2016.03-mys-6ulx+ga175019 (Aug 31 2021 - 00:42:41 -0700)
CPU: Freescale i.MX6ULL rev1.1 528 MHz (running at 396 MHz)
CPU: Industrial temperature grade (-40C to 115C) at 41C
Reset cause: POR
Board: MYS-MX6ULL 14x14
I2C: ready
DRAM: 256 MiB
NAND: 256 MiB
MMC: FSL_SDHC: 0
Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: FEC0
Normal Boot
And environment variables:
baudrate=115200
board_name=MYS6ULL
board_rev=14X14
bootargs=console=ttymxc0,115200 ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs mtdparts=gpmi-nand:5m(boot),1m(env),8m(kernel),2m(dtb),160m(rootfs1),-(userdata)
bootcmd_mfg=run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};
bootdelay=3
console=ttymxc0
envflag=1
ethact=FEC0
ethaddr=f4:4d:30:53:40:11
ethprime=FEC
fdt_addr=0x83000000
fdt_high=0xffffffff
initrd_addr=0x83800000
initrd_high=0xffffffff
loadaddr=0x80800000
mfgtool_args=setenv bootargs console=${console},${baudrate} rdinit=/linuxrc g_mass_storage.stall=0 g_mass_storage.removable=1 g_mass_storage.file=/fat g_mass_storage.ro=1 g_mass_storage.idVendor=0x066F g_mass_storage.idProduct=0x37FF g_mass_storage.iSerialNumber="" mtdparts=5m(boot),1m(env),8m(kernel),2m(dtb),160m(rootfs1),-(userdata) clk_ignore_unused
mtdids=nand0=gpmi-nand
nand_erasesize=20000
nand_oobsize=40
nand_writesize=800
panel=TFT43AB
partition=nand0,0
Environment size: 993/1048572 bytes
已解决! 转到解答。
I manually wrote those commands from boot.scr in the terminal and kernel has been loaded:
setenv mmcroot '/dev/mmcblk0p2 rootwait rw rootdelay=5 mem=256M'
setenv mmcargs 'setenv bootargs console=${console},${baudrate} \ root=${mmcroot} mtdparts=gpmi-nand:5m(boot),10m(kernel),\ 1m(dtb),-(rootfs)'
run mmcargs
fatload mmc 0 0x83000000 zImage
fatload mmc 0 0x84000000 mys-imx6ull-14x14-evk-emmc.dtb
bootz 0x83000000 - 0x84000000
But why does it work that way? According to the guide, boot.scr is necessary for eMMC, not NAND.
Hi
one can try to decrease cma size, "linux,cma" in dts
also recommended to debug it using AN4553 Using Open Source Debugging Tools
for Linux on i.MX Processors
https://www.nxp.com/docs/en/application-note/AN4553.pdf
Best regards
igor
suggest to apply for support to vendor of MYS-6ULY2-256N2 board:
http://www.myirtech.com/support.asp
Best regards
igor
I manually wrote those commands from boot.scr in the terminal and kernel has been loaded:
setenv mmcroot '/dev/mmcblk0p2 rootwait rw rootdelay=5 mem=256M'
setenv mmcargs 'setenv bootargs console=${console},${baudrate} \ root=${mmcroot} mtdparts=gpmi-nand:5m(boot),10m(kernel),\ 1m(dtb),-(rootfs)'
run mmcargs
fatload mmc 0 0x83000000 zImage
fatload mmc 0 0x84000000 mys-imx6ull-14x14-evk-emmc.dtb
bootz 0x83000000 - 0x84000000
But why does it work that way? According to the guide, boot.scr is necessary for eMMC, not NAND.
I set cma size to <0x10000000>, but it hasn't affected booting.
I contacted the vendor tech support, they run my image without a problem. I attached their log.
Could I burn the image in a wrong way? I tried Win32DiskImager on Windows and dd command on Ubuntu (to be precise, sudo dd if=core-image-base-mys6ull14x14.rootfs.sdcard of=/dev/sdb1 bs=4M), but result is always the same.