G120HDR Gadgeteer programs

Jeff_ghielectroncs · July 3, 2013, 10:37am

It may be that after you saw the com port you did not un jumper your boot loader pins. Otherwise when the chip reboots after the successful transfer it will just boot back to the boot loader.

steenis · July 3, 2013, 10:41am

No, I unjumpered on the point Brett said.

steenis · July 3, 2013, 10:56am

YES, the sixth or seventh time I tried, the tinybooter was uploaded.
Pinging says:
Connecting to device…G120_G120
Loader (TinyBooter) Version: 4.2.10.0
Firmware (TinyCLR) Version: 4.2.10.1

AND uploading the testprogram gave the same error as in post #80,
I will only repeat a part:
…
Assembly: Microsoft.SPOT.Net.Security (4.2.0.0) Attaching deployed file.
Assembly: GHI.Premium.Hardware (4.2.10.0) Attaching deployed file.
Assembly: Microsoft.SPOT.Touch (4.2.0.0) ***********************************************************************

ERROR!!! Firmware version does not match managed code version!!! *

Invalid native checksum: Microsoft.SPOT.Touch 0x4940D53E!=0x2D4E2DCC *

Resolving.
Link failure: some assembly references cannot be resolved!!
Assembly: Gadgeteer (2.42.0.0) needs assembly ‘Microsoft.SPOT.TinyCore’ (4.2.0.0)
Assembly: Gadgeteer (2.42.0.0) needs assembly ‘Microsoft.SPOT.Net’ (4.2.0.0)
Etcetera

So, updating the tinybooter was perhaps good, but it did not help.

Gus_Issa · July 3, 2013, 11:21am

Did you start a new project?

steenis · July 3, 2013, 12:23pm

I will do that this evening or tomorrow.

It was a good idea, but I don’t know why?

The new project gave these errors

The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 1 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 1 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 1 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D
#### Exception Gadgeteer.Socket+InvalidSocketException - 0x00000000 (1) ####
#### Message: Cannot register socket - socket number 1 already used
#### Gadgeteer.Socket+SocketInterfaces::RegisterSocket [IP: 02f9] ####
#### IngenuityMicro.Gadgeteer.G120Hdr::.ctor [IP: 0095] ####
#### GadgeteerApp1.Program::Main [IP: 0004] ####
A first chance exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.dll
An unhandled exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.dll

Additional information: Cannot register socket - socket number 1 already used

Uncaught exception
The thread ‘’ (0x1) has exited with code 0 (0x0).
Done.

Waiting for debug commands…

The program ‘[2] Micro Framework application: Managed’ has exited with code 0 (0x0).

I connected the Multicolorled with the blue-socket, that is socket 6.

Brett · July 3, 2013, 5:38pm

it’s great news that you got your firmware completely updated.

The reason for starting a new project is that VS keeps a copy of the code it deploys to your device, and if you upgrade your SDK to a newer version this leads to a worse mismatch between your code and the device firmware. So starting a new project will avoid this, and is the way to be most sure that there’s no lingering issues. With a larger project, you’d start a new project of the appropriate type, copy your code over from the old project, update any code needed (if the API changed or whatever) and then you’d be set. An alternate way (but sometimes harder to make sure you get right) is to remove all the items listed in “References”, and then re-add them which will add the current versions.

steenis · July 4, 2013, 3:52am

@ Brett

And if I delete the two debug folders in bin and obj ?

steenis · July 4, 2013, 7:55am

@ andre.m

No, it correlates to the remarks of Brett in post #95.

I think the answer to post #94 has to come from Justin.

Justin · July 4, 2013, 8:02am

@ steenis - screen grab of your setup and code…

steenis · July 4, 2013, 8:16am

@ Justin

I want to upload a zip-file of the project, but that failed. How can I upload a zip-file?

Justin · July 4, 2013, 8:18am

@ steenis - send me email - justin at ingenuitymicro dot com

steenis · July 4, 2013, 8:29am

@ Justin - did you get it ?
If so, you can remove the address.

Justin · July 4, 2013, 8:38am

@ steenis - Nope - might be Google being heavy handed again - make sure there is no bin or obj folders…

steenis · July 4, 2013, 12:18pm

@ Justin,

New project, same program, I think these are the same errors plus it did not upload.

‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘H:\VS2010 G120\GadgeteerApp2\GadgeteerApp2\bin\Debug\le\GadgeteerApp2.exe’, Symbols loaded.
The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D
Warning: socket 3 is not compliant with Gadgeteer : SupportedTypes list is null/empty
Using mainboard GHI Electronics FEZCobra II version 1.0

Here it stopped uploading.

Second time:

‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘H:\VS2010 G120\GadgeteerApp2\GadgeteerApp2\bin\Debug\le\GadgeteerApp2.exe’, Symbols loaded.
The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D
Warning: socket 3 is not compliant with Gadgeteer : SupportedTypes list is null/empty
Using mainboard GHI Electronics FEZCobra II version 1.0
#### Exception Gadgeteer.Socket+InvalidSocketException - 0x00000000 (1) ####
#### Message: No DaisyLink modules are detected on socket 6. Please check that the DaisyLink module MulticolorLed is plugged in to the correct socket.
#### Gadgeteer.Modules.DaisyLinkModule::.ctor [IP: 0044] ####
#### Gadgeteer.Modules.GHIElectronics.MulticolorLed::.ctor [IP: 0019] ####
#### GadgeteerApp2.Program::InitializeModules [IP: 0006] ####
A first chance exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.DaisyLink.dll
An unhandled exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.DaisyLink.dll

Additional information: No DaisyLink modules are detected on socket 6. Please check that the DaisyLink module MulticolorLed is plugged in to the correct socket.

Uncaught exception
The thread ‘’ (0x1) has exited with code 0 (0x0).
WARN: Total initialization time exceeds 10 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
WARN: Total initialization time exceeds 20 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
WARN: Total initialization time exceeds 30 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
WARN: Total initialization time exceeds 40 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
WARN: Total initialization time exceeds 50 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
WARN: Total initialization time exceeds 60 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
The program ‘[3] Micro Framework application: Managed’ has exited with code 0 (0x0).

I interrupted uploading.

Justin · July 4, 2013, 12:21pm

@ steenis - They are just warnings - looks like it is running?

steenis · July 4, 2013, 1:17pm

No, I interrupted uploading, because it took very long. Uploading a second time failed.
Errors:

‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘C:\Program Files (x86)\IngenuityMicro\Microsoft .NET Gadgeteer\Mainboards\G120Hdr\NETMF 4.2\le\IngenuityMicro.Gadgeteer.G120Hdr.dll’, Symbols loaded.
‘Microsoft.SPOT.Debugger.CorDebug.dll’ (Managed): Loaded ‘H:\VS2010 G120\GadgeteerApp2\GadgeteerApp2\bin\Debug\le\GadgeteerApp2.exe’, Symbols loaded.
The thread ‘’ (0x2) has exited with code 0 (0x0).
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 3 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 6 must be specified for socket of type D
Warning: socket 2 is not compliant with Gadgeteer : Cpu pin 7 must be specified for socket of type D
Warning: socket 3 is not compliant with Gadgeteer : SupportedTypes list is null/empty
Using mainboard GHI Electronics FEZCobra II version 1.0
#### Exception Gadgeteer.Socket+InvalidSocketException - 0x00000000 (1) ####
#### Message: No DaisyLink modules are detected on socket 6. Please check that the DaisyLink module MulticolorLed is plugged in to the correct socket.
#### Gadgeteer.Modules.DaisyLinkModule::.ctor [IP: 0044] ####
#### Gadgeteer.Modules.GHIElectronics.MulticolorLed::.ctor [IP: 0019] ####
#### GadgeteerApp2.Program::InitializeModules [IP: 0006] ####
A first chance exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.DaisyLink.dll
An unhandled exception of type ‘Gadgeteer.Socket.InvalidSocketException’ occurred in Gadgeteer.DaisyLink.dll

Additional information: No DaisyLink modules are detected on socket 6. Please check that the DaisyLink module MulticolorLed is plugged in to the correct socket.

WARN: Total initialization time exceeds 10 seconds.
: ProgramStarted is blocking execution, which means events and timers will not run properly.
: Make sure not to use blocking code such as while(true) - use a GT.Timer instead.
Uncaught exception
The thread ‘’ (0x1) has exited with code 0 (0x0).
The program ‘[2] Micro Framework application: Managed’ has exited with code 0 (0x0).

The multicolorled is connected to the blue socket.

Justin · July 4, 2013, 1:26pm

Simple test here works, led is one of the few modules i don’t have…

steenis · July 4, 2013, 1:29pm

I stop this for today, hope to see you tomorrow.

Brett · July 4, 2013, 5:15pm

This is interesting because the error actually reports the mainboard isn’t compliant with Gadgeteer. That to me points to another failure in your installation of the SDK, since the SDK would be what is adding the definition of the mainboard, your code doesn’t do it !

@ Gus/team, any insight into what part of the process would cause this type of behaviour?

Justin · July 5, 2013, 2:33am

@ Brett - because there are no pins specified for socket 2 and user socket…