120 replies to this topic

[Chris Walker]

Thanks for the quick reply Chris. Do I also need to change the AssemblyVersion in AssemblyInfo.cs?

Not unless you want to. That's the version that the author is calling his DLL...not the version of NETMF. They might be the same, if the author chose to do it that way. It's up to them.

[Douglas.Hampshire]

I tried updating my N2+ from 4.30 beta to 4.3.1 all went smooth including the Netduino Update to 4.3.1, however after reboot The MFDeploy tool no longer sees the device. If I put it back into boot loader mode it shows up in the update tool and allows it to be updated again but with same results. I have tried erasing the app and re-updating but still no joy. Any Ideas?

Thanks,

Doug

[Chris Walker]

Hi Doug,

I tried updating my N2+ from 4.30 beta to 4.3.1 all went smooth including the Netduino Update to 4.3.1, however after reboot The MFDeploy tool no longer sees the device. If I put it back into boot loader mode it shows up in the update tool and allows it to be updated again but with same results. I have tried erasing the app and re-updating but still no joy. Any Ideas?

Does the device appear in Device Manager? What does it appear as?

What version of the Netduino SDK do you have installed? 4.3.1?

Chris

[GeBrander]

I am getting a "1628: Failed to complete installation" error when installing the DfuSe_Demo software. Anyone also problems with it?

 

Windows 8.1 x64

Visual Studio 2013

 

On an Intel NUC Core i5 system

 

Already tried the x64 and x86 version, no block on the file in Windows, also tried runas Administrator and compatibility mode with different sessions. Redownloaded the setup files but also no success.

[Douglas.Hampshire]

It did show up under Other as a unknown device and stated that it does identify any device drivers for it. I ran repair on the 4.3.1 sdk and the drivers installed and it is now working.

Thanks for the tip

[cce1911]

Hi cce1911,
 

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.

Now

 

Chris,

I just wanted to let you know that I was able to resolve my problem by compiling the toolbox with the 4.3.1 code.

-Capel

[Chris Walker]

Hi GeBrander,

I am getting a "1628: Failed to complete installation" error when installing the DfuSe_Demo software. Anyone also problems with it?

Hmm, interesting. I have the same setup as you (Windows 8.1 x64, VS 2013).

Can you check in your two Program Files folders, and make sure you clear out any old copies of DFUSE first? And before you do that, make sure no old versions are in "control panel > programs and features"?

Also, be careful when deleting files from "Program Files"...that's manual surgery. I typically rename folders instead of deleting them--to make sure I can "go back" easily.

Chris

[mbargar13]

I have tried to get the NetduinoUpdate tool to see the netduino but i get nothing. I am on 4.2.2 and have been able to re-flash to the old firmware of 4.2.2, but the the tool just wont see the netduino. I have followed the instructions and it just does'nt see it. Any ideas?

[Chris Walker]

Hi mbargar13,

I have tried to get the NetduinoUpdate tool to see the netduino but i get nothing. I am on 4.2.2 and have been able to re-flash to the old firmware of 4.2.2, but the the tool just wont see the netduino. I have followed the instructions and it just does'nt see it. Any ideas?

What tool did you use to reflash the old 4.2.2 firmware?

If you're using DFUSE tools:
1. When "ST Device in DFU mode" appears in the DFUSE tools (when your board is in bootloader mode), does the device also simultaneously appear in "Netduino Update"?
2. If the answer to #1 is "no", what version of DFUSE tools are you running? Are they the version recommended in in the first post of this thread?
3. If the answer to #1 is "no" and you're running the tools from the first post...is there anything different about your computer (regional settings, language etc.) which our enumeration might be tripping up on?

Chris

[mbargar13]

Hi mbargar13,

What tool did you use to reflash the old 4.2.2 firmware?

If you're using DFUSE tools:
1. When "ST Device in DFU mode" appears in the DFUSE tools (when your board is in bootloader mode), does the device also simultaneously appear in "Netduino Update"?
2. If the answer to #1 is "no", what version of DFUSE tools are you running? Are they the version recommended in in the first post of this thread?
3. If the answer to #1 is "no" and you're running the tools from the first post...is there anything different about your computer (regional settings, language etc.) which our enumeration might be tripping up on?

Chris

 

