8 replies to this topic

[Nevyn]

This weekends experiment with the N+ required me to work out how to talk to the N+ over the network. So what better than a small web server. All went well for the first hour or two and then came the acid test - talk to the N+ with a browser. Yippeeee - I'm serving web pages - but only when the debugger is attached and I have a breakpoint set. In any other case I get the following message displayed by the browser: ReadResponse() failed: The server did not return a response for this request. Has anyone else seen this? Thanks in advance, Mark

[Chris Walker]

Hi Nevyn, Hmm, haven't seen that. Instead of debugging, if you open up MFDeploy.exe (Start > Program > .NET MF SDK > Tools) and "connect (F5)" to your Netduino Plus...do you see the same issue? Chris

[Nevyn]

Hmm, haven't seen that. Instead of debugging, if you open up MFDeploy.exe (Start > Program > .NET MF SDK > Tools) and "connect (F5)" to your Netduino Plus...do you see the same issue?

Still the same problem. Here's what I did:

• Fired up MFDeploy as described and received a connected message.
• Started Fiddler and then Chrome.
• Issued a request for the default web page and received the same error as described. HTTP response code is 504.

Now I am issuing some response codes for errors but I do not have 504 anywhere in my code so it's coming from somewhere else.

I have just tried this without Fiddler between the browser and the N+ I get error 324 (Empty Response).

Regards,
Mark

[Nevyn]

Think I have finally found the solution but in doing so it has me a little perplexed. In my app I had the following code:

using (Socket client = _socket.Accept())
{
    int requestSize;

    requestSize = client.Available;
    if (requestSize > 0)
    {
        // Process request here.
    }
}

When the debugger is attached to the project requestSize is always set to the size of the request, in this case 480 bytes. When the debugger is not attached requestSize is zero even though there is some data available. The subsequent call to client.Receive(...) does in fact pull back the 480 bytes of the request even though client.Available is zero.

Is this expected behaviour?

Thanks to all who looked at this.

Regards,
Mark

[Chris Walker]

Hi Nevyn, The RequestSize should be identical whether or not you are attached to the debugger. If you have a small repro case, we'd be happy to look at it. Chris

[Nevyn]

Hi Nevyn,

The RequestSize should be identical whether or not you are attached to the debugger.

If you have a small repro case, we'd be happy to look at it.

Chris

Chris - tried to reproduce in a smaller example but I'm now consistently getting 0 bytes available. According to the API reference I think it should always have a value as there is data there to read and I think I'm creating a non-blocking socket.

Regards,
Mark

[Chris Walker]

Hi Mark, Can you post your example which is getting 0 bytes? Also, make sure you update to the newest firmware (4.1.0.6 rc1 or 4.1.1 a6)... Chris

[Nevyn]

Can you post your example which is getting 0 bytes? Also, make sure you update to the newest firmware (4.1.0.6 rc1 or 4.1.1 a6)...

Updated to the 4.1.0.6 RC1 and code is working.

Updated worked like a dream - always nervous when flashing / updating firmware.

Thanks for the help,
Mark

[Chris Walker]

Updated to the 4.1.0.6 RC1 and code is working.

Updated worked like a dream - always nervous when flashing / updating firmware.

Thanks for the help,
Mark

Hi Mark,

So glad that the update fixed things for you. Woot!

BTW, it's more or less impossible to "brick" a Netduino via firmware update. We've built in multiple backup procedures and in the worst-case scenario you can erase your Netduino (connecting the 3.3V header to the gold ERASE pad via a jumper wire) and reflash everything from scratch. You can even recompile everything from scratch; viva open source

Chris