Hi, My BSP is iMX53_QSB WinCE700, I could download image via ethernet but Can't transport via KITL

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

Hi, My BSP is iMX53_QSB WinCE700, I could download image via ethernet but Can't transport via KITL

ソリューションへジャンプ
1,166件の閲覧回数
changhsin-wen
Contributor II

Hello everyone,

  I'm playing with WinCE700 and my BSP is iMX53_QSB  and could download image via ethernet (through switch) but Can't transport via KITL if enable KITL it will stuck in OEMInit and can't fetch file system. I've Confused and felt lost

in this problem anyone got the same problem as I do :smileycry: ?


build option.png


conective option.png

boot menu.png

OEMinit.png

ラベル(1)
タグ(1)
1 解決策
909件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi Chang

please look at

How to use KITL to debug i.mx53

also look at recommendations of WCE700_MX53_ER_1105_SMD_UserGuide.pdf

IMX53_TABLET_1105_WCE7_BSP_DOCS

-active / passive KITL modes of target i.MX53 (Eboot)

should meet host PC (Platform Builder) configuration.

If the SMD board is configured for active KITL, the image waits for a

Platform Builder connection before booting the OS image. Because the OS

image is already resident in Flash memory, it is necessary to reconfigure the

Platform Builder to jump directly to the image by selecting Target >

Connectivity Options > Core Service Settings > Download Image:

Never (jump to image).

-section 5.3 (Platform Builder Limitations/Issues):

Connection to Platform Builder Remote Tools may fail.

Workaround :

Network configuration for PC workstation may have MTU

(Maximum Transmit Size) size set to less than 1500, which is

not compatible with the KITL MTU size.

Best regards

igor

元の投稿で解決策を見る

4 返答(返信)
910件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi Chang

please look at

How to use KITL to debug i.mx53

also look at recommendations of WCE700_MX53_ER_1105_SMD_UserGuide.pdf

IMX53_TABLET_1105_WCE7_BSP_DOCS

-active / passive KITL modes of target i.MX53 (Eboot)

should meet host PC (Platform Builder) configuration.

If the SMD board is configured for active KITL, the image waits for a

Platform Builder connection before booting the OS image. Because the OS

image is already resident in Flash memory, it is necessary to reconfigure the

Platform Builder to jump directly to the image by selecting Target >

Connectivity Options > Core Service Settings > Download Image:

Never (jump to image).

-section 5.3 (Platform Builder Limitations/Issues):

Connection to Platform Builder Remote Tools may fail.

Workaround :

Network configuration for PC workstation may have MTU

(Maximum Transmit Size) size set to less than 1500, which is

not compatible with the KITL MTU size.

Best regards

igor

909件の閲覧回数
changhsin-wen
Contributor II

Hello Igor,

Thank you for kindly advice :smileylaugh: ! I've reading your  useful information and after change eboot and set KITL work mode as interrupt, enable KITL enable mode  and finally success:smileylaugh: !!

But when start remote tool like FileViewer, it end up restart like following :smileycry:  anyone encounter the same problem as I do?

1.png

5.png

2.png

Sincerely,

Chang

0 件の賞賛
返信
909件の閲覧回数
igorpadykov
NXP Employee
NXP Employee

Hi Chang

probably it is more suitable to post this to microsoft FAQ forum,

like below

USB KITL and USB OTG driver conflict

~igor

909件の閲覧回数
changhsin-wen
Contributor II

Hi igor,

I read your post and change MTU size, but Remote tool still error  in message 0xC000005 and I connect device through Ethernet (via switch).

Truly grateful for your sharing and advice, I'll try to post to microsoft FAQ too :smileylaugh:. Wish you have a nice day !

6.png

Sincerely,

Chang

0 件の賞賛
返信