android_M6.0.1_2.1.0 boot failure

blackhuang · ‎06-27-2019

Dear nxp fae:

我在使用I.MX6Q是出现以下问题;

系统使用的是android_M6.0.1_2.1.0。下载工具使用的是android_m6.0.1_2.1.0_ga_tool。

板子上使用官方参考的pmic,仅仅是修该了i2c.

uboot:

.scl = {
  .i2c_mode = MX6_PAD_EIM_EB2__I2C2_SCL | I2C_PAD, /*change KEY_COL3   QSHK*/
  .gpio_mode = MX6_PAD_EIM_EB2__GPIO2_IO30 | I2C_PAD,
  .gp = IMX_GPIO_NR(2, 30)
},
.sda = {
  .i2c_mode = MX6_PAD_EIM_D16__I2C2_SDA | I2C_PAD, /*change KEY_ROW3   QSHK*/
  .gpio_mode = MX6_PAD_EIM_D16__GPIO3_IO16 | I2C_PAD,
  .gp = IMX_GPIO_NR(3, 16)
}

//        .scl = {
//                .i2c_mode = MX6_PAD_KEY_COL3__I2C2_SCL | I2C_PAD,
//                .gpio_mode = MX6_PAD_KEY_COL3__GPIO4_IO12 | I2C_PAD,
//                .gp = IMX_GPIO_NR(4, 12)
//        },
//        .sda = {
//                .i2c_mode = MX6_PAD_KEY_ROW3__I2C2_SDA | I2C_PAD,
//               .gpio_mode = MX6_PAD_KEY_ROW3__GPIO4_IO13 | I2C_PAD,
//                .gp = IMX_GPIO_NR(4, 13)
//       }

kernel:

fsl,pins = <
    MX6QDL_PAD_EIM_EB2__I2C2_SCL  0x4001b8b1
    MX6QDL_PAD_EIM_D16__I2C2_SDA  0x4001b8b1
   >;
  };

//  pinctrl_i2c2: i2c2grp {
//   fsl,pins = <
//    MX6QDL_PAD_KEY_COL3__I2C2_SCL  0x4001b8b1
//    MX6QDL_PAD_KEY_ROW3__I2C2_SDA  0x4001b8b1
//   >;
//  };

我已将镜像dd到SD卡中启动。出现binder: 192:192 transaction failed 29189, size 0-0。

设置setenv bootargs console=ttymxc0,115200 init=/init video=mxcfb0:dev=lcd, CLAA-WVGA,if= RGB565,bpp=32 video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off vmalloc=256M androidboot.console=ttymxc0 consoleblank=0 androidboot.hardware=freescale cma=384M androidboot.selinux=disabled androidboot.dm_verity=disabled

又出现如下问题：

init: write_file: Unable to write to '/sys/power/state': Invalid argument
init: Service 'media' is being killed...
init: Service 'netd' is being killed...
init: Service 'media' (pid 3559) killed by signal 9
init: Service 'media' (pid 3559) killing any children in process group
init: Service 'netd' (pid 3558) killed by signal 9
init: Service 'netd' (pid 3558) killing any children in process group
init: Starting service 'surfaceflinger'...
init: Service 'surfaceflinger' (pid 3776) killed by signal 11
init: Service 'surfaceflinger' (pid 3776) killing any children in process group
init: Starting service 'netd'...
init: Starting service 'media'...
init: Starting service 'zygote'...
init: Service 'zygote' (pid 3780) killed by signal 11
init: Service 'zygote' (pid 3780) killing any children in process group
init: write_file: Unable to open '/sys/android_power/request_state': No such file or directory

我的核心版跟官方开发板主要区别在gpio口的使用上。

上述现象都是用过dd到sd卡上启动出现的问题。

我尝试用MFG下载到核心板上的emmc。又出现新的问题如下

U-Boot 2015.04-imx_v2015.04_4.1.15_1.0.0_ga+g384e1c1 (Mar 13 2016 - 17:31:03)

CPU:   Freescale i.MX6Q rev1.5 at 792 MHz
CPU:   Temperature 23 C
Reset cause: POR
Board: MX6-SabreSD
I2C:   ready
DRAM: 1 GiB
Can't find PMIC:PFUZE100
initcall sequence 4ff933d8 failed at call 17803708 (err=-19)
### ERROR ### Please RESET the board ###

已将生成的文件放在android_m6.0.1_2.1.0_ga_tool\mfgtools\Profiles\Linux\OS Firmware\files\android\sabresd下

问题1：核心板上的i2c修改了，MFG内的相关文件是否也要修改？

问题2：已将androidboot.selinux=disabled androidboot.dm_verity=disabled，主要有啥引起init: Service 'media' is being killed...init: Service 'netd' is being killed...init: Service 'media' (pid 3559) killed by signal 9 ？？？？

附件是启动logo

非常希望能够尽快得到您们的回复，对于您们的回复将不胜感激！！！！

weidong_sun · ‎06-30-2019

Hello black,

抱歉，回复晚了一些！请看一下建议：

问题1：核心板上的i2c修改了，MFG内的相关文件是否也要修改？

