i.MX28 USB-OTG problem

cancel
Showing results for 
Search instead for 
Did you mean: 

i.MX28 USB-OTG problem

Jump to solution
6,010 Views
prateekraghuvan
Contributor II

Hi,

     I used IMX_MFG_TOOL to program nand flash for i.MX28.

Connected - i.MX28 EVK Board Connected using USB-OTG to PC. PC detected it as HID complaint Device and i am successfully able to

update the nand flash using IMX_MFG_TOOL. Now, when i connect my customized i.MX28 hardware Board (similar to EVK Board), PC detects it as

Unknown device though i use same device driver supplied in IMX_MFG_TOOL software.

I followed these steps (on customized hardware),

  1. Selected Boot Mode as USB (iMX28_BSP_UG.pdf- http://elk.informatik.fh-augsburg.de/gnublin-cdrom/Linux/L2.6.35_10.12.01_SDK_docs/i.MX28_Linux_BSP_...  PageN0.- 3-21, Table 1. Boot Mode Values).
  2. Connected USB-OTG in device mode to PC.
  3. Updated device driver (PC side) with the one supplied in software package - Mfgtools-Rel-1.6.2.042 from freescale.

Result - PC detects my customized board as Unknown device.

my question is am i missing any step or configuration, which is there in EVK Board and not on my customized Board, Or is it something else?

Any help would be appreciated, Thanks in advance.

Labels (1)
Tags (1)
0 Kudos
1 Solution
297 Views
VladanJovanovic
NXP Employee
NXP Employee

It might work, but I’m not sure as I never tried it like that. I think zImage for “Manufacturing Firmware” profile also has some options enabled that are required for proper operation and it could be much bigger than what is really needed. So probably makes sense to do have a separate LTIB setup for updater firmware binary.

View solution in original post

0 Kudos
27 Replies
240 Views
ashwineedhakate
Contributor I

Anybody can tell me where I ll get the source code of this USB-OTG recovery mode?

0 Kudos
240 Views
prateekraghuvan
Contributor II

Approach to generate updater image in new LTIB installation did work fine for me. Thanks to Vladan for his tremendous help and technical support.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

Does your customized board work otherwise? Have you verified it powers on properly etc.? This may be caused by i.MX28 not being powered on properly, and thus internal ROM is not executed (to initialize device and USB connection for programming).

0 Kudos
251 Views
prateekraghuvan
Contributor II

Thanks for reply....Now i PC can detect it as HID complaint device. But when i try to program NAND flash using IMX_MFG_TOOL, it exits with an error saying device not connected. Below is the log for the session.

Thursday, December 06, 2012 15:57:00

1 - Panel A Start processing Singlechip NAND <LIST/>.1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware.".1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware." SUCCESS code=0.1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware.".1 - Panel A DoBoot() - Failed to load updater_ivt.sb to Recovery mode device. (err=1167)1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware." FAIL code=1167.Panel A: Updater Error 0x48f (1167) - The device is not connected.2 - Panel A Finished processing Singlechip NAND <LIST/> : FAIL code=1167.

Also, there is MT29F4G08ABADAWP which is 4GB NAND on EVK Board, Whereas i am having MT29F1G08ABADAWP which is 4GB NAND. Please suggest me, where am i going wrong...

0 Kudos
240 Views
dongh
Contributor I

Hi there, I came across a similar problem. Basically, for my customized board with iMX280, I am unable to connect the iMX280 USB to a PC in USB recovery mode. The PC detects it as an unknown device. By probing the D+ line, I can see it is pulled high by iMX280 for 240ms, then goes low with a packet of 68ms. But nothing happens after that and eventually and the D+ line stays low. After a while, the D+ line goes high again and stay high.

The power rails seems to be okay as compared to the iMX28 EVK.

I can see you have the same problem initially (USB unknown device). How do you get it resolved?

0 Kudos
240 Views
fluiss
Contributor I

Hi Dong,

I found the same problem regarding the USB in my custom board. Did you fix it??

Thank you!!

0 Kudos
240 Views
dongh
Contributor I

Hi Fernando,

I have resolved the issue. What happened to my board is, we added a USB upstream terminator between the iMX280 USB controller and the USB connector. This USB upstream terminator is the problem. After removing it and wiring the D+ and D- line directly to the USB connector, the problem is fixed and iMX280 can be detected in USB recovery mode using the factory tool.


Best Regards,

Dong

0 Kudos
240 Views
fluiss
Contributor I

Hi Dong,

Thank you very much for answering me. So you removed all the resistors from the USB circuit (Rs's and the R to Vbus), and the ESD protections as well??

Many thanks again. BR,

Fernando

El 13/02/2013, a las 23:07, Dong Hui escribió:

i.MX28 USB-OTG problem

created by Dong Hui in i.MX Community - View the full discussion

Hi Fernando,

I have resolved the issue. What happened to my board is, we added a USB upstream terminator between the iMX280 USB controller and the USB connector. This USB upstream terminator is the problem. After removing it and wiring the D+ and D- line directly to the USB connector, the problem is fixed and iMX280 can be detected in USB recovery mode using the factory tool.

Best Regards,

Dong

Reply to this message by replying to this email -or- go to the message on Freescale Community

Start a new discussion in i.MX Community by email or at Freescale Community

0 Kudos
240 Views
dongh
Contributor I

First of all, you don't need 1.5K pull-up on D+ line to Vbus. This is built into iMX280.

Secondly, what I found is, the resistance (~22R) and capacitances (~30pF) which behaves as the EMI filter on the D+ and D- lines, would cause the USB interface to fail (signal distortion).

Lastly, ESD protection is still required. Just use the same one or similar one in the reference design.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

What do you get on the debug serial port? That's usually quite informative and helpful to see what goes wrong.

0 Kudos
251 Views
prateekraghuvan
Contributor II

I am able to see the debug prints your talking about in EVK only,but i am not able to see it on customized board. Also i have attached the log of USBanalyzer report for communication between PC to EVK and PC to my board. Please let me know if it is informative.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

Why are you not able to see debug prints on your own i.MX28 board - no debug serial port or it doesn't work?

Have you modified MfgTool updater firmware so that it can run on your board? MfgTool load small linux kernel (updater firmware) to target board (i.MX28EVK or your own custom board) so it can do the programming. Default updater firmware works on i.MX28EVK, but may not work on your own board (for example, if different memory is used) and needs to be built from LTIB (there's an option for that).

0 Kudos
251 Views
prateekraghuvan
Contributor II

Debug prints are enabled on my Board, but i am not getting any debug prints in this case, i am unable to figure out why?

I'll try to build my firmware for my board, and get back to you with the results.

Thanks.

0 Kudos
251 Views
prateekraghuvan
Contributor II

I tried to generate mfgtool firmware using LTIB (for my kernel source) and got some success. Log is attached below:

Tuesday, December 11, 2012 20:39:01

1 - Panel A Start processing Singlechip NAND <LIST/>.

1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware.".

1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware." SUCCESS code=0.

1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware.".

1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware." SUCCESS code=0.

1 - Panel A Start <CMD/> type="push" body="mknod class/mtd,mtd0,/dev/mtd0" file="" timeout="10" onError="" text="".

looks like there is a timeout happening, while it detects the update, is it not able to detect NAND on board ? Still not getting any debug prints. Thanks.

0 Kudos
251 Views
prateekraghuvan
Contributor II

The updated log is as follows :

Tuesday, December 11, 2012 20:34:40

1 - Panel A Start processing Singlechip NAND <LIST/>.

1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware.".

1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="60" onError="" text="Booting update firmware." SUCCESS code=0.

1 - Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware.".

1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="60" onError="" text="Booting update firmware." SUCCESS code=0.

1 - Panel A Start <CMD/> type="find" body="Updater" file="" timeout="180" onError="" text="".

1 - Panel A Finished <CMD/> type="find" body="Updater" file="" timeout="180" onError="" text="" FAIL code=-65536.

Panel A: Updater Error 0xffff0000 (-65536) -

2 - Panel A Finished processing Singlechip NAND <LIST/> : FAIL code=-65536.

Panel A: Operation stopped by user.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

Please see why debug UART is not working:

- where is it connected (AUART0, I2C0 or PWM pins)?

- are fuses in i.MX28 burned accordingly (USE_ALT_DEBUG_UART_PINS)?

Already internal ROM should be printing out on that port so it's extremely useful for debugging. And it's much more informative than output from MfgTool itself.

0 Kudos
251 Views
prateekraghuvan
Contributor II

Here is the debug print log :

PowerPrep start initialize power...

Configured for 5v only power source. Battery powered operation disabled.

LLLCOct 30 201217:58:53

FRAC 0x92925552

memory type is DDR2

Wait for ddr ready 1power 0x00820616

Frac 0x92925552

start change cpu freq

hbus 0x00000003

cpu 0x00010001

start test memory accress

ddr2 0x40000000

finish simple test

LLLLLLLFLCLFLLJUncompressing Linux... done, booting the kernel.

VEN--> init/main.c 541

Linux version 2.6.35.3-571-gcca29a0 (hari@MELANGE) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #3 PREEMPT Wed Dec 12 14:59:53 IST 2012

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177

CPU: VIVT data cache, VIVT instruction cache

Machine: Freescale MX28EVK board

Memory policy: ECC disabled, Data cache writeback

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

Kernel command line: console=ttyAM0,115200 rdinit=/linuxrc rw gpmi

PID hash table entries: 512 (order: -1, 2048 bytes)

Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)

Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)

Memory: 128MB = 128MB total

Memory: 119636k/119636k available, 11436k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    DMA     : 0xfde00000 - 0xffe00000   (  32 MB)

    vmalloc : 0xc8800000 - 0xf0000000   ( 632 MB)

    lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)

    modules : 0xbf000000 - 0xc0000000   (  16 MB)

      .init : 0xc0008000 - 0xc0046000   ( 248 kB)

      .text : 0xc0046000 - 0xc056a000   (5264 kB)

      .data : 0xc056a000 - 0xc05a5e40   ( 240 kB)

SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

Hierarchical RCU implementation.

  RCU-based detection of stalled CPUs is disabled.

  Verbose stalled-CPUs detection is disabled.

NR_IRQS:296

Console: colour dummy device 80x30

console [ttyAM0] enabled

Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)

pid_max: default: 32768 minimum: 301

Security Framework initialized

SELinux:  Initializing.

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

devtmpfs: initialized

regulator: core version 0.5

NET: Registered protocol family 16

regulator: vddd: 800 <--> 1575 mV at 1500 mV fast normal

regulator: vdddbo: 800 <--> 1575 mV fast normal

regulator: vdda: 1500 <--> 2275 mV at 1800 mV fast normal

vddio = 3380000, val=10

regulator: vddio: 2880 <--> 3680 mV at 3380 mV fast normal

regulator: overall_current: fast normal

regulator: vbus5v:

regulator: mxs-duart-1: fast normal

regulator: mxs-bl-1: fast normal

regulator: mxs-i2c-1: fast normal

regulator: mmc_ssp-1: fast normal

regulator: mmc_ssp-2: fast normal

regulator: charger-1: fast normal

regulator: power-test-1: fast normal

regulator: cpufreq-1: fast normal

i.MX IRAM pool: 124 KB@0xc8820000

Initializing GPMI pins

