Hi

I have got Microsoft Windows CE Debug Shell Version 2.00 and build 0102 in my hand for downloading an image file into a set-top box. The problem is that I have difficulties connecting eshell with the target set-top box. Loading eboot.sre from TFTP server to the set-top box via serial port works (the box gets IP), but after it has finished it drops the address and I cannot connect to the box. There is a possibility to set a static IP for the box, but when pinging the box after setting the static IP in place, I get request time out. I have tried several device names in eshell from IPs to MACs and also the actual box's device name - I assume the device name asked for is supposed to be an IP address?

If anybody could tell me what I am doing wrong or how to establish a connection between set-top box and eshell I would be really grateful

With bet regards

eRKs

Re: eshell.exe by Steve

Steve
Mon Jan 12 09:02:37 CST 2004

Are you the device manufacturer? the device name is whatever eboot decides
it to be and is not necessarily related to a network address...

--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com



Re: eshell.exe by anonymous

anonymous
Tue Jan 13 04:46:05 CST 2004

I am not the manufacturer
After I load eboot.sre I get a menu in the terminal window and when I choose to download Windows CE over Ethernet (firts choice) besides before that I have opened eshell and chosen eboot.bin image and the device name that I use is STWHDTV259661. After I have done all that I get an error in the terminal window as follows

[1] Download Windows CE over Etherne
[2] Run firmware monito
[3] List PCI device
[4] Configure network setting
[5] Flash Operations Men
[6] Download Windows CE to Flash over Etherne
[7] Extract Windows CE from NAND Flash, Execute from RA

Searchin

Search for Vendor ID = 20100BSearchin

Search for Vendor ID = 91021282ID:91021282 Bus:00000000 Device:12 Funct:0 C
ass:02000040 IRQ:00000042 Ethernet Card Found: "DEC21140 100 base-T
Base Address = AE00FF00, Interrupt = 42
ERROR: InitDMABuffer being called
InitTxDescriptor::: dwTRANSMIT_DESCRIPTORS_HEAD = 0xA1FA0000..
InitTxDescriptor::: dwTRANSMIT_BUFFER_START = 0xA1FA02A0..
InitTxDescriptor::: dwTRANSMIT_RING_SIZE = 0x2A..
InitRxDescriptor::: dwRECEIVE_DESCRIPTORS_HEAD = 0xA1FB0000..
InitRxDescriptor::: dwRECEIVE_BUFFER_START = 0xA1FB02A0..
InitRxDescriptor::: dwRECEIVE_RING_SIZE = 0x2A..
DEC21140::: Init using i/o address : 0xAE00FF00 - mem offset = 0x
MAC = 50-0-9B-94-E9-
TDES0 = 0x8000000
TDES0 = 0x8000000
TDES0 = 0x8000000
TDES0 = 0x8000000
DEC21140Init()::: Done
Ethernet Card Initialized OK
Device Name = STWHDTV25966
MAC Address = 50009B94E90
System ready
Preparing for download..
Checksum bad, decompressing image..
<+ReadNandImageData><dwBinOffset = 00000000, dwBinLength = 00000000><-ReadNandImageData::ERROR> FAILED to open NAND BINFS partitio
FATAL ERROR: Unable to Extract NAND Image, HALTING.

SPIN at line 1095 of file c:\wince420\platform\ip400\eboot\main\oemmain.

I used the same device name given here
I also recorded all the transmission with ethereal and it is peculiar that after the loading of eboot.sre nothing else is recorded I mean after choosing to load the Windows CE over Ethernet the box doesn't ask for an IP or doesn't even try to load anything - as if it doesn't communicate with the server at all.

Re: eshell.exe by Steve

Steve
Tue Jan 13 06:32:24 CST 2004

You need to seek support from the device manufacturer, as they wrote the
boot loader and have all the information on what it expects and how you need
to configure an OS image for download to the device.

As a random stab in the dark:
"Preparing for download...
Checksum bad, decompressing image..."

sounds like the download address is in conflict with what the boot loader is
using for it's own RAM and the downloaded records are being corrupted from
the conflicting use.


--
Steve Maillet (eMVP)
Entelechy Consulting
smaillet_AT_EntelechyConsulting_DOT_com



Re: eshell.exe by anonymous

anonymous
Tue Jan 13 07:26:15 CST 2004

Thanks for Your help!