topic Re: 定制Uboot报Can't find PMIC:PFUZE100 in i.MX Processors

定制Uboot报Can't find PMIC:PFUZE100

leavs — Tue, 19 Apr 2016 10:03:34 GMT

参考 fsl-yocto-imx-4.1.15_1.0.0 BSP文档定制Uboot，移植完成之后，在串口中出现如下错误：

******************************************************************************************************

U-Boot 2015.04-imx_v2015.04_4.1.15_1.0.0_ga+gd7d7c43 (Apr 19 2016 - 17:38:20)

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

CPU: Temperature 29 C

Reset cause: POR

Board: MX6-SabreSD

I2C: ready

DRAM: 2 GiB

Can't find PMIC:PFUZE100

initcall sequence 8ff937c8 failed at call 178036c0 (err=-19)

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

*********************************************************************************************************

开发板是我们自己设计的，不确定为什么会报这个错误，有什么解决方法吗？

Re: 定制Uboot报Can't find PMIC:PFUZE100

igorpadykov — Wed, 20 Apr 2016 00:29:57 GMT

Hi leavs

suggest to check signals by oscilloscope and check values of

i2c pull-up resistors. For custom board bringup it may be useful

to follow Chapter 1 Porting U-Boot attached Porting Guide.

Best regards

igor

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

Note: If this post answers your question, please click the Correct Answer button. Thank you!

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

Re: 定制Uboot报Can't find PMIC:PFUZE100

leavs — Wed, 20 Apr 2016 03:19:18 GMT

Hi igorpadykov,

Thanks, I check my board , My board has no PMIC, I wan't to know how to disable it in the code.

Re: 定制Uboot报Can't find PMIC:PFUZE100

ispsubb — Fri, 29 Apr 2016 01:09:26 GMT

Who can help me ?

I have the same problem in my board , my board have no PMIC ! I try to modify mfgtool firmware uboot , Shielding the pmic code 。Then "Can't find PMIC:PFUZE100 " problem is ok 。 But in the kernel we meet the same problem . The log as

Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};

Hit any key to stop autoboot: 0

Kernel image @ 0x12000000 [ 0x000000 - 0x520f48 ]

## 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: 7508220 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 1800d77d

No PMIC found!

Starting kernel ...

Booting Linux on physical CPU 0x0

Linux version 3.14.52-1.1.0_ga-mfgtool+g5f6f0a5 (mphotool@HP-Z228) (gcc version 4.9.2 (GCC) ) #1 SMP PREEMPT Thu Apr 28 16:14:36 CST 2016

CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d

CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine model: Freescale i.MX6 Quad SABRE Smart Device Board

cma: CMA: reserved 320 MiB at 3c000000

Memory policy: Data cache writealloc

PERCPU: Embedded 8 pages/cpu @ab733000 s8320 r8192 d16256 u32768

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260096

Kernel command line: console=ttymxc0,115200 rdinit=/linuxrc g_mass_storage.stall=0 g_mass_storage.removable=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: 693580K/1048576K available (6668K kernel code, 353K rwdata, 2292K rodata, 380K init, 421K bss, 354996K reserved, 0K highmem)

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

vmalloc : 0xc0800000 - 0xff000000 (1000 MB)

lowmem : 0x80000000 - 0xc0000000 (1024 MB)

pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)

modules : 0x7f000000 - 0x7fe00000 ( 14 MB)

.text : 0x80008000 - 0x808c8588 (8962 kB)

.init : 0x808c9000 - 0x80928080 ( 381 kB)

.data : 0x8092a000 - 0x80982740 ( 354 kB)

.bss : 0x8098274c - 0x809ebc70 ( 422 kB)

SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1

Preemptible hierarchical RCU implementation.

RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.

RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2

NR_IRQS:16 nr_irqs:16 16

L310 cache controller enabled

l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x32070000, Cache size: 1024 kB

Switching to timer-based delay loop

sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682ns

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

Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)

Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)

CPU: Testing write buffer coherency: ok

CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

Setting up static identity map for 0x10658e18 - 0x10658e70

CPU1: Booted secondary processor

CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

Brought up 2 CPUs

SMP: Total of 2 processors activated (12.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

pinctrl core: initialized pinctrl subsystem

regulator-dummy: no parameters

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.2

Use WDOG2 as reset source

syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered

vdd1p1: 800 <--> 1375 mV at 1100 mV

vdd3p0: 2625 <--> 3400 mV at 3000 mV

vdd2p5: 2000 <--> 2750 mV at 2400 mV

vddarm: 725 <--> 1450 mV at 1150 mV

vddpu: 725 <--> 1450 mV

vddsoc: 725 <--> 1450 mV at 1175 mV

syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered

syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered

hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.

hw-breakpoint: maximum watchpoint size is 4 bytes.

imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver

bio: create slab <bio-0> at 0

mxs-dma 110000.dma-apbh: initialized

usb_otg_vbus: 5000 mV

usb_h1_vbus: 5000 mV

wm8962-supply: no parameters

mipi_dsi_pwr_on: no parameters

sensor-supply: 3300 mV

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

usbphy_nop1.12 supply vcc not found, using dummy regulator

usbphy_nop2.13 supply vcc not found, using dummy regulator

i2c i2c-0: IMX I2C adapter registered

i2c i2c-1: IMX I2C adapter registered

i2c i2c-2: IMX I2C adapter registered

Linux video capture interface: v2.00

pps_core: LinuxPPS API ver. 1 registered

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.

cfg80211: Calling CRDA to update world regulatory domain

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)

TCP: reno registered

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: 7328K (82c01000 - 83329000)

hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

imx rpmsg driver is registered.

imx_busfreq busfreq.16: DDR medium rate not supported.

Bus freq driver module loaded

futex hash table entries: 512 (order: 3, 32768 bytes)

VFS: Disk quotas dquot_6.5.2

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

jffs2: version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.

fuse init (API version 7.22)

msgmni has been set to 2008

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

imx-weim 21b8000.weim: Driver registered.

backlight.30 supply power not found, using dummy regulator

mxc_mipi_dsi 21e0000.mipi: i.MX MIPI DSI driver probed

MIPI DSI driver module loaded

mxc_sdc_fb fb.25: 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.26: registered mxc display driver hdmi

mxc_sdc_fb fb.27: registered mxc display driver lcd

mxc_sdc_fb fb.27: ipu0-di0 already in use

mxc_sdc_fb: probe of fb.27 failed with error -16

mxc_sdc_fb fb.28: 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.2

imx-sdma 20ec000.sdma: initialized

pfuze100-regulator 1-0008: unrecognized pfuze chip ID!

pfuze100-regulator: probe of 1-0008 failed with error -5

Serial: IMX driver

2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58, base_baud = 5000000) is a IMX

console [ttymxc0] enabled

serial: Freescale lpuart driver

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

ahci-imx 2200000.sata: fsl,transmit-level-mV not specified, using 00000024

ahci-imx 2200000.sata: fsl,transmit-boost-mdB not specified, using 00000480

ahci-imx 2200000.sata: fsl,transmit-atten-16ths not specified, using 00002000

ahci-imx 2200000.sata: fsl,receive-eq-mdB not specified, using 05000000

ahci-imx 2200000.sata: SSS flag set, parallel bus scan disabled

ahci-imx 2200000.sata: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode

ahci-imx 2200000.sata: flags: ncq sntf stag pm led clo only pmp pio slum part ccc apst

scsi0 : ahci_platform

ata1: SATA max UDMA/133 mmio [mem 0x02200000-0x02203fff] port 0x100 irq 71

m25p80 spi0.0: found mr25h256, expected m25p32

m25p80 spi0.0: mr25h256 (32 Kbytes)

spi_imx 2008000.ecspi: probed

2188000.ethernet supply phy not found, using dummy regulator

pps pps0: new PPS source ptp0

fec 2188000.ethernet (unregistered net_device): Invalid MAC address: 00:00:00:00:00:00

fec 2188000.ethernet (unregistered net_device): Using random MAC address: 82:dc:6f:d7:cf:52

