Tinybooter with TCP/IP

With Netmf version 4.0, what do we need change to do get both Tinybooter and
TinyCLR debug/debploy over TCP/IP?

Seems a litte more complicated than including TCP libs and changing
platform_selector.h

Any help would be appreciated!

-Armand

Hello Armand,That scenario is not really supported for a couple reasons.

Hello Armand,

That scenario is not really supported for a couple reasons.  The main reason
we did not support remote firmware update was because it would nearly double
the size of memory required.  This is because TinyBooter and the CLR are two
different applications (they do not share libraries).  And since the network
stack is one of the largest components it would make this unfeasible.

And the second reason for not allowing remote updates, is that we did not
have a good enough security model to allow remote updates.  Currently
Tinybooter relies on a signature hash of the image which is not checked until
the old image is replaced by the new one (again for memory reasons).  This is
acceptable if you have to have a direct connection because you own the device
already.  However, for remote devices it is not because anyone could wipe out
the original image.

We had planned for adding remote firmware updates in the future, but I am
not sure where it falls on the priority list at this point.   I believe a few
other customers have either created their own installers or ported .Net MF to
an OS that supported this feature already.  That could also be an option for
you.

Thanks,
Zach

Thanks for clarifying Zach,I see.

Thanks for clarifying Zach,

I see.  I had the impression that Tinybooter was used to deploy assemblies
as well.  With MFDeploy and TinyCLR configured for TCP/IP we can remote
upgrade applications, correct?

-Armand

Application upgrades can be performed via TCP/IP using MFDeploy or

Application upgrades can be performed via TCP/IP using MFDeploy or Visual
Studio as long as the device uses TCP/IP as the default debugger port.  In
addition, this only works for Debug versions of the firmware.  The feature is
disabled for RTM firmware for the same security reasons we do not allow remote
firmware updates.

Thanks,
Zach

So the only way to upgrade RTMs in the wilderness is through serial port orif

So the only way to upgrade RTMs in the wilderness is through serial port or
if the stack exists USB?

-Armand

Yes, unless the Porting Kit vendor has implemented some other means."Armand R.

Yes, unless the Porting Kit vendor has implemented some other means.

I see. Many thanks for all of the responses! -Armand"ZachL" wrote:

I see.  Many thanks for all of the responses! -Armand