VEN--> arch/arm/mach-mx28/device.c 754 mx28_init_mmc MMC0 is enabled

usb DR wakeup device is registered

IMX usb wakeup probe

audit: cannot initialize inotify handle

bio: create slab <bio-0> at 0

GCD register_devices:371

EEPROM MISC is Register

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

Advanced Linux Sound Architecture Driver Version 1.0.23.

Switching to clocksource mxs clock source

NET: Registered protocol family 2

IP route cache hash table entries: 1024 (order: 0, 4096 bytes)

TCP established hash table entries: 4096 (order: 3, 32768 bytes)

TCP bind hash table entries: 4096 (order: 2, 16384 bytes)

TCP: Hash tables configured (established 4096 bind 4096)

TCP reno registered

UDP hash table entries: 256 (order: 0, 4096 bytes)

UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

NET: Registered protocol family 1

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

rootfs image is not initramfs (junk in compressed archive); looks like an initrd

Freeing initrd memory: 4096K

Bus freq driver module loaded

IMX usb wakeup probe

usb h1 wakeup device is registered

GCD drivers/gpio/pca953x.c:207:8

Probing at24_probe ..

page_size 16, num_addresses 4, write_max 16, use_smbus 0

at24 Reading ...

Done

mxs_cpu_init: cpufreq init finished

