EvanLaske

Anyway, this has been fixed in the v4.1.1 alpha 5 firmware.

I know this is probably a stupid question, but is this fix included in the 4.1.1 beta firmware as well. (I just don't want to be wrong in assuming that everything from alpha made it into the beta)

Joe,

I also wanted to make sure the problem that was occuring is the same one I am experiencing: As long as I didn't put the code loaded on the netduino into debug mode through VS (whether that's because I reset it with the reset button, unplugged and re-plugged in the USB cord, or booted with only the power port). The only way that COM2 worked was through starting the code by deploying in VS and having it boot it up.

Could you try if the attached project "fixes" your problem?

I looked at the code, and it looks like the things I was going to try. I just had no idea (I didn't try) that the SPI port would function properly if configured with GPIO_NONE as the SSEL pin. I'll have to go ahead and try just using the pin externally until there is a firmware fix.

Maybe in my free-time I'll look into the firmware myself and figure out if there's a quick fix... Until then, this patch should work.

Thanks for your help! I'll have to look into the amount of time lost in the managed code fix. I am sure it's relatively hefty.

It's up to Chris to reply for a permanent fix, but!

If you need it quickly I can try to write a software work-around for it, I think it's possible. Only requirement would be that you use a modified version of my MultiSPI class. I have an idea about how to work around the problem. It will slow down the SPI bus a bit though, if I get it to work.

I'd be curious to see what is causing this problem in the firmware. I haven't delved into it to even know what's going on in there yet, but I'm sure I will sometime. I just was hoping it'd be on my own terms, lol.

Also, I've heard you talk about the MultiSPI class, but haven't seen it. I'd like to see if we can use it.

Any word on what causes this in the Firmware; or a fix for this? I am working on a project and we just so happened to already design a board to use this pin as a SSEL pin on the Netduino Mini... That was of course before we tried that same hardware-SPI pin on the Netduino and found it didn't work.

I know your problem was fixed, but you might want to look into this code on the forums:

I2C EEPROM "Library"

It uses the I2CBus class from Fusionware to implement an EEPROM API, which the 24LC256 is part of. I am working on improving a couple things on it, but it works well. I haven't tested random read/write operations with it, but then again, I am running the current release firmware (not beta).

Just thought it might save you some time.

Edit: I decided to test the random read/write, and it worked even with the stock firmware. Although, I am using an off-brand chip currently (CAT24C256), I originally was using the Microchip chip.