MFG TOOLS有一个OS Firmware目录，这里有MFG TOOLS用的u-boot/xxx.dtb/kernel/rootfs，CPU ROM CODE会根据MFG TOOLS的LIST中的命令，把这4个文件下载到DDR3里，然后运行起来，把指定路径的工作u-boot/dtb/kernel/rootfs烧写进SD卡或者EMMC等。所以，OS Firmware下的4个文件也需要针对你的板子编译出来，放到这个目录。如果你替换掉默认的，那么备份好它们，进行替换。这样，list中的文件名，就不需要修改了。

问题2：已将androidboot.selinux=disabled androidboot.dm_verity=disabled，主要有啥引起init: Service 'media' is being killed...init: Service 'netd' is being killed...init: Service 'media' (pid 3559) killed by signal 9 ？？？？

android source code默认编译出来的是for emmc的，你需要修改一下，具体的修改方法，在android user's guide pdf文档里。

-------------------------------

Sorry, the reply is a little late! Take a look at the suggestions:

(1)

MFG TOOLS has an OS Firmware directory. There are u-boot/xxx.dtb/kernel/rootfs for MFG TOOLS. CPU ROM CODE downloads these four files to DDR3 according to the command in LIST of MFG TOOLS. Then it runs and burns u-boot/dtb/kernel/tfroots in SD card or EMMC. So, four files under OS Firmware also need to be compiled for your board and put into this directory. If you replace the defaults, back them up and replace them. In this way, the file name in the list does not need to be changed.

(2)

Android source code is compiled by default for EMMC, You need to modify it. The specific modification method is in the Android user's Guide PDF document.

---------------------------------

Have a nice day!

BR,

Weidong

blackhuang · ‎07-01-2019

Hi Wigros,

根据您的建议，尝试解决问题1.

根据ucl2.xml文件。查找到所需要更换的文件

根据提示替换files下：u-boot-imx6qsabresd_sd.imx/zImagezImage-imx6q-sabresd.dtb和firmware下：u-boot-imx6qsabresd_sd.imx/zImagezImage-imx6q-sabresd.dtb。分别使用的是系统编译结果~/myandroid/out/target/product/sabresd_6dq/u-boot-imx6q.imx

~/myandroid/kernel_imx/arch/arm/boot/zImage

~/myandroid/out/target/product/sabresd_6dq/imx6q-sabresd.dtb

更好文件名替换。暂时没有使用rootfs,就没有进行更换。

但是烧写显示

很抱歉，再次请教您。我还需要操作什么。能够使我正确的烧写。

非常感谢您的帮助。期望您能够尽快回复

weidong_sun · ‎07-02-2019

Hi, Black,

很显然，你遇到的问题，是OS Firmware下的MFG Tools用的image要么没有做好，要么就是4个文件没有都下载进去。所以，你再检查一遍，首先文件名字不能错，其次，android user's guide里，有如何编译MFG tools用的image的方法。也请你核对一下。

上面的MFG TOOLS界面，似乎是windows找不到板子。应该是MFG tools的image部分出了问题.

----------------------------------

Obviously, the problem you encounter is that the image used by MFG Tools under OS Firmware is either not well done or four files are not downloaded. So, check again. First of all, the file name can't be wrong. Second, in the Android user's guide, there is a way to compile the image used by MFG tools. Please check it, too.

The above MFG TOOLS interface, it seems that Windows can not find the board. It should be the image part of MFG ools that has gone wrong.

-------------------------------------

Have a nice day!

BR,

Weidong

blackhuang · ‎07-03-2019

Hi Wigros,

我已经将生成的image（仅仅修改i2c的定义）少些到官方开发板上，是没有问题的。我现在只想弄明白我更改的pmic的i2c后。需要替换OS Firmware\firmware和OS Firmware\files内的那些文件。如之前我的回答截图所示。

我这边尝试了很多次。没有一次能够正常。还希望您能够多多帮助。非常感谢！！！

weidong_sun · ‎07-03-2019

Hi Black,

This is the path of MFG tool on my computer:

E:\i.MX Processor\L4.9.11_1.0.0-ga_mfg-tools.tar\L4.9.11_1.0.0-ga_mfg-tools\mfgtools\Profiles\Linux\OS Firmware\firmware

There are many files in the directory, but according to files' name, you will know which one you should use, for example , if you design your board on the basis of I.MX6DL SabreSDB , OS Firmware will be :

u-boot : u-boot-imx6dlsabresd_sd.imx

dtb: zImage-imx6dl-sabresd.dtb

kernel: zImage ( multiple platforms share one kernel)

