I've successfully installed a Yocto Image on NAND from an SD using a Variscite evaluation board with an i.MX6 SOLO SOM
Now I'm trying to perform the same action from my custom board but, although I'm not seeing any error during the flash process, it fails to boot.
These are the steps followed to flash the bootloader:
./flash_erase /dev/mtd0 0 0
./kobs-ng init -x $MEDIA/$SPL_IMAGE --search_exponent=1 -v
./flash_erase /dev/mtd1 0 0 2
./nandwrite -p /dev/mtd1 $MEDIA/$UBOOT_IMAGE
While these are the steps for the kernel
./flash_erase /dev/mtd2 0 0 2> /dev/null
./nandwrite -p /dev/mtd2 $MEDIA/$KERNEL_IMAGE > /dev/null
./nandwrite -p /dev/mtd1 -s 0x1e0000 $MEDIA/$KERNEL_DTB > /dev/null
Where:
MEDIA=/opt/images/Yocto
SPL_IMAGE=SPL-nand
UBOOT_IMAGE=u-boot.img-nand
KERNEL_IMAGE=uImage
KERNEL_DTB=imx6dl-var-som-solo.dtb
The only difference I can appreciate executing these commands is running kobs-ng -version 1.3-
Notice the following differences:
| Property | Evaluation board | Custom board |
|---|
| ECC Strength | 8 | 4 |
| Page Size in Bytes | 2110 | 2084 |
| Block Mark Byte Offset | 1999 | 2018 |
| Block Mark Bit Offset | 0 | 4 |
| m_u32EccBlockNEccType | 4 | 2 |
| m_u32EccBlock0EccType | 4 | 2 |
| m_u32BadBlockMarkerByte | 1999 | 2018 |
| m_u32BadBlockMarkerStartBit | 0 | 4 |
Why are these properties different if SOM is the same? Both, binaries and executables are the same aswell
Could these differences causes the issue?
FYI Running cat /proc/cpuinfo gets the same result in both boards
processor : 0
model name : ARMv7 Processor rev 10 (v7l)
BogoMIPS : 3.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpd32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc09
CPU revision : 10
Hardware : Freescale i.MX6 Quad/DualLite (Device Tree)
Revision : 0000
Serial : 0000000000000000
As a first approach I could cross-compile latest kobs from here but I duno if somebody else faced this problem.
I've also read about this issue but it seems it's not the same problem.
Thks in advance
