where can i find windows driver for pcie connection of xilinx fpga board?
I designed block diagram for PCIe but I can't see device manager in computer. I take error from computer that Error [Code10] or Error [Code52].
I'm trying to connect to the serial port of my Xilinx Ultrascale ZCU102 with my Macbook Pro (OS: Big Sur 11.2). The board is connected with a USB - miniUSB cable to a hub USB C connected to one of the Mac USB C ports.
With lsusb | grep Serial I get correctly listed both the USB adapter and sd card reader which compose the hub. However, I cannot figure out how to see data transmitted by the board through UART. I've tried with Serial Tools, but the two serial ports I can see does not show anything. Then, I've tried to list devices with ls \dev, but I cannot figure out what can be the device.
How can I solve?
Thank you in advance
I would like to know if there is a way to connect an esp32 cam via an esp32 to the pc to program it.
I have only found tutorials to connect it via an arduino or FTDI...
ESP32-CAM doesn't have USB->serial converter so the only way to program ESP32 for the first time is via serial. After uploading sketch via USB-TTL converter you can use OTA to update ESP32 via Wi-Fi but if you don't have FTDI converter it's useless.
Another solution is to use arduino board as USB-TTL converter because converter is already included on most of the arduino boards (nano, UNO..).
Yes, you can connect it to a PC - but, as you said, only using an Arduino or FTDI.
You can't connect it directly.
The ESP32-CAM doesn't support USB for communications. FTDI allows the PC's USB connection to communicate with the ESP32-CAM's serial port. They can't communicate without some kind of adapter - that's what FTDI or an Arduino are for.
I was following the Coral Dev Board get started guide - Get started with the Dev Board (https://coral.withgoogle.com/docs/dev-board/get-started/). Everything worked fine until to the step - Connect to the board's shell via MDT.
I've waited about 5 minutes until the flashing to complete, and the terminal prompt returned to me, then I tried the command:
mdt devices
The terminal returns nothing. Unlike the guide says it supposes to return my board hostname and IP address. I've checked the USB-C OTG and USB-C power cable, they are all connected well.
I've also tried this solution: https://superuser.com/questions/1452786/coral-dev-board-not-recongized-on-mdt-shell. I went to Network under System Preferences, and clicked "+" icon, but I couldn't find the mendel device.
I'm using Macbook Pro running on macOS Catalina. The fastboot and mdt commands are both working.
I just found a solution:
Just plug micro-B USB cable, then run:
screen /dev/cu.SLAB_USBtoUART 115200
If it shows blank, wait a couple seconds, then plug usb-c power cable, the system of the dev board will start loading, the login prompt will come out. After I logged in, I plugged the usb-c cable into data port(keep the micro-B USB cable in at the same time), then run:
mdt devices
or
mdt shell
This solution works for me only when I have turned on the wifi of the dev board and connect it to the same wifi network. If you want to turn on the wifi network of coral dev board, run the command on screen terminal:
nmtui
The Network Manager TUI prompt will come out then you can connect to your wifi network.
It's a problem on macOS Catalina. It doesn't "see" USB connection as a network connection and as such it is impossible to connect to Coral Dev Board.
I have the same issue, but I tried with another MAC with older macOS and it worked just fine.
Now, I don't have yet the solution, but at least we all know the problem ;-)
Regards,
Rui
First check the that the device is detected by running dmesg command.
Normally you should see something like this
$ dmesg
...
[107834.681816] usb 2-3: new high-speed USB device number 3 using xhci_hcd
[107834.845073] usb 2-3: New USB device found, idVendor=18d1, idProduct=9304, bcdDevice= 4.19
[107834.845077] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[107834.845079] usb 2-3: Product: Mendel
[107834.845081] usb 2-3: Manufacturer: Google,LLC
[107834.845083] usb 2-3: SerialNumber: bored-horse
[107834.985296] cdc_acm 2-3:1.0: ttyACM0: USB ACM device
[107834.986069] usbcore: registered new interface driver cdc_acm
[107834.986070] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[107835.005045] cdc_ether 2-3:1.2 usb0: register 'cdc_ether' at usb-0000:06:00.3-3, CDC Ethernet Device, aa:9f:04:54:dc:45
[107835.005124] usbcore: registered new interface driver cdc_ether
[107835.019787] cdc_ether 2-3:1.2 enxaa9f0454dc45: renamed from usb0
[107897.336866] IPv6: MLD: clamping QRV from 1 to 2!
[107956.344960] usb 2-3: USB disconnect, device number 3
[107956.345357] cdc_ether 2-3:1.2 enxaa9f0454dc45: unregister 'cdc_ether' usb-0000:06:00.3-3, CDC Ethernet Device
...
After that, check your network interfaces using ip command
$ ip link
Then look for the one with the one with the same MAC address as the one that appears in the logs of dmesg.
Once you find it, run this command to assign an IP address
$ sudo dhclient <name of the network interface of coral dev board>
Now you should see an IP assigned to the interface.
$ ip a
After that, run mdt devices and you should see the dev board connected.
$ mdt devices
bored-horse (192.168.100.2)
I had the same problem in Debian (Buster). I was able to follow all the steps to connect and flash the device until 'mdt shell' and I would receive a 'Unable to find any devices on your local network segment' message.
Opening the network settings and enabling 'USB' as a network interface worked for me.
After connecting to the Coral Dev Board the first time and exchanging private keys, I unplugged the USB cable. After that, my computer was offline until I re-enabled the ethernet connection. It seems that enabling the USB network disabled the ethernet. At that point, mdt shell was able to connect via the ethernet network.
So I've just spent most of the afternoon with this issue. After I downgraded the OS to Chef it seemed to work fine as the USB device (OTG port) would initialize on boot and then the SSH key could be pushed through. However, with the latest OS (Eagle) this was not the case.
The fix was simple:
Remove the USB C OTG port cable from the board
Reboot the Coral board
Wait for boot sequence to complete
Connect the USB C OTG port cable to the board
Run "mdt shell"
key is pushed through!
Now I can set up the WiFi or connect Ethernet and remove that cable once again and now I can freely call mdt shell and it connects every time.
I'm trying to executed a project made with Quartus on an Ubuntu 16.04 on a MAX 10 FPGA which is connected by WIFI with my computer, and I can't connect it by USB. I didn't find option on Quartus to be able to executed the compiled program with a wireless connection.
Questions :
Is there a module to add on Quartus to add the wireless connection in the Programmer section?
If it's not possible, which files must I transfer (using the scp command) and which one is the executable?