Forums

Hi, 

Below is exactly what my customer wants - 

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

How to change firmware of the product remotely?

Assume I will make product with Stellaris LM3S9B96 .

I will have a installation where my product will be in LAN Ethernet can be connected on web also. I will able to ping my product from my remote location.

Please let me know, Can I change firmware of my product remotely?

What method will be used? Is it telnet or FTP transfer? Or something else?

Please slightly elaborate on your solution ?

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

Thanks

Sum. 

Hello Sum,

We do provide a boot loader example as a part of StellarisWare for the LM3S9B96 products. This can act as an application loader and an update mechanism for application firmware. However, the current boot loader example uses TFTP and that is a non-routable protocol (local subnet access only).

You can find detailed information on the provided boot loader sample's capabilities here.

Mitch,

are you sure that the TFTP is a non-routable protocol?

Hello MrBool,

I guess I have always assumed that to be the case based on past usage but the RFC seems to say otherwise. It does appear to be routable.

Thanks for the comment.

TFTP may be routable, but BOOTP is not.  BOOTP is used to locate the server before the file transfer over TFTP is used.

Of course, none of this precludes anyone from writing their own custom firmware update process (which I've done for my own projects).

You can implement a cross-gateway BOOTP request by specifying the gateway address for the network in which the controller is present.

Along with this, you also need to specify the number of hops (<16) for the BOOTP request.

Also, if you have a fully qualified DNS name for the server from which you wish to take the bin file, you can provide the same in the define for the ENET_BOOTP_SERVER in the bl_config.h file. Make sure the define is uncommented.

All of these parameters are a part of the structure for the tBOOTPPacket defined in the bl_enet.c file.

Hope this was helpful.