I understand what you are saying, I did open an original project, but I believe that this is nothing to do with the project or the way the project was built.
Anyway, I did a test.
I have 2 identical specimens A and B as seen in Picture Nr 1. Both updated to version 184.108.40.206 and both running the same very complicated test application: it shows a nice image on a screen and uses a timer to turn an onboard LED on and off, in other words keeps it busy.
using GTM = Gadgeteer.Modules;
public class Program : Gadgeteer.Program
bool ledOn = false;
public static void Main()
Mainboard = new GHIElectronics.Gadgeteer.FEZHydra();
Program program = new Program();
program.Run(); // Starts Dispatcher
display_CP7 = new GTM.GHIElectronics.Display_CP7(10, 11, 12, 6);
display_CP7.SimpleGraphics.DisplayImage(Resources.GetBitmap(Resources.BitmapResources.Image_800x480), 0, 0);
Gadgeteer.Timer timer = new Gadgeteer.Timer(1000); // every second (1000ms)
timer.Tick += new Gadgeteer.Timer.TickEventHandler(timer_Tick);
void timer_Tick(Gadgeteer.Timer timer)
ledOn = !ledOn;
The Specimen B was updated to version 220.127.116.11 using another PC, created new project, used same program.cs same code. The result can be seen in Picture Nr 2. LEDs on both A and B are flashing.
Interesting moment is, that while flashing both specimens with 18.104.22.168, screens were white from [em]Hydra found at Port#:[/em] till [em]TinyBooter updated sucessfully.[/em], when they went black. But then I was updating specimen B with 22.214.171.124 it didn’t go back to black, stayed white.
Another thing, if I reset A (126.96.36.199), screen would flash white for a second, prints FEZ_Hydra and Build Date in a top left corner and starts with application. Specimen B (188.8.131.52) wouldn’t do that. Screen would darken for a second and then come back to white.
Thats the story…