imx6ul custom board nand programming

[chandraevolute]

I am having a custom board based on IMX6UL, we are using NAND. I have modified all the changes mentioned in 

How-To use NAND boot on i.MX6UL EVK board this page

Below is the Log which I got from debug port.It is not proceeding further Starting Kernel. QAfter this mfgtool says "No device connected". Can anyone point what may be the issue.

U-Boot 2015.04-imx_v2015.04_3.14.38_6ul_ga+g5d63276 (Nov 08 2016 - 10:04:09)

CPU: Freescale i.MX6UL rev1.0 at 396 MHz
CPU: Temperature 44 C
Reset cause: POR
Board: PLUM
I2C: ready
DRAM: 512 MiB
NAND: 128 MiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: Phy 1 not found
PHY reset timed out
FEC1
Error: FEC1 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 @ 0x80800000 [ 0x000000 - 0x529378 ]
## Loading init Ramdisk from Legacy Image at 83800000 ...
Image Name: fsl-image-mfgtool-initramfs-imx_
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7485694 Bytes = 7.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300b82b

Starting kernel ...

[igorpadykov]

is it working without nand ?

with mfg tool without nand, is there "No device connected" error ?

[chandraevolute]

We have only NAND interface, we dont have SDCard. 

Now we are able to pass through Starting kernel. And struck at UTP waiting for device to appear. Below is the kernel log while programming to NAND

io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
imx-weim 21b8000.weim: Driver registered.
Serial: IMX driver
2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58, base_baud = 5000000) is a IMX
console [ttymxc0] enabled
21e8000.serial: ttymxc1 at MMIO 0x21e8000 (irq = 59, base_baud = 5000000) is a IMX
serial: Freescale lpuart driver
imx sema4 driver is registered.
brd: module loaded
loop: module loaded
snvs_rtc 20cc034.snvs-rtc-lp: rtc core: registered 20cc034.snvs-rtc-lp as rtc0
i2c /dev entries driver
imx2-wdt 20bc000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)
cpu cpu0: dev_pm_opp_get_opp_count: device OPP not found (-19)
Registering SWP/SWPB emulation handler
VSD_3V3: disabling
can-3v3: disabling
regulator-dummy: disabling
snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 17:51:32 UTC (64292)
clk: Not disabling unused clocks
Freeing unused kernel memory: 268K (80479000 - 804bc000)
Starting UTP
uuc 0.5 [built Aug 18 2015 20:29:48]
UTP: Waiting for device to appear

[igorpadykov]

"UTP: Waiting for device to appear"

means that usb module is not working. One

can try for example run uboot with jtag and test

usb in uboot. Additionally run linux with tftp from uboot

and check usb in linux.

Best regards
igor

[chandraevolute]

Hi Igor

I am able to flash the images to my custom board using NAND-128Mb. 

Thanks for your kind support

[igorpadykov]

Hi chandra

if this is new custom board first please run ddr test

https://community.freescale.com/docs/DOC-105652 

find new board calibration coefficients and update uboot *.cfg file in

uboot-imx.git - Freescale i.MX u-boot Tree 

then rebuild mfg tools firmware using attached Yocto Guide

sect.6.2 Manufacturing Tool, MFGTool and replace new files in

folder ..OS Firmware/firmware.

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

[chandraevolute]

Hi igorpadykov‌

Followed the steps you mentioned but still having the same issue...

It is hanging at "Starting Kernel" and Mfgtool says No device connected 

[igorpadykov]

"No device connected" issue is not related to nand, please

recheck all steps and make fresh build of firmware.

Also check that USB_ID is float or high state.

[chandraevolute]

hi igorpadykov‌

I am facing the same issue which is in this link

mfgtool stops with "No Device Connected" with "Failure Rate: 0%". 

[igorpadykov]

please remove nand from build configuration and test

if "No device connected" error will disappear

~igor

[chandraevolute]

Hi igorpadykov‌

As of now the USB_ID is float. What should be the USB_ID state??

[chandraevolute]

Can any one help

[igorpadykov]

had board passed ddr test, if yes, is it able to boot

from sd card, full image can be written to sd on host machine

sudo dd if=<image name>.sdcard of=/dev/sdx bs=1M && sync

[chandraevolute]

Yes baord has passed both DDR3 calibration and Stress test. Images I am not able to program Images to NAND Below is the log while programming images to the NAND. After some time MfgTool displays "No device connected". We have only NAND and there is no SD card slot in our custom board, attached is the log from Mfgtool

U-Boot 2015.04-imx_v2015.04_3.14.38_6ul_ga+g5d63276 (Nov 08 2016 - 10:04:09)

CPU: Freescale i.MX6UL rev1.0 at 396 MHz
CPU: Temperature 44 C
Reset cause: POR
Board: PLUM
I2C: ready
DRAM: 512 MiB
NAND: 128 MiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

Display: TFT43AB (480x272)
Video: 480x272x24
In: serial
Out: serial
Err: serial
Net: Phy 1 not found
PHY reset timed out
FEC1
Error: FEC1 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 @ 0x80800000 [ 0x000000 - 0x529378 ]
## Loading init Ramdisk from Legacy Image at 83800000 ...
Image Name: fsl-image-mfgtool-initramfs-imx_
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7485694 Bytes = 7.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 83000000
Booting using the fdt blob at 0x83000000
Using Device Tree in place at 83000000, end 8300b82b

Starting kernel ...