Hi everybody,


We are having problems with downloading an image through USB on our
platform.

We have implemented USB RNDIS in our bootloader (based on rne_mdd) so that
we can download (and also debug) our image through USB. During the
developments, we did not have problem with the desktop machine we used for
the download, we were able to load big NK.BIN files (tested up to 23MB).

We are now trying to download using other desktop machines and the download
often hangs after 5MB. It seems that when we have a standalone machine (not
connected to the network), the situation is better (but not perfect). When
changing USB IDs, the situation is temporarily better. Moreover, some MAC
addresses (that we can configure in our bootloader menu) make the download
impossible.

Using a USB sniffer software on our desktop, the last frame sent is an
acknowledge from the device to the desktop.


Our hardware platform is based on the S3C2412 processor from Samsung, and
the OS is CE5. Desktop PCs are all WindowsXP.


Has someone else already had such a problem? Somebody has an idea? Is there
a "magic" configuration of the desktop that could solve all our problems?


Thanks in advance


BR



--
--
--
----------------------------------------------------------------
Anthony Pellerin (eMVP)
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------

Re: USB and KITL : image download often hangs by Marco

Marco
Wed Jul 11 10:16:25 CDT 2007

Hi Anthony,

as for the MAC address to be used in RNDIS, you may check an old
posting of mine (and following thread) in this newsgroup:
http://groups.google.it/group/microsoft.public.windowsce.platbuilder/msg/0941cd1c2d1c57cd

Using a Samsung CPU, I wonder why you are trying to use RNDIS instead
of the excellent and reliable USB-serial implementation provided by
Samsung. Yes, with PB 5.0 you need another tool (DNW) to download the
image, but this may even turn out into an advantage to the developer,
since while the image is downloaded, PB has time to realize it must
set up the debug environment and start a KITL connection with a target.

Though I didn't have problems like yours, I found RNDIS not trivial to
set up for the average user, with the PB communication service
(CESVCHOST) unable to detect and use adapters installed after it started.

Marco Contenti
PROJECT s.a.s. (MSWEP)
www.projectsas.it
marco.contenti@<see domain above>

Anthony Pellerin ha scritto:
> Hi everybody,
>
>
> We are having problems with downloading an image through USB on our
> platform.
>
> We have implemented USB RNDIS in our bootloader (based on rne_mdd) so that
> we can download (and also debug) our image through USB. During the
> developments, we did not have problem with the desktop machine we used for
> the download, we were able to load big NK.BIN files (tested up to 23MB).
>
> We are now trying to download using other desktop machines and the download
> often hangs after 5MB. It seems that when we have a standalone machine (not
> connected to the network), the situation is better (but not perfect). When
> changing USB IDs, the situation is temporarily better. Moreover, some MAC
> addresses (that we can configure in our bootloader menu) make the download
> impossible.
>
> Using a USB sniffer software on our desktop, the last frame sent is an
> acknowledge from the device to the desktop.
>
>
> Our hardware platform is based on the S3C2412 processor from Samsung, and
> the OS is CE5. Desktop PCs are all WindowsXP.
>
>
> Has someone else already had such a problem? Somebody has an idea? Is there
> a "magic" configuration of the desktop that could solve all our problems?
>
>
> Thanks in advance
>
>
> BR
>
>
>

Re: USB and KITL : image download often hangs by Anthony

Anthony
Thu Jul 12 08:04:09 CDT 2007

Thanks for answering, and for your suggestion.
The code that allow downloading and debugging with KITL is the same. So,
even if we are able to download using DNW, we will still have problems with
KITL (we already have those problems for time to time where the KITL
connection hangs).

BR

--
--
--
----------------------------------------------------------------
Anthony Pellerin (eMVP)
ADENEO (ADESET)
Windows Embedded Consultant
<apellerin AT adeneo DOT adetelgroup DOT com>
http://www.adeneo.adetelgroup.com
Tél : +33 (0)4.72.18.57.77
Fax : +33 (0)4.72.18.57.78
----------------------------------------------------------------
"Marco Contenti" <marco.contenti@nospam.com> a écrit dans le message de
news: u0SM868wHHA.4392@TK2MSFTNGP04.phx.gbl...
> Hi Anthony,
>
> as for the MAC address to be used in RNDIS, you may check an old posting
> of mine (and following thread) in this newsgroup:
> http://groups.google.it/group/microsoft.public.windowsce.platbuilder/msg/0941cd1c2d1c57cd
>
> Using a Samsung CPU, I wonder why you are trying to use RNDIS instead of
> the excellent and reliable USB-serial implementation provided by Samsung.
> Yes, with PB 5.0 you need another tool (DNW) to download the image, but
> this may even turn out into an advantage to the developer, since while the
> image is downloaded, PB has time to realize it must set up the debug
> environment and start a KITL connection with a target.
>
> Though I didn't have problems like yours, I found RNDIS not trivial to set
> up for the average user, with the PB communication service (CESVCHOST)
> unable to detect and use adapters installed after it started.
>
> Marco Contenti
> PROJECT s.a.s. (MSWEP)
> www.projectsas.it
> marco.contenti@<see domain above>
>
> Anthony Pellerin ha scritto:
>> Hi everybody,
>>
>>
>> We are having problems with downloading an image through USB on our
>> platform.
>>
>> We have implemented USB RNDIS in our bootloader (based on rne_mdd) so
>> that we can download (and also debug) our image through USB. During the
>> developments, we did not have problem with the desktop machine we used
>> for the download, we were able to load big NK.BIN files (tested up to
>> 23MB).
>>
>> We are now trying to download using other desktop machines and the
>> download often hangs after 5MB. It seems that when we have a standalone
>> machine (not connected to the network), the situation is better (but not
>> perfect). When changing USB IDs, the situation is temporarily better.
>> Moreover, some MAC addresses (that we can configure in our bootloader
>> menu) make the download impossible.
>>
>> Using a USB sniffer software on our desktop, the last frame sent is an
>> acknowledge from the device to the desktop.
>>
>>
>> Our hardware platform is based on the S3C2412 processor from Samsung, and
>> the OS is CE5. Desktop PCs are all WindowsXP.
>>
>>
>> Has someone else already had such a problem? Somebody has an idea? Is
>> there a "magic" configuration of the desktop that could solve all our
>> problems?
>>
>>
>> Thanks in advance
>>
>>
>> BR
>>
>>


Re: USB and KITL : image download often hangs by Marco

Marco
Thu Jul 12 09:13:12 CDT 2007

Do you mean you have problems with the KITL connection over USB with
serial emulation, not only with RNDIS?
I am working on the 2440 family right now and have been working on the
2410 for a while in the past, but didn't use the 2412. I never had
problems with KITL over USB serial.
On all BSPs I used, the USB debug libraries came without source code.
If this applies to your case too, you should have got (or written
yourself) a completely different driver for KITL over RNDIS.
Excluding hardware issues, this means that there may be a problem in
low-level USB implementation common to both drivers. Is this possible?

The USB serial emulation is simpler and far more efficient (10x?) than
RNDIS for the download/KITL connection. This is probably the reason
why Microsoft decided to support it on CE 6.0.

Marco Contenti
PROJECT s.a.s. (MSWEP)
www.projectsas.it
marco.contenti@<see domain above>

Anthony Pellerin ha scritto:
> Thanks for answering, and for your suggestion.
> The code that allow downloading and debugging with KITL is the same. So,
> even if we are able to download using DNW, we will still have problems with
> KITL (we already have those problems for time to time where the KITL
> connection hangs).
>
> BR
>