Good news is coming.....
- ... "soon"
- ... "likely in the next few weeks"
- ... "in the coming weeks and months"
- ... "in the future"

  | ||||||||||||||
The Netduino forums have been replaced by new forums at community.wildernesslabs.co.
This site has been preserved for archival purposes only
and the ability to make new accounts or posts has been turned off.
CW2's ContentThere have been 148 items by CW2 (Search limited from 10-May 23) #59469 Windows on Devices? When?Posted by CW2 on 30 July 2014 - 03:49 PM in General Discussion
#59798 Windows on Devices? When?Posted by CW2 on 20 August 2014 - 03:50 PM in General Discussion #58907 Windows on Devices? When?Posted by CW2 on 26 June 2014 - 11:31 AM in General Discussion
In the dotnetConf 2014 session New Innovations in .NET Runtime Andrew Pardoe said:
#59997 Windows on Devices? When?Posted by CW2 on 05 September 2014 - 06:09 AM in General Discussion
Not from my own experience, as I don't use RTOS on any Arduino, but quick check reveals that ChibiOS, BeRTOS, FreeRTOS support AVR (and there is about 40 more in the Wikipedia list that mentions AVR). #56736 Netduino Plus 2 Firmware v4.3.1Posted by CW2 on 10 March 2014 - 11:17 AM in Netduino Plus 2 (and Netduino Plus 1)
I guess you have not set the proper cpu architecture - I think without it the compiler generates some ARM code, which is not supported on Cortex-M cores and TinyCLR is stuck in an fault handler. You'd need to add <DEVICE_TYPE>cortex-m3</DEVICE_TYPE> to Netduino2.settings; and also Microsoft.Spot.system.MDK.Targets might need some additional changes. #59249 Beta: Visual Studio 2013 supportPosted by CW2 on 16 July 2014 - 12:35 PM in Visual Studio I think the most recent is comment by Sal Ramirez on the official .NET Micro Framework blog (posted on 7/11/2014):
#57039 Adafruit Ultimate GPS with N+2. Any experiences?Posted by CW2 on 23 March 2014 - 10:20 PM in Netduino Plus 2 (and Netduino Plus 1)
Was Netduino running during that time?
How far is Netduino from the GPS module? Have you tried adding some shielding to Netduino? If not, try placing a grounded metal sheet between Netduino and the GPS module, or carefully wrap Netduino in aluminium foil and connect it to ground - but make sure it does not short out the pins on the bottom, better to place some paper or tape there. #57050 Adafruit Ultimate GPS with N+2. Any experiences?Posted by CW2 on 24 March 2014 - 07:47 AM in Netduino Plus 2 (and Netduino Plus 1)
#56883 I2C Bus Problem - DebuggingPosted by CW2 on 17 March 2014 - 10:13 PM in General Discussion
For Netduino 2 you need to modify only files in Targets\Native\Netduino_STM32. The STM32 folder contains the original Oberon's implementation, which is not used - Netduino_STM32 is basically STM32 + Secret Labs' modifications.
In fact, you could delete all subdirectories in Targets\Native and Solutions that do not have Netduino,Template or Windows in their name - I usually do that to reduce code search result noise... #58446 Netduino Fritzing partPosted by CW2 on 28 May 2014 - 06:37 AM in General Discussion
#58437 Creating a custom board with Netduino firmware?Posted by CW2 on 27 May 2014 - 05:54 PM in Netduino 2 (and Netduino 1)
That pin configuration is microcontroller-specific. It means the GPIO pin is shared (multiplexed) with another peripheral - it can be configured as third pin of GPIO port A, or TX line of UART2. There is a big table in the datasheet that describes pin functions - most pins have more than one features (I think theoretically up to 15 in ST micros) and sometimes the same signal can be enabled on different pins (e.g. UART2 TX is available also on PD5).
Regarding the names in schematic symbols, it depends - you'd probably need to include at least the GPIO identifier and maybe the alternate function when it is important in your design - like in the above example, "PA2/UART2_TX" indicates the use of TX serial line. Listing all the available features on each pin would require quite large symbol, but I have seen such schematics too (usually, the part is split into several symbols that contain logically grouped features). I think in Fritzing, you can have additional information in the pin description, which is displayed in form of tooltip... #59622 Creating a custom board with Netduino firmware?Posted by CW2 on 08 August 2014 - 08:44 PM in Netduino 2 (and Netduino 1) Impressive. Hats off to doing it all in Fritzing. #58428 Creating a custom board with Netduino firmware?Posted by CW2 on 27 May 2014 - 02:08 PM in Netduino 2 (and Netduino 1) Have a look at the description in the datasheet, it explains it in great detail.
The use of the rest of bootloader pull-up/down resistors is described in the Application Note 2606: basically, when a peripheral (USART, CAN, USB) is used to connect to the bootloader, its "pins have to be kept at a high or low level and must not be left floating during the detection phase". #57323 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 03 April 2014 - 10:20 AM in Beta Firmware and Drivers
Well, you don't have to use that (if you mean the firmware source). Adding GCC support allows you to use free GCC-based toolchains to compile the firmware - otherwise, you have to pay several thousand dollars for commercial ARM toolchains (such as Keil MDK). #56879 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 17 March 2014 - 04:58 PM in Beta Firmware and Drivers Those are libraries and stubs for tools and Windows2 solution, which do not need to be rebuilt when you make changes to a particular solution (your firmware).
There are a few 'clean' targets, you can display them for example by launching msbuild Solutions\Netduino2\dotnetmf.proj /t:Help For a 'complete clean' build, delete the build output directory rmdir /s /q BuildOutput #56876 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 17 March 2014 - 03:57 PM in Beta Firmware and Drivers
No, you can safely ignore this warning. IIRC it is caused by incorrect ToolsVersion attribute value in a few project files, which causes MSBuild 3.5 to be run, instead of 4.0. I have already fixed such issues, but in separate 'cleanup' branch, which will be integrated into a future release... #56874 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 17 March 2014 - 03:46 PM in Beta Firmware and Drivers
According to .NET Micro Framework Porting Kit 4.3 ReleaseNotes.txt "Either Visual Studio 2012 (Express edition or greater) or both .NET Framework 3.5 and Windows SDK for Windows" is required. #56866 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 17 March 2014 - 12:39 PM in Beta Firmware and Drivers Prerequisites
How to build the firmware with GCC
Important notes
Attached Files
Edit 2014-03-18 19:30 UTC: Added Visual Studio to prerequisite list #56884 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 17 March 2014 - 10:42 PM in Beta Firmware and Drivers Well, assuming that you don't have JTAG/SWD in-circuit debugger, the options are... ...challenging
#57195 Netduino 2 Firmware v4.3.1 with GCC supportPosted by CW2 on 28 March 2014 - 11:06 PM in Beta Firmware and Drivers
Yes, the GCC-related modifications have been made for Netduino 2 firmware only. But the most-important ones were made in the core .NET Micro Framework source code and are shared by Netduino Plus 2 firmware too - basically, adding a proper scatterfile and fixing possible GCC compiler errors in the additional libraries the Plus 2 firmware uses (network etc.) should be all that is needed to make GCC built firmware for the Plus 2.
Well, the modifications are available under Apache 2.0 license, so both Microsoft .NET Framework and Secret Labs teams can easily integrate them into their respective code And there are always alternative ways #59621 High Resolution Quad Encoder ProblemPosted by CW2 on 08 August 2014 - 08:40 PM in General Discussion
If you are referring to quadrature encoder inputs then no, it is not a secret. It is described in the STM32 datasheet, in fact many [modern] microcontrollers have such interface. For STM32F4 there is firmware with QuadratureEncoder class by NicolasG (for FEZ Cerberus, but it should not require too much work to port it over to Netduino gen 2). #59616 High Resolution Quad Encoder ProblemPosted by CW2 on 08 August 2014 - 07:19 PM in General Discussion
They cant, but some of them (gen 2) have [hardware] timers with quadrature encoder inputs #57316 .NET MF 4.3 QFE1 RTMPosted by CW2 on 03 April 2014 - 06:46 AM in General Discussion The SDK and Porting Kit Documentation link was fixed today #59394 Control 80V DC Motor/Bulb Using Netduino 2Posted by CW2 on 25 July 2014 - 01:54 PM in General Discussion There is one major problem with interfacing P-channel MOSFET to a microcontroller when switching [relatively high] voltage - when the control circuit closes, the switched voltage (i.e. 12, 60 or 80V) is applied to the microcontroller pin and it will be destroyed, because Netduino max pin voltage is less than 10V.
You have to use second N-channel MOSFET (or NPN BJT) placed between Netduino pin and P-channel MOSFET gate to control it. The proper circuit looks like this:
You can replace Q3 + R3 with N-channel MOSFET (use R3 as pull-down, connected between gate and ground to ensure safe 'off' state).
I would recommend you to get a few different transistors and try low voltage (3.3V - 5V) circuits first, switching simple loads like LED and evaluate the possible configurations. After you understand how they work, you can 'upgrade' to higher voltage and current. Random messing with wires without understanding the basics is not going to end well... #59389 Control 80V DC Motor/Bulb Using Netduino 2Posted by CW2 on 25 July 2014 - 12:52 PM in General Discussion Yes, if you want to control the positive wire, you'd need P-channel MOSFET. The control logic is inverted, low gate voltage is 'on', high gate voltage is 'off'; and there should be a "pull-up" resistor between gate and +V to ensure safe 'off' state.
Yes, N-channel MOSFET is cheaper than P-channel; N-channel is a little bit better (lower resistance, which means lower power losses, which means smaller heatsink : )
| ||||||||||||||
|
||||||||||||||
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | ||||||||||||||