rhamer

I am wondering if it is possible to deploy and debug via the ethernet port rather than the USB? It appears from what I have read it is possible on some other manufacturers boards. Regards Rohan

I have started this thread as a place to gather any wisdom regarding the dreaded deployment problems plaguing the Netduino. These problems are extremely frustrating, and so any ideas would be greatly appreciated. So, if you have discovered a way of bringing your Netduino back to life, or even better, stopping the problem all together, then please share it here. For the record I have tried typing "plugh" and "xyzzy" to no avail (one for the old timers) :-) My particular problems are the BSOD and failing to deploy. so far the only guaranteed solution is to do the following; 1 Cancel the deployment. 2 Unplug the USB. 3 Power down the project (my Netduino is a mounted as a sub board to a larger PCB that also powers it) 4 run mfdeploy 5 plug in USB 6 erase current programming (this is a few steps in mfdeploy) 7 if still not working, shutdown VS2010 (sometimes this gives BSOD) 8 if still not working reboot PC. Regards Rohan

I know this is a loaded question, but is there really any actual date defined for the release of V4.2? I am having so much trouble with the current Beta, that I just cant imagine it being any time this year. Unfortunately I have only a few weeks left to finish my product, and I just can't afford the time I waste every day with deployment issues. it may be ok for a hobbiest, but for a comercial application like mine, it is costing far too much in lost time. I chose the Netduino against the wishes of my superiors, because I can see that it will be a fantastic platform one day. But right now I think I'll be retiring before I see that happen. Today I kept a record, and over 4 hours was wasted over the course of a day with deployment issues, that would constantly stop me in my tracks. I don't know what it is that triggers them, nor do I know the magic formula for getting it going again, but it involves everything up to and including rebooting the PC and manually erasing the Netduino. I just can't wait any longer, and I'm going to have to find another solution. My only hope is a positive response to this post, and a new much more stable version within a week. So what are the chances? Regards Rohan

What I mean is, are there timers that I can set an interval for, enable or disable, and have an event fire (and handled through an event handler) when the timer expires? Exactly like a timer gadget in the grown up .net If so can someone point me to an example. Regards Rohan

I have just encountered some strange behaviour with the socket.send() method in V4.2

using the following code, I get an exception thrown on every ninth byte.

    Public Function SendData(Data As Byte) As Boolean

        Dim ret As Boolean
        Dim DataByteArray() = {Data}

        Try
            clientSocket.Send(DataByteArray)
            ret = True
        Catch ex As Exception
            ret = False
        End Try

        Return ret

    End Function

This happens reliably every time.

The other odd thing is when I look at the data using wireshark, the data in the packets is always as follows.

1 data byte
7 data bytes
(exception thrown byte never sent)
1 data byte
7 data bytes
(exception thrown byte never sent)

this pattern continues until there is no more data to send.

If I catch the false return from the above method and just call the method again with the same byte, it works, so it is not the contents of the byte that is the problem (it is also different with every ninth byte not being the same data anyway)

Recalling the same method after an exception fixes the problem in as much as the byte is eventually sent, but it slows down the execution dramatically as you can imagine, and is not an acceptable workaround.

Can anybody think of something I might be doing wrong?

Regards

Rohan