Creating custom Android 9 image for EDM1-IMX6Q

cancel
Showing results for 
Search instead for 
Did you mean: 

Creating custom Android 9 image for EDM1-IMX6Q

75 Views
Contributor I

I downloaded the code from git and compiled it with "cook -j4" without any errors.
After that I used the command gen_virtual_images which created a 3.6GB test.img file .
I moved it to a bootable SDCard and on power on it reboots in a loop. I need to know more about gen_virtual_images as there is no documentation about the same . When I use this u-boot.imx is not created. Could that be the reason behind the problem as all other files mentioned for EDM1-IMX6Q are generated .

I get the following message :

U-Boot SPL 2018.03-ga5a39eea7f (Sep 29 2020 - 20:39:29 +0530)
Trying to boot from MMC1


U-Boot 2018.03-ga5a39eea7f (Sep 29 2020 - 20:39:29 +0530)

CPU: Freescale i.MX6Q rev1.3 996 MHz (running at 792 MHz)
CPU: Extended Commercial temperature grade (-20C to 105C) at 30C
Reset cause: POR
SOM: imx6q-edm1
Available EDM1 baseboard: Fairy, Gnome, TC0700
I2C: ready
DRAM: 2 GiB
PMIC: PFUZE100 ID=0x10
MMC: FSL_SDHC: 0, FSL_SDHC: 1
No panel detected: default to hj070na
Display: hj070na (1024x600)
In: serial
Out: serial
Err: serial
SOM: imx6q-edm1
Available EDM1 baseboard: Fairy, Gnome, TC0700
flash target is MMC:0
Net: FEC [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
RNG instantiation done (3600)
RNG already instantiated 0x40000003
verify OK, boot 'boot'
kernel @ 14008000 (10315592)
ramdisk @ 15000000 (1835188)
fdt @ 14f00000 (52563)
## Booting Android Image at 0x14007800 ...
Kernel load addr 0x14008000 size 10074 KiB
## Flattened Device Tree blob at 14f00000
Booting using the fdt blob at 0x14f00000
XIP Kernel Image ... OK
Using Device Tree in place at 14f00000, end 14f0fd52

Starting kernel ...

imx6q-pcie 1ffc000.pcie: phy link never came up
imx6q-pcie 1ffc000.pcie: failed to initialize host
imx6q-pcie 1ffc000.pcie: unable to add pcie port.
mxc_sdc_fb fb@1: Can't get fb option for mxcfb1!
edt_ft5x06 1-0038: touchscreen probe failed
ov5645_read_reg:write reg error:reg=300a
init: bool android::init::FirstStageMount::InitRequiredDevices(): partition(s) not found after polling timeout: boot, system, vbmeta, vendor
init: Failed to mount required partitions early ...
reboot: Restarting system with command 'bootloader'

 

0 Kudos
2 Replies

65 Views
NXP TechSupport
NXP TechSupport

I recommend you that you contact the board supplier, since the Android BSP can be build in different ways, you can review the method, that we use in NXP boards, and the documentation on how to boot a NXP board with an Android Image, we use our tool named UUU,

 

Here you can find the details

 

https://www.nxp.com/design/software/embedded-software/i-mx-software/android-os-for-i-mx-applications...

 

0 Kudos

59 Views
Contributor I

Thank You for the reply.

I am not getting any great help from my supplier so I thought of raising my queries in the community.
It would be of great help if you could resolve my query.
Can you please verify that the file u-boot.imx not generated after compiling Android 9.0 could be the issue ?

Also I am using the board EDM1-IMX6Q-10-R20-E16-9377  with Fairy and Android version tn-p9.0.0_2.2.0-ga .
Is this Android version compatible with EDM1-IMX6Q ?

0 Kudos