Windows 10 Build 10586 IoT Core - updated

[slate_dk]

EDIT: now officially released; updated links

ISO http://go.microsoft.com/fwlink/?LinkId=691711

Release notes http://ms-iot.github.io/content/en-US/w ... tesRTM.htm

IoT Core Dashboard http://go.microsoft.com/fwlink/?LinkID=708576

Blog post https://blogs.windows.com/windowsexperi ... um=twitter

[ricl]

Be careful. Installing this on the Pi seems to break VS 2015 deployment (at least on pre RC1, I don't have the heart to do another install/de-install to find out if RC1 has the same problems).

You can still install appx/cer bundles but, at present, I can find no way to get VS to deploy an app, new or old.

[ricl]

So it looks like there is no c:\RDBG in the leaked 10586. Hence no MSVSMON.EXE and thus no deploy/debugging.

[Code Chief]

Nice but shame about the missing debug tools. Also interesting, build 1511 of Windows 10 just appeared on MSDN subscriber downloads. But sadly no MSDN ISO for the Raspberry Pi this time. They did do that for RTM, seems to be held-back for some reason this time. I guess it has something to do with the upcoming announcements next week.

[Code Chief]

Ok after testing the new MSDN desktop shows "version 1511" (not build 1511), how strange. Really not Windows "10" anymore! Running WINVER.EXE shows "Version 1511 (OS Build 10586.3)" instead of "Version 10.0 (Build 10240)".

I tested the image you linked to and the reported version on the IoT start application is 10.0.10586.0. Hmm... not exactly an aligned OS build. In a perfect world we should see an RTM release of this IoT build as version 1511.0.10586.3 if the version reported by WINVER on a desktop is the new style Microsoft have adopted. Maybe that comes next week at that developer conference thingy. Clearly the first two digits are the year (15 = 2015) and the second two the month (11 = November).

I like that, also Windows Update and many other improvements are visible in the web interface. I hope new WiFi adapters are supported. It has better audio options but still no DirectX driver (Microsoft Basic Display Driver) still visible in the device tree.

Regarding the remote debugger I think it's deliberate that it is not included. Because on the debugging page of the web interface there is now a "Start VIsual Studio Remote Debugger" heading with a big start button. Clicking that tells you that it must be installed first and provides a link to the IoT site, specifically the MemoryStatus Console Application sample.

Good news I think, because I have problems with driver development and misalignment between SDK/WDK versions is the cause I think. When Microsoft release the ARM remote debug tools separately for IoT/RasPi then we can install compatible versions with whatever Visual Studio/SDK/WDK version we have at the time. At least I hope that is the plan and that they follow-up with that download link soon!

Thanks for sharing that link, very interesting!

[ricl]

I've tried everyway but loose....and still no deploy/debug. Until MS put up a page on how to copy the 10586 debug client over to the Pi I'm stuck.

Audio appears to now support USB but requires linking to the 10563 IoT extensions to work as opposed to 10240. This may mean that Apps will need to re-compiled to run against 10568 if they use Audio which will be a nuisance. Also, for some reason, the headphone jack on the Pi itself does not appear to work as an output, but the USB Audio does!

Windows Update is nice. Soon we will have to write apps that work against a moving range of output targets. Always one for fun test and debug setups!

I rather suspect that this unintended leak is not what the final 10586 release will be but who knows.

[slate_dk]

I went back to the article from where I got the news:
http://microsoft-news.com/windows-10-bu ... core-leaks

apparently the source is a tweet with links for the various platforms. I think it is legit, they are just not publicly released.

And I expect that updated tools will be released asap. The first update for VS2015 is almost ready, so I expect stuff to happen next week in connection with the Connect event next week (18+19)

[ricl]

I went back to the article from where I got the news:
http://microsoft-news.com/windows-10-bu ... core-leaks

apparently the source is a tweet with links for the various platforms. I think it is legit, they are just not publicly released.

And I expect that updated tools will be released asap. The first update for VS2015 is almost ready, so I expect stuff to happen next week in connection with the Connect event next week (18+19)

It's not only there, its in loads of places with the MS download servers being the original source. In the past when these sort of things have occurred they have rarely turned out to be the actual final release. Just a few steps short of it usually. Who knows though, only time alone will reveal a/the truth.

(And VS RC1 also breaks debug/deploy onto the Pi as well so neither are suitable for install at present if you are using IoT).

[Code Chief]

Another change is in the firmware config.txt:

gpu_mem=32 # set ARM to 480Mb DRAM, VC to 32Mb DRAM
framebuffer_ignore_alpha=1 # Ignore the alpha channel for Windows.
framebuffer_swap=1 # Set the frame buffer to be Windows BGR compatible.
disable_overscan=1 # Disable overscan
init_uart_clock=16000000 # Set UART clock to 16Mhz
hdmi_group=2 # Use VESA Display Mode Timing over CEA
arm_freq=900
arm_freq_min=900
force_turbo=1

So they are setting a fixed clock now. I know that from another company who made a HAT running on Linux with many sensors, who found was necessary to force turbo to get rid of sync issues with some SPI and I2C chips. So Microsoft seem to be moving forwards with their testing/stability (finding and solving the same issues).

Great progress anyway and plenty of teasers for what is to come I hope the deploy/debug issues with different versions can be solved quickly, because they must be stable first to increase the speed of both their remaining development and our "maker" development which justifies the whole project. Looking forward to next week...

p.s. it's probably a good idea to copy those last few lines into your RTM config.txt to minimize issues in the meantime. Personally I also set hdmi_group to 1 which solves initialization problems with some external monitors (I use a 7" FPV monitor).

[breakstring]

The good news is TP-Link TL-WN725N wireless adapter works now.

[ravindrank]

Folks I got the remote debugger running...it turned out to be very simple...

I copied over the c:\rdbg folder from the previous build to the new sd card already running 10586. (I had to reinstall 10556 just to get the files as I wiped my card in a hurry to checkout the new build)

After that it was a matter of run running c:\rdbg\RegisterOneCoreRdbg.cmd and then a reboot and then run StartOneCoreRdbg.cmd..

The debugger doesn't show up in VS list of devices but I used the IP address and voila it deployed my UWP app as usual..

Just wrote up a quick article: http://social.technet.microsoft.com/wik ... 0-iot.aspx

cheers and thx for the new build and hints..

[ricl]

The one last thing I hadn't tried, using the IP address. I did all the other steps . Ah well, a large amount of time consumed installing and removing RC1 wasted.

Thanks for the tip/info.

[ravindrank]

Although since yesterday, it stopped working..Not if it was Windows Update.. which may have done something on the Pi..
It tries to deploy updated .NET core frameworks to Raspi and fails with an error...looking into it.. I guess I will wipe the SD and start again..

[Perez89]

Folks I got the remote debugger running...it turned out to be very simple...

I copied over the c:\rdbg folder from the previous build to the new sd card already running 10586. (I had to reinstall 10556 just to get the files as I wiped my card in a hurry to checkout the new build)

After that it was a matter of run running c:\rdbg\RegisterOneCoreRdbg.cmd and then a reboot and then run StartOneCoreRdbg.cmd..

The debugger doesn't show up in VS list of devices but I used the IP address and voila it deployed my UWP app as usual..

Just wrote up a quick article: http://social.technet.microsoft.com/wik ... 0-iot.aspx

cheers and thx for the new build and hints..

Hi,

I dont find the c:\rdbg folder :/

[ravindrank]

You need to copy it from the previous Windows IoT build 10556 installed on your SD card

[ravindrank]

I updated the steps:
http://social.technet.microsoft.com/wik ... 0-iot.aspx

Edit:updated link

[Perez89]

people use ravindrank solution!!! it is working 100%!!!

Hi,

I found, i needed to use ftp to access the file :p

ftp://<TARGET_DEVICE>
e.g. "ftp://192.168.1.100"

I done everything you said, and is everything working, i'm programming for 10586 build.

the 725n pen wireless is also working.

The only problem that is occuring is something related with .net, that I needed uncheck.(this is related with the version of the debbugger version, i dont understand, but as I uncheck the .net option, everything is working fine)

thanks

sry my english >.<

[slate_dk]

Updated first post with new links as 586 just went "officiel"

[jerseytechguy]

It still appears with the official release that the remote debugger is missing. Nice going Microsoft!

[arrow201]

It still appears with the official release that the remote debugger is missing. Nice going Microsoft!

Ugh ...I'm not at home yet to try the following at the bottom of this page:

https://social.msdn.microsoft.com/Forum ... WindowsIoT

...this fellow said he got it working by changing a debug option to "Universal", maybe need to apply Update 1 to VS2015 first(?).
He didn't mention if he could set breakpoints.

[dobova86]

There's some tricky situation with VS015 Upd 1. I have 2 machine with win10-1511/vs2015 upd1 installed, but only 1 has in the property for the IOT project "Win SDK 10586". The other has only 10240. I really don't know the matter but I think that VS2015 need some update to "update 1" itself. I have used "vs2015.1.EXE /Layout" to download Update1 and probably this is the reason why.

[HalHunt]

Visual Studio 2015 with update 1 debugging works fine with Windows 10 Iot Core build 10586. There is no need to copy over the old remote debugging folder from a previous Iot ISO. Simply open the web management portal (http://minwinpc:8080) and select "Debugging" in the left navigation list. Click the big "Start" button under the "Start Visual Studio Remote Debugger" section. Note the port in the popup JavaScript alert message. For example mine was minwinpc:8116. This is what you need to use in Visual Studio for remote debugging (along with Authentication Mode: None). Hope this helps!

[btusca]

Visual Studio 2015 with Update 1 doesnt work fine.
I'm still getting errors like:
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named '192.168.1.16:8116'. The Visual Studio 2015 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
when i choose raspberry ip as remote connection and "none" as authentication mode.

I can't deploy ANYTHING on the raspberry.
BUT I can deploy 'Blink' with Windows IoT Dashboard and make it works!!! (Daf***???)
WHY can I make it work with Windows IoT Dashboard and with VS 2015 works so BAD?
Im running out of ideas, I reinstall everything, every sdk and VS. Any ideas? Could it be possible that Windows IoT Dashboard works fine because add the msvsmon and VS dont?

I appreciate if someone can give me a hand with this so I can start using this and then give back a hand to another one.

[ricl]

Make sure you have installed VS update 1 correctly. Not applying the updates in full or in the wrong order can cause what you are seeing. People who have had this problem in the past, when they followed the steps on the MS site found it went away. Of course your case could be different.

Visual Studio 2015 Update 1
November 30, 2015

https://www.visualstudio.com/en-us/news ... e1-vs.aspx

The debugger no longer comes with the IoT platform itself. It is deployed by VS when needed, since 10586

[btusca]

Thanks, I downloaded again from there!
Should I Install the feature "Windows 10 SDK (10.0.10240)" ?