Last Issue Review:
Playing with Raspberry Pi 3 + A Quick Test
Playing with Raspberry Pi 3 + To Do a Good Job, One Must First Sharpen One’s Tools
Playing with Raspberry Pi 3 + Configuration and Review of Bluetooth
Microsoft has launched the Windows 10 IoT system for Raspberry Pi, and in the evaluation plan for Raspberry Pi 3, the evaluation of the Windows 10 IoT system was planned. After receiving the Raspberry Pi 3, I have always wanted to experience it properly. After completing the previous evaluations as per the plan, I can finally experience Windows 10 IoT!
Visit the Raspberry Pi official website at https://www.raspberrypi.org/, and go to the system download page https://www.raspberrypi.org/downloads/ to download the Windows 10 IoT system image. Unlike other system image files, you can click to download directly from the Raspberry Pi official community. Clicking on the WINDOWS 10 IOT CORE system icon will redirect you to Microsoft’s download page.
From Microsoft’s download page, the stable version of the Windows 10 IoT system only supports Raspberry Pi 2, and Raspberry Pi 3 can only download the preview version. To download the Windows 10 IoT Core preview version system that supports Raspberry Pi 3, you need to register and log in, and also join the insider program. Fortunately, I had previously done Windows development, and my account is still active. After joining the insider program, I could download it.
Windows10_InsiderPreview_IoTCore_RPi_ARM32_en-us_14931.iso is 705MB in size. This is an ISO image file. Open the ISO image file with a virtual drive, and inside is an .msi file for installation. Double-click to install the files inside. After installation, the flash file to be written is placed in C:\Program Files (x86)\Microsoft IoT\FFU\RaspberryPi2\flash.ffu.
After installation, you can see a file named flash.ffu in the installation directory. This file is used to burn to the SD card. My computer runs Windows 10, so I can directly use dism.exe in the command line to burn it. Other systems might be a bit more complicated.
Insert the MicroSD card to be burned into the card reader and connect it to the computer. Enter the command line with administrator privileges, cd to C:\Program Files (x86)\Microsoft IoT\FFU\RaspberryPi2 directory, input the diskpart command to enter the diskpart command console, then input the listdisk command to view the disks connected to the current computer, and remember the disk number of the SD card, which is disk 1 in my computer. Input exit to exit the diskpart command console, and run the dism.exe burn command in the directory of the flash.ffu file to burn it to the MicroSD card.
Input the command below to start the burning process.
dism.exe /Apply-Image /ImageFile:Flash.ffu /ApplyDrive:\.\PhysicalDrive1 /SkipPlatformCheck
After burning is complete, insert the MicroSD card into Raspberry Pi 3, connect the corresponding USB keyboard and mouse, network cable, HDMI monitor, etc., and power on to start Raspberry Pi. The screen will show the familiar Windows logo, and the first boot will be relatively slow, so patience is required. It will successfully boot in a few minutes.
However, there were a few small episodes in between: at first, I used a Kingston 8G MicroSD card. After the first burn, it failed to start for half an hour. After cutting off the power, there was no display when I powered it back on. I had to burn it again, and when I powered it on, the classic Windows boot error screen appeared. At this point, I suspected it was an SD card issue because this card had been used for a while and was class 4…
So I replaced it with a SanDisk 16G class 10 and re-burned it, which finally succeeded. Phew.
Since the photos were taken at night, the blue color turned white. Then the slow boot process began, which took an incredibly long time, consuming seven or eight minutes, and there were several reboots in between. After booting, the language setting page appeared, where I selected Chinese and clicked next.
Skipping the network setup, the system entered a simple graphical interface environment, where it defaulted to the device information page. The homepage only has device information, command line, tutorials, settings, and power off, which is extremely simple! On the device information page, you can see the device name, network, IP address, OS version, and the information of connected devices.
The tutorial page’s remote screenshot
Open the settings page, enter Bluetooth, and search for and pair with the mobile phone’s Bluetooth. During the first pairing process, it crashed. After re-pairing once, it succeeded.
Download a tool called IoT Dashboard from the Windows 10 IoT download page for remote connection. Click “Open Windows Device Portal in Browser”. We can find that the address in the browser is http://192.168.1.5:8080/, and next time we log in, we can skip the Dashboard.
We open the webpage and log in with the default username and password: Username: Administrator Password: p@ssw0rd.
Change the device name to Win10IoTPi3, click save after modification, the system will black out and reboot, then enter an endless black screen… I had to cut off the power and restart. After powering on, I found I couldn’t access remotely, and the network port indicator light was not on. My heart sank, did it break? The screen entered the protection program, and moving the mouse or keyboard had no response. Well, I cut off the power and restarted, and it miraculously worked again… Phew. What a troublesome MS!
Click on the left operation panel, and in the Performance page, you can get the current system’s CPU, I/O, Memory and Network status, displayed graphically.
In the lower right corner of the default homepage, there is a screenshot tool that is very useful, allowing you to automatically save remote desktop screenshots to your local machine.
Summary:
During the use of the Windows 10 IoT system, there were multiple black screens, and the system was extremely unstable, with severe lag during remote login. Overall, the support for Pi3 is not good enough. I hope Windows 10 IoT can improve further so that we can develop on a stable system.
Welcome to click to read the original text to communicate and exchange with the author.
Follow EEWORLD (Electronic Engineering World) WeChat public account: reply “contribution”, your original work will have the opportunity to appear in our WeChat push.
To communicate with more industry peers, please click to read the original text to log in to the EEWORLD forum.
WeChat ID: EEWORLD Forum Activities E In Your Palm
Follow EEWORLD Service Account EE Benefits At Your Fingertips
WeChat ID: EEXINRUI Chip Information Sharp Interpretation
