Chris Walker

Hi dmil4781,

Interesting. USB 3.0 ports are USB 2.0 ports with extra pins for the secondary (high-speed) USB 3.0 bus. That kind of behavior really shouldn't happen with USB devices. [There could be a glitch in the NETMF MFUSB drivers...something that we could report to Microsoft if it's a blocking issue.]

Are you alright using your 2.0 ports?

BTW, welcome to the Netduino community,

Chris

Hey ilovetofu,

Can you share more details about your setup?

How does it differ from other Netduino-based keypad projects, electronically? [As a basis...to help understand what you are experiencing...]

BTW, welcome to the Netduino community!

Chris

Hi Greg,

Do you have screenshots of the procedure you're using for flashing the board via DFU? Let's focus on the ST DFU tools for now...those are the "failsafe backup" and should work regardless.

Chris

Hey Dr Who,

On-chip temp sensors aren't part of the core NETMF runtime.

For commercial applications, it can be cool to know what the chip's temperature is, for sure. [No pun intended.]

Chris

The main Netduino Update window always says "STM Device in DFU Mode." 
 
All I want to do is erase the horribly awry code that's running on it. Help!

Aargh, no fun. That sounds like a flaky USB cable (or a USB port that is liking the Netduino "sometimes" during boot). If the STDFU drivers can't pull the OTP flash data during enumeration, you'll see this.

It sounds like you're up and running now, building your new bot...but if you ever run into this in the future you can also use the STDFU tools. In particular the STDFU Tester utility will let you erase the first page of "app deployment" flash by page range...which would get you back up and running. Not a pretty workaround, but a backup option just in case.

Chris