The previous blog explained what needs to be done to be able to deploy and debug apps with latest build for IoT-Core (Build 10586). On the Microsoft IoT forums it was reported by some that if they didn’t set up as in the previous blog they got a pin request. This blog provides some detail as to how the Universal (Unencrypted Mode) authentication works. It also explains why some got the PIN request.
You need Visual Studio 2015 Update 1 to deploy and debug Universal Windows Platform Apps onto IoT-Core Build 10586, the Dec 3rd 2015 release. You MUST use Universal (Unencrypted Mode) authentication not NONE when Deploying/Debugging.
Windows 10 desktop/tablet has undergone a major refresh. At the same time Windows Mobile (Windows Phone 10) has RTMed. Also Windows 10 IoT-Core has also invoked two license versions with its latest concurrent release.
Available as an update or as a complete Visual Studio 2015 Plus Update 1 installation. Note this is needed for Build 10856 (the latest version) of Windows 10 IoT-Core as connectivity fails with the RTM version of Visual Studio 2015. Looks like its not available yet as the free Community Edition on VisualStudio.com.
Whilst awaiting my replacement board, I’ve been looking at the Microsoft IoT-Core sample projects. Besides the RPI2 and Minoowboard Max howtos they have added howtos for the Dragonboard where GPIO etc is used. Given the need for level shifting, I’ve ordered some Sparkfun version: SparkFun Voltage-Level Translator Breakout – TXB0104 from Sparkfun Coming from a land Downunder in the land of Oz I’ve ordered from Little Bird Electronics in Queensland. I’ve ordered Sparkfun from them previously and they have a good range and are prompt with shipping: SparkFun Voltage-Level Translator Breakout – TXB0104 from Little Bird SparkFun's Description of SparkFun Voltage-Level Translator Breakout - TXB0104 This is a breakout board for the Texas Instruments TXB0104 module. The TXB0104 is a 4-bit bidirectional voltage-level translator with automatic direction sensing. This 4-bit noninverting translator uses two separate configurable power-supply rails. The A port is designed to track VCCA. VCCA accepts any supply vol ...
Still not booted up yet. Arrow are sending me a new board so I’ll go into recess with this blog series until it arrives. Today’s info includes a video captured from a Dragonboard which highlights the usefulness of DirectX being supported by the Dragonboard’s GPU. Also a further list of its capabilities.
Still no joy with my board. Purchased a new 12V 1.5A Plug-pack with a a better sized connector but can’t get any life from my board.
When power is applied: …
Also covers some aspects of the board as taken from the Microsoft documentation
Well, today has been a disaster. After hunting around I found a couple of connectors and 12V power supplies but no joy. I haven’t got the board to boot. I think the first connector was too hollow and the 12V (the internal connection of the plug wasn’t touching the internal pin of the socket on the board. With a few other tries I was able to get connectivity but the board just vibrated when powered up. I did briefly get a blue or purple LED to momentarily light up. At one stage touching the board under the power socket burn my finger! I have logged the issue with Arrow.
Also Dragonboard v RPI2
Index of my trials and tribulations (as separate blogs) with bringing up a Qualcomm Dragonboard 410c to run Windows 10 IoT-Core. Starts with the purchase. Then goes onto powering it up and will go onto installing the OS and developing apps. Previous posts on this topic are indexed here and don’t show on the main page.
Got it today after driving around and around at the airport trying to find the new home for DHL.