Raspberry pi windows драйвера



Инструкция по установке Windows 10 на Raspberry Pi 4 от Tom’s Hardware

В середине июля 2020 года эксперты портала Tom’s Hardware опубликовали инструкцию по установке Windows 10 на Raspberry Pi 4. Вдобавок они проверили, как работают некоторые сторонние программы (GIMP Photo Editor, Arduino IDE и Python 3.8) в этой связке микрокомпьютера на ARM и последней версии Windows.

Вопрос «зачем» тут не особо уместен, так как экспериментаторам был важен сам факт того, что это можно сделать и все будет работать. Да, медленно и с тормозами и проблемами, но будет.

Официально, единственная операционная система Microsoft для Raspberry Pi — это устаревшая на текущий момент версия Windows 10 IoT Core, которая, например, позволяет выполнять код Visual Studio на микрокомпьютере, но там даже нет графического интерфейса. Тем не менее, разработчики (например, проект «Windows on Raspberry Pi» в Discord) своими силами сделали необходимы программы и нашли способ по установке и запуску полноценной версии Windows 10 на Raspberry Pi 4.

Эксперты портала Tom’s Hardware дополнительно уведомили, что они не могут ручаться за безопасность или законность любых пользовательских файлов, созданных сообществом «Windows on Raspberry Pi», поэтому все действия далее они делали на свой страх и риск.

В 2019 году эксперты портала Tom’s Hardware уже попытались установить Windows 10 на Raspberry Pi 3, но тогда этот трудный процесс у них закончился по большей части проблемами, ошибками и тормозами после установки.

В настоящее время даже после всех стараний команды проекта «Windows on Raspberry», после установки Windows 10 на Raspberry Pi 4 не работают встроенные в микрокомпьютер порт Ethernet, модули Wi-Fi, Bluetooth и GPIO, аудио через HDMI также недоступно. Для сетевого подключения нужно использовать Wi-Fi USB-адаптер, а для вывода звука Bluetooth через USB-адаптер.

Для установки Windows 10 на Raspberry Pi 4 понадобятся:

  • последняя версия Raspberry Pi 4 с 4GB или 8GB ОЗУ;
  • карта памяти microSD на 16 GB или больше;
  • ПК с Windows 10 и доступом в сеть интернет для создания нужной загрузочной сборки;
  • адаптер USB to Ethernet или WiFi dongle;
  • Bluetooth dongle (если нужен Bluetooth).

Инструкция по установке Windows 10 на Raspberry Pi 4:

  • нужно скачать и распаковать на ПК последнюю версию инструмента WoR 2.0.0 alpha 3, там будет архив на 4.7G;
  • зайти на Windows on Raspberry Pi Discord server в разделе Downloads channel скачать последнюю стабильную версию Windows on ARM (0.2.1), ссылка на этот файл PublicFlukeByte.iso;
  • запустить WoR Alpha tool и выбрать язык установки;
  • вставить в ПК карту памяти и выбрать ее в WoR Alpha tool в разделе «Select device», там же выбрать режим «Raspberry Pi 4 experimental mode»;
  • далее в разделе «Select image» указать место расположения на ПК ранее скаченного файла PublicFlukeByte.iso;
  • далее в разделе «Select drivers» выбрать опцию «Use the latest package available on the server.»;
  • далее в разделе «UEFI firmware» выбрать опцию «Use the latest firmware available on the server.»;
  • потом нужно проверить конфигурацию загрузочной сборки и начат ее записать на карту памяти, причем запись может продолжаться более двух часов, в зависимости от параметров карты памяти;
  • скачать и распаковать на ПК патч для Raspberry Pi 4 по активации USB-портов и 3 ГБ ОЗУ в Windows 10, скопировать файл winpatch.exe в корень диска C: на ПК;
  • пропатчить сборку на карте памяти: в командной строке на ПК выполнить
    «winpatch X:\Windows\System32\drivers\USBXHCI.SYS 910063E8370000EA 910063E8360000EA 3700010AD5033F9F 3600010AD5033F9F», где Х — буква диска с картой памяти;
  • рекомендуется также «разогнать» в настройках Raspberry Pi, но тогда лучше заранее обеспокоиться установкой на микрокомпьютер системы охлаждения, для этого необходимо в файле config.txt на загрузочном карте памяти выставить параметры: «over_voltage=6» и «arm_freq=2000»;
  • теперь можно извлечь загрузочную карту памяти из ПК, вставить ее в Raspberry Pi 4 и начать стандартную установку ОС Windows 10;
  • после окончания процесса установки Windows 10 на Raspberry Pi 4 необходимо активировать в ОС возможность полноценно использовать 3 ГБ ОЗУ, для этого нужно под администратором в командной строке запустить: «bcdedit /deletevalue truncatememory», далее необходимо перезагрузить микрокомпьютер;
  • далее можно подключить сетевые USB-адаптеры, настроить их и скачивать и устанавливать из интернета необходимые для работы приложения, включая браузеры и другое ПО.