libphy: fec_enet_mii_bus: probed

fec 2188000.ethernet eth0: registered PHC device 0

ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver

ehci-mxc: Freescale On-Chip EHCI Host driver

usbcore: registered new interface driver usb-storage

2184800.usbmisc supply vbus-wakeup not found, using dummy regulator

ci_hdrc ci_hdrc.0: EHCI Host Controller

ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1

ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

ci_hdrc ci_hdrc.1: doesn't support gadget

ci_hdrc ci_hdrc.1: EHCI Host Controller

ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2

ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

mousedev: PS/2 mouse device common for all mice

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 20cc034.snvs-rtc-lp: can't get snvs-rtc clock

snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0

i2c /dev entries driver

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

IR RC5 (streamzap) protocol handler initialized

IR SANYO protocol handler initialized

IR MCE Keyboard/mouse protocol handler initialized

mxc_v4l2_output v4l2_out.33: V4L2 device registered as video16

mxc_v4l2_output v4l2_out.33: V4L2 device registered as video17

mxc_v4l2_output v4l2_out.33: V4L2 device registered as video18

mxc_v4l2_output v4l2_out.33: V4L2 device registered as video19

mxc_v4l2_output v4l2_out.33: V4L2 device registered as video20

imx2-wdt 20c0000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

sdhci-pltfm: SDHCI platform and OF driver helper

mmc1: no vqmmc regulator found

mmc1: no vmmc regulator found

ata1: SATA link down (SStatus 0 SControl 300)

ahci-imx 2200000.sata: no device found, disabling link.

ahci-imx 2200000.sata: pass ahci_imx..hotplug=1 to enable hotplug

mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA

mmc2: no vqmmc regulator found

mmc2: no vmmc regulator found

mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA

mmc3: no vqmmc regulator found

mmc3: no vmmc regulator found

mmc3: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA

Galcore version 5.0.11.33433

PU: Power-on latency exceeded, new value 2162333 ns

mmc3: new high speed DDR MMC card at address 0001

mmcblk3: mmc3:0001 SEM04G 3.68 GiB

mmcblk3boot0: mmc3:0001 SEM04G partition 1 1.00 MiB

mmcblk3boot1: mmc3:0001 SEM04G partition 2 1.00 MiB

mmcblk3rpmb: mmc3:0001 SEM04G partition 3 128 KiB

mmcblk3: p1

mmcblk3boot1: unknown partition table

mmcblk3boot0: unknown partition table

mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed

mxc_vpu 2040000.vpu: VPU initialized

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

wm8962 0-001a: Failed to read ID register

wm8962: probe of 0-001a failed with error -5

imx-wm8962 sound.23: failed to find codec platform device

imx-wm8962: probe of sound.23 failed with error -22

TCP: cubic registered

NET: Registered protocol family 10

sit: IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

Key type dns_resolver registered

cpu cpu0: failed to get regulators
imx6q-cpufreq: probe of imx6q-cpufreq.0 failed with error -2

Registering SWP/SWPB emulation handler

sensor-supply: disabling

wm8962-supply: disabling

regulator-dummy: disabling

imx mcc test is registered.

Number of LUNs=8

Mass Storage Function, version: 2009/09/11

LUN: removable file: (no medium)

Number of LUNs=1

LUN: removable file: (no medium)

Number of LUNs=1

g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11

g_mass_storage gadget: g_mass_storage ready

input: gpio-keys.22 as /devices/soc0/gpio-keys.22/input/input2

snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:00 UTC (0)

ALSA device list:

No soundcards found.

Freeing unused kernel memory: 380K (808c9000 - 80928000)

Starting UTP

uuc 0.5 [built Dec 3 2015 08:26:46]

UTP: Waiting for device to appear

UTP: file/device node /dev/utp already exists

cpu_id is 0

Re: 定制Uboot报Can't find PMIC:PFUZE100

BiyongSUN — Fri, 29 Apr 2016 07:36:24 GMT

Please use the ldo enable device tree for dicrete power supply.

Re: 定制Uboot报Can't find PMIC:PFUZE100

