Rage9532

I'm trying to get a Netduino Plus upgraded to 4.2 but an unable to get it to start TinyBooter 4.2. I can erase the chip with 3.3v to the ERASE pad, then replug the board into USB. Samba 2.1-CDC can see the board, execute the scripts, and upload the TinyBooterDecompressor.bin file and a compare of the file and what's loaded passed. Close Samba then unplug and replug the board with the button held down to start the TinyBooter. Wait a few seconds and start MFDeploy. Switch MFDeploy to USB and the NetduinoPlus never shows up in the drop down next to it and an unable to ping the TinyBooter. I've tried this 20 times with no success. But, I can use the exact same procedure to successfully use MFDeploy to ping TinyBooter out of the 4.1 firmware package. It'll even take the 4.1 firmware without any problems. I just cannot get it to run TinyBooter out of the 4.2.0.0 firmware package. I've also redownloaded it a few times to make sure it's not corrupted. [ E D I T ] Nevermind! I screwed up and was not using the new MFDeploy version in C:\Program Files (x86)\Microsoft .NET Micro Framework\v4.2\Tools [palm to forehead smack]

Hi guys! This is my first post here. I'm am very new to micros and electronics, so please excuse if this is a light-weight question. I've been playing around with a N+ for the last week and find it pretty easy to do just about anything at a pin-level in code, with each pin being individually addressable. But, what if you want to treat a block of pins as a single unit? I believe the ATMegas call this a PORT. Each pin maps to a single bit in a value written to the PORT making it very easy to change the values of multiple pins with a single write operation. I haven't seen anything similar in the .NETMF or N+ SDKs. Is there some equivalent that I'm missing?? I know, I could easily write an emulation of this myself, but what I'm looking to do is save all the CPU cycles by avoiding the bit-shifting over a byte. Great litle product! I'm already looking forward to 4.2.