I followed the process to upgrade to 4.2.2 by using the steps on the main post, though I am using "DfuSe Demo (v3.0.3)

1. No, if i put the device in bootlooder mode and open the DFU tool i can see it and flash it fine, but when I open the "NetduinoUpdate" tool I done see anything
2. Yes I have downloaded the correct tools and I am using "DfuSe Demo (v3.0.3)"
3. Standard United States settings, nothing unusual

[Chris Walker]

Hi mbargar13,

Can you do the following really quickly, to help us debug this with you?

1. Put your Netduino into bootloader mode.
2. Open DFUSE on the left side of your screen and NetduinoUpdate on the right side of your screen.
3. Take a screenshot, with the two side by side, and attach it to this thread (or PM me with it, if you prefer).

Chris

[mbargar13]

Hi mbargar13,

Can you do the following really quickly, to help us debug this with you?

1. Put your Netduino into bootloader mode.
2. Open DFUSE on the left side of your screen and NetduinoUpdate on the right side of your screen.
3. Take a screenshot, with the two side by side, and attach it to this thread (or PM me with it, if you prefer).

Chris

Attached Files

•  Netduino_UpdateTool.jpg   216.38KB   9 downloads

[MoonWalker]

Hi Chris,

 

went all smooth thank you for your effort!!

 

br

Attila

[Jason.Net]

Works like a charm in VS2012.

 

Thanks for all of the hard work.

[Homey]

Chris

 

Is CTS/RTS working in this firmware release by initializing the serial port with Handshake.RequestToSend?  Aka automatically toggling pins 7,8 (Com2 RTS, CTS)?  I apologize in advance if this is answered somewhere else.

 

Thanks

 

Homey

[Chris Walker]

Hi Homey,

Is CTS/RTS working in this firmware release by initializing the serial port with Handshake.RequestToSend?  Aka automatically toggling pins 7,8 (Com2 RTS, CTS)?  I apologize in advance if this is answered somewhere else.

Yes, pins D7/D8 should be actin gas COM2 RTS/CTS if the serial port is initialized that way. If it is not working properly for you, please let us know so we can file a bug report.

Chris

[sspw]

 

Hi mbargar13,

Can you do the following really quickly, to help us debug this with you?

1. Put your Netduino into bootloader mode.
2. Open DFUSE on the left side of your screen and NetduinoUpdate on the right side of your screen.
3. Take a screenshot, with the two side by side, and attach it to this thread (or PM me with it, if you prefer).

Chris

 

I had same problem. Successful firmware update then didnt show up. I went back and repaired the 4.3.1 sdk install and the drivers work now.

[mbargar13]

 

Hi mbargar13,

Can you do the following really quickly, to help us debug this with you?

1. Put your Netduino into bootloader mode.
2. Open DFUSE on the left side of your screen and NetduinoUpdate on the right side of your screen.
3. Take a screenshot, with the two side by side, and attach it to this thread (or PM me with it, if you prefer).

Chris

 

Any idea on this one yet? I did a repair of the 4.3.1 SDK and still don't get anything to show up. I can flash it the old way if I can have access to the dfu file.

[mbargar13]

Any idea on this one yet? I did a repair of the 4.3.1 SDK and still don't get anything to show up. I can flash it the old way if I can have access to the dfu file.

Ok so the code i guess looks for the Firmware folder, i moved all of my firmware files around and that was causing the app not work correctly. I just now unzipped the file and left it the way it was and ran it that way and it worked.

[Chris Walker]

Hi mbargar13,

Ok so the code i guess looks for the Firmware folder, i moved all of my firmware files around and that was causing the app not work correctly. I just now unzipped the file and left it the way it was and ran it that way and it worked.

Very interesting. In theory the app should show boards as "ST device in DFU mode" if matching firmware is not present...but there may be some combination of folder movements which causes the device to not appear at all. If you have some free time and can let us know exactly how the files were re-arranged...we'd love to eliminate that as an edge case for future users.

On DFU files...if you ever want to create a DFU file (to flash the manual way), use ST's "DFU File Manager" program. It can convert each of the .S19 files to .DFU files for you.

I'm really glad this is working now for you (with the update app unzipped the default way). If you run into any other issues, please let us know. And if you have time to give us more feedback on the manually-moved-folders issue, thank you a bunch in advance.

Chris