查看: 5288|回复: 3

[已解决] imx6烧写Linux系统出错

[复制链接]

该用户从未签到

1

主题

2

帖子

0

新手上路

Rank: 1

积分
9
最后登录
2017-4-14
发表于 2017-4-13 17:35:14 | 显示全部楼层 |阅读模式
本帖最后由 小智MM 于 2017-4-18 17:30 编辑

在淘宝买的MY-IMX6-CB314开发板,根据烧写手册http://wiki.myzr.com.cn/index.ph ... E5.92.8CPC.E6.9C.BA
用MfgTool往板子上烧写程序时报错,MfgTool.log日志如下:
DLL version: 2.6.2
Thursday, April 13, 2017 17:13:47   Start new logging
ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[040F1FF0]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[040F7378]
ModuleID[2] LevelID[1]: new MxHidDeviceClass
ModuleID[2] LevelID[10]: new MxHidDevice[04100340]
ModuleID[2] LevelID[10]: Device Manager thread is running
ModuleID[2] LevelID[1]: Can't set m_hStopEvent before it initialized or it already stop

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0
ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is F:\ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is F:\ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is F:\ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0
ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]
ModuleID[2] LevelID[10]: *********MxHidDevice[04100340] Jump to Ramkernel successfully!**********
ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&ID_0054#5&521a615&0&10#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&ID_0054#5&521a615&0&10#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&ID_0054\5&521A615&0&10, _deviceInstanceID: USB\VID_15A2&ID_0054\5&521A615&0&10
ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:1-Port:10
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT, Notify
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Remove
ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceRemoveEvent.
ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device remove1
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set
ModuleID[2] LevelID[10]: delete MxHidDevice[04100340]
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_066F&ID_37FF#5&521a615&0&10#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_066F&ID_37FF#5&521a615&0&10#{a5dcbf10-6530-11d2-901f-00c04fb951ed})
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[Msc,DiskDeviceClass] vid_066f&pid_37ff, not handled
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - VOLUME_ARRIVAL_EVT(H)
ModuleID[2] LevelID[10]: DeviceManager:evChangeWnd::OnDeviceChange() - end
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT(H)
ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice()  H
ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1
ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:1
ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 0410CAD0
ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 10
ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice() successful H add to current list, retrycount: 0
ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 10
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT-Disk(H), Hub:1-Port:10
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT, Notify
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh
ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive
ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.
ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1
ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 1
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ flash_erase /dev/mtd0 0 0
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send
ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=$FILE of=/dev/mtd0 bs=512
ModuleID[2] LevelID[1]: PortMgrDlg(0)--MSCDevice--Command Push(no file) excute failed
ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)
ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed
ModuleID[2] LevelID[10]: CCmdOpreation[0] thread is Closed
ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - EVENT_KILL
ModuleID[2] LevelID[10]: CMyExceptionHandler::OnMsgExceptionEvent() - KillExceptionHandlerThread
ModuleID[2] LevelID[10]: Exception Handler thread is closed
ModuleID[2] LevelID[1]: delete MxHidDeviceClass
ModuleID[2] LevelID[10]: Device Manager thread is closed


请问是哪个地方出错,如何解决?
我知道答案 目前已有3人回答
回复

使用道具 举报

该用户从未签到

1

主题

2

帖子

0

新手上路

Rank: 1

积分
9
最后登录
2017-4-14
 楼主| 发表于 2017-4-13 17:39:03 | 显示全部楼层
[profiles]
chip = Linux

[platform]
board = MY-IMX6

[LIST]
# 请根据需要烧录的系统选择其中一项 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
name = Linux-3.0.35
#name = Linux-3.14.52
#name = Android-4.2.2
#name = Android-4.4.2
#name = Android-5.1.1
#name = Ubuntu-11.10
#name = Ubuntu-12.04

[variable]
# 请根据评估板主型号选择其中一项 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#ek_name = myimx6ek140
#ek_name = myimx6ek200
ek_name = myimx6ek314
#ek_name = myimx6ekpob

# 请根据评估板的CPU类型和内存大小选择其中一项 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
#ek_spec = 6qp
#ek_spec = 6qp-2g
ek_spec = 6q
#ek_spec = 6q-2g
#ek_spec = 6u
#ek_spec = 6s
#ek_spec = 6s-1g
#ek_spec = 6g
#ek_spec = 6g-512m
# 说明:6u 即 i.MX6DualLite, 6g 即 i.MX6UltraLite。

# 请选择需要的文件系统,Linux-3.0.35 可使用的文件系统如下 ~~~~~~~~~~~~~~~~~~~~~~
#rootfs_l3035_file = rootfs-linux-minimal.tar.bz2
rootfs_l3035_file = rootfs-linux.tar.bz2
#rootfs_l3035_file = rootfs-linux-qt4.tar.bz2

# 请选择需要的文件系统,Linux-3.14.52 可使用的文件系统如下 ~~~~~~~~~~~~~~~~~~~~~
#rootfs_l31452_file = distro-core-image-base.tar.bz2
rootfs_l31452_file = distro-fsl-image.tar.bz2
#rootfs_l31452_file = distro-fsl-image-qt5.tar.bz2
#rootfs_l31452_file = distro-fsl-image-nogpu.tar.bz2


cfg.ini设置如上

回复 支持 反对

使用道具 举报

该用户从未签到

6

主题

14

帖子

0

注册会员

Rank: 2

积分
58
最后登录
2017-4-17
发表于 2017-4-17 21:11:54 | 显示全部楼层
MY的板子就是有问题,你试试板子应该起来了。如果你想没问题,可以自己改一下。
回复 支持 反对

使用道具 举报

该用户从未签到

20

主题

809

帖子

1

超级版主

Rank: 8Rank: 8

积分
1566
最后登录
2023-1-17
发表于 2017-4-18 17:29:45 | 显示全部楼层
楼主你好,应该是mfgtool烧写配置文件没有设置正确吧。你这里用的不是我们官网的板子,建议你联系你购买板子的技术支持。他们应该熟悉你的问题。你
回复 支持 反对

使用道具 举报

您需要登录后才可以回帖 注册/登录

本版积分规则

关闭

站长推荐上一条 /3 下一条

Archiver|手机版|小黑屋|恩智浦技术社区

GMT+8, 2025-7-20 12:24 , Processed in 0.090205 second(s), 24 queries , MemCache On.

Powered by Discuz! X3.4

Copyright © 2001-2024, Tencent Cloud.

快速回复 返回顶部 返回列表