 |
||||||||||||||
|
|
|
||||||||||||
CW2's ContentThere have been 148 items by CW2 (Search limited from 29-April 23) #57132 Accessing the Timer/Counter block
Well, there are no classes for direct timer access in the current version of .NET Micro Framework, mainly due to the fact that the managed (C#) code is interpreted and running considerably slowly than native (C++) code. IIRC simple pin toggling loop on Netduino gen. 1 can achieve ~10 kHz. Even if you were able to access the timers, you would not have much time to run managed code in the interrupt handler (if at all).
What do you want to do? #57051 Analog Output
In addition to what Nevyn said, you could use PWM with low-pass RC filter as cheap D/A converter. #57050 Adafruit Ultimate GPS with N+2. Any experiences?
#57039 Adafruit Ultimate GPS with N+2. Any experiences?
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. #57035 Interrupt Port and Input Port Read Values are Wrong on First Interrupt.
I have not tried to reproduce the behavior, but there is one fundamental issue with using port.Read() in the interrupt handler: because the interrupts are queued, the handler is executed after a certain period of time, thus port.Read() returns the port state at the time the interrupt handler is being executed, not when the interrupt occurred. This can cause incorrect results, especially when the pulse duration or frequency is close to execution time of the interrupt handler (managed code).
I guess a better way is to use two interrupt ports, both set up for falling and rising edge (InterruptEdgeBoth) and use the handler parameters data1 (port number), data2 (port state, 1/0) and timestamp in a state machine (you can reuse one xxx_OnInterrupt handler). #56884 Netduino 2 Firmware v4.3.1 with GCC support
Well, assuming that you don't have JTAG/SWD in-circuit debugger, the options are... ...challenging
#56883 I2C Bus Problem - Debugging
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... #56879 Netduino 2 Firmware v4.3.1 with GCC support
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 support
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 support
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. #56867 Compiling Custom Netduino Firmware: Step-By-Step Instructions - Help
#56866 Netduino 2 Firmware v4.3.1 with GCC support
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 #56778 Native Code in C++
Well, it depends on what exactly do you mean by "MiniJTAG"?
You'd need in-circuit debugger/programmer to deploy and debug the code, popular choices are for example ST-LINK/V2 or Segger J-Link. There are many others, but you should check VisualGDB support; they have tutorials for ST-Link and J-Link, so these two should work. They have standard 20 pin 0.1" pitch JTAG connector, so you'd need also an adapter for 10 pin 0.05" pitch mini JTAG, which looks like this or this, and if your Netduino does not come with the pin header, you'd need it too (FCI part at Digikey, or similar).
Tip: You can make el cheapo mini JTAG header from a copper wire: cut 10 pieces about 10 mm long from solid core copper wire that fits into Netduino board holes, insert them all into the female header so they stay in place and have proper length, stick through the board, solder and carefully cut the excess #56773 Emulator, can it handle OneWire ?
What exactly would you need to do? The 1-Wire protocol has built-in mechanism for enumerating the devices present on the bus, all implementations I've seen support that - in the particular case of .NET Micro Framework, have a look at OneWire.FindAllDevices() method. #56765 Native Code in C++
Unfortunately, Visual Studio does not support deployment over JTAG and I am not sure its ARM compiler can generate code for Cortex-M series. Probably the closest thing is VisualGDB. #56736 Netduino Plus 2 Firmware v4.3.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. #56666 ND1 - Input is always TRUE
#56639 ND1 - Input is always TRUE
Quiz question: What return value do you expect from an unconnected input pin?
The thing is that you created input pin with ResistorMode.PullUp, which means the pin is in logic high (returns true), unless it is connected to other logic level (logic low, ground). Thus, if you want your input pin Read() method to return false, you have to wire the pin to GND.
If you use a port in output mode, its Read() method basically just returns the current state - i.e. the initial state passed via constructor parameter or what was set in the last call of Write() method. #56625 Source Control for Porting Kit and netduino
There are certainly more ways how to do it, based on personal preferences and development workflow, but you'd probably need to set up a few branches - I usually use something like this:
master O-- ... --[My 1.0]...
\ ^
netmf \--[NETMF4.3]--[NETMF4.3QFE1] ... [NETMF vNext] /
\ \ (merge) /
netduino \--[SL 4.3.1] ... [SL vNext]... /
\ /
my-netduino-changes \[Change #1]--[Change #2]... /
This allows me to have complete reference of the official .NET Micro Framework codebase (it would be easier if the Microsoft team decided to use git on CodePlex) and also vendor firmware releases. Every new release is simply added to the appropriate branch, then you can decide what changes will be merged where, if at all. Similarly, development of modifications (features, bug fixes, whatever) happens in a dedicated branch and the finished work will be merged where needed - although it might sound a little bit complicated at first, it is actually very easy to do, especially in git.
#56577 Compiling Custom Netduino Firmware: Step-By-Step Instructions - Help
The Cortex-M is not supported in the build files, you'd have to add appropriate -mcpu directive in the Microsoft.Spot.System.GCC.Targets file; plus a few other changes. The easiest way is to download Microsoft.Spot.system.gcc.targets from NicolasG's repository, copy it into \Tools\Targets directory (overwrite the existing one). However, you'll get several other errors, some were introduced in BitConverter.cpp, also there are missing GCC scatterfiles in Netduino2 solutions, which are mandatory for the linker. I am now working on fixing GCC support for Netduino2 solutions, I'll publish the source code with detailed instructions when it's done. #56570 Compiling Custom Netduino Firmware: Step-By-Step Instructions - Help
The 'PORT' parameter is not used in NETMF 4.3, you should call setenv_gcc.cmd:
setenv_gcc.cmd 4.6.2 C:\Yagarto-4.6.2
The version number (4.6.2) must match the directory name in lib\gcc\arm-none-eabi. #56508 Compiling Custom Netduino Firmware: Step-By-Step Instructions - Help
The Express edition is not enough for building the firmware, you need Visual C++ compiler too, that means Visual Studio 2012 Professional or higher. #56283 PT100
Short answer: the PT100 is a resistive sensor, so you cannot connect it directly to an analog input. Long answer: You'd have to use at least a voltage divider circuit, so you can measure the voltage drop over the sensor and make sure to use low current - usually up to [only] 1 mA, to prevent sensor damage and also reduce self-heating. PT100 is a precision sensor and getting accurate measurements require non-trivial circuits - for example, PT100 has about 20 ? difference in temperature range 0 - 50°C, which at 1 mA translates to 20 mV; also the parameters of microcontroller's ADC has to be considered. I'd recommend you to do some more research and have a look at articles like PT100 sensor - help a beginner? or Can't get a precise reading with PT100 temperature sensor. You might end up with the bridge configuration plus op-amps, or a specialized IC... | ||||||||||||||
|
||||||||||||||
|
|
|
||||||||||||
|
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | |
||||||||||||
|
||||||||||||||
Posted by
