UTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.

rheehans — Tue, 07 Apr 2015 23:49:22 GMT

hi all

I did binary programming in emmc that connected SD4 with MFC Tool, but I did not succeed as below image...

debug message is

========================================

If you created or changed a DOS partition, /dev/foo7, say, then use dd(1)

to zero the first 512 bytes: dd if=/dev/zero of=/dev/foo7 bs=512 count=1

(See fdisk(8).)

UTP: sending Success to kernel for command $ sh mksdcard.sh /dev/mmcblk0.

utp_poll: pass returned.

UTP: received command '$ dd if=/dev/zero of=/dev/mmcblk0 bs=1k seek=384 conv=fsync count=129'

UTP: executing "dd if=/dev/zero of=/dev/mmcblk0 bs=1k seek=384 conv=fsync count=129"

129+0 records in

129+0 records out

UTP: sending Success to kernel for command $ dd if=/dev/zero of=/dev/mmcblk0 bs=1k seek=384 conv=fsync count=129.

utp_poll: pass returned.

UTP: received command '$ echo 0 > /sys/block/mmcblk0boot0/force_ro'

UTP: executing "echo 0 > /sys/block/mmcblk0boot0/force_ro"

sh: /sys/block/mmcblk0boot0/force_ro: No such file or directory

UTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.

==========================================================

======================= mfctool.log ===========================

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:8, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:2, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:3, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:4, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:5, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:6, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:7, Volume->_diskNumber:7

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 008EA078

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 1

ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice() successful L add to current list, retrycount: 0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 1

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT-Disk(L), Hub:3-Port:1

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 send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ tar xf $FILE

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ sh mksdcard.sh /dev/mmcblk0

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=/dev/zero of=/dev/mmcblk0 bs=1k seek=384 conv=fsync count=129

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ echo 0 > /sys/block/mmcblk0boot0/force_ro

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]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_0480&PID_0200#20140525005600F#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

=============================================================

please recommand about this error...

Re: UTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.

igorpadykov — Mon, 13 Apr 2015 00:50:10 GMT

Hi Rhee

if this is custom board, then MFG Tool should be rebuild according to

board configuration, below link with similar problem

use mfgtool download imx6ql eMMC error | Freescale Community

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

i.MX ProcessorsのトピックUTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.

UTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.

Re: UTP: sending Non-success to kernel for command $ echo 0 > /sys/block/mmcblk0boot0/force_ro.