Main Site Documentation

IFU with FW 4.2.8


#1

I had a 1st glimpse to IFU in 4.2.8.
So far I have only read the SDK docs, which implies me that IFU is supprisingly simple.

But when I look at the sample I come up with some questions:

SystemUpdate.Initialize( SystemUpdate.SystemUpdateType.Config | SystemUpdate.SystemUpdateType.Deployment | SystemUpdate.SystemUpdateType.Firmware );
            LoadDataFromSD(@ "SD\ER_DAT", SystemUpdate.SystemUpdateType.Firmware);
            LoadDataFromSD(@ "SD\ER_CONFIG", SystemUpdate.SystemUpdateType.Config);
            LoadDataFromSD(@ "SD\ER_FLASH", SystemUpdate.SystemUpdateType.Firmware);
            LoadDataFromSD(@ "SD\ManagedApp.hex", SystemUpdate.SystemUpdateType.Deployment);               
            _led.Write(true);
            if (SystemUpdate.CanUpdate) SystemUpdate.FlashAndReset();

Where do I get the files from?
I assume that ER_DAT might be Firmware.hex, ER_FLASH might be Firmware2.hex, ER_CONFIG might be Config.hex and ManagedApp.hex is my application.
Is that assumption correct?

Then I come to my 2nd question: Where do I get ManagedApp.hex (or MyApp.hex) from? Do I create it with MFDeploy as if I would deploy it with MFDeploy or the FW Updater?

And 3rd question:
Do I need to have the …sig files in parallel? Well I assume no, because how could the SystemUpdate.Load() method know where the array is comming from.

This leads me to my final question:
Do you plan (or have) a method to manually check .hex files with theire .sig file?


#2

Sorry because this made you confuse.
Question 1:

  • ER_DAT is firmware2
  • ER_FLASH is firmware
  • ER_CONFIG is config
    Question 2:
  • Yes, you can use MFDeploy to extract your C# application in hex file. Note that MFDeploy work fine on EMX but on G120, you have to wait for a long time, maybe 10-20 mins.
  • Question 3:
  • No need sig file in case using IFU.

Importance:

  • Don’t disconnect power or reset while IFU is running.
  • It takes few minutes to finish, and running IFU on G120 is faster than EMX.

#3

We will not support the core feature added in 4.2 as of now. It is new and no one used it yet. We can’t afford the risk involved in using it commercially.

We have enough headaches caused by switching the TCP/IP stacks to the new open source one :frowning:


#4

Thank you for the quick answer.
What do you mean by ‘you can use MFDeploy to extract’? Can I use something else?
What exactly takes 10-20 min. on the G120? Connect, download hex file? Will this be improoved in the future?


#5

The NETMF docs say that SystemUpdate is only an ‘interface’ for IFU, and it’s up to the manufacturer to implement it accordingly.


#6

Not sure, It’s been a while since I read into this topic. But when Gus told me that GHI will not support this feature in the near future I stopped reading.
But I think it was some pdf document from netmf.codeplex.com.
btw. The GHI Interface is way simpler.


#7

See the image below, I meant that.

What exactly takes 10-20 min. => I meant when you hit OK button on “Create Application Deployment” window, MFDeploy looks like no responding, you have to wait for a long time.


#8

Exactly. This feature is needed for commercial users, who want things to be very solid.


#9

Two more little questions:
If I download MyApp.hex from a EMX board via MFDeploy, can I use the same file for an G120 or do I need a seperate hex for every SOM?
The Docs say TinyBooter can not be updated by IFU. When is a update to TinyBooter usually necesarry?


#10

Will you not need to compile two applications, one for each SOM anyway? They use different references etc…


#11

I don’t see why.
The only reference that might be different is GHI.Premium.Hardware.EMX / .G120.
These only containes const for Pins. But I want to read the Pins from SD/file anyway, so I usually will not add these references.
Everything else should be the same. I already test the same code on EMX and G120, but currently I always deploy with VS.


#12

You can’t use the same file


#13

Where can I find docs describing the IFU procedure for the G120?


#14

Heh heh. I shoulda known!

OK, so the new IFU looks really straightforward, and this answers my question of how I can perform IFU over a serial port from a couple weeks back. As Reinhard asked, when is a TinyBooter update necessary?


#15

@ Gus: does the new IFU on 4.2.9 still need to partition the flash in a updater partition and a application partition?


#16

The new one is different and simpler, no need ot do anything special http://wiki.tinyclr.com/index.php?title=In-Field_Update


#17

Thanks, that does make things easier for sure :slight_smile:


#18

The doc says that the GHI IFU(Premium 4.2.10) doesn’t allow to update TinyBooter while it was possible on the 4.1.8. Could it be a limitation in the future. Does GHI plan to update the tinybooter?

As we already have products in the field (a little bit everywhere in the world) how to update these devices from 4.1.8 to 4.2.10 without pb.
the 4.1.8 looks for some files that has been renamed…

CLR2.HEX is it now firmware2.hex ?
CLR.HEX is it now firmware.hex ?


#19

It seems that it will not be possible…


#20

@ leforban -

I think there is no plan for tinybooter so far