audit: initializing netlink socket (disabled)

type=2000 audit(0.750:1): initialized

VFS: Disk quotas dquot_6.5.2

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

squashfs: version 4.0 (2009/01/31) Phillip Lougher

JFS: nTxBlock = 966, nTxLock = 7733

msgmni has been set to 241

alg: No test for stdrng (krng)

cryptodev: driver loaded.

Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

LVDS GPIO 21

GCD init_panel:80

lcdif_set_rate:1157

GCD: init_bl:246

GCD mxsbl_set_intensity:239

GCD set_bl_intensity:316: Intensity 50

GCD bl_to_power:298

GCD bl_to_power:298

SIVA: drivers/video/fbmem.c fb_prepare_logo 575

SIVA: drivers/video/fbmem.c fb_prepare_logo 593

SIVA: drivers/video/fbmem.c fb_prepare_logo 600

SIVA: drivers/video/fbmem.c fb_prepare_logo 636

Console: switching to colour frame buffer device 60x34

SIVA: drivers/video/fbmem.c fb_show_logo_line 434

SIVA: drivers/video/fbmem.c fb_show_logo_line 473

SIVA: drivers/video/fbmem.c fb_do_show_logo 398

GCD blank_panel:196

GCD release_panel:185

GCD free_bl:270

GCD init_panel:80

lcdif_set_rate:1157

GCD: init_bl:246

GCD mxsbl_set_intensity:239

GCD set_bl_intensity:316: Intensity 50

GCD bl_to_power:298

GCD bl_to_power:298

GCD blank_panel:196

IMX28 LRADC Temperature Driver Version 1 (C)

IMX28 LRADC Temperature Driver Version 1 (C) GCD

IMX28 LRADC Temperature Driver is Register with Minor number 1

mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART

------------------ROHIT  : recent ---------------

mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0

Found APPUART 3.1.0

------------------ROHIT  : recent ---------------

mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1

Found APPUART 3.1.0

------------------ROHIT  : recent ---------------

mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2

Found APPUART 3.1.0

------------------ROHIT  : recent ---------------

mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3

Found APPUART 3.1.0

------------------ROHIT  : recent ---------------

mxs-auart.4: ttySP4 at MMIO 0x80072000 (irq = 116) is a mxs-auart.4

Found APPUART 3.1.0

brd: module loaded

loop: module loaded

Misc MDB Device driver

MISC MDBD Driver is registered

i.MX GPMI NFC

NFC: Version 1, 8-chip GPMI and BCH

Boot ROM: Version 1, Single-chip boot area, block mark swapping supported

Scanning for NAND Flash chips...

NAND device: Manufacturer ID: 0x2c, Chip ID: 0xf1 (Micron NAND 128MiB 3,3V 8-bit)

mfr_id 2c

nand_device_mfr_directory[0].id:  98

nand_device_mfr_directory[1].id:  ec

nand_device_mfr_directory[2].id:  4

nand_device_mfr_directory[3].id:  8f

nand_device_mfr_directory[4].id:  7

nand_device_mfr_directory[5].id:  20

nand_device_mfr_directory[6].id:  ad

nand_device_mfr_directory[7].id:  2c

attempt identify device

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

NAND Flash Device Information

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

Manufacturer      : Micron (0x2c)

Device Code       : 0xf1

Cell Technology   : SLC

Chip Size         : 128 MiB

