louyo

Dumb question I guess. I am running the 4.2 SDK and get the following error when I build:

OneWire' does not exist in the namespace 'Microsoft.SPOT.Hardware'

I do have the using Microsof.SPOT.Hardware statement included and the assembly shows up in References. 

Could you please point me to the error of my ways? Is there another version of the dll somewhere?

Thanks much,

Lou

oops, the dummy just found the Hardware.OneWire reference. 

Apologies.

Louyo

Dumb question I guess. I am running the 4.2 SDK and get the following error when I build:

OneWire' does not exist in the namespace 'Microsoft.SPOT.Hardware'

I do have the using Microsof.SPOT.Hardware statement included and the assembly shows up in References. 

Could you please point me to the error of my ways? Is there another version of the dll somewhere?

Thanks much,

Lou

Hmm, that is really bizarre. It should just be pulling in one byte for you. If there's a way for us to repro this here (i.e. feed it data via HyperTerminal instead of via a physical device), we'd be happy to try to repro. Chris

OK, another update. I put a  debug print statement in the routine that gets data from the camera and writes it to the file. I wanted to see how much it read before it crashed. It read the whole thing! The file it wrote, however, was corrupt, not a valid jpeg. That routine gets 120 bytes from the com port and then opens the file, writes the 120 bytes and closes the file (maybe).

SWAG:

It seems to be an: async, reentrant or plain old timing problem and part of the problem is the streamwriter closing thingie, see that thread. This is brought  on by the faster processor. So, for a workaround, one is going to have to find all the asynchrous stuff (or renentrant) and make sure to block until it finishes.

Just my SWAG.

My current "fix" is to press on with my N+ and leave the N+2 for another set of SDK/firmware.

Thanks for taking the time to help those of us mired in the slow group.

Louyo

Hmm, that is really bizarre. It should just be pulling in one byte for you. If there's a way for us to repro this here (i.e. feed it data via HyperTerminal instead of via a physical device), we'd be happy to try to repro. Chris

10-4, thanks for the offer. I will muddle along as I have time, I have moved back to NP as it works there. I didn't get the storage improvement that I hoped for on NP2 anyway. The speed improvement is nice though. I need to go back in and trim more of the code I don't need. 

Thanks again,

Lou

Hi Lou, When you get the exception, how many bytes long is _response? What are the values of _responseIndex and expectedResponseLength? Chris

Response index is 4, expectedResponseLength is 1

_response is 21 bytes long 

Louyo