Hi,
I am working on a board based on i.MX6UL. I am using "MT29F8G08ABABA" nand on i.mx6ul. I am using u-boot version "2015.04". Sometimes I am facing an issue that No NAND device is detected and sometime device is detected.
Can you help us to resolve this issue ASAP ?
Is this issue related to Fail to boot from NAND flash | NXP Community ?
Waiting for response.
/////// Failed to detect NAND log ////////////////////////////
U-Boot 2015.04-imx_v2015.04_3.14.52_1.1.0_ga+g6cf684a (Aug 10 2016 - 11:30:25)
CPU: Freescale i.MX6UL rev1.0 at 396 MHz
CPU: Temperature 24 C
Reset cause: POR
Board: MX6UL Volansys BR
I2C: ready
DRAM: 256 MiB
PMIC: PFUZE3001 DEV_ID=0x31 REV_ID=0x11
NAND: 0 MiB // No Nand device is detected
MMC: Inside FSU_config 0
FSL_SDHC: 0
*** Warning - readenv() failed, using default environment // Failed to read environment from NAND
In: serial
Out: serial
Err: serial
Net: FEC0
Normal Boot
Hit any key to stop autoboot: 0
=> set ethaddr 70:B3:D5:9A:E0:06
=> boot
no devices available
no devices available
Bad Linux ARM zImage magic!
=>
/////////////////////////////////////////
Working log
//////////////////
U-Boot 2015.04-imx_v2015.04_3.14.52_1.1.0_ga+g6cf684a (Aug 10 2016 - 11:30:25)
CPU: Freescale i.MX6UL rev1.0 at 396 MHz
CPU: Temperature 33 C
Reset cause: POR
Board: MX6UL Volansys BR
I2C: ready
DRAM: 256 MiB
PMIC: PFUZE3001 DEV_ID=0x31 REV_ID=0x11
NAND: 1024 MiB
MMC: Inside FSU_config 0
FSL_SDHC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: FEC0
Normal Boot
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x4000000, size 0x800000
8388608 bytes read: OK
NAND read: device 0 offset 0x5000000, size 0x100000
1048576 bytes read: OK
Kernel image @ 0x80800000 [ 0x000000 - 0x55abd0 ]
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300a692
switch to ldo_bypass mode!
Starting kernel ...
/////////////////////////////////////////////////////
-
Thanks,
Dhvanil Patel
Hi Dhvanil
this may be caused by signal integrity issues, so one can inspect
nand lines with oscilloscope and tweak its drive strength. Also one can
try to slightly change nand voltage.
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi igor,
Thank you for your prompt response.
Can you please elaborate more on this signal integrity issue? Which nand single should I inspect ? All data lines or control signals ? The NAND voltage is 3.3V. We are not able to change this voltage.
-
Dhvanil Patel
Hi Dhvanil
yes all data lines or control signals.
Best regards
igor