Pages per Block   : 64

Page Geometry     : 2048+64

ECC Strength      : 4 bits

ECC Size          : 512 B

Data Setup Time   : 30 ns

Data Hold Time    : 20 ns

Address Setup Time: 10 ns

GPMI Sample Delay : 6 ns

tREA              : Unknown

tRLOH             : Unknown

tRHOH             : Unknown

Description       : <None>

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

Physical Geometry

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

Chip Count             : 1

Page Data Size in Bytes: 2048 (0x800)

Page OOB Size in Bytes : 64

Block Size in Bytes    : 131072 (0x20000)

Block Size in Pages    : 64 (0x40)

Chip Size in Bytes     : 134217728 (0x8000000)

Chip Size in Pages     : 65536 (0x10000)

Chip Size in Blocks    : 1024 (0x400)

Medium Size in Bytes   : 134217728 (0x8000000)

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

NFC Geometry

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

ECC Algorithm          : BCH

ECC Strength           : 8

Page Size in Bytes     : 2112

Metadata Size in Bytes : 10

ECC Chunk Size in Bytes: 512

ECC Chunk Count        : 4

Payload Size in Bytes  : 2048

Auxiliary Size in Bytes: 16

Auxiliary Status Offset: 12

Block Mark Byte Offset : 1999

Block Mark Bit Offset  : 0

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

Boot ROM Geometry

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

Boot Area Count            : 1

Boot Area Size in Bytes    : 20971520 (0x1400000)

Stride Size in Pages       : 64

Search Area Stride Exponent: 2

Scanning device for bad blocks

Boot area protection is enabled.

uboot    : c04f0c3d

u-boot env  : 0

kern1    : 0 fs1    : 1e0000 kern2    : 0 fs2    : 200000 application : 0

Creating 7 MTD partitions on "gpmi-nfc-main":

0x000000000000-0x0000001e0000 : "u-boot"

0x0000001e0000-0x000000200000 : "u-boot-env"

0x000000200000-0x000000700000 : "kern1"

0x000000700000-0x000002f00000 : "fs1"

0x000002f00000-0x000003400000 : "kern2"

0x000003400000-0x000005c00000 : "fs2"

0x000005c00000-0x000008000000 : "gpmi-nfc-general-use"

PPP generic driver version 2.4.2

PPP Deflate Compression module registered

usbcore: registered new interface driver asix

usbcore: registered new interface driver cdc_ether

usbcore: registered new interface driver net1080

usbcore: registered new interface driver cdc_subset

usbcore: registered new interface driver zaurus

usbcore: registered new interface driver MOSCHIP usb-ethernet driver

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

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

fsl-ehci fsl-ehci: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci: new USB bus registered, assigned bus number 1

fsl-ehci fsl-ehci: irq 93, io base 0x80080000

fsl-ehci fsl-ehci: USB 2.0 started, EHCI 1.00

usb usb1: New USB device found, idVendor=1d6b, idProduct=0002

usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb1: Product: Freescale On-Chip EHCI Host Controller

usb usb1: Manufacturer: Linux 2.6.35.3-571-gcca29a0 ehci_hcd

usb usb1: SerialNumber: fsl-ehci

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

can't find transceiver

fsl-ehci fsl-ehci: init fsl-ehci fail, -19

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

GCD blank_panel:196

fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller

fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 2

fsl-ehci fsl-ehci.0: irq 92, io base 0x80090000

fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00

usb usb2: New USB device found, idVendor=1d6b, idProduct=0002

usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

usb usb2: Product: Freescale On-Chip EHCI Host Controller

usb usb2: Manufacturer: Linux 2.6.35.3-571-gcca29a0 ehci_hcd

usb usb2: SerialNumber: fsl-ehci.0

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

usbcore: registered new interface driver cdc_acm

cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

usbcore: registered new interface driver usbserial

usbserial: USB Serial Driver core

USB Serial support registered for Sierra USB modem

usbcore: registered new interface driver sierra

sierra: v.1.7.16:USB Driver for Sierra Wireless USB modems

