[SOLVED] Booting Linux from eMMC (A62 SBC-A62-J-QUAD)

I am new to iMX6 based boards. I have just began to use the A62 SBC-A62-J-QUAD since few days.
I am trying to follow the wiki described by Seco at the link: http://wikitech.seco.com/index.php/BSP_5.0_Flashing_eMMC to restore
This seems to be generic and applicable to wide a range of iMX6 boards.

Is it possible to get a specific URL where to download the files to use:
zImage (which is the one to use?)
uboot.imx (which one among the ones listed in http://imx6-binary.seco.com/U-BOOT/?)
dtb file (which is the one to use?)
Is any bootargs file required to make the boot process working on SBC-A62-J-QUAD?

Is the eMMC partitioning described in the wiki valid for SBC-A62-J-QUAD?

Is there any need to flash code on /dev/mmcblk0boot0 partition?

Thanks in advance for your help!

 

For your first question, read the first line under overview (http://wikitech.seco.com/index.php/BSP_5.0_Flashing_eMMC) ... and for the bootargs, you need to be connected with the serial debugger on the card and stop the boot at u-boot stage (like bios in standard pc), at this step you can use different option ...

 

Thanks for the hints. I was suspecting that the serial cable was required to modify the bootargs.

Regarding the bootloader to use, what is the correct one to select in the BSP 5.0?
I see three options:
u-boot-a62-QD-2GB-2014.imx 04-Feb-2017 01:35 299K
u-boot-a62-QD-256MBx4-2014.imx 04-Feb-2017 01:35 299K
u-boot-a62-QD-512MB-2014.imx 04-Feb-2017 01:35 299K

What is dtb file to use? This seems not included in the assets of http://imx6-binary.seco.com/

 

Ask seco for that, i didn't use their image, i use yocto ...

 

Issue solved!

The filesystem image I have used to prepare the eMMC partitions was derived by the a62_q_udoobuntu2 image, downloadable at the page: http://www.udoo.org/bsp-download-page/ (UDOObuntu 2 FOR QUAD).

I have solved the issue following the detailed instructions posted by ddewaele at the forum page:http://www.udoo.org/forum/threads/from-udoo-quad-to-sa62.3391/ (thanks ddewaele!)
I am going to post there additional findings seen during the experiments.

It was key to use a UART console to set-up the U-Boot environment variables as described by ddwaele in the forum page. The onboard eMMC is not getting enumerated as /dev/mmcblk0, but as /dev/mmcblk3.