rootfs: fsl-image-mfgtool-initramfs-imx_mfgtools.cpio.gz.u-boot (ramdisk, you don't need to change it, use this one, please!)

So you only need to compile u-boot/dtb/kernel for your board, and rootf don't need to be modified.

Have a nice day!

BR,

Weidong

blackhuang · ‎07-04-2019

Hi Wigros,

按照要求，我已将android_m6.0.1_2.1.0_ga_tool\mfgtools\Profiles\Linux\OS Firmware\firmware下的u-boot-imx6qsabresd_sd.imx更换为我生成的uboot.imx(使用MFG命令)。但是出现如下现象:MFG UI界面显示Jumping to OS image跳到No Device Connected，然后一直卡在No Device Connected，串口信息如下。

U-Boot 2015.04-dirty (Jul 04 2019 - 13:30:43)

CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 33 C
Reset cause: POR
Board: MX6-SabreSD
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
No panel detected: default to Hannstar-XGA
Display: Hannstar-XGA (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Error: FEC address not set.

Boot from USB for mfgtools
Use default environment for mfgtools
Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};
Hit any key to stop autoboot: 0
Kernel image @ 0x12000000 [ 0x000000 - 0x8505f0 ]
## Loading init Ramdisk from Legacy Image at 12c00000 ...
Image Name: fsl-image-mfgtool-initramfs-imx6
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7565864 Bytes = 7.2 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 1800e5d0
switch to ldo_bypass mode!

Starting kernel ...

Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 4.1.15-dirty (vmuser@ubuntu) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #2 SMP PREEMPT Wed Jul 3 13:33:38 CST 2019
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: Freescale i.MX6 Quad SABRE Smart Device Board
Memory policy: Data cache writealloc
PERCPU: Embedded 13 pages/cpu @eef9f000 s22144 r8192 d22912 u53248
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260368
Kernel command line: console=ttymxc0,115200 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= enable_wait_mode=off
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 1012724K/1047552K available (11566K kernel code, 972K rwdata, 3684K rodata, 1024K init, 655K bss, 34828K reserved, 0K cma-reserved, 269312K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0000000 - 0xff000000 ( 240 MB)
lowmem : 0xc0000000 - 0xef800000 ( 760 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0xc0008000 - 0xc0fe49bc (16243 kB)
.init : 0xc1000000 - 0xc1100000 (1024 kB)
.data : 0xc1100000 - 0xc11f3050 ( 973 kB)
.bss : 0xc11f3050 - 0xc1296f24 ( 656 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
Additional per-CPU info printed with stalls.
NR_IRQS:16 nr_irqs:16 16
L2C-310 erratum 769419 enabled
L2C-310 enabling early BRESP for Cortex-A9
L2C-310 full line of zeros enabled for Cortex-A9
L2C-310 ID prefetch enabled, offset 16 lines
L2C-310 dynamic clock gating enabled, standby mode enabled
L2C-310 cache controller enabled, 16 ways, 1024 kB
L2C-310: CACHE_ID 0x410000c7, AUX_CTRL 0x76070001
mxc_clocksource_init 3000000
Switching to timer-based delay loop, resolution 333ns
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns
clocksource mxc_timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
pid_max: default: 32768 minimum: 301
Security Framework initialized
SELinux: Initializing.
AppArmor: AppArmor disabled by boot time parameter
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Initializing cgroup subsys freezer
Initializing cgroup subsys debug
CPU: Testing write buffer coherency: ok
CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
Setting up static identity map for 0x10100000 - 0x10100058
CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
Brought up 4 CPUs
SMP: Total of 4 processors activated (24.00 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
CPU identified as i.MX6Q, silicon rev 1.5
anatop_regulator 20c8000.anatop:regulator-vddcore@140: Failed to read a valid default voltage selector.
anatop_regulator: probe of 20c8000.anatop:regulator-vddcore@140 failed with error -22
anatop_regulator 20c8000.anatop:regulator-vddsoc@140: Failed to read a valid default voltage selector.
anatop_regulator: probe of 20c8000.anatop:regulator-vddsoc@140 failed with error -22
!!request miniPCIE Power On gpio
hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 4 bytes.
VDSO is not a valid ELF object!
imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver
mxs-dma 110000.dma-apbh: initialized
MPCIE_3V3: Failed to request enable GPIO83: -16
reg-fixed-voltage regulators:regulator@3: Failed to register regulator: -16
reg-fixed-voltage: probe of regulators:regulator@3 failed with error -16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
2000000.aips-bus:usbphy_nop1 supply vcc not found, using dummy regulator
2000000.aips-bus:usbphy_nop2 supply vcc not found, using dummy regulator
i2c i2c-0: IMX I2C adapter registered
i2c i2c-0: can't use DMA
imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_EIM_D16 already requested by 20e0000.iomuxc; cannot claim for 21a4000.i2c
imx6q-pinctrl 20e0000.iomuxc: pin-36 (21a4000.i2c) status -22
imx6q-pinctrl 20e0000.iomuxc: could not request pin 36 (MX6Q_PAD_EIM_D16) from group i2c2grp on device 20e0000.iomuxc
imx-i2c 21a4000.i2c: Error applying setting, reverse things back
i2c i2c-1: IMX I2C adapter registered
i2c i2c-1: can't use DMA
i2c i2c-2: IMX I2C adapter registered
i2c i2c-2: can't use DMA
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Initialized.
Bluetooth: Core ver 2.20
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
Switched to clocksource mxc_timer1
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 7392K (c2c00000 - c3338000)
CPU PMU: Failed to parse /soc/pmu/interrupt-affinity[0]
hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
imx rpmsg driver is registered.
Bus freq driver module loaded
console [pstore-1] enabled
pstore: Registered ramoops as persistent store backend
ramoops: attached 0x100000@0x4bf00000, ecc: 0/0
mxc_ramoops device success loaded
bt power gpio is:2
rfkill: BT RF going to : on
mxc_bt_rfkill_reset
mxc_bt_rfkill driver success loaded
futex hash table entries: 1024 (order: 4, 65536 bytes)
audit: initializing netlink subsys (disabled)
audit: type=2000 audit(1.040:1): initialized
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
ntfs: driver 2.1.32 [Flags: R/W DEBUG].
jffs2: version 2.2. (NAND) ?? 2001-2006 Red Hat, Inc.
fuse init (API version 7.23)
bounce: pool size: 64 pages
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-weim 21b8000.weim: Driver registered.
pwm-backlight supply power not found, using dummy regulator
mxc_mipi_dsi 21e0000.mipi: i.MX MIPI DSI driver probed
MIPI DSI driver module loaded
MIPI DSI driver module loaded
mxc_sdc_fb fb@0: registered mxc display driver ldb
imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 128x48
mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1
fbcvt: 1920x1080@60: CVT Name - 2.073M9
mxc_sdc_fb fb@1: registered mxc display driver hdmi
mxc_sdc_fb fb@2: registered mxc display driver lcd
mxc_sdc_fb fb@2: ipu0-di0 already in use
mxc_sdc_fb: probe of fb@2 failed with error -16
mxc_sdc_fb fb@3: registered mxc display driver ldb
imx-sdma 20ec000.sdma: no iram assigned, using external mem
imx-sdma 20ec000.sdma: no event needs to be remapped
imx-sdma 20ec000.sdma: loaded firmware 3.3
imx-sdma 20ec000.sdma: initialized
pfuze100-regulator 1-0008: unrecognized pfuze chip ID!
pfuze100-regulator: probe of 1-0008 failed with error -110
2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 25, base_baud = 5000000) is a IMX
console [ttymxc0] enabled
21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 300, base_baud = 5000000) is a IMX
imx sema4 driver is registered.
[drm] Initialized drm 1.1.0 20060810
[drm] Initialized vivante 1.0.0 20120216 on minor 0
brd: module loaded
loop: module loaded
zram: Created 1 device(s)
imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_KEY_COL1 already requested by 21f4000.serial; cannot claim for 2008000.ecspi
imx6q-pinctrl 20e0000.iomuxc: pin-128 (2008000.ecspi) status -22
imx6q-pinctrl 20e0000.iomuxc: could not request pin 128 (MX6Q_PAD_KEY_COL1) from group ecspi1grp on device 20e0000.iomuxc
spi_imx 2008000.ecspi: Error applying setting, reverse things back
m25p80 spi0.0: unrecognized JEDEC id bytes: 00, 0, 0
spi_imx 2008000.ecspi: probed
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
CAN device driver interface
2188000.ethernet supply phy not found, using dummy regulator
pps pps0: new PPS source ptp0
fec 2188000.ethernet (unnamed net_device) (uninitialized): Invalid MAC address: 00:00:00:00:00:00
fec 2188000.ethernet (unnamed net_device) (uninitialized): Using random MAC address: f6:f4:8c:f8:c1:2f
libphy: fec_enet_mii_bus: probed
fec 2188000.ethernet eth0: registered PHC device 0
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver r8152
usbcore: registered new interface driver asix
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver cdc_eem
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-mxc: Freescale On-Chip EHCI Host driver
usbcore: registered new interface driver cdc_acm
cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver ftdi_sio
usbserial: USB Serial support registered for FTDI USB Serial Device
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
usbcore: registered new interface driver usb_ehset_test
2184800.usbmisc supply vbus-wakeup not found, using dummy regulator
reg-fixed-voltage regulators:regulator@0: Failed to resolve vin-supply for usb_otg_vbus
imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517
reg-fixed-voltage regulators:regulator@1: Failed to resolve vin-supply for usb_h1_vbus
imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517
mousedev: PS/2 mouse device common for all mice
usbcore: registered new interface driver xpad
usbcore: registered new interface driver usb_acecad
usbcore: registered new interface driver aiptek
usbcore: registered new interface driver gtco
usbcore: registered new interface driver hanwang
usbcore: registered new interface driver kbtab
egalax_ts 1-0004: Failed to read firmware version
egalax_ts: probe of 1-0004 failed with error -5
egalax_ts 2-0004: Failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5
snvs_rtc 20cc000.snvs:snvs-rtc-lp: rtc core: registered 20cc000.snvs:snvs-r as rtc0
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR Sharp protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR XMP protocol handler initialized
ov564x 0-003c: cannot get io voltage
ov564x 0-003c: cannot get core voltage
ov564x 0-003c: cannot get analog voltage
ov5640_read_reg:write reg error:reg=300a
camera ov5640 is not found
ov5640_power_on: cannot get analog voltage error
ov5640_read_reg:write reg error:reg=300a
camera ov5640_mipi is not found
mxc_v4l2_output v4l2_out: V4L2 device registered as video16
mxc_v4l2_output v4l2_out: V4L2 device registered as video17
mxc_v4l2_output v4l2_out: V4L2 device registered as video18
mxc_v4l2_output v4l2_out: V4L2 device registered as video19
mxc_v4l2_output v4l2_out: V4L2 device registered as video20
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
mag3110 2-000e: check mag3110 chip ID
mag3110 2-000e: read chip ID 0xfffffffb is not equal to 0xc4!
mag3110: probe of 2-000e failed with error -22
mma8x5x 0-001c: read chip ID 0xfffffffb is not equal to 0x1a,0x2a,0x3a,0x4a,0x5a!
mma8x5x: probe of 0-001c failed with error -22
imx2-wdt 20c0000.wdog: use WDOG_B to reboot.
imx2-wdt 20c0000.wdog: timeout 60 sec (nowayout=0)
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.31.0-ioctl (2015-3-12) initialised: dm-devel@redhat.com
Bluetooth: HCI UART driver ver 2.3
Bluetooth: HCI UART protocol H4 registered
Bluetooth: HCI UART protocol BCSP registered
Bluetooth: HCI UART protocol ATH3K registered
usbcore: registered new interface driver btusb
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
/soc/aips-bus@02100000/usdhc@02194000: voltage-ranges unspecified
sdhci-esdhc-imx 2194000.usdhc: Got WP GPIO
sdhci-esdhc-imx 2194000.usdhc: assigned as wifi host
sdhci-esdhc-imx 2194000.usdhc: No vmmc regulator found
sdhci-esdhc-imx 2194000.usdhc: No vqmmc regulator found
mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA
/soc/aips-bus@02100000/usdhc@02198000: voltage-ranges unspecified
sdhci-esdhc-imx 2198000.usdhc: Got CD GPIO
sdhci-esdhc-imx 2198000.usdhc: Got WP GPIO
sdhci-esdhc-imx 2198000.usdhc: No vmmc regulator found
sdhci-esdhc-imx 2198000.usdhc: No vqmmc regulator found
mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA
/soc/aips-bus@02100000/usdhc@0219c000: voltage-ranges unspecified
sdhci-esdhc-imx 219c000.usdhc: No vmmc regulator found
sdhci-esdhc-imx 219c000.usdhc: No vqmmc regulator found
mmc3: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA
mxc_vpu 2040000.vpu_fsl: VPU initialized
mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
mxc_hdmi_cec soc:hdmi_cec@00120000: HDMI CEC initialized
Galcore version 5.0.11.41671
mmc2: new high speed SDHC card at address aaaa
mmcblk2: mmc2:aaaa SU04G 3.69 GiB
mmcblk2: p1 p2 p3 < p5 p6 p7 p8 p9 > p4
leds-gpio: probe of leds failed with error -2
mmc3: MAN_BKOPS_EN bit is not set
caam 2100000.caam: Entropy delay = 3200
mmc3: new DDR MMC card at address 0001
mmcblk3: mmc3:0001 SEM08G 7.28 GiB
mmcblk3boot0: mmc3:0001 SEM08G partition 1 2.00 MiB
mmcblk3boot1: mmc3:0001 SEM08G partition 2 2.00 MiB
mmcblk3rpmb: mmc3:0001 SEM08G partition 3 2.00 MiB
caam 2100000.caam: Instantiated RNG4 SH0
caam 2100000.caam: Instantiated RNG4 SH1
caam 2100000.caam: device ID = 0x0a16010000000000 (Era -524)
caam 2100000.caam: job rings = 2, qi = 0
caam algorithms registered in /proc/crypto
caam_jr 2101000.jr0: registering rng-caam
platform caam_sm: blkkey_ex: 4 keystore units available
platform caam_sm: 64-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: 64-bit black key:
platform caam_sm: [0000] 7f b6 da eb 78 af a8 91
platform caam_sm: [0008] 23 2d 45 8a e1 8c da 37
platform caam_sm: 128-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: 128-bit black key:
platform caam_sm: [0000] c3 f1 7f 42 67 4b 86 a0
platform caam_sm: [0008] 6d 60 f6 ab 88 aa bc e1
platform caam_sm: 192-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: [0016] 10 11 12 13 14 15 16 17
platform caam_sm: 192-bit black key:
platform caam_sm: [0000] 60 44 a8 32 4f db 3e dd
platform caam_sm: [0008] 7b 18 f0 ae 11 83 45 f4
platform caam_sm: [0016] 5a c8 9e f5 5d fb fb 3a
platform caam_sm: [0024] 9a ca 39 05 67 c6 47 49
platform caam_sm: 256-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: [0016] 10 11 12 13 14 15 16 17
platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f
platform caam_sm: 256-bit black key:
platform caam_sm: [0000] 18 6f a4 62 d0 e0 68 14
platform caam_sm: [0008] 14 e9 81 53 f4 11 d9 9f
platform caam_sm: [0016] 0a b6 e5 ce 6f 16 2f a9
platform caam_sm: [0024] a7 b6 7f 1d b7 b8 ed c3
platform caam_sm: 64-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 128-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 196-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 256-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 64-bit black key in blob:
platform caam_sm: [0000] ac 09 a2 d9 8c 14 b9 57
platform caam_sm: [0008] e6 20 b8 b6 19 57 63 3d
platform caam_sm: [0016] 3b 0c 15 ab 7e d1 b4 6d
platform caam_sm: [0024] f2 f7 fb 0a d7 b9 08 ce
platform caam_sm: [0032] f3 e3 25 73 03 38 61 b8
platform caam_sm: [0040] 3d 79 65 a7 f2 fc a8 28
platform caam_sm: [0048] a4 5a b4 92 8c 9c 18 0a
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 128-bit black key in blob:
platform caam_sm: [0000] c6 29 5d 6d ac 2e 54 00
platform caam_sm: [0008] 53 2c 80 8e a6 28 bf c0
platform caam_sm: [0016] 06 3a 0a 6c 54 63 0a e3
platform caam_sm: [0024] 17 8e 7f 33 9f fa 86 b7
platform caam_sm: [0032] 33 22 dd b8 ea 5a 81 b6
platform caam_sm: [0040] ca 3b 30 c2 21 44 2b b0
platform caam_sm: [0048] 81 6c 39 88 cf 6c 7e 89
platform caam_sm: [0056] b0 64 e3 e6 66 f0 2a 7e
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 192-bit black key in blob:
platform caam_sm: [0000] 1e 73 05 4f 9f cf 77 41
platform caam_sm: [0008] 94 3b de 09 7f 7d 62 1e
platform caam_sm: [0016] 99 09 ca cc dd 14 29 2e
platform caam_sm: [0024] a0 97 c6 ce d1 90 7c 03
platform caam_sm: [0032] 31 ad 82 ec 85 9e 89 9f
platform caam_sm: [0040] 8a 8a 48 fc 16 26 2e 3f
platform caam_sm: [0048] ed 20 df d2 a1 d3 03 28
platform caam_sm: [0056] c6 02 95 12 76 df f8 a5
platform caam_sm: [0064] 11 06 8a 93 b4 2d d0 2a
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 256-bit black key in blob:
platform caam_sm: [0000] e1 34 cc 25 ce 16 04 aa
platform caam_sm: [0008] c8 af e9 69 ac c5 de 56
platform caam_sm: [0016] ba 9d 48 8d ea 03 94 d4
platform caam_sm: [0024] d0 28 d2 1c 67 a8 1e ec
platform caam_sm: [0032] b7 2f 4b ee 30 88 6a 19
platform caam_sm: [0040] fb 38 7b 1e 9e 85 3e 56
platform caam_sm: [0048] c6 61 dd 30 07 b9 dd fa
platform caam_sm: [0056] 1b af 1d ca 5b 47 c3 ad
platform caam_sm: [0064] 5f ac 3a c2 05 e7 33 7c
platform caam_sm: [0072] 2f 9e 79 2f 3c c5 d4 54
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: restored 64-bit black key:
platform caam_sm: [0000] 10 ad cc bb ed 30 e6 a5
platform caam_sm: [0008] f0 5c 7a 58 57 71 34 b8
platform caam_sm: restored 128-bit black key:
platform caam_sm: [0000] c3 f1 7f 42 67 4b 86 a0
platform caam_sm: [0008] 6d 60 f6 ab 88 aa bc e1
platform caam_sm: restored 192-bit black key:
platform caam_sm: [0000] 60 44 a8 32 4f db 3e dd
platform caam_sm: [0008] 7b 18 f0 ae 11 83 45 f4
platform caam_sm: [0016] ea 2a e4 ac 48 04 dd 4a
platform caam_sm: [0024] b8 6f d8 18 b4 05 18 76
platform caam_sm: restored 256-bit black key:
platform caam_sm: [0000] 18 6f a4 62 d0 e0 68 14
platform caam_sm: [0008] 14 e9 81 53 f4 11 d9 9f
platform caam_sm: [0016] 0a b6 e5 ce 6f 16 2f a9
platform caam_sm: [0024] a7 b6 7f 1d b7 b8 ed c3
snvs-secvio 20cc000.caam-snvs: can't get snvs clock
snvs-secvio 20cc000.caam-snvs: violation handlers armed - non-secure state
caam_keyblob caam_keyblob: caam keyblob initialized
hidraw: raw HID events driver (C) Jiri Kosina
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ashmem: initialized
usbcore: registered new interface driver snd-usb-audio
wm8962 0-001a: customer id 0 revision D
fsl-asrc 2034000.asrc: driver registered
input: WM8962 Beep Generator as /devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-001a/input/input2
imx-wm8962 sound: wm8962 <-> 202c000.ssi mapping ok
imx-wm8962 sound: snd-soc-dummy-dai <-> 2034000.asrc mapping ok
imx-wm8962 sound: wm8962 <-> 202c000.ssi mapping ok
imx-audio-hdmi sound-hdmi: hdmi-hifi <-> soc:hdmi_audio@00120000 mapping ok
NET: Registered protocol family 26
u32 classifier
Actions configured
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (15939 buckets, 63756 max)
ctnetlink v0.93: registering with nfnetlink.
xt_time: kernel timezone is -0000
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
Initializing XFRM netlink socket
NET: Registered protocol family 10
mip6: Mobile IPv6
ip6_tables: (C) 2000-2006 Netfilter Core Team
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
NET: Registered protocol family 15
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20120528 t)
can: netlink gateway (rev 20130117) max_hops=1
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
8021q: 802.1Q VLAN Support v1.8
Key type dns_resolver registered
cpu cpu0: failed to get regulators
imx6q-cpufreq: probe of imx6q-cpufreq.0 failed with error -2
reg-fixed-voltage regulators:regulator@0: Failed to resolve vin-supply for usb_otg_vbus
imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517
reg-fixed-voltage regulators:regulator@1: Failed to resolve vin-supply for usb_h1_vbus
imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517
dhd_module_init in
Power-up adapter 'DHD generic adapter'
wifi_platform_bus_enumerate device present 1
failed to power up DHD generic adapter, 3 retry left
wifi_platform_bus_enumerate device present 0
wifi_platform_bus_enumerate device present 1
failed to power up DHD generic adapter, 2 retry left
wifi_platform_bus_enumerate device present 0
wifi_platform_bus_enumerate device present 1
failed to power up DHD generic adapter, 1 retry left
wifi_platform_bus_enumerate device present 0
wifi_platform_bus_enumerate device present 1
failed to power up DHD generic adapter, 0 retry left
wifi_platform_bus_enumerate device present 0
failed to power up DHD generic adapter, max retry reached**
input: gpio-keys as /devices/soc0/gpio-keys/input/input5
snvs_rtc 20cc000.snvs:snvs-rtc-lp: setting system clock to 1970-01-01 00:00:10 UTC (10)
reg-fixed-voltage regulators:regulator@0: Failed to resolve vin-supply for usb_otg_vbus
imx_usb 2184000.usb: Can't register ci_hdrc platform device, err=-517
reg-fixed-voltage regulators:regulator@1: Failed to resolve vin-supply for usb_h1_vbus
imx_usb 2184200.usb: Can't register ci_hdrc platform device, err=-517
wlreg_on: disabling
wm8962-supply: disabling
usb_h1_vbus: disabling
usb_otg_vbus: disabling
ALSA device list:
#0: wm8962-audio
#1: imx-hdmi-soc
Freeing unused kernel memory: 1024K (c1000000 - c1100000)
Starting UTP
uuc 0.5 [built Mar 12 2016 19:04:20]
UTP: Waiting for device to appear

https://community.nxp.com/message/854534 社区里这个问题和现象和我基本上一样。我按照建议检查后。也没有发现啥问题。

看现象是我的小系统没起来，是我生成的zImage有问题？还是？

再次麻烦您看一下，非常感谢！！！

weidong_sun · ‎07-04-2019

Hi black,

OS Firmware has already run, but I don't know why "usb_otg_vbus: disabling", what happened? this is the root cause why your windows doesn't find USB device.

Have a nice day!

BR,

Weidong

blackhuang · ‎07-04-2019

Hi Wigros

imx6qdl-sabresd.dtsi设备树中我没有改动，

reg_usb_otg_vbus: regulator@0 {
compatible = "regulator-fixed";
reg = <0>;
regulator-name = "usb_otg_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
gpio = <&gpio3 22 0>;
enable-active-high;
vin-supply = <&swbst_reg>;
};

reg_usb_h1_vbus: regulator@1 {
compatible = "regulator-fixed";
reg = <1>;
regulator-name = "usb_h1_vbus";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
gpio = <&gpio1 29 0>;
enable-active-high;
vin-supply = <&swbst_reg>;
};

&usbh1 {
vbus-supply = <&reg_usb_h1_vbus>;
status = "okay";
};

&usbotg {
vbus-supply = <&reg_usb_otg_vbus>;
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_usbotg>;
disable-over-current;
srp-disable;
hnp-disable;
adp-disable;
status = "okay";
};

内核驱动也是正常是能的

电路图也是参考原厂开发板

mfgtool 启动uboot 后出现 no device | NXP Community 尝试之前的方法加入dr_mode = "host";也不行。

我特地拿之前android4.3的镜像测试，硬件无问题，烧写正常。

还有那些需改更改或者主要的地方，还麻烦不吝赐教！

非常感谢您之前的帮助！！！！

weidong_sun · ‎07-04-2019

Hi black,

Tell me informations on i2c connected to PMIC:

1. IOMUX pad

2. which i2c

weidong

blackhuang · ‎07-04-2019

Hi Wigros,

设备树如附件，

otg中gpio = <&gpio3 22 0>;硬件未使用。

host中gpio = <&gpio1 29 0>;硬件未使用

pmic使用的是i2c2.

weidong_sun · ‎07-07-2019

Hi black,

in the .dsti file,

EIM_D16 , the pin has been used for 2 times. One is multiplexed as I2C pin, the othe is for GPIO.

MX6QDL_PAD_EIM_D16__GPIO3_IO16 0x80000000

MX6QDL_PAD_EIM_D16__I2C2_SDA 0x4001b8b1

In u-boot, you should do like this in mx6sabresd.c

#ifdef CONFIG_SYS_I2C
/*
static struct i2c_pads_info i2c_pad_info1 = {
   .scl = {
       .i2c_mode = MX6_PAD_KEY_COL3__I2C2_SCL | I2C_PAD,
       .gpio_mode = MX6_PAD_KEY_COL3__GPIO4_IO12 | I2C_PAD,
       .gp = IMX_GPIO_NR(4, 12)
   },
   .sda = {
       .i2c_mode = MX6_PAD_KEY_ROW3__I2C2_SDA | I2C_PAD,
       .gpio_mode = MX6_PAD_KEY_ROW3__GPIO4_IO13 | I2C_PAD,
       .gp = IMX_GPIO_NR(4, 13)
   }
};
*/
static struct i2c_pads_info i2c_pad_info1 = {
   .scl = {
       .i2c_mode = MX6_PAD_EIM_EB2__I2C2_SCL | I2C_PAD,
       .gpio_mode = MX6_PAD_EIM_EB2__GPIO2_IO30 | I2C_PAD,
       .gp = IMX_GPIO_NR(2, 30)
   },
   .sda = {
       .i2c_mode = MX6_PAD_EIM_D16__I2C2_SDA | I2C_PAD,
       .gpio_mode = MX6_PAD_EIM_D16__GPIO3_IO16 | I2C_PAD,
       .gp = IMX_GPIO_NR(3, 16)
   }
};
#endif

Check it carefully, please!

Have a nice day!

BR,

weidong

blackhuang · ‎07-03-2019

Hi Wigros

我将生成的boot-imx6q.img/recovery-imx6q.img/system.img/u-boot-imx6q.imx文件放在android_m6.0.1_2.1.0_ga_tool\mfgtools\Profiles\Linux\OS Firmware\files\android\sabresd下。

使用MFG tools下mfgtool2-android-mx6q-sabresd-emmc.vbs，出现如下信息。

U-Boot 2015.04-imx_v2015.04_4.1.15_1.0.0_ga+g384e1c1 (Mar 13 2016 - 17:31:03)

CPU: Freescale i.MX6Q rev1.5 at 792 MHz

CPU: Temperature 32 C

Reset cause: POR

Board: MX6-SabreSD

I2C: ready

DRAM: 1 GiB

Can't find PMIC:PFUZE100

initcall sequence 4ff933d8 failed at call 17803708 (err=-19)

### ERROR ### Please RESET the board ###

根据ucl2.xml提示我将便宜生成的u-boot-imx6q.imx更改为u-boot-imx6qsabresd_sd.imx和将编译的imx6q-sabresd.dtb更改为zImage-imx6q-sabresd.dtb以及zImage都放在android_m6.0.1_2.1.0_ga_tool\mfgtools\Profiles\Linux\OS Firmware\firmware下。

同样步骤将上述三分文件也放在android_m6.0.1_2.1.0_ga_tool\mfgtools\Profiles\Linux\OS Firmware\files下。

使用mfgtool2-android-mx6q-sabresd-emmc.vbs又出现

U-Boot 2015.04-dirty (Jul 03 2019 - 15:20:35)

CPU: Freescale i.MX6Q rev1.5 at 792 MHz

CPU: Temperature 43 C

Reset cause: POR

Board: MX6-SabreSD

I2C: ready

DRAM: 1 GiB

PMIC: PFUZE100 ID=0x10

MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In: serial

Out: serial

Err: serial

unsupported boot devices

check_and_clean: reg 0, flag_set 0

MMC: no card present

Block device mmc 0 not supported

rw_block, get_block_size return 0

read_bootctl, rw_block read failed

read command failed

Fastboot: Normal

SATA isn't buildin

Net: FEC [PRIME]

Error: FEC address not set.

Boot from USB for mfgtools

Use default environment for mfgtools

Run bootcmd_mfg: <NULL>

=>

MFG显示为之前图所示。

更改i2c我已测试编译好的镜像放在官方开发板上是没有问题的。

但是更改之后去烧写自己的板子时就出现上述错误，而且已经是量产产品。需求更改升级android6.0

还麻烦您再次帮助！！！！非常感谢！

blackhuang · ‎06-30-2019

Hi Wigros

非常感谢您对于我的帮助，问题1我已经理解。但是对于问题2，我已将按照android user's guide 更改

The default configuration in the source code package takes internal eMMC as the boot storage. It can be changed to make the
SD card in SD Slot 3 as the boot storage as follows:
1. Remove /out/target/product/sabresd_6dq/root directory and boot*.img.
2. Remove /out/target/product/sabresd_6dq/recovery directory and recovery*.img.
3. Build the boot.img and recovery.img as follows:
make bootimage BUILD_TARGET_DEVICE=sd
make recoveryimage BUILD_TARGET_DEVICE=sd

但是还是出现我上述的现象。

我这边对核心板分只是更改了相应gpio口的定义，个人认为与系统没有太大的关系。

您这边是否有其他建议？

非常感谢您的回复。