ARC USBOTG Device Controller driver (1 August 2005)

Can't find OTG driver!

mice: PS/2 mouse device common for all mice

input: MXS touchscreen as /devices/virtual/input/input0

rtc-pcf8563 1-0051: chip found, driver version 0.4.3

rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc0

i2c /dev entries driver

Linux video capture interface: v2.00

mxs-pxp mxs-pxp.0: initialized

mxs watchdog: initialized, heartbeat 19 sec

mxs-mmc: MXS SSP Controller MMC Interface driver

__mxs_reset_block(f0010000): timeout when resetting

mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96

dcp dcp.0: DCP crypto enabled.!

usbcore: registered new interface driver snd-usb-audio

ALSA device list:

  No soundcards found.

TCP cubic registered

NET: Registered protocol family 17

rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.

rtc-pcf8563 1-0051: setting system clock to 2000-04-11 06:00:39 UTC (955432839)

RAMDISK: Couldn't find valid RAM disk image starting at 0.

Root-NFS: No NFS server available, giving up.

VFS: Unable to mount root fs via NFS, trying floppy.

VFS: Cannot open root device "(null)" or unknown-block(2,0)

Please append a correct "root=" boot option; here are the available partitions:

1f00            1920 mtdblock0 (driver?)

1f01             128 mtdblock1 (driver?)

1f02            5120 mtdblock2 (driver?)

1f03           40960 mtdblock3 (driver?)

1f04            5120 mtdblock4 (driver?)

1f05           40960 mtdblock5 (driver?)

1f06           36864 mtdblock6 (driver?)

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)

Backtrace:

[<c004a60c>] (dump_backtrace+0x0/0x114) from [<c0431af0>] (dump_stack+0x18/0x1c)

r7:c04ec77d r6:00008000 r5:c77f1000 r4:c05a6d28

[<c0431ad8>] (dump_stack+0x0/0x1c) from [<c0431b6c>] (panic+0x78/0xf4)

[<c0431af4>] (panic+0x0/0xf4) from [<c0009048>] (mount_block_root+0x1d8/0x218)

r3:00000000 r2:00000001 r1:c7c27f60 r0:c04ec824

[<c0008e70>] (mount_block_root+0x0/0x218) from [<c000914c>] (mount_root+0xc4/0xfc)

[<c0009088>] (mount_root+0x0/0xfc) from [<c00092f0>] (prepare_namespace+0x16c/0x1d0)

r5:c002a4c8 r4:c05a6100

[<c0009184>] (prepare_namespace+0x0/0x1d0) from [<c00084f8>] (kernel_init+0x128/0x174)

r5:c002a4c8 r4:c05a5ec0

[<c00083d0>] (kernel_init+0x0/0x174) from [<c0068aac>] (do_exit+0x0/0x750)

r5:c00083d0 r4:00000000

...looks like my kernel configuration in LTIB is different then which is required to program NAND. Thanks.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

What are you booting here - updater firmware kernel on your custom board, or is this "full" Linux kernel you'd like to boot on your custom board?

In any case, kernel is not able to find root partition to mount. Where is it stored?

In case this is updater firmware, there should be initramfs stored after the linux kernel.

In case this is  full kernel, you should pass a "root=" parameter to kernel to tell it where to locate file system on (NAND, SD, NFS...).

251 Views
prateekraghuvan
Contributor II

Thanks for reply Vladan, It is updater firmware..and if you check log for custom Board, in line no. 99 and 100 you will see:

"

Trying to unpack rootfs image as initramfs...

rootfs image is not initramfs (junk in compressed archive); looks like an initrd

" ... I don't understand why is it saying that because this initramfs is generated from a LTIB option only..Any idea.

0 Kudos
251 Views
VladanJovanovic
NXP Employee
NXP Employee

Not sure either. Did you generate updater binary from a separate LTIB installation or from the same one where you build your normal Linux environment?

From what I know updater binary should be built from separate install, as then you choose Manufacturing firmware profile very early during one of first LTIB setup screen. It won't work otherwise I believe.