i.MX ProcessorsのトピックRe: i.MX28 USB-OTG problem

i.MX28 USB-OTG problem

prateekraghuvan — Thu, 29 Nov 2012 07:32:58 GMT

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),

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_UG.pdf PageN0.- 3-21, Table 1. Boot Mode Values).
Connected USB-OTG in device mode to PC.
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.

Re: i.MX28 USB-OTG problem

VladanJovanovic — Tue, 04 Dec 2012 13:36:40 GMT

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

Re: i.MX28 USB-OTG problem

prateekraghuvan — Thu, 06 Dec 2012 11:53:57 GMT

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

Re: i.MX28 USB-OTG problem

prateekraghuvan — Thu, 06 Dec 2012 11:55:34 GMT

^^*Correction I am sorry MT29F1G08ABADAWP is 1GB. I have 1GB NAND on my customized board.

Re: i.MX28 USB-OTG problem

VladanJovanovic — Fri, 07 Dec 2012 08:46:12 GMT

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

Re: i.MX28 USB-OTG problem

prateekraghuvan — Fri, 07 Dec 2012 10:47:37 GMT

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.

Re: i.MX28 USB-OTG problem

prateekraghuvan — Fri, 07 Dec 2012 10:52:07 GMT

I don't see an option here to attach any file other than image. i'll find out a way to send you the log, anyway. Thanks

Re: i.MX28 USB-OTG problem

VladanJovanovic — Mon, 10 Dec 2012 10:22:00 GMT

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

Re: i.MX28 USB-OTG problem

prateekraghuvan — Mon, 10 Dec 2012 13:39:04 GMT

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.

Re: i.MX28 USB-OTG problem

prateekraghuvan — Tue, 11 Dec 2012 15:25:09 GMT

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.

Re: i.MX28 USB-OTG problem

prateekraghuvan — Tue, 11 Dec 2012 15:26:59 GMT

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.

Re: i.MX28 USB-OTG problem

VladanJovanovic — Tue, 11 Dec 2012 17:44:46 GMT

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.

Re: i.MX28 USB-OTG problem

prateekraghuvan — Wed, 12 Dec 2012 10:38:02 GMT

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

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