AnsweredAssumed Answered

MFGTool:Why can't I see the utp starting when burn mx28 board?

Question asked by h k on Dec 8, 2015
Latest reply on Dec 8, 2015 by h k

Hi everyone,

When I use mfgtool burn the mx28evk, the utp module seems abnormal, below is a normal burning process copied from somewhere:

 

mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:00:26 UTC (26)

Freeing init memory: 124K

mxs-kbd mxs-kbd.0: Invalid button: raw = 1085, normalized = 1104, vddio = 3687

Starting UTP

disable turn off display

uuc 0.4 [built Feb 21 2014 08:19:00]

UTP: Waiting for device to appear

utp_mk_devnode: creating node '/dev/utp' with 10+222

cpu_id is 28

mxs-kbd mxs-kbd.0: Invalid button: raw = 1099, normalized = 1132, vddio = 3643

mxs-kbd mxs-kbd.0: Invalid button: raw = 1112, normalized = 1140, vddio = 3661

mxs-kbd mxs-kbd.0: Invalid button: raw = 1125, normalized = 1159, vddio = 3641

g_file_storage gadget: high speed config #1

UTP: received command 'mknod class/mtd,mtd0,/dev/mtd0'

 

while my console log is:

 

Initializing USB Mass Storage driver...

usbcore: registered new interface driver usb-storage

USB Mass Storage support registered.

ARC USBOTG Device Controller driver (1 August 2005)

check_parameters:UTP settings are in place now, overriding defaults

g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008

g_file_storage gadget: Number of LUNs=1

fsl-usb2-udc: bind to driver g_file_storage

mice: PS/2 mouse device common for all mice

input: gpio-keys as /devices/platform/gpio-keys.0/input/input0

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

MXS RTC driver v1.0 hardware v2.3.0

mxs-rtc mxs-rtc.0: rtc core: registered mxs-rtc as rtc0

i2c /dev entries driver

IR NEC protocol handler initialized

IR RC5(x) protocol handler initialized

IR RC6 protocol handler initialized

IR JVC protocol handler initialized

IR Sony protocol handler initialized

Linux video capture interface: v2.00

This is 5V only build.

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

leds-gpio: probe of leds-gpio failed with error -16

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:59 UTC (59)

Freeing init memory: 180K

init started: BusyBox v1.15.0 ()

starting pid 1090, 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 1117, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1117) exited. Scheduling for restart.

starting pid 1118, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

process '/sbin/getty -L ttyAM0 115200 vt100' (pid 1118) exited. Scheduling for restart.

starting pid 1119, tty '': '/sbin/getty -L ttyAM0 115200 vt100'

 

 

Thanks in advance.

Outcomes