|CPU||Intel i7 8700|
|MB||ASRock Z390 Phantom Gaming-ITX/ac|
|Wi-Fi||AirportBrcmFixup.kext||Wi-Fi work without this actually. The device information will show Thrid Party Card instead.|
|BLE||BrcmNonPatchRAM2.kext||Modified, check commit history.|
DW1820A's Wi-Fi works OOB.
DW1820A's device ID
14e4:43a3 was included in
IO80211Family.kext, and there's no need to fake it into any card else in Clover's device tab.
Sysinf will show
Third-Party Wireless Card.
Still no need to fake devide ID.
Sysinf will show
AirPort Extreme (0x14E4, 0x23).
Firmware Version says
Firmware Version: Broadcom BCM43xx 1.0 (184.108.40.206 AirPortDriverBrcmNIC-1305.8)
DW1820A's bluetooth module requires firmware uploading(RAMUSB).
By shutting down the system ( maybe also disconnect the power supply ), and waiting long enough (likely 5 minutes), the uploaded firmware will be released.
If we enter macOS now, without a bluetooth firmware uploader(
BrcmFirmwareRepo.kext), the bluetooth won't work, and the firmware version will be 4096.
Upload firmware via macOS
I havn't firgure out how to upload firmware via macOS correctly.
BrcmFirmwareRepo.kext, I did see the bluetooth changed into version 5799 ( meaning firmware was uploaded ), but bluetooth won't work. It's hard to connect to bluetooth devices, and devices will keep disconnecting.
I thought it might be the firmware in the original kext being too old, so I tried recompiling the kext with firmware extracted from newest driver. The version changed into 4689, but still bluetooth was not working correctly.
And if I reboot into windows after this incorrect uploading, the device manager will told me that DW1820A was not correctly configured. I have to release the firmware first.
Upload firmware via Windows
The incorrect firmware must be released first, otherwise DW1820A will enter a weird state, as mentioned above.
Currently I'm uploading the firmware with
Windows, using driver downloaded from DELL, firmware version 4689.
After uploading, rebooting into macOS with only modified
BrcmNonPatchRAM2.kext placed inside
clover/kexts/other, the bluetooth will work. Although the manual metioned it still depends on BrcmPatchRam2.
Someone mentioned he could upload the firmware via
Windows in virtual machine. That should be able to save some rebooting.