Эксперты портала Tom’s Hardware установили на Raspberry Pi 4 с Windows 10 браузер Microsoft Edge, программы GIMP Photo Editor, Arduino IDE и Python 3.8 с оболочкой Python REPL. Все программы запускались и работали нормально. По скорости работы с этой ОС микрокомпьютер оказался на уровне Intel Celeron или Atom начального уровня. Время загрузки ОС Windows 10 составило 2 минуты 12 секунд. Просмотр видео в YouTube возможен, но со средними настройками разрешения роликов. Из проблем — на эту сборку не удалось установить редактор кода Visual Studio Code. Также не работал модуль Python под названием GPIO Zero, который используется для взаимодействия с GPIO Raspberry Pi. Возможно, что в будущем эти моменты будут доработаны разработчиками проекта «Windows on Raspberry Pi».

Ранее в феврале 2020 года Raspberry Pi Foundation выпустил обновленную версию (v1.2) Raspberry Pi 4, в которой было исправлено несколько проблем, включая совместимость с различными USB-C кабелями. Тогда микрокомпьютер не распознавал некоторые кабели как источник питания из-за проблем со схемой питания.

В конце мая 2020 года в продажу поступила 8-гигабайтная модель Raspberry Pi 4. Она доступна по цене в $75. Вдобавок создатели портативного ПК сняли с продажи версию с 1 ГБ оперативной памяти, теперь за $35 можно приобрести Raspberry Pi 4 с 2 ГБ ОЗУ.

Источник

Downloads

Before you proceed to download the software below, see our official installation guide.

Chances are that you’re coming from an outdated tutorial, so it’s recommended to follow the guide above to prevent any issues with the installation.

Windows on Raspberry imager

Requirements:
  • a computer with Windows 10 version 1703 or later. (Wine is not supported — see the PE-based installer for other OSes)
  • a Raspberry Pi 2 rev 1.2, 3, 4 or 400. (minimum RAM requirement is 1 GB, but it will generally result in poor performance, especially on boards older than Raspberry Pi 4)

a good/reliable drive that has at least 8 GB of available space. It can be:

  • an SD card (A1 rating is highly recommended; non-A1 rated cards may be too slow)
  • an USB device (preferably SSD, or any drive that has decent random I/O speeds).

A slow drive can also cause other issues, besides being a bottleneck.

  • a Windows 10 ARM64 build 19041 or newer image (including insider builds of Windows 11): WIM/ESD, ISO or FFU
  • Windows on Raspberry PE-based installer

    This is not a straightforward wizard tool like the Windows-only imager, so please follow the appropriate guide for it: How to install from other OSes.

    Requirements:

    Same as for the Windows-only version, with some exceptions:

    • no specific OS required, as long as the tools needed to create the PE-based installer are available or can be compiled for it.
    • the Windows 10 ARM64 image can only have the ISO format. The reason for this is that some required files from the ISO cannot be found in the WIM/ESD.
    • storage-wise, you need either:
      • a drive that has at least 32 GB, for self-installation
      • a drive that has at least 8 GB for the installation media, and another destination drive that has at least 16 GB for the OS (e.g.: an USB drive and an SD card)

    Boot partition mount utility

    Easily mount the boot partition of your Windows on Raspberry installation. Works directly on the Raspberry Pi or another computer.

    PiMon

    A simple hardware monitor for your Raspberry Pi running Windows. (https://github.com/driver1998/PiMon)

    Windows images

    What about FFU images?

    FFU images can speed up the deployment process significantly, especially on slow devices. They are not available for download due to legal reasons, but you can safely generate them yourself: How to generate FFU images?

    Copyright © 2018-2022 Mario Bălănică. All Rights Reserved.

    This project is not affiliated with the Raspberry Pi Foundation or Microsoft Corporation.

    Источник

    Raspberry pi windows драйвера

    I got the Pico up and running on my PI with Thonny but when I try the same with my PC it seems that windows 7 requires a driver for the board and I can not find any mention of it online anywhere. Can any one help ?. The board is showing in Device Manager as «Board CDC» yet can not find a driver.
    This I think has the effect of making Thonny think that the board is busy after uploading the firmware and/or not pressing the boot select button upon plugin.

    Re: Pico — Windows 7 Driver needed ?

    I forgot to update that to say it also worked for me on Windows 7 as well as XP.

    Re: Pico — Windows 7 Driver needed ?

    Thanks Hippy, that worked a treat. Surprising as Im normally a failure at following those things.

    Re: Pico — Windows 7 Driver needed ?

    I’m having the same issue I think, «C» works but when I try drag the pico_micropython_20210121.uf2 file to the Pi Pico it still showa a yellow exclaimation mark in Devices and there is no COM port listed in Thonny.

    If I try the link posted and edit the file and then try to install it says the INF you selected can’t does not support this type of file.

    Any Help thanks.

    Re: Pico — Windows 7 Driver needed ?

    Well, here goes nothing. Ill try to do a step by step of what I did and worked for me. This is to make windows 7 recognise the pico when not in bootsel mode and thus allowing the pico to be recognised in Thonny.

    2. unzip the amtel_devices_cdc.inf file to a folder named «pico-serial»
    3. Change the name of amtel_devices_cdc.inf file to pico-serial.inf
    4. open/edit the pico-serial.inf in a basic editor like notepad
    5. remove and replace the lines under the following headings :

    6. Close and save and make sure your retain the name as pico-serial.inf
    7. Go to your pc device list, find the pico under Ports, named something like CDC Device. A yellow exclamation mark indicates it.
    8. Right click on the CDC Device and update or install driver choosing the file you created from the location you saved it at.

    Worked for me, fingers crossed for you.

    Re: Pico — Windows 7 Driver needed ?

    Re: Pico — Windows 7 Driver needed ?

    Many thanks! I am deliberately using a Windows 7 device for this process. I tried yesterday and everything worked perfectly on a MacBook Pro, but today, no joy, with Win7.

    I am testing the board and the «MicroPython on Raspberry PI» book to pass on to a nephew. Other than a brief mention of «other computer», there is no reference to the need to add a driver for Win7 drivers. I am glad that I figured out how to «ask the right question» on the RPI forum and found your excellent answer.

    (Interestingly, the «Arduino equivalent» IDE seemed to work with all of their board on Macintosh, Windows and Linux. )

    Re: Pico — Windows 7 Driver needed ?

    Re: Pico — Windows 7 Driver needed ?

    Well, here goes nothing. Ill try to do a step by step of what I did and worked for me. This is to make windows 7 recognise the pico when not in bootsel mode and thus allowing the pico to be recognised in Thonny.

    2. unzip the amtel_devices_cdc.inf file to a folder named «pico-serial»
    3. Change the name of amtel_devices_cdc.inf file to pico-serial.inf
    4. open/edit the pico-serial.inf in a basic editor like notepad
    5. remove and replace the lines under the following headings :

    6. Close and save and make sure your retain the name as pico-serial.inf
    7. Go to your pc device list, find the pico under Ports, named something like CDC Device. A yellow exclamation mark indicates it.
    8. Right click on the CDC Device and update or install driver choosing the file you created from the location you saved it at.

    Worked for me, fingers crossed for you.

    ***The following is for my Win7 laptop***

    yep it worked for me as well (I’d already installed micropython (the only version that didn’t have unstable in the file name) using a Pi-zero and VNC). Now I don’t know if the pico will talk to Thonny on win7 as I was trying to get the pico to work with my win8.1 laptop and I haven’t installed Thonny on my Win7 laptop (Mu is a non starter). But as the Pico now has a com port on win7 I reckon it will work with arduino!

    When in bootsel mode I get:

    USB Composite Device (tick)Ready to use
    USB Mass Storage Device (tick)Ready to use
    RP2 Boot (cross)No driver found
    RPI RP2 USB Device (tick)Ready to use

    So the big question is there a fix for RP2 Boot? Or can that error be ignored?

    Now as a general observation the Pico isn’t the only board that has a CDC problem with Win7/8.1!! I have 2 different «sense» boards which should work with arduino, the manufacturers say that the boards work with win7. but does win7/8.1 give them a com port? Not a chance! But I am wondering if something similar to the above Pico fix could work with the other boards.

    Источник

    worproject/RPi-Windows-Drivers

    Use Git or checkout with SVN using the web URL.

    Work fast with our official CLI. Learn more.

    Launching GitHub Desktop

    If nothing happens, download GitHub Desktop and try again.

    Launching GitHub Desktop

    If nothing happens, download GitHub Desktop and try again.

    Launching Xcode

    If nothing happens, download Xcode and try again.

    Launching Visual Studio Code

    Your codespace will open once ready.

    There was a problem preparing your codespace, please try again.

    Latest commit

    Git stats

    Files

    Failed to load latest commit information.

    README.md

    Windows on ARM(64) device drivers for the Raspberry Pi platform

    This repository is currently used only for publishing binary releases: https://github.com/worproject/RPi-Windows-Drivers/releases

    The source code for some of the prebuilt drivers can be found here: https://github.com/raspberrypi/windows-drivers

    most of the drivers require the Test Signing mode to be enabled.

    ARM32 drivers can’t be installed on an ARM64 image or vice versa.

    drivers included in the latest release that can’t be found in the «bsp» repository above were either extracted from old builds of Windows 10 IoT Core (ARM32 binaries) or recompiled for ARM64 by their developers (thanks to MCCI and Microchip).

    some of the new drivers / features are not yet open-sourced because the code needs to be heavily refactored. It’s good enough to «get the thing working», but it can’t be used as a base for further development. Watch the repository above for updates on this.

    To UEFI / driver developers

    The driver package for Raspberry Pi 4 installs a DSDT & SSDT table override that:

    changes the _HIDs of the

    • PL011 controller to BCM2887
    • XHCI controller to RPI0D10

    so Windows won’t install the incompatible inbox drivers instead of our own versions. This is not necessary if the drivers are properly signed.

    fixes the PWM definition and adds an analog audio device

    adds dummy HDMI controller and digital audio devices

    For ACPI changes in the UEFI to take effect, you need to uninstall this override by deleting dsdtpatch from the package or the ACPITABL.dat file from %SystemRoot%\System32\ . As a result, Bluetooth, audio and the USB filter driver may stop working.

    Device Driver Status Additional information
    7-inch DSI touch screen Display: firmware-controlled, Touch: no driver available Partially working Only the display works, but the resolution may be wrong. See the RPi docs for details on how to change it through config.txt.
    CSI Camera Module No driver available Not working
    3-pin case fan UEFI-controlled Partially working Fan control can be enabled in the UEFI settings, but it will always stay on due to temperature control not working in Windows

    Raspberry Pi 4 / 400 (ARM64)

    Device Driver Status Additional information
    eMMC2 SDHCI sdbus.sys (bcmemmc2.inf) Partially working a faster SD controller meant to replace SDHOST. No DMA, HS200/HS400 and UHS-I support at the moment.
    Arasan SD/SDIO Host Controller bcm2836sdhc.sys Working
    SD2.0 Host Controller rpisdhc.sys Untested SDHOST can no longer be routed to the SD card slot (but it’s available on the GPIO header)
    GPIO bcmgpio.sys Working
    SPI bcmspi.sys Working
    AUXSPI bcmauxspi.sys Working
    I2C bcmi2c.sys Working
    PWM bcm2836pwm.sys Working
    Audio Jack (PWM-driven) rpiwav.sys Working
    Mini UART pi_miniuart.sys Working
    PL011 UART SerPL011.sys Working
    VC4 Mailbox Interface rpiq.sys Working
    VC4 Host Interface Queue vchiq.sys Not working
    VC4 GPU (Graphics) roskmd.sys Not working the driver loads, but it doesn’t do much as it’s unfinished
    HDMI Audio rpi4hdmiwav.sys, rpi4hdmiwavbridge.sys Partially working only the HDMI0 port is supported (next to the USB-C port on RPi 4 or the SD card slot on RPi 400)
    Basic Display Adapter (frame buffer) MSBDD (Inbox) Working
    DesignWare HS USB 2.0 OTG Controller mcci_dwchsotg_hcd.sys, mcci_dwchsotg_hub.sys Partially working RAM must be limited to 1 GB
    VIA VL805 XHCI Host Controller rpiuxflt.sys (USBXHCI.SYS filter) Partially working workaround: UASP support is disabled as it prevents booting from USB 3.0 drives. The filter driver also reduces transfer speeds quite significantly.
    Broadcom GENET Gigabit Ethernet Controller bcmgenet_netadapterXX.sys Working due to the fact that the NetAdapterCx API is unstable, there are 3 versions of this driver: one for build 19041/2, one for builds 19536 up to 21296, and the last one for builds 21301 and newer
    CYW43455 Wireless LAN No driver available Not working
    CYW43455 UART Bluetooth cywbtserialbus.sys Working

    Raspberry Pi 3 (ARM64)

    Device Driver Status Additional information
    Arasan SD/SDIO Host Controller bcm2836sdhc.sys Working
    SD2.0 Host Controller rpisdhc.sys Working
    GPIO bcmgpio.sys Working
    SPI bcmspi.sys Working
    AUXSPI bcmauxspi.sys Working
    I2C bcmi2c.sys Working
    PWM bcm2836pwm.sys Working
    Audio Jack (PWM-driven) rpiwav.sys Working
    Mini UART pi_miniuart.sys Working
    PL011 UART SerPL011.sys Working
    VC4 Mailbox Interface rpiq.sys Working
    VC4 Host Interface Queue vchiq.sys Not working
    VC4 GPU (Graphics) roskmd.sys Not working the driver loads, but it doesn’t do much as it’s unfinished
    HDMI Audio No driver available Not working
    Basic Display Adapter (frame buffer) MSBDD (Inbox) Working
    DesignWare HS USB 2.0 OTG Controller mcci_dwchsotg_hcd.sys, mcci_dwchsotg_hub.sys Working
    LAN9514 USB Ethernet Adapter lan9500-arm64-n650f.sys Working Ethernet support for RPi 3 B
    LAN7515 USB Ethernet Adapter lan7800-arm64-n650f.sys Working Ethernet support for RPi 3 B+
    CYW43438 Wireless LAN No driver available Not working WLAN support for RPi 3 B
    CYW43455 Wireless LAN No driver available Not working WLAN support for RPi 3 B+
    CYW43438 UART Bluetooth cywbtserialbus.sys Partially working Bluetooth support for RPi 3 B -> the bus speed is limited as the RTS/CTS lines are not exposed (the driver may crash regardless)
    CYW43455 UART Bluetooth cywbtserialbus.sys Partially working Bluetooth support for RPi 3 B+ -> the bus speed is limited until hardware flow control support is added in the PL011 driver

    About

    Windows on ARM device drivers for the Raspberry Pi single-board computer.

    Источник

    You may also like...