You have reached the legacy GHI Electronics, LLC website, for the new website please visit here. For the new forum please visit here.

You must be logged in to reply.

Page 1 of 5 out of 41 messages.

GHI Electronics NETMF 2016 SDK Pre-Release 2

9 likes
Posted 1yr ago
by John_ghielectroncs | Employee
Posted 1yr ago
by John_ghielectroncs | Employee
Today we're releasing the NETMF SDK 2016 R1 Pre-Release 2. As long as there are no major issues, this is planned to be the last pre-release for this SDK. Changes in this pre-release are mostly minor. See the release notes for complete details.

- Fixed built in Ethernet LEDs not working
- Fixed various minor issues around CAN, USB client, CDC, and SPI
- Fixed COM2 handshaking on G120 failing due to a pin reservation issue
- Minor networking improvements
- Minor Gadgeteer fixes
- Added SmsSent to Cellular Radio
- Added TinyBooter update in IFU to EMX
- Added the ability to select the COM port used for loader updates in FEZ Config
- Improved loader update instructions and choices in FEZ Config

There are two bigger changes though:

First, we have updated our code signing certificate. You may get warnings that the SDK installer, USB drivers, and FEZ Config are not well known from Windows since it is a new certificate. This will go away as the SDK is used more.

Next, our devices no longer need the USB driver for MFDeploy, Visual Studio, and FEZ Config to see them. They now expose the proper USB configuration needed for Windows to automatically configure them as WinUSB devices and for Micro Framework to discover them. This requires a new TinyBooter for every device though and will only work for devices using the 4.3.8.1 firmware or later.

Additionally, Windows 10 also automatically configures USB serial ports. This means that the USB driver for the GHI Bootloader Interface is no longer needed on Windows 10 and above.

So if you are on Windows 10, are using the 4.3.8.1 firmware or later, and do not need the signed CDC driver, installing the USB driver package is now optional, though everything will still work fine if you do install it. Our SDK installer will still install it by default for now.

Lastly, while we still do not officially support it, we are making an unsupported patch available that allows you to use Visual Studio 2015 with our SDK. The issue with unsupported IL can manifest itself in very weird and subtle ways causing your program to behave erratically or in seemingly impossible ways. We recommend Visual Studio 2013 for production use.

Make sure you are using the latest Gadgeteer core as well.

Latest .NET Gadgeteer Core: http://gadgeteer.codeplex.com/downloads/get/1519812
VS2015 patch instructions: https://www.ghielectronics.com/docs/346/using-visual-studio-2015
2016 R1 Pre-Release 2: https://www.ghielectronics.com/support/netmf/sdk/40/ghi-electronics-netmf-sdk-2016-r1-pre-release-2
1 like
Reply #1 — Posted 1yr ago
by mhstr | Senior | 1,220 exp
Reply #1 — Posted 1yr ago
by mhstr | Senior | 1,220 exp
Hi all,
I have tried to use new 2016 R1 Pre-Release 2 on my daughter's W10 laptop(because my laptop is running W7 and I did not want to change my current setting due to maintain my current G400 project) and I was not successful unfortunately.
I have uninstalled previously installed GHI 2016 R1 Pre-Release 1 and installed Pre-Release 2 - also GHI USB drivers were installed during this installation as they have been offered to install.
Then I have reinstalled bootloader on my G400 and successfully installed new TinyBooter 4.3.8.1. During this process I have received a message a message that something is incorrect with recommendation to restart a laptop so new fimware 4.3.8.1. was not installed.
I have tried to use different laptop running W7 and it seems the installation of new SDK 2016 R1 Pre-Release was successful here so I was able to install also new firmware 4.3.8.1 on my G400 PCB.

I am curious if I am alone with this issue on W10 or somebody else has the same problem.
I would like to also ask if previously installed PCBs with TinyBooter 4.3.8.0 and firmware 4.3.8.0 should be able to update by IFU(and I hope yes) to new TinyBooter 4.3.8.1 together with new firmware 4.3.8.1 and of course with new application updated to 4.3.8.1 libraries? (These PCBs have been already able to update TinyBooter through IFU as 4.3.8.0 introduced this feature).
Reply #2 — Posted 1yr ago
by willgeorge | King | 33,998 exp
Reply #2 — Posted 1yr ago
by willgeorge | King | 33,998 exp
@mhstr -
I have Windows 10 Pro and my installation went fine.

I did have to restart my PC due to a error message when trying to install the new firmware on my Raptor.
(Warning to reboot received from FEZConfig). After that installing the firmware went without any problems.

Edit: Warning was about USB issue
Reply #3 — Posted 1yr ago
by mhstr | Senior | 1,220 exp
Reply #3 — Posted 1yr ago
by mhstr | Senior | 1,220 exp
OK, it seems it was the same warning also on my daughter's laptop but after restart the situation was the same.
Even after restart the FEZ Config didn't see my G400 PCB connected to the USB.
I have tried all USB ports and the situation is the same for all USB ports.
I can see G400 under device manager (without any warning) but neither FEZ Config nor VS2013 is not able to see G400.

I will try to reinstall SDK 2016 R1 Pre-Release 2 to see if it helps...
Reply #4 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
Reply #4 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
several attempts to download GHI Electronics NETMF SDK 2016 R1 Pre-Release 2 (57.06 MB) provided the error message:
'The signature of this program is corrupt or invalid' with the only option 'Delete'
Window 10 insider 14316.
Reply #5 — Posted 1yr ago
by Gus_ghielectroncs | Employee
Reply #5 — Posted 1yr ago
by Gus_ghielectroncs | Employee
@SouthernStars - try a different browser please
Reply #6 — Posted 1yr ago (modified)
by Brett | Superhuman | 125,590 exp
Reply #6 — Posted 1yr ago (modified)
by Brett | Superhuman | 125,590 exp
That error is because of GHI's certificate change. @Gus, what was the cert change you made?

Edit:
I've also noticed that the validation at the end of download seems to take a LONG time (still happening half an hour later), wonder if that's related to the change. Edit2: no, related to the large download like mentioned below.
1 like
Reply #7 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
Reply #7 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
I fear it is worse. There is a known issue with Windows Insider build 14316 with large downloads and in this context, 57 MB is large.
BTW, it is also impossible to update VS, due to several failures while downloading modules by setup, with modeless dialogs with message 'Unknown Error'.
As a result, VS is left in an unusable state, and uniinstall and reinstall doesn't work for the same reason.
Reply #8 — Posted 1yr ago
by Mr. John Smith | Legend | 42,263 exp
Reply #8 — Posted 1yr ago
by Mr. John Smith | Legend | 42,263 exp
@SouthernStars - have you tried a download manager like FlashGet?
Reply #9 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
Reply #9 — Posted 1yr ago
by SouthernStars | Senior | 1,436 exp
For a single file download I may use a W8 computer on our network and then copy it to another computer, but with setup downloading automatically several files we have no control about the donwloader. Hopefully, with about one fast ring release about twice a week, it will be fixed very soon.

Page 1 of 5 out of 41 messages.

You must be logged in to reply.