imx51 burn wince6.0,mfgtool.exe can't burn wince6.0 by SD/MMC(klm8g2fe3b-b001)

Arcatus · ‎09-22-2014

hello,everybody,below is my Configuration information

mfgtool.log:

Monday, September 22, 2014 11:54:59

1 - Panel A Start processing SD/MMC <LIST/>.

Panel A Start <CMD/> type="find" body="BootStrap" file="" timeout="60" onError="" text="".

1 - Panel A Finished <CMD/> type="find" body="BootStrap" file="" timeout="60" onError="" text="" SUCCESS code=0x0.

Panel A Start <CMD/> type="init" body="Memory" file="MX51_DDR.xml" timeout="10" onError="" text="".

1 - Panel A Finished <CMD/> type="init" body="Memory" file="MX51_DDR.xml" timeout="10" onError="" text="" SUCCESS code=0x0.

Panel A Start <CMD/> type="load" body="" file="uce.nb0" timeout="10" onError="" text="Doing preLoad."".

1 - Panel A Finished <CMD/> type="load" body="" file="uce.nb0" timeout="10" onError="" text="Doing preLoad."" SUCCESS code=0x0.

Panel A Start <CMD/> type="load" body="" file="eboot_uut.nb0" timeout="10" onError="" text="Loading OS image.".

1 - Panel A Finished <CMD/> type="load" body="" file="eboot_uut.nb0" timeout="10" onError="" text="Loading OS image." SUCCESS code=0x0.

Panel A Start <CMD/> type="jump" body="" file="" timeout="10" onError="" text=" Jumping to OS image. ".

1 - Panel A Finished <CMD/> type="jump" body="" file="" timeout="10" onError="" text=" Jumping to OS image. " 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 UtpUpdate Event: VolumeArrival Msg: (null) DevState: Updater OpState: WAITING_FOR_DEVICE

1 - Panel A Finished <CMD/> type="find" body="Updater" file="" timeout="180" onError="" text="" SUCCESS code=0x0.

Panel A Start <CMD/> type="push" body="MediaType:SDMMC" file="" timeout="10" onError="" text="Send media type.".

1 - Panel A Finished <CMD/> type="push" body="MediaType:SDMMC" file="" timeout="10" onError="" text="Send media type." SUCCESS code=0x0.

Panel A Start <CMD/> type="push" body="QueryStoreStatus:DSK1:,Timeout:10" file="" timeout="10" onError="" text="Query store status.".

1 - Panel A Finished <CMD/> type="push" body="QueryStoreStatus:DSK1:,Timeout:10" file="" timeout="10" onError="" text="Query store status." FAIL code=0xbad20001.

Panel A: Reason is unknown,failed to run command: type="push" body="QueryStoreStatus:DSK1:,Timeout:10" file="" timeout="10" onError="" text="Query store status."

2 - Panel A Finished processing SD/MMC <LIST/> : FAIL code=-1160642559.

play.ini:

[PROFILE]

PLAYER=MX51 WinCE Update

VERSION=2

[OPERATIONS]

MX_UPDATE=51 RKL MMC WinCE Update,120,0

UTP_UPDATE=OS Firmware,120,1

[OS Firmware]

UCL_INSTALL_SECTION=SD/MMC

[51 RKL MMC WinCE Update]

UCL_INSTALL_SECTION=SD/MMC

serial port Configuration information

com2:115200 8 N 1

INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

BSP Clock Configuration:

CKIH = 22579200 Hz

PLL1 = 800000000 Hz

PLL2 = 665000000 Hz

PLL3 = 216000000 Hz

LP_APM = 24000000 Hz

ARM = 800000000 Hz

AXI_A = 166250000 Hz

AXI_B = 133000000 Hz

EMI_SLOW = 133000000 Hz

AHB = 133000000 Hz

IPG = 66500000 Hz

PERCLK = 8000000 Hz

CKIL_SYNC = 32768 Hz

DDR = 200000000 Hz

ARM_AXI = 166250000 Hz

IPU_HSP = 133000000 Hz

VPU_AXI = 166250000 Hz

GPU = 166250000 Hz

GPU2D = 166250000 Hz

DEBUG_APB = 166250000 Hz

ENFC = 26600000 Hz

USBOH3 = 66500000 Hz

ESDHC1 = 47500000 Hz

ESDHC2 = 47500000 Hz

ESDHC3 = 47500000 Hz

ESDHC4 = 47500000 Hz

UART = 24000000 Hz

SSI1 = 5644800 Hz

SSI2 = 5644800 Hz

SSI3 = 5644800 Hz

SSI_EXT1 = 10285714 Hz

SSI_EXT2 = 10285714 Hz

USB_PHY = 24000000 Hz

TVE_216_54 = 216000000 Hz

DI = 27000000 Hz

VPU_RCLK = 24000000 Hz

SPDIF0 = 1142857 Hz

SPDIF1 = 1142857 Hz

SLIMBUS = 66500000 Hz

SIM = 66500000 Hz

FIRI = 24000000 Hz

HSI2C = 66500000 Hz

SSI_LP_APM = 22579200 Hz

SPDIF_XTAL = 24000000 Hz

HSC1 = 216000000 Hz

HSC2 = 216000000 Hz

ESC = 15428571 Hz

CSI_MCLK1 = 24629629 Hz

CSI_MCLK2 = 24629629 Hz

ECSPI = 66500000 Hz

LPSR = 0 Hz

PGC = 66500000 Hz

