Oh yes, of course! Updated. Thanks
Hi Chris, maybe a good idea to update the downloads page for the new firmware?
Netduino Plus 2 Firmware v4.3.1
120 replies to this topic
Posted 01 March 2014 - 12:51 AM
Oh yes, of course! Updated. Thanks
Posted 02 March 2014 - 12:25 PM
This version does not work in VS2013? It is working well for me in VS2012, but when I go to make a new project in VS 2013, it does not have the micro framework templates as a option.
Thanks for the update.
Posted 03 March 2014 - 05:44 AM
Uninstall the NETMF SDK and Netduino SDK. Then install them from here:
That should get you up and running in VS2013.
Welcome to the Netduino community,
Posted 03 March 2014 - 02:36 PM
Sorry, I misunderstood. I thought this version was a new version of the VS2013 beta. Thanks
Posted 06 March 2014 - 02:42 PM
after installing fw 4.3.1 i have this bugs :
Assembly: Toolbox.NETMF.Hardware.Core (18.104.22.168) needs assembly 'mscorlib' (22.214.171.124)
Assembly: Toolbox.NETMF.Hardware.Core (126.96.36.199) needs assembly 'Microsoft.SPOT.Hardware' (188.8.131.52)
Assembly: Toolbox.NETMF.Hardware.Core (184.108.40.206) needs assembly 'Microsoft.SPOT.Hardware.PWM' (220.127.116.11)
Assembly: Toolbox.NETMF.Hardware.Core (18.104.22.168) needs assembly 'Toolbox.NETMF.Core' (22.214.171.124)
Assembly: Toolbox.NETMF.Hardware.Core (126.96.36.199) needs assembly 'Microsoft.SPOT.Native' (188.8.131.52)
where to get 4.3.1 toolbox ?
Posted 06 March 2014 - 05:43 PM
The Toolbox source code is included, so you can compile the code in 4.3.1 to get the dll's for your project.
There are several demo's on youtube on Howto compile to get a dll.
Posted 06 March 2014 - 07:55 PM
Thanks for answer,
but i didnt find that...would you like to be kindly more detailed.
Posted 06 March 2014 - 09:58 PM
The NetduinoUpdate deploy software made it effortlessly.
This also solved my problem to erase certain apps using webserver.
"- Somewhere there's a bug to fix..."
Posted 10 March 2014 - 09:16 AM
I compiled 4.3.1 firmware with mdk 4.71.
There is no scatterfile in TinyBooter for MDK. So I copied from scatterfile_bootloader_rvds.xml.
Also scatterfile_tinyclr_mdk.xml file is little bit strange compared with scatterfile_tinyclr_rvds.xml. So I replaced mdk.xml with rvds.xml.
Finally, I succeeded compilation. TinyBooter is working. But TinyCLR doesn't. It wasn't detected on MF deploy.
What should I do?
Posted 10 March 2014 - 10:16 AM
We haven't build MDK scatter files for the Netduino_STM32 BSP yet. It's on the roadmap, but today we use RVDS.
There will likely be small differences between the two build processes, even though they technically use the same ARM compiler now.
My first guess is that there is something wrong with the core-coupled memory (TCM) allocation in your setup. If you feel comfortable tweaking the scatter files, move everything to the main 128KB block (as is done in TinyBooter's scatter file) and remove the TCM section--and see if that works for you.
P.S. we use RVCT 4.1 to compile the firmware. 4.71 may or may not work...not yet tested.
Posted 10 March 2014 - 11:17 AM
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.
Posted 11 March 2014 - 04:31 AM
probably a dumb question, but can you use VS 2010 with this update or do you have to update to VS 2012 to use it?
Posted 11 March 2014 - 05:22 AM
No worries, no dumb questions here.
.NET Micro Framework requires Visual Studio 2012 (or VS2013 with our experimental SDK builds).
Posted 11 March 2014 - 11:02 AM
I got a brand new ND2 + yesterday. I plan to create
a small application which sent data from ND2 + to a web page.
Currently I have everything installt on 4.2Version (NETMF, SDK) (because Netduino GO). VSExpress10 and Window7
What do you think?
Should I immediately upgrade to the new NETMF4.3?
But i think this does also mean to install the new 4.3SDK? ... and ...
that also means upgradeing the ND2 + to 4.3 firmware?
Or can I leave everything on 4.2Version?
Thanks for your response...
Posted 11 March 2014 - 08:21 PM
If you want to upgrade some of your devices to 4.3.1, that's not a problem: the new SDK will still work with devices running older 4.1 and 4.2 firmware.
If you are using .NET MF 4.2 firmware on all of your devices, I'd recommend sticking with Visual Studio 2010 and the 4.2 SDK until you upgrade boards. Why? Because with the 4.2 SDK, Visual Studio is speed-optimized for debugging boards running 4.2 firmware.
That said...we run the latest SDK on all of our computers, working with older and newer board firmware regularly
Posted 19 March 2014 - 04:18 AM
I've upgraded to vs2012, .netmf 4.3 and flashed the firmware successfully. I've upgraded my projects and their references to the 4.3 dlls, but when I go to deploy my programs the I'm getting errors with the .net microframework toolbox. I downloaded the 4.3 DLLs but I'm getting the following.
Link failure: some assembly references cannot be resolved!!
Assembly: Toolbox.NETMF.Hardware.Ic74HC595 (184.108.40.206) needs assembly 'mscorlib' (220.127.116.11)
My mscorlib is version 18.104.22.168.
Posted 19 March 2014 - 04:57 AM
That library was built against the .NET MF 4.3 beta (4.3.0) instead of the production-ready 4.3 QFE1 release (4.3.1).
Do you have the source (so you can change the target framework in Project Properties)?
Posted 19 March 2014 - 12:34 PM
I have downloaded the source, but I'm not real sure how to upgrade it to 4.3.1. Do I have to change the target framework on all 40 projects? Do I have to manually edit the AssemblyInfo files and change AssemblyVersion("22.214.171.124")?
Posted 19 March 2014 - 12:52 PM
In each project, go to project properties (right-click on the project name, select the "properties" menu option).
Then change the "Target Framework" from NETMF 4.3 to NETMF 4.2. It will probably close the window for you when you do this, to save the changes.
Then change the target framework back to NETMF 4.3.
Repeat the above for each project. If there are forty, it may take you 15 minutes. Tedious and no fun, but it should change everything from 'pre-production 4.3' to 'production 4.3.1' for you.
Posted 19 March 2014 - 12:58 PM
Thanks for the quick reply Chris. Do I also need to change the AssemblyVersion in AssemblyInfo.cs?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
|This webpage is licensed under a Creative Commons Attribution-ShareAlike License.|