There are reports on this forum of the firmware being corrupted in a low voltage situation. I don't mind
the processor shutting down on low voltage, but self-destruction is pathological.
I have asked that Intel look at this in the next board revision.
For now - for me - my interface to the board is only through WiFi. No wires.
I have personally bricked my Galileo board. Meaning the SPI image was corrupted and the board would no longer boot, and the only way to fix it was with a Dediprog, and a SPI image that had to be built from scratch. Something that at least some makers would not be able to do.
I would recommend connecting power before the USB. Then when powering down, disconnect the USB then the power cable. The Ethernet alone does not draw power, so it does not matter when you plug that in.
The problem is that the Galileo draws about 500mA on it's own with no shields attached. The typical USB connection only provides 500mA. So, if you have something connected that draws a lot of power (in my case it was a motor controller) then you have a risk of the board not having enough power.
My theory is that when the Galileo looses power, it resets itself, and if the power drain continues during the boot process (when the SPI is being accessed) that can corrupt the SPI image. That is just a guess, I have not really done any experiments to verify that.
1 of 1 people found this helpful
It is ok to plug in the Ethernet cable before the power cable since the Ethernet does not provide any power. The USB can provide a max of 500mA and the Intel® Galileo draws 550mA (without any shields or wireless card). Using the USB as a power source can corrupt the SPI image as chofrock mentioned.
Dediprogs can be ordered from Dediprog in China. However, if you are in the US finding a local supplier is best (due to shipping cost and shipping time)
You will need the SF-100 In-Situ ROM Programmer for Serial Flash model SF100 ($230) and you will need a 2x4 cable SF100 ISP cable ISP1-CB ($6)
I did not buy one. The lab I work in had them. In fact I use them quite often in my normal job (which has nothing to do with Galileo). :-)
The IDE supports serial connections only (COMXX). And you would need an SD Linux image to use WiFi.
If I wanted to upload sketches from the IDE, I would use a usb cable, being careful to plug in power first.
As it is, my Linux won't work with the IDE anyway (GLIBC), and I have my hands full playing on the Linux side.
my Linux won't work with the IDE anyway (GLIBC), and I have my hands full playing on the Linux side.
Are you doing any programming in C/C++?.. if so, are you using the same compiler toolset that ships with Arduino?
The reason I ask is because I compile using my own IDE, which is configurable for different programming toolsets and target platforms. I'm looking at all things Galileo related, so anything that can be done with it outside of arduino is of great interest to me.
All of my tools were brought in through the clanton-full distro. I use G++ to compile all my son's c++ homework. Helps him understand what the C++ standard is, compared to Microsoft's idea of a standard. Anything extra I needed - like git and Ruby - was built from source on the Galileo. I actually know nothing about what toolset the Arduino IDE ships with - except the generated code uses ULIBC. I hope Intel gives us a version that uses GLIBC.