Spider firmware update impossible

Archive
1

Hi all,

I’m getting mad trying to update my new Spider stater kit !
I’ve tried several way to update the firmware with no success.
First of all, I’ve tried with FEZ_Config_v011:
_ I’ve put my Spider in loader mode ( 1,2,3 ON ), configured as COM3
_ In FEZ_Config, I’ve tried the serial connection which failed
_ I’ve pressed the Reset button and the connection became a GHI .Net Micro Framework USB debbuging interface ( always with switches 1,2,3 ON )
_ In FEZ_Config I’ve managed the USB connection to EMX_Gadgeteer
_ Device version said:

Connecting to device…EMX_Gadgeteer
Loader (TinyBooter) Version: 4.1.6.0
Firmware (TinyCLR) Version: Not available.

_ Click on Firmware update then EMX, it finds:

Config.hex
Firmware.hex
Firmware2.hex

_ Click on Next

The Config.hex and Firmware.hex managed to be deployed BUT the Firmware2.hex failed ( 75% of the progressbar ) !!!

Here is the output:

EMX_Gadgeteer is connected
Please wait while rebooting in TinyBooter mode…
Found TinyBooter version: 4.1.6.0

Updating Firmware. Please wait…

Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\EMX\Firmware\Config.hex
Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\EMX\Firmware\Firmware.hex
Deploying C:\Program Files (x86)\GHI Electronics\GHI Premium NETMF v4.2 SDK\EMX\Firmware\Firmware2.hex… fail!

From this point, I’ve tried to deploy with MFDeploy, and it also fails on Firmware2.hex !

So can anyone help me on that because I have a nice unusable starter kit !

Many thanks.
Fred.

2

You need to update TinyBooter, which is something you should only need to do one time. Due to the tool being release couple days a go and cleaning up our download section, the update may not be easy today. You have 2 options, wait till Monday and we will give you everythgn you need. Or you can try now buy following this (spider uses EMX) http://ghielectronics.com/docs/54/firmware-update-emx

The little card that came with spider shows you how to set it in loader mode (3 switches down)

Not to worry, we will upload complete instructions on Monday. Sorry about this confusion.

Welcome to the community.

3

Many thanks for your reply.
I’m going to wait until monday in order to have a simplier way to update the TinyBooter !

I’m please to enter this community :slight_smile:

4

I have the same problem, I eagerly await Monday ! :wink:

5

We’ve posted the older updaters in a zip file:
http://www.ghielectronics.com/downloads/firmware/GHI_NETMF_Firmware_Updaters_legacy.zip

However, these are only necessary if you have a need to update “Tinybooter.” Otherwise, we’d prefer you use the new tool and provide us with feedback for improvements.

6

The update has succeed, but I still have an error “a3000000” when I try to start in debug mode.

I use the latest SDK (4.2.10) :

Found debugger!

Create TS.

Loading start at a0e00000, end a0e1383c

Assembly: mscorlib (4.2.0.0) Assembly: Microsoft.SPOT.Native (4.2.0.0) Assembly: Microsoft.SPOT.Security.PKCS11 (4.2
.0.0) Assembly: System.Security (4.2.0.0) Loading Deployment Assemblies.

Attaching deployed file.

Assembly: GTM.Seeed.Compass (1.6.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Net.Security (4.2.0.0) Attaching deployed file.

Assembly: Gadgeteer.DaisyLink (2.42.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Camera (1.1.2.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Extender (1.1.2.0) Attaching deployed file.

Assembly: GHI.Premium.Net (4.2.10.0) Attaching deployed file.

Assembly: GTM.Seeed.Gyro (1.6.0.0) Attaching deployed file.

Assembly: GTM.Seeed.GPS (2.0.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Touch (4.2.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Net (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Load (1.1.2.0) Attaching deployed file.

Assembly: System.Net.Security (4.2.0.0) Attaching deployed file.

Assembly: GHIElectronics.Gadgeteer.FEZSpider (1.1.2.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware.PWM (4.2.0.1) Attaching deployed file.

Assembly: GTM.GHIElectronics.PulseInOut (1.1.2.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware.SerialPort (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Ethernet_J11D (1.1.4.0) Attaching deployed file.

Assembly: GHI.Premium.System (4.2.10.0) Attaching deployed file.

Assembly: Microsoft.VisualBasic (1.0.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Distance_US3 (1.0.1.0) Attaching deployed file.

Assembly: System (4.2.0.0) Attaching deployed file.

Assembly: GMISoft.Micro (1.0.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.Current_ACS712 (1.1.2.0) Attaching deployed file.

Assembly: Gadgeteer.WebServer (2.42.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.XBee (1.1.2.0) Attaching deployed file.

Assembly: 2DDrone (1.0.0.0) Attaching deployed file.

Assembly: System.Http (4.2.0.0) Attaching deployed file.

Assembly: Gadgeteer.Serial (2.42.0.0) Attaching deployed file.

Assembly: GHI.Premium.Hardware (4.2.10.0) Attaching deployed file.

Assembly: GTM.Seeed.TemperatureHumidity (1.6.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.TinyCore (4.2.0.0) Attaching deployed file.

Assembly: GHI.Premium.USBHost (4.2.10.0) Attaching deployed file.

Assembly: System.IO (4.2.0.0) Attaching deployed file.

Assembly: GHI.Premium.IO (4.2.10.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Hardware (4.2.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.Graphics (4.2.0.0) Attaching deployed file.

Assembly: Gadgeteer.WebClient (2.42.0.0) Attaching deployed file.

Assembly: Microsoft.SPOT.IO (4.2.0.0) Attaching deployed file.

Assembly: GTM.GHIElectronics.UsbClientDP (1.1.2.0) Attaching deployed file.

Assembly: Gadgeteer (2.42.0.0) Resolving.

Link failure: some assembly references cannot be resolved!!

Assembly: GMISoft.Micro (1.0.0.0) needs assembly ‘GTM.GHIElectronics.Camera’ (1.1.1.0)

Assembly: 2DDrone (1.0.0.0) needs assembly ‘GMISoft.Micro’ (1.0.0.0)

Assembly: 2DDrone (1.0.0.0) needs assembly ‘GTM.GHIElectronics.Camera’ (1.1.1.0)

Error: a3000000

Waiting for debug commands…

The program ‘[2] Micro Framework application: Managed’ has exited with code 0 (0x0).
The program ‘[5472] GroundStation.vshost.exe: Program Trace’ has exited with code 0 (0x0).
The program ‘[5472] GroundStation.vshost.exe: Managed (v4.0.30319)’ has exited with code 0 (0x0).

7

This should help http://www.ghielectronics.com/docs/165/netmf-and-gadgeteer-troubleshooting

8

@ GMISoft - more cough importantly i see the magical word drone…do tell :wink:

and welcome :slight_smile:

9

Lol justin, I’ve noticed the same…

10

@ Patrick - ain’t we a fine bunch :whistle:

11

It looks like a “well sensored” device as well.

**

Welcome GMISoft !

12

In fact, I’ve built a control card for any vehicle (ROver, Drone, Copter, submarine,…) and IA algorythm based on computervision to make it as autonomous as possible.

We expect to launch the prototype in 6 weeks…

That’s why I’m so in a hurry to skip that kind of problem as quickly as possible, we are short in time, so every hour lost are really costly…

Thanks for your welcome :wink:

13

Sounds very interesting!! Looking forward to learning more about it when you are in a position to do so.

14

This thread may also be of help: http://www.ghielectronics.com/community/forum/topic?id=8317&page=1#msg81733

15

By updating all references, It’s now working. Now I can start again my debug!

Thanks a lot !