cege7480

Hmm... So this gets interesting. Yesterday I was playing with MFDeploy but having some weird connection issues (couldn't ping etc). There was a post by Chris somewhere that said to unplug, hold down the reset button, plug in USB, immediatly hit ping. This worked and was able to do everything in MFdeploy without issue. So.. I repeated the exact same step. Of course, as soon as I unplugged the USB, my machine hardbooted. But then, when bringing it back up, the netduino had also rebooted (and program was erased, this is good), and I could then deploy code again. I haven't yet tried the unplug USB test after this started working, would like to do something constructive before rebooting for the 14th time tonight. Does that shed any light into what is happening?

cege7480: Which firmware version? Firmware 4.2rc5 (beta) still has some bsod issues.
I found that if my Netduino doesn't deploy, I disconnect my netduino, thén press F5, and then connect my netduino. A work-around, but it helps against the bsod issue in 4.2

Here is the output when I ran an Erase from MFDeploy (the only thing that seemed to be able to talk to it... If I unplug the Netduino I don't even go BSOD, just right to POST.

Rebooting...
AutoNegotiate complete
DM9161_GetLinkSpeed passed
Link detected 0x0
ip address from interface info: 192.168.254.73

TinyCLR (Build 4.1.2821.0)
Starting...
Created EE.
Started Hardware.
Found debugger!
Create TS.
Loading start at 14d324, end 162e8c
Attaching file.
Assembly: mscorlib (4.1.2821.0) (3880 RAM - 33236 ROM - 19134 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Native (4.1.2821.0) (1144 RAM - 6516 ROM - 4479 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware (4.1.2821.0) (1752 RAM - 11440 ROM - 7371 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Net (4.1.2821.0) (704 RAM - 5060 ROM - 2452 METADATA)
Attaching file.
Assembly: System (4.1.2821.0) (872 RAM - 5992 ROM - 3206 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.IO (4.1.2821.0) (740 RAM - 4620 ROM - 2522 METADATA)
Attaching file.
Assembly: System.IO (4.1.2821.0) (1548 RAM - 13292 ROM - 5862 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware.SerialPort (4.1.2821.0) (512 RAM - 3488 ROM - 1543 METADATA)
Attaching file.
Assembly: Microsoft.SPOT.Hardware.Usb (4.1.2821.0) (580 RAM - 3740 ROM - 1844 METADATA)
Attaching file.
Assembly: SecretLabs.NETMF.Hardware (4.1.0.0) (256 RAM - 1108 ROM - 491 METADATA)
Attaching file.
Assembly: SecretLabs.NETMF.Diagnostics (4.1.0.0) (180 RAM - 440 ROM - 166 METADATA)
Loading Deployment Assemblies.
Resolving.

Total: (10500 RAM - 88932 ROM - 49070 METADATA)

Total: (10500 RAM - 88932 ROM - 49070 METADATA)
Ready.
Cannot find any entrypoint!
Done.
Waiting for debug commands...

I'm having a similar issue. Although the PC recognizes the N+, (deployed fine as of last night and many times before, no new firmware etc). It just stops when trying to deploy. More odd, if I unplug the USB, the machine hard reboots immediately. Uninstalled the USB device, rebooted. Everything. I'm at a loss...Any help appreciated. ------ Build started: Project: NetduinoPlusApplication1, Configuration: Debug Any CPU ------ NetduinoPlusApplication1 -> C:\dev\netduino\NetduinoApplication1\NetduinoPlusApplication1\bin\Debug\NetduinoPlusApplication1.exe ------ Deploy started: Project: NetduinoPlusApplication1, Configuration: Debug Any CPU ------ ------ Deploy started: Project: NetduinoPlusApplication1, Configuration: Debug Any CPU ------ Unable to communicate with device - USB:NetduinoPlus========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ========== ========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

This week? Can I pre-order?

May have figured out what you were talking about through experimentation. Here's a picture of what I'm working with right now. The Touch Display by nwazet is pretty awesome with just it's demo and ease of setup. Add in the JavaScript editor and package it for 70 bux and it's a winner. That aside.

 2012-07-21T13-55-22_0.jpg   502.81KB   56 downloads


One of the features of the display is to both read and write to the SD card in order to save calibration settings and store some images to read and display on the screen.

As you can see I've got my Arduino Ethernet Shield Sandwich hooked into Socket6. Powered up and RX/TX are flashing, showing 100M link, etc. I'm hoping that means I didn't mess anything up in creating this and my rookie soldering skills. LCD Display on Socket1 [I believe I read that 1-4 = 1 Channel, 5-8 another. Can't remember what type of channel it was, may not even be related.] but figured keep them far apart, reduce chances of issues. BTW, Is this where virtual I/O comes into play?

When attempting to read or write to the device it gets a general exception. I'm not sure if this is related to the un-implemented I/O options you have not implemented, the proxy between shield and Go. etc. Or I'm attempting to do too much (reading the SD card of the arduino). Forgive my babbling.

Going to experiment with a few things and see what I come up with.

Cheers,
Chris