3 replies to this topic

[Robert L.]

I have a 3 questions I have not seen answered anywhere else, answers would be very much appreciated: I think that the data/programming inside the N+ board consists of the following 5 things: TinyBooterDecompressor.bin ER_CONFIG ER_FLASH Network configuration (MAC address, etc) managed code that I wrote in C# So question 1, is the above correct? --------------------------------------------- I see that by using MFDeploy I can package my application into a .hex file, which can then be deployed to additional boards. So I am wondering if this tool could be used to update products that have already been shipped to customers. In particular, what does the hex file created from my application include: ER_CONFIG ?? ER_FLASH ?? Network configuration (MAC address, etc) ?? (included or perhaps erased?) managed code that I wrote in C# (I assume this one is included) Ideally it would include all of the above except for the network configuration, which would be left alone. ------------------ Last question: what is the chance that the "GOLD" version of 4.2 will use the same TinyBooterDecompressor.bin that is currently being distributed with 4.2 RC3 ?

[Chris Walker]

Hi Robert, Your Netduino contains the following: 1. TinyBooterDecompressor.bin (the NETMF bootloader) 2. ER_CONFIG (your MAC address settings, USB device name, etc.) 3. ER_FLASH (the .NET Micro Framework CLR) 4. Your managed code (C#/VB) application In MFDeploy, there is an option to create a HEX file (application deployment) from your managed code. You can then flash items #2-#4 using MFDeploy or a custom application built on top of the MFDeployEngine library. TinyBooterDecompressor.bin may change a bit for the gold version of NETMF 4.2 firmware. At minimum, we'll update its version # to reflect RTM. Chris

[ryan_sorensen]

In MFDeploy, there is an option to create a HEX file (application deployment) from your managed code. You can then flash items #2-#4 using MFDeploy or a custom application built on top of the MFDeployEngine library.

Hi Chris,

I'm getting ready to deploy a large number of Netduino Pluses, but I am having trouble finding this option in MfDeploy. Can you please elaborate on the steps required to create a HEX file from managed code?

Thanks,
Ryan

[Llaves]

Hi Chris,

I'm getting ready to deploy a large number of Netduino Pluses, but I am having trouble finding this option in MfDeploy. Can you please elaborate on the steps required to create a HEX file from managed code?

Thanks,
Ryan

This is what I just discovered by trial and error.
Compile your program in Visual Studio and deploy to the N+. Now launch MFDeploy. Make sure your N+ is connected and the settings in MFDeploy are correct (in my case, Device is USB and NetduinoPlus_NetduinoPlus). Now the unobvious part (at least for me). Click Target->Create Application Deployment. Under "Deployment File" fill in the path and name for the .hex file you want created from the application that is currently on the N+. Create a key or not depending on your needs. Click OK and off you go- the .hex file will be created. Personally I would have expected to create an App Deployment from the output of the compiler, not from what's on the board, but it seems to have worked for me.