OSC = 24000000 Hz

CKIH_CAMP1 = 22579200 Hz

CKIH2_CAMP2 = 0 Hz

CKIH2 = 0 Hz

FPM = 33554432 Hz

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Sep 22 2014 10:17:14

INFO: BoardID = 0x0.

Microsoft Windows CE Ethernet Bootloader 1.0 for MX51 EVK (Sep 22 2014 10:23:01)

INFO: SBMR = 0xE060C003.

g_pBSPArgs->g_SDHCBootPort=1;//boot from eSDHC1!

INFO: Bootloader launched from SD.

System ready!

Preparing for download...

BL_JUMP

INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

BSP Clock Configuration:

CKIH = 22579200 Hz

PLL1 = 800000000 Hz

PLL2 = 665000000 Hz

PLL3 = 216000000 Hz

LP_APM = 24000000 Hz

ARM = 800000000 Hz

AXI_A = 166250000 Hz

AXI_B = 133000000 Hz

EMI_SLOW = 133000000 Hz

AHB = 133000000 Hz

IPG = 66500000 Hz

PERCLK = 8000000 Hz

CKIL_SYNC = 32768 Hz

DDR = 200000000 Hz

ARM_AXI = 166250000 Hz

IPU_HSP = 133000000 Hz

VPU_AXI = 166250000 Hz

GPU = 166250000 Hz

GPU2D = 166250000 Hz

DEBUG_APB = 166250000 Hz

ENFC = 26600000 Hz

USBOH3 = 66500000 Hz

ESDHC1 = 47500000 Hz

ESDHC2 = 47500000 Hz

ESDHC3 = 47500000 Hz

ESDHC4 = 47500000 Hz

UART = 24000000 Hz

SSI1 = 5644800 Hz

SSI2 = 5644800 Hz

SSI3 = 5644800 Hz

SSI_EXT1 = 10285714 Hz

SSI_EXT2 = 10285714 Hz

USB_PHY = 24000000 Hz

TVE_216_54 = 216000000 Hz

DI = 27000000 Hz

VPU_RCLK = 24000000 Hz

SPDIF0 = 1142857 Hz

SPDIF1 = 1142857 Hz

SLIMBUS = 66500000 Hz

SIM = 66500000 Hz

FIRI = 24000000 Hz

HSI2C = 66500000 Hz

SSI_LP_APM = 22579200 Hz

SPDIF_XTAL = 24000000 Hz

HSC1 = 216000000 Hz

HSC2 = 216000000 Hz

ESC = 15428571 Hz

CSI_MCLK1 = 24629629 Hz

CSI_MCLK2 = 24629629 Hz

ECSPI = 66500000 Hz

LPSR = 0 Hz

PGC = 66500000 Hz

OSC = 24000000 Hz

CKIH_CAMP1 = 22579200 Hz

CKIH2_CAMP2 = 0 Hz

CKIH2 = 0 Hz

FPM = 33554432 Hz

Windows CE Kernel for ARM (Thumb Enabled) Built on May 7 2012 at 12:47:43

INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb

OEMInit: silicon r呝?偮蓚j???V)?偮羠jOALIoCtlHalInitRTC(2006/1/1 12:0:0.000)

WARNING: SRTC was reset.

BSPPmicInit start .

BSPPmicInit end .

+OALIoCtlQueryBoardId ()g_dwBoardID = 0

BOT_InternalInit with Drivers\Active\13

Exception 'Data Abort' (4): Thread-Id=01ef0002(pth=9272a63c), Proc-Id=00400002(pprc=80749308) 'NK.EXE', VM-active=01aa0002(pprc=965f596c) 'udevice.exe'

PC=c01d409c(gwes.dll+0x0005409c) RA=c01d4084(gwes.dll+0x00054084) SP=d07cfdd8, BVA=00000104

UFN_ATTACH with key = Drivers\Active\13

UFN_CONFIGURED: BOT_OpenInterface again

UTP command:Media type: SDMMC.

UTP command:QueryStoreStatus.

UTP command:Check if disk is ready.

Please be patient to wait...

Send storage disk name: DSK1:.

Send time out: 10.

Opening disk DSK1: failed.Error code is 4319

ERROR:UceCommandDeal fail.

where is my error for looking at my printed information?In this process, the SD card to mount the drive letter appears on the screen of the computer, but also cannot format or cannot be opened?What can i do?Help me,Please!!

igorpadykov · ‎09-24-2014

If you could write with ATK you can continue to use it.

~igor

View solution in original post

igorpadykov · ‎09-23-2014

Hi Arctic

KLM8G2FE3B is eMMC 4.41 verson while i.MX51 eSDHC supports up to rev.4.2 only

as decribed in sect.31.1.1 "Features" MCIMX51RM MCIMX51 Multimedia Applications Processor

SD/MMC driver checks for chip revision and may not work properly if it is not designed for

support of particular revision. So suggest to check with another chips.

Best regards

igor

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

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

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

Arcatus · ‎09-24-2014

Hi igorpadykov,

Before wrong operation,I can boot wince6.0 from SD/MMC normally,but OS didn‘t display SD folder "SD memory".So I want to deal with it,Below is my wrong operation

Booting IMX51 from SD/MMC(klm8g2fe3b-b001)

After seting wrong eboot menu information ,cause the system can't start any more,I look for lots of forum or blog,they all can't solve my question.how shoud can i do?

igorpadykov · ‎09-24-2014

If you could write with ATK you can continue to use it.

~igor