That was fast. And I’m still worried.
I’ve tried your suggestions about 20 times with variations before I gave up and posted. I wish getting it back was that easy. Here’s what I did.
I grounded pin 8 according to the directions (last time I did this it was pin 9) and powered it up, waited more than 5 seconds, ungrounded, ran the batch file (which was in a different place than the documentation) and got the following log:
-I- Waiting …
-I- TCL platform : Windows NT
-I- SAM-BA CDC 2.10 on : windows
-I- Retrieved arguments from command line :
-I- argv 0 : at91sam9rl64-ek
-I- argv 1 : TinyBooterLoader.tcl
-I- argv 2 :
-E- Connection at91sam9rl64-ek not found
-E- Connection list : com1 com3
Device Manager showed it as a camera at com3
After a reset (tried both the button and powered down) and a power back up it showed on Device Manager as a FEZ Hydra on usb. It also displayed the stuff in the screen from the previous post.
Running FEZ config yielded a status of No Device. Trying to ping yields:
Failure - Device is not connected or not responding.
I am running plain Netmf on my Hydra and not using the GHI classes. So far I have about 30 modules written for a sophisticated ui, but I needed access to an analog pin.
All attempts failed, could not use GetSocket (no Hydra init), so I used the generic netmf SPOT interface. I was getting run time errors on all analog pins I chose except when I ran this single line:
Microsoft.SPOT.Hardware.AnalogInput x = new Microsoft.SPOT.Hardware.AnalogInput(Cpu.AnalogChannel.ANALOG_NONE, 10, 0.0, 10);
Now it’s toast.
I would be glad to send you the code, but it’s close to 10,000 lines.
Any other suggestions would be appreciated. I had no idea these were so fragile and fussy! Do you have another product that is more robust?