Hi Chris,
Does this version support OneWire? As I remember it was planned to support it?
Thanks
Emmanuel

  | ||||||||||||||
Netduino Plus 1 Firmware v4.2.0 (update 1)
Started by Chris Walker, Sep 19 2012 10:03 PM
144 replies to this topic
#81Posted 19 February 2013 - 01:16 PM Hi Chris,
Does this version support OneWire? As I remember it was planned to support it?
Thanks
Emmanuel #82Posted 22 February 2013 - 01:52 PM
Ok, I fail already at the first step What exactly is the ERASE pad?
Greets, Markus NeonMika.Webserver
If you need help with NeonMika.Webserver, please just leave a note in the thread and/or contact me via Skype
----------------------------------------------------------------------------------------------------------------------------------------------------------------------- #84Posted 22 February 2013 - 03:59 PM Markus,
On the generation 1 boards (except mini) you uses a small gold colored square just inboard of the D0 header for erasing the board. Use a jumper from 3.3 vdc and touch the square for about a 1/2 second.
Then reflash.
The generation 2 boards are erased with STDFU Tester.
Chuck #85Posted 23 February 2013 - 11:57 AM
Same blocking problem, Your solution works well!
Thank you! Emmanuel #86Posted 25 February 2013 - 03:43 AM
Hi Emmanuel,
No OneWire support for the first-generation Netduinos yet in 4.2. CW2 sent over some bugfixes for the OneWire support recently, so now we're trying to find room to squish it in We're also trying to squish the 4.3 firmware to fit onto Netduino Plus 1. It's quite possible that we won't be able to get both the 4.3 enhancements and OneWire to fit on the first-generation boards...but if we can then this might skip 4.2 and concentrate all of our efforts on getting Netduino Plus 1 + OneWire + NETMF 4.3 together. Netduino 2 and Netduino Plus 2 both support OneWire, since there was plenty of room for it. Chris
#87Posted 26 February 2013 - 01:34 PM Hi Chris,
I have tried to update to my Netduino Plus to 4.2.0 update1 under VMware Player 5.0.1 with Windows 7. Tried that 6-7 times. I have erased the Netduino and uploaded the bootloader for 4.2, followed every single step to the point.
No joy at all. Got some monkey symbols in FMDeploy when trying to connect and set my Network settings. Most of the time cannot recognise and connect to the device
Any ideas?
PS I've tried this with 4.1.0.6 - every time the process goes smoothly. #88Posted 27 February 2013 - 03:32 AM
Hi georgejh,
Hi Try switching to the legacy MFUSB drivers in VMware. http://forums.netdui...-mfusb-drivers/ There may be a compatibility issues between the integrated WinUSB drivers and VMware that would affect the first generation Netduino Plus (since its hardware is designed not to re-enumerate during reset). Chris #89Posted 27 February 2013 - 12:40 PM
Cool, I'll try that ASAP and will report results here. Cheers #90Posted 27 February 2013 - 06:04 PM No joy at all - both drivers are working with 4.1.0.6 but neither is working with 4.2.0.1 #91Posted 28 February 2013 - 05:22 AM
Hi georgejh,
What edition and version of VMware are you using? On what host operating system? It's possible that VMware doesn't agree with the new USB setup in .NET MF 4.2. There was a lot of work that went into making .NET MF 4.2 work on Netduino gen1 but in the end you may be better served with .NET MF 4.1. Other VMs such as the no-charge Oracle VirtualBox may work better as well. I haven't tested the new gen2 hardware with VMware, but we designed it with the new USB setup from .NET MF 4.2 in mind. BTW--I'm surprised that the WinUSB driver worked with 4.1.0.6, since 4.1.0.6 doesn't have the WinUSB configuration reports. But I suppose that's a testament to the robustness of the WinUSB drivers. Chris #92Posted 28 February 2013 - 08:36 AM
Latest VMware Player 5.0.1 build-894247 with Windows 7 32bit SP1 with all up to date updates installed #93Posted 01 March 2013 - 12:16 AM
Do
Would you have time to install Oracle VirtualBox and see if it exhibits the same issue? Officially (from the product specs page) there is "limited USB support" for VMware and Oracle VirtualBox. This is due to the way that VMs deal with virtualized USB. That said...we'd still like to provide the best possible experience (although in this case...it may be through another VM or through gen2 hardware). Chris #94Posted 01 March 2013 - 10:13 PM
It is definitely virtual machines issue - not working neither on VMware neither on VirtualBox but work in non VM environment. #95Posted 03 March 2013 - 06:11 PM
I'm tryng to update my netduino plus from v4.1 to v4.2.0.1 to work with this on windows 8 , and I've followed all the pass: I installed without problems TinyBooterDecompressor (I followed this wiki: [url="http://wiki.netduino.com/Installing-the-TinyBooterDecompressor-step-by-step.ashx"]http://wiki.netduino.com/Installing-the-TinyBooterDecompressor-step-by-step.ashx).After this , when launched mdfdeploy and pressed "ping", Netduino retuned ": Pinging ... TinyBooter Bootloader build info: Netduino Plus (v4.2.0.1) by Secret Labs LLC" Once installed tinybooterdecompressor after running the ping test,I selected the files ER_FLASH and ER_CONFIG , and pressed Deploy and wait at the end (CChk signature Signature PASS) After flashing and rebooting except if I press the button of the Netduino, the Netduino is not Recognized by Windows 8 Only if I press the button of the Netduino when attach the usb, the Netduino is recongnize ok by Windows 8 but if I run MdfDeploy when I try to verify the version of the current firmware by Selecting the "Target-> Device Capabilities" menu option the result was "not supported" ( of course if I try to launch Visual Studio and try to deploy source dont' work) I don't know where can be the problem .....!!Lot of thanks!!(sorry for my bad english)
#96Posted 03 March 2013 - 09:56 PM
#97Posted 03 March 2013 - 10:04 PM I've had the same problem that you said in the post . I'm interested in how you had fix it . Don't you use the mfdeploy to flash the Netduino Plus to 4.2.0.1 firmware ?(I've understantanded that you flash the 4.2.0.1 firmware using SAM-BA(not with the mdfdeply)? #98Posted 05 March 2013 - 07:16 AM
Hi soloelectronico,
Can you try switching to the legacy MFUSB drivers and see if that gets your Netduino Plus working on your machine? To clarify, you use SAM-BA to flash the TinyBooter bootloader to Netduino Plus 1. Then you use MFDeploy to flash TinyCLR (.NET MF runtime). The gen1 hardware can't handle loading everything in one pass. Chris #99Posted 05 March 2013 - 10:03 PM
#100Posted 07 March 2013 - 10:50 PM
Hello Chris The only thing that is different of the wiki is the version of SAM-BA (v-12) and the name of the version of board ( AT91SAM7X512 AU) because the only item similar is at91sam7x512-ek (ek when the mine is AU) . I'd tried a lot of times to flash Netduino Plus and after the install the Tini BoooterDecompresoor when I try to run mdfdeploy with the 4.1 and 4.2 firmware before this when I plugged it isn´t recognized by my computer ( except I pressed the button) 0 user(s) are reading this topic0 members, 0 guests, 0 anonymous users | ||||||||||||||
|
||||||||||||||
This webpage is licensed under a Creative Commons Attribution-ShareAlike License. | ||||||||||||||