A couple of years back, I tried some gpio programming using a newly purchased Raspberry Pi 3 Model B running Win 10 IoT. I found it slow and painful; a total bear to just blink an led with Visual Studio. I quickly switched back to Linux/Raspbian and mostly used the WiringPi library with command line gcc compiler. So, do any of you guys have suggestions for gpio programming on Win 10 Iot that I might find less painful?
found old EEPROM 3 June 2020 on PI400 resulted in no USB 3 boot support . Updated both fimmware & eeprom to latest 18 july 2021 & everything went flawlessly but before i have cross checked usb boot config via raspian os today its time to test everything as suggested by the Great PI Player @Chibi ANUBIS
After reading this thread, I also just yesterday got a 4 gig Pi 4 B booting and running Win 10 IoT, using a USB 3.0 memory stick. I must say it is fairly usable. (At least for looking at the Windows desktop...) My last adventure in this direction was back around 2016, when the Pi 3 and Win 10 were both fairly new. I think there was a Win 10 version available through the "NOOBS" installer back then, but probably taken down since. I still would hate configuring Visual Studio on an intel desktop machine just to compile and send code to the Pi. That smells too much like an Arduino.
Yeah, sure. Go back and look at post #34 by @Chibi ANUBIS. The WoR utility seems to have an option for the RPI 3B+. If usb thumb drive doesn't work, get a decent micro sd card; I'm having fairly good luck with a 64G V30 card. Performance is decent on the RPI 4B, ymmv.
My FranckenBuild Code: C:\Windows\system32>dism /Get-WimInfo /WimFile:d:\sources\install.wim /index:1 Outil Gestion et maintenance des images de déploiement Version : 10.0.19041.844 Détails pour l’image : d:\sources\install.wim Index : 1 Nom : Windows 10 Enterprise LTSC Description : Windows 10 Enterprise LTSC Taille : 13 376 898 472 octets Peut être démarré par WIM : Non Architecture : arm64 Couche HAL : <non défini> Version : 10.0.19041 Build du Service Pack : 1202 Niveau du Service Pack : 0 Édition : EnterpriseS Installation : Client Type de produit : WinNT Suite de produits : Terminal Server Racine système : WINDOWS Répertoires: 28585 Fichiers : 91316 Création : 07/12/2019 - 18:14:37 Modification : 26/12/2021 - 19:39:00 Langues : fr-FR (Par défaut) L’opération a réussi. C:\Windows\system32>dism /Get-WimInfo /WimFile:d:\sources\install.wim /index:2 Outil Gestion et maintenance des images de déploiement Version : 10.0.19041.844 Détails pour l’image : d:\sources\install.wim Index : 2 Nom : Windows 10 IoT Enterprise LTSC Description : Windows 10 IoT Enterprise LTSC Taille : 13 376 741 992 octets Peut être démarré par WIM : Non Architecture : arm64 Couche HAL : <non défini> Version : 10.0.19041 Build du Service Pack : 1202 Niveau du Service Pack : 0 Édition : IoTEnterpriseS Installation : Client Type de produit : WinNT Suite de produits : Terminal Server Racine système : WINDOWS Répertoires: 28586 Fichiers : 91317 Création : 07/12/2019 - 18:14:37 Modification : 26/12/2021 - 20:01:42 Langues : fr-FR (Par défaut) L’opération a réussi.
To reconstruct 19044 arm64 LTSC with Abbody's script, use fr-FR Pro's install.wim and extract the content of fr-FR language pack to lp, then it is 19041.1 French image. Then integrate updates to winre.wim and install.wim in the sequences: 1. SSU (winre\install) 2. 21H2 Enablement (install) 3. LCU (winre\install) Or use 3rd-party update tool. For example, Abbody's update script.
@xinso Code: ============================================================ Running W10UI v10.15 ============================================================ ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Extracting .cab files from .msu files... ============================================================ 1/1: windows10.0-kb5008212-arm64_6ce6eda1c3a796226246597f763161a6469508b5.msu ============================================================ Extracting files from update cabinets (.cab)... *** This will require some disk space, please be patient *** ============================================================ 1/2: Windows10.0-KB5005260-arm64.cab [SSU] 2/2: Windows10.0-KB5008212-arm64.cab [Combined] 3/4: Windows10.0-KB5007273-arm64_inout.cab [SSU] 4/4: Windows10.0-KB5008212-arm64_inout.cab [LCU] ============================================================ Mounting EnterpriseS.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing servicing stack update... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 Processing 1 of 2 - Adding package Package_for_ServicingStack~31bf3856ad364e35~arm64~~19041.1161.1.1 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_ServicingStack_1371~31bf3856ad364e35~arm64~~19041.1371.1.0 [==========================100.0%==========================] The operation completed successfully. ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.19041.1 Image Version: 10.0.19041.1 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~arm64~~19041.1415.1.6 [==========================100.0%==========================] An error occurred - Package_for_RollupFix Error: 0x800f0984 Error: 0x800f0984 DISM failed. No operation was performed. For more information, review the log file. The DISM log file can be found at C:\Windows\Logs\DISM\DismLCU.log