Hi,
I have a problem with mfgtool and an iMX28 on a custom board.
I generate updater_ivt.sb with ltib on ubuntu 12.04 and I use mfgtool 1.6.2.048 on windows 7 32bits.
The programming of the board works one time but now it doesn't work.
I have this log from mfgtool :
Friday, November 21, 2014 16:57:56
3 - Panel A Start processing SD Misu <LIST/>.
Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting hab update firmware.".
3 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting hab update firmware." SUCCESS code=0x0.
Panel A Start <CMD/> type="find" body="Updater" file="" timeout="240" onError="" text="".
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A UtpUpdate Event: VolumeArrival Msg: (null) DevState: Updater OpState: WAITING_FOR_DEVICE
3 - Panel A Finished <CMD/> type="find" body="Updater" file="" timeout="240" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ echo Programmation" file="" timeout="10" onError="" text="DONE".
3 - Panel A Finished <CMD/> type="push" body="$ echo Programmation" file="" timeout="10" onError="" text="DONE" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block,mmcblk0,/dev/mmcblk0,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block,mmcblk0,/dev/mmcblk0,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="send" file="files/fdisk.input" timeout="10" onError="" text="Sending fdisk input".
3 - Panel A Finished <CMD/> type="push" body="send" file="files/fdisk.input" timeout="10" onError="" text="Sending fdisk input" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ fdisk -u /dev/mmcblk0 < $FILE" file="" timeout="10" onError="" text="Partitioning SD card".
3 - Panel A Finished <CMD/> type="push" body="$ fdisk -u /dev/mmcblk0 < $FILE" file="" timeout="10" onError="" text="Partitioning SD card" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p1,/dev/mmcblk0p1,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p1,/dev/mmcblk0p1,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p2,/dev/mmcblk0p2,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p2,/dev/mmcblk0p2,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p3,/dev/mmcblk0p3,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p3,/dev/mmcblk0p3,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p5,/dev/mmcblk0p5,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p5,/dev/mmcblk0p5,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p6,/dev/mmcblk0p6,block" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="mknod block/mmcblk0,mmcblk0p6,/dev/mmcblk0p6,block" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ mkfs.vfat /dev/mmcblk0p3" file="" timeout="10" onError="" text="Formatting Linux partition".
3 - Panel A Finished <CMD/> type="push" body="$ mkfs.vfat /dev/mmcblk0p3" file="" timeout="10" onError="" text="Formatting Linux partition" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ mkfs.ext3 /dev/mmcblk0p5" file="" timeout="10" onError="" text="Formatting rootfs partition".
3 - Panel A Finished <CMD/> type="push" body="$ mkfs.ext3 /dev/mmcblk0p5" file="" timeout="10" onError="" text="Formatting rootfs partition" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ mkfs.vfat /dev/mmcblk0p6" file="" timeout="10" onError="" text="Formatting data partition".
3 - Panel A Finished <CMD/> type="push" body="$ mkfs.vfat /dev/mmcblk0p6" file="" timeout="10" onError="" text="Formatting data partition" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ mkdir -p /mnt/mmcblk0p3" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="$ mkdir -p /mnt/mmcblk0p3" file="" timeout="10" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ mount /dev/mmcblk0p3 /mnt/mmcblk0p3" file="" timeout="10" onError="" text="".
3 - Panel A Finished <CMD/> type="push" body="$ mount /dev/mmcblk0p3 /mnt/mmcblk0p3" file="" timeout="10" onError="" text="" FAIL code=0x2000.
Panel A: Reason is unknown,failed to run command: type="push" body="$ mount /dev/mmcblk0p3 /mnt/mmcblk0p3" file="" timeout="10" onError="" text=""
4 - Panel A Finished processing SD Misu <LIST/> : FAIL code=8192.
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A: Reason is unknown,Operation stopped by user. Le processus s
Tuesday, November 25, 2014 11:58:06
1 - Panel A Start processing SD Misu <LIST/>.
Panel A Start <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting hab update firmware.".
1 - Panel A Finished <CMD/> type="boot" body="Recovery" file="updater_ivt.sb" timeout="10" onError="" text="Booting hab update firmware." SUCCESS code=0x0.
Panel A Start <CMD/> type="find" body="Updater" file="" timeout="240" onError="" text="".
Panel A UtpUpdate Event: DeviceRemoval Msg: (null) DevState: Disconnected OpState: WAITING_FOR_DEVICE
Panel A UtpUpdate Event: VolumeArrival Msg: (null) DevState: Updater OpState: WAITING_FOR_DEVICE
1 - Panel A Finished <CMD/> type="find" body="Updater" file="" timeout="240" onError="" text="" SUCCESS code=0x0.
Panel A Start <CMD/> type="push" body="$ echo Programmation" file="" timeout="10" onError="" text="DONE".
1 - Panel A Finished <CMD/> type="push" body="$ echo Programmation" file="" timeout="10" onError="" text="DONE" FAIL code=0xffffffff.
Panel A: Operation is not completed.,failed to run command: type="push" body="$ echo Programmation" file="" timeout="10" onError="" text="DONE"
2 - Panel A Finished processing SD Misu <LIST/> : FAIL code=-1.
Panel A: Reason is unknown,Operation stopped by user. Le processus s
When I plug my board to the computer, I see the device on mfgtool. I click on "START", the download of the firmware works and the board boots with the linux image.
At the end of the boot, I have this message on mfgtool : Operation is not completed,.,failed to run command: type="push" body="$echo Programmation" file="" timeout="10" onError="" text="DONE"
After that, I have a new "mobile device" on windows device manager. And if click on "STOP3, I see Linux File-Stor Gadget USB Device
Is there someone who knows this problem ?
Linux log :
0x8020a01d
HTLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLLFLC
PowerPrep start initialize power...
Battery Voltage = 1.86V
No battery or bad battery detected!!!.Disabling battery vo8
FRAC 0x92925552
memory type is DDR2 - misu
Wait for ddr ready 1 -
power 0x00820616
Frac 0x92925552
start change cpu freq
hbus 0x00000003
cpu 0x00010001
start test external memory access
ddr2 0x40000000
finish simple test
LLLLLLLFLCLFLLJUncompressing Linux... done, booting the kernel.
Linux version 2.6.35.3-670-g914558e (victorien@BENNEVIS-VMTUX1204) (gcc version 4.4.4 (4.4.4_09.06.2010) ) #14 Fri Nov 21 16:54:164
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Ophrys Systemes Misu board rev002
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: -e console=ttyAM0,115200 rdinit=/linuxrc rw gpmi
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 55328k/55328k available, 10208k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xfde00000 - 0xffe00000 ( 32 MB)
vmalloc : 0xc4800000 - 0xf0000000 ( 696 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0027000 ( 124 kB)
.text : 0xc0027000 - 0xc0305000 (2936 kB)
.data : 0xc0306000 - 0xc0324dc0 ( 124 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:288
Console: colour dummy device 80x30
console [ttyAM0] enabled
Calibrating delay loop... 226.09 BogoMIPS (lpj=1130496)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
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@0xc4820000
usb DR wakeup device is registered
IMX usb wakeup probe
audit: cannot initialize inotify handle
bio: create slab <bio-0> at 0
SCSI subsystem initialized
Switching to clocksource mxs clock source
Trying to unpack rootfs image as initramfs...
Freeing initrd memory: 6144K
Bus freq driver module loaded
mxs_cpu_init: cpufreq init finished
audit: initializing netlink socket (disabled)
type=2000 audit(2.100:1): initialized
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 120
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
io scheduler noop registered (default)
Console: switching to colour frame buffer device 100x30
mxs-duart.0: ttyAM0 at MMIO 0x80074000 (irq = 47) is a DebugUART
mxs-auart.0: ttySP0 at MMIO 0x8006a000 (irq = 112) is a mxs-auart.0
Found APPUART 3.1.0
mxs-auart.1: ttySP1 at MMIO 0x8006c000 (irq = 113) is a mxs-auart.1
Found APPUART 3.1.0
mxs-auart.2: ttySP2 at MMIO 0x8006e000 (irq = 114) is a mxs-auart.2
Found APPUART 3.1.0
mxs-auart.3: ttySP3 at MMIO 0x80070000 (irq = 115) is a mxs-auart.3
Found APPUART 3.1.0
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
Loading iSCSI transport class v2.0-870.
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...
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [send_command] DMA error
gpmi-nfc gpmi-nfc.0: [mil_cmd_ctrl] Chip: 0, Error -110
Command Bytes: 90 00
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
gpmi-nfc gpmi-nfc.0: [gpmi_nfc_dma_go] Chip: 0, DMA Channel: 4, Error -110
gpmi-nfc gpmi-nfc.0: [read_data] DMA error
No NAND device found.
gpmi-nfc gpmi-nfc.0: Chip scan failed
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: mxs-kbd as /devices/platform/mxs-kbd.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
WARNING : No battery connected !
Aborting power driver initialization
mxs-battery: probe of mxs-battery.0 failed with error 1
mxs-mmc: MXS SSP Controller MMC Interface driver
mxs-mmc mxs-mmc.0: mmc0: MXS SSP MMC DMAIRQ 82 ERRIRQ 96
mxs-rtc mxs-rtc.0: setting system clock to 1970-01-01 00:01:27 UTC (87)
Freeing init memory: 124K
mmc0: new high speed SDHC card at address 0002
mmcblk0: mmc0:0002 00000 7.41 GiB
mmcblk0:
Starting UTP
ln: /etc/mtab: File exists
disable turn off display
uuc 0.4 [built Nov 18 2014 11:50:23]
UTP: Waiting for device to appear
utp_mk_devnode: creating node '/dev/utp' with 10+222
cpu_id is 28
g_file_storage gadget: high speed config #1
1.
You may try to clear SD card under Linux, using dd command :
$ sudo dd if=/dev/zero of=/dev/sdb bs=1M count=100
2.
Please check if USB3 is used on Your host PC. Some issues were
observed with USB3 and MFG.
Have a great day,
Yuri.
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Your answer 1 is correct. This issue appended when I tested the formating of the SD card with mfgtool. And when I rebooted I still have partition on sd card that was use for mass storage