blackt1ger

Okay, so I  pull out my NetDuino 2 Plus because I need to test some breakout boards via SPI.  Ideal situation, rapid code writing, good testing.

First I upgrade everything to VS2013, firmware, sdk, MF.NET to 4.3.  Got the problem that is the topic of this post.

After a day fighting with it, I decide, "Okay, downgrade, everything used to work....". 

Now, I'm at VS 2010 with MF 4.2, sdk 4.2, firmware 4.2.2.  Still get the same error message.

Steps taken include using NetDuino Update to erase the app image, DFSU (or whatever it's called) works ( I had to reflash to 4.2 with that), NetDuino Update works ( I had to flash to 4.3 with that).....

I'm back on MF 4.2 and Visual Studio 2010. 

I confirmed that my USB driver is from Secret Labs and has the appropriate version number (4.2) for now.

Any suggestions?  Anybody knows what's wrong?

Well, I've got a pretty darn repeatable BSOD situation.  I remember earlier reading that they wished they could get a repeatable case.

Essentially it occurred when I deadlocked the STM in the HAL layer while debugging or attached via MFDeploy.  First, the system disconnects me saying it lost connection.  Then Netduino is dead.  I push-button restart it, and BLAMO - the BSOD.

I could probably tighten up the steps a bit, but a) my computer doesn't like the BSOD, it takes a reeaaaalllly long time to stabilize after rebooting, c) I keep losing points on my "system reliability", d) I'm afraid the WER is gonna tattle to Microsoft and they will revoke my Operating System license.

--Ken

Okay, excuse my blasphemy, but I'm investigating putting FreeOS (or similar) on my Netduino and building a native app.  Yes, this would be a lot of work.....

The way this came about was a need to create/test/build a new STM32 based board.  I took stock of what I had laying around and noticed that the Netduino Plus 2 that I have fits the bill perfectly (well, almost).

What I like is there is not a lot of extra junk on the board (accelerometer, LED's, POT's, Kitchen Sinks, etc).  However, I don't want to totally toast the board from running the base MicroFramework.

I however, need to understand a few things about flashing.  First, I can DFUSE stuff and I can MFDeploy stuff successfully.  I've built firmware and used MFDeploy to push "BuildOutputTHUMB2GCC4.6leFLASHreleaseNetduinoPlus2bintinyclr.hex" 

What I need to understand are the underlying bits - what does DFUSE connect to?  I presume the BootLoader.  Does STM have their own bootloader?  What does MFDeploy connect to? 

And most importantly --- what should I NOT do, to keep everything running?  Ideally, I want to move from a Native STM app to a MicroFramework app and back.

I'm okay with reading docs, if someone can point me to something that is pertinent.  I don't want to start reading the STM FLASH programming guide and then realize that "Oh, Netduino does something a bit different....." after I totally brick my board, have to solder in the JTAG connector headers and buy the STLink cable.

I was wondering if a cheap oscope could be made from the Netduino+2 that I have. 

From my understanding at looking at the code, the AnalogPort read function blocks until it finishes acquisition in the full 12-bit mode.  I've timed this to roughly 70us per read which would only give me a less than 14Khz frequency, if I only used 1 channel.

The ST manual indicates that a smaller resolution would reduce the read time and that a continuous read is possible.

Would if be feasible to modify the Firmware 4.2.2 to a) reduce the analog precision, make the analog precision variable, and/or c) support a continuous read capability?

I'm new to ST (and ARM) but I think I could have a go at it.

Is there a good way to compile the firmware on a Win7 box?