AnsweredAssumed Answered

i.MX6 bring up custom board issue. CPU type changed during designing custom board.

Question asked by kiwon yang on Apr 30, 2019
Latest reply on Apr 30, 2019 by igorpadykov

Hello, 

We bought a imx6qp-sabresd board and tested for designing custom board.

When we were designing custom board, most circuit designs are base on imx6qp-sabresd board, but there are some differences

 

Differences:

1. First, we changed CPU; IMX6QP(part No.:MCIMX6QP6AVT1AA)   to   IMX6 Solo(part No.:MCIMX6S7CVM08AC).

   => Since we changes CPU IMX6QP to IMX6SOLO, we are applying dtb and config with MX6dl files on our custom board. Does it matter using iMX6SOLO CPU and iMX6dl files on our custom board that is designed base on imx6qp-sabresd board. Would it make some problems because they might have different CPU blocks, etc? We thought that iMX6SOLO and iMX6QP have same pin assignment and block so that will okay...

 

2. Reference board-imx6qp-sabresd have 4 DDR-RAM, but we are using 2 DDR-RAM.

   => We changed some ddr address values for reducing 4-RAM to 2-RAM. We had finished DDR-RAM stress test successfully.

 

3. Using difference eMMC.

   => Not porting yet.

 

Progress: <bring up custom board issue>

We are using mfgtools for uploading u-boot.imx, zImage, and imx6dl-sabresd.dtb. When upload these files mfgtools stop after jumping to OS image. It look downloading files to RAM is fine, maybe emmc porting makes stop at that point.

 

However, When is booting up, it is booting only u-boot up. Kernel stops at before Starting kernel log. We tried modifying imx6dl_sabresd.dts, imx6qdl.dtsi, uboot&kernel code etc...couldn't find yet.. So now we assume that  using iMX6SOLO CPU on board that designed based on imx6qp-sabresd makes issue..??

How can I solve bring up problems?

 

Please reply any informations!

----------------------------------------------------------------------------------------------------------------------------------
U-Boot 2018.03-ga05e66c-dirty (Apr 30 2019 - 11:14:10 +0900)

CPU: Freescale i.MX6SOLO rev1.3 at 792MHz
CPU: Industrial temperature grade (-40C to 105C) at 52C
Reset cause: POR
Model: Freescale i.MX6 DualLite SABRE Smart Device Board
Board: MX6-SabreSD
DRAM: 512 MiB
PMIC: PFUZE100! DEV_ID=0x10 REV_ID=0x21
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environment

Failed (-5)
No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In: serial
Out: serial
Err: serial
Card did not respond to voltage select!
Net: No ethernet found.
Fastboot: Normal
Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;if iminfo ${initrd_addr}; then if test ${tee} = yes; then bootm ${tee_addr} ${initrd_addr} ${fdt_addr}; else bootz ${loadaddr} ${initrd_addr} ${fdt_addr}; fi; else echo "Run fastboot ..."; fastboot 0; fi;
Hit any key to stop autoboot: 0

## Checking Image at 12c00000 ...
Legacy image found
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 9054538 Bytes = 8.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Kernel image @ 0x12000000 [ 0x000000 - 0x70c170 ]
## Loading init Ramdisk from Legacy Image at 12c00000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 9054538 Bytes = 8.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800c371

 

---------------------------hang------------------------------------

Outcomes