ispsubb — Tue, 03 May 2016 06:31:22 GMT

你好，我用L3.14.52_1.1.0_ga-mfg-tools.tar 中自带的 mfgtool2-yocto-mx-sabresd-emmc-1.2g.vbs 打开去烧写，这个脚本打开看过了，里面内容如下：

Set wshShell = CreateObject("WScript.shell")

wshShell.run "mfgtool2.exe -c ""linux"" -l ""eMMC"" -s ""board=sabresd"" -s ""mmc=3"" -s ""ldo=-ldo"" -s ""sxdtb=sdb"" "

Set wshShell = Nothing

烧写的现象是一样的，还是烧不进去。

jump to the os image 后卡在 no device detect 的地方。

Re: 定制Uboot报Can't find PMIC:PFUZE100

BiyongSUN — Tue, 03 May 2016 21:53:47 GMT

1. Have you modified the device tree for your customer board?

2. Have you finished the DDR calibration and apply the result to the uboot as porting guide mentioned?

i.MX6/7 DDR Stress Test Tool V2.52

3. Have you got the entire log from the power on to check?

Re: 定制Uboot报Can't find PMIC:PFUZE100

ispsubb — Wed, 04 May 2016 01:51:53 GMT

1. Have you modified the device tree for your customer board?

现在是烧写不了，尝试修改过mfgtool uboot ，linux 固件。你指的device tree应该如何修改？我尝试去掉pmic ，但与其他相关性较大。并且在mfgtool uboot中置空了对pmic 初始化的函数，这样才可以不至于卡在Can't find PMIC:PFUZE100

2. Have you finished the DDR calibration and apply the result to the uboot as porting guide mentioned?

DDR 较准与压力测试有做，并且回填到了mfgtool firmware 。用的1.03 版本的工具做的测试。

3. Have you got the entire log from the power on to check?

我们有 fsl demo 板，我将demo烧写成功与我们的板烧写不成功的log有做对比，没有从中发现什么问题。

另外：我有尝试mfgtool2-yocto-mx-sabresd-emmc-1.2g.vbs , 就是LDO打开的，现象log一样。

您的邮箱是多少呢？能不能直接给你发邮件？这个问题卡了很久，然后你的回复虽然很及时，但我要过很久才能查看得到。

Re: 定制Uboot报Can't find PMIC:PFUZE100

BiyongSUN — Wed, 04 May 2016 19:55:32 GMT

1. Please use the L4.1.15_1.0.0_ga-mfg-tools to try for your L4.1.15_1.0.0.

Please try this first.

2. CONFIG_LDO_BYPASS_CHECK is the definition in uboot-imx\include\configs\mx6_common.h

If you undefine it, will never see the No PMIC found!

3. How about the VBUS hardware design, it is swiched by usb id or fixed the supply by board?

Because it is blocking at the polulate disk, it could be that reason the VBUS is conflicted with VBUS on PC, which is not isolated the VBUS phyiscally.

You can try to change to another computer to check. and also you can check with the window device manage to see if you have the Updater .

<UCL>

<CFG>

</CFG>

Re: 定制Uboot报Can't find PMIC:PFUZE100

ispsubb — Thu, 05 May 2016 01:05:54 GMT

感谢biyong.sun 的帮助。前面的提到的点都是正确的。

昨天下午得到你们的FAE帮助，问题解决了，这里我mark一下。

关于这一点：

2. CONFIG_LDO_BYPASS_CHECK is the definition in uboot-imx\include\configs\mx6_common.h

If you undefine it, will never see the No PMIC found!

这一点我有去注释掉，但我编译的时候编译不过，bitbake -c compile u-boot-imx-mfgtool

但我在uboot 中注释掉了对pmic 初始化的函数，这样没有卡住在uboot。

另外我们的板，还有一个原因是采用的mini USB ，然后用了一根转接线，而问题就在这根转接线上，这个OTG转来接U盘的。

在L3.0.35是可以的，但在L3.14.52上是不行的。这一点是得到你们同事的确认。最开始有怀疑这根线，就是因为L3.0.35可以烧，就pass掉这一点了。L3.14.52做得更加规范了。

Re: 定制Uboot报Can't find PMIC:PFUZE100

void_ — Wed, 18 May 2016 03:44:40 GMT

你好，我现在也出现了和你一样的情况，用MFG工具烧录5.1的镜像时出现Can't find PMIC:PFUZE100 ，原因就和你的一样没有PMIC，所以能否告知你是如何制作新的MFG工具中uboot固件呢？

Re: 定制Uboot报Can't find PMIC:PFUZE100

ispsubb — Wed, 18 May 2016 09:08:54 GMT

Can't find PMIC:PFUZE100 屏蔽掉相应的代码，就可以了。

加你QQ告诉你

Re: 定制Uboot报Can't find PMIC:PFUZE100

void_ — Thu, 19 May 2016 00:59:38 GMT

QQ469790714 谢谢

Re: 定制Uboot报Can't find PMIC:PFUZE100

BiyongSUN — Thu, 19 May 2016 04:50:25 GMT

You can modify the u-boot/include/configs/mx6_common.h to avoid ldo bypass check, which can fit the discrete power supply.

48 #define CONFIG_LDO_BYPASS_CHECK

49 #undef CONFIG_LDO_BYPASS_CHECK

Re: 定制Uboot报Can't find PMIC:PFUZE100

void_ — Thu, 19 May 2016 06:09:39 GMT

非常谢谢你的回答，但是如何屏蔽Can't find PMIC:PFUZE100 这个问题我已经知道如何处理了，我强调的问题是如何通过源码编译生成MFG中使用的uboot固件

Re: 定制Uboot报Can't find PMIC:PFUZE100

BiyongSUN — Mon, 23 May 2016 04:45:16 GMT

In the BSP 3.10 and later, the uboot is shared with mfg tool.

Re: 定制Uboot报Can't find PMIC:PFUZE100

chenli_2016 — Thu, 28 Jul 2016 08:57:45 GMT

li chao：

你好，我们公司的板子是基于sabresd改的，也出现类似问题，打印信息如下：

U-Boot 2015.04-gf608cff-dirty (Jul 28 2016 - 16:50:55)

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

CPU: Temperature 37 C

Reset cause: POR

Board: MX6-SabreSD

I2C: ready

DRAM: 1 GiB

force_idle_bus: sda=0 scl=0 sda.gp=0x6d scl.gp=0x6c

force_idle_bus: failed to clear bus, sda=0 scl=0

wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020

i2c_init_transfer: failed for chip 0x8 retry=0

wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020

i2c_init_transfer: failed for chip 0x8 retry=1

wait_for_sr_state: Arbitration lost sr=93 cr=80 state=2020

i2c_init_transfer: failed for chip 0x8 retry=2

i2c_init_transfer: give up i2c_regs=021a4000

Can't find PMIC:PFUZE100

initcall sequence 4ff92608 failed at call 17803668 (err=-19)

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

请问你说的:Can't find PMIC:PFUZE100 屏蔽掉相应的代码，就可以了

相应代码的是哪些呢？我的QQ597367138，能告知你的QQ吗？

谢谢！

Re: 定制Uboot报Can't find PMIC:PFUZE100

chenli_2016 — Thu, 28 Jul 2016 09:01:08 GMT

HongBo Liu

你好：

我们公司的板子根据imx6q_sabresd裁剪的，烧写遇到和你相同的问题，请问Can't find PMIC:PFUZE100 这个问题你是怎样解决的？

Re: 定制Uboot报Can't find PMIC:PFUZE100

ygzhou — Thu, 28 Jul 2016 09:40:28 GMT

Hi li chao:

我也遇到同样的问题，Can't find PMIC:PFUZE100，怎么蔽掉相应的代码，能否也告知一下，谢谢

Re: 定制Uboot报Can't find PMIC:PFUZE100

jiepeng — Thu, 28 Jul 2016 19:57:18 GMT

我也遇到同样的问题，只是我已经处理了，遇到新的问题

希望能加qq：281362556 或者wetchat：aiwesky 交流

I got the same problem