Passing though a USB3 PCI card in hyper-v so I can do full JTAG debugging in a VM

 By far my most powerful build box is my Dell R720 which im using as a Hyper-V  host.

Ive got a lovely Wrover Kit dev board, which has on-board JTAG debugging, but to use it ive historically had to plug it into my laptop, and build there. The laptop is a 4 core i5, so it takes forever to build and deploy, and the progress is no fun.

Ive managed to successfully pass though a PCI USB card to the virtual machine I usually use for ESP32 dev, and it works brilliantly

https://community.spiceworks.com/how_to/189969-hyper-v-pcie-including-usb-pass-through-not-just-graphics-devices?from_category=22
PCIROOT(0)#PCI(0200)#PCI(0000)

Dismount-VMHostAssignableDevice -LocationPath 'PCIROOT(0)#PCI(0200)#PCI(0000)' -force

Add-VMAssignableDevice -LocationPath 'PCIROOT(0)#PCI(0200)#PCI(0000)' -VMName 'v-dev'


This gives me full remote control of the device via both serial and JTAG. The only thing I cant do is see the screen, but I dont use that much.

Comments

Post a Comment

Popular posts from this blog

SSD Upgrade on Lenovo Legion Go - Part 1 - Backup the original drive using Veeam

Image
0. Prerequisites a) An adapter to allow you to plug USB devices into the Legion Go. I used this from Amazon: https://www.amazon.co.uk/dp/B09H44S96B?psc=1&ref=ppx_yo2ov_dt_b_product_details You might want to do some research on this - its doubled in price since I bought it last week, and its very slow (25Mb/s to the external SSD which can do 500Mb/s, but it might be the cage) If you buy this adaptor, make sure you plug the drive into the 1 out of the 4 USB ports that supports USB 3 :) b) An external drive big enough to hold the Legion Go SSD (in my case, 512Gb). I use a Samsung SATA SSD in a USB3 cage, since that is what I have. c) A Windows 11 iso. This can be downloaded from Microsoft (this is used to create the recovery media) The windows ISO is only needed if the computer doesn't have a recovery partition, which the Legion Go DOES, so this is not needed here. 1. Plug in a blank USB stick for the recovery media 2. Download Standalone Veeam Agent for Microsoft Windows here: ht
Read more

Introducing Easynow - an ESPHome component to make sensor proxying via ESPNow easy in ESPHome.

Image
I think my ESPNow proxy components are now working well enough to release. https://gitlab.com/ripnetuk-public/espnow/ripnetuk-esphome-easynow It can be used in ESPHome simply by adding YAML, since ESPHome can pull external components direct from a Git repo - well done ESPHome :) Initial tests are good - using the same device that I was getting roughly 8 hours out of (from a discarded [popular device] - 700maH),  On previous measurements, I was timing the main part of the discharge curve, from 4v down to 3v, and was getting approx. 8-9h of runtime. This was taking a reading every 60s and passing to HomeAssistant via the regular API (ie, using the built in ESPHome stuff) BEFORE Easynow So it was taking between ~18:00 to ~02:45 to discharge from 4v to 3v. Thats about 8/9 hours. WITH Easynow Well, this is awkward. Its worked so well that after 8 hours, it havent even yet got down to the 4v ive been testing at: yet its still successfully reading the temperature every 30s: So far, id call th
Read more