Hi all,
when burn the board through otg port, the process fail.
partial console trace is :
dcp dcp.0: DCP crypto enabled.!
usbcore: registered new interface driver hiddev
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
regulator_init_complete: incomplete constraints, leaving vbus5v on
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:27 UTC (27)
Freeing init memory: 176K
init started: BusyBox v1.15.0 ()
starting pid 1082, tty '': '/etc/rc.d/rcS'
Mounting /proc and /sys
Setting the hostname to freescale
Mounting filesystems
mount: mounting shm on /dev/shm failed: No such file or directory
mount: mounting usbfs on /proc/bus/usb failed: No such file or directory
Starting inetd:
starting pid 1109, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1109) exited. Scheduling for restart.
starting pid 1110, tty '': '/sbin/getty -L ttyAM0 115200 vt100'
process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1110) exited. Scheduling for restart.
MFGTOOL log and the ucl.xml contents are:
Friday, December 04, 2015 17:34:05
1 - Panel A Start processing SPI-NOR (kernel only) <LIST/>.
Panel A Start <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="10" onError="" text="Booting update firmware.".
1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater.sb" timeout="10" onError="" text="Booting update firmware." SUCCESS code=0x0.
Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting update firmware.".
1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting update firmware." SUCCESS code=0x0.
Panel A Start <CMD/> type="find" body="Updater" file="" timeout="180" onError="" text="".
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A Current state: 10
1 - Panel A Finished <CMD/> type="find" body="Updater" file="" timeout="180" onError="" text="" FAIL code=0xffff0006.
Panel A: Operation is timeout.,failed to run command: type="find" body="Updater" file="" timeout="180" onError="" text=""
2 - Panel A Finished processing SPI-NOR (kernel only) <LIST/> : FAIL code=-65530.
Panel A: Reason is unknown,
<LIST name="SPI-NOR (kernel only)" desc="test">
<CMD type="boot" body="Recovery" file="updater.sb" if="HabDisable">Booting update firmware.</CMD>
<CMD type="boot" body="Recovery" file="updater_ivt.sb" if="HabEnable">Booting update firmware.</CMD>
<CMD type="find" body="Updater" timeout="180">
<CMD type="push" body="mknod class/mtd,mtd1,/dev/mtd1"/>
<CMD type="push" body="$ flash_eraseall /dev/mtd1">Erasing kernel partition</CMD>
<CMD type="push" body="send" file="files/imx28_ivt_linux.sb">Sending kernel</CMD>
<CMD type="push" body="$ dd if=$FILE of=/dev/mtd1">Programming kernel</CMD>
<CMD type="push" body="$ echo Update Complete!">Done</CMD>
</LIST>
Could be the usb driver's problem or something else? What does the find command exactly do during the 180 seconds waiting?
Many thanks
