# RFSoC4x2 PYNQ.remote issue **URL:** \ **Category:** Support\ **Created:** [January 21, 2026, 8:27am UTC](https://discuss.pynq.io/t/rfsoc4x2-pynq-remote-issue/8970 "2026-01-21T08:27:46Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![ismail](https://avatars.discourse-cdn.com/v4/letter/i/779978/32.png) [@ismail](https://discuss.pynq.io/u/ismail)\ **Post date:** [January 21, 2026, 8:27am UTC](https://discuss.pynq.io/t/rfsoc4x2-pynq-remote-issue/8970/1 "2026-01-21T08:27:46Z")
Hi, I am currently trying to use PYNQ.remote with the RFSoC4x2 board. With a VM running Ubuntu 22.04 LTS, with Vivado, Vitis, PetaLinux 2024.1, and Docker, I have successfully built a PYNQ.remote SD card image for the RFSoC4x2 using the process described in the following AMD PYNQ support thread: > [@Building pynq.remote image checkenv error \[RFSoC 4x2\]](https://discuss.pynq.io/t/building-pynq-remote-image-checkenv-error-rfsoc-4x2/8961): > > Hello, I am trying to build a custom image for the RFSoC 4x2 board so my team and I can use the new remote features of 3.1.2. Unfortunately, I am running into an error I cannot figure out: I get this checkenv error but can’t seem to fix it. I have opened Vitis and used the “source” command to make sure the container can access it. Vitis is located in the standard /tools/Xilinx/… directory. It is structured the same as Vivado and I have not altered it since it was installed. I have ch… My initial build failed; however, the second build completed successfully and generated the RFSoC4x2-3.1.1.img file. I suspect the first build failed because Yocto could not find a cached build artifact and then rebuilt it from scratch on the second attempt. I powered up the RFSoC4x2 with the image flashed to an SD card and connected the board to a serial console using a standard micro-USB cable. The board boots through U-Boot, starts the Linux kernel, and reaches the login prompt. However, once at the login prompt, the following message is repeatedly printed every few seconds: > usb usb2-port1: Cannot enable. Maybe the USB cable is bad? I have tested the USB cable on other devices and data transfer appears to work correctly. I attempted to log in using “xilinx” as both the username and password between these messages, but the system responds with “Login incorrect.” The OLED display on the RFSoC board also remains blank. Has anyone experienced this issue before, or does anyone know the cause of this and how it might be resolved? I have attached a log of the messages displayed by the RFSoC4x2 on the serial console during startup. [serial\_console\_output.txt](https://discuss.pynq.io/uploads/short-url/ubAou1pnEDIprUMxU27cqdVAz45.txt) (40.1 KB) Any help or suggestions will be appreciated. Thank you. ---
**Author:** ![Ironmanna](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.pynq.io/ironmanna/32/7444_2.png) [@Ironmanna](https://discuss.pynq.io/u/Ironmanna)\ **Post date:** [January 21, 2026, 9:21am UTC](https://discuss.pynq.io/t/rfsoc4x2-pynq-remote-issue/8970/2 "2026-01-21T09:21:19Z")
Hi @ismail Have you tried logging in using petalinux? At the initial boot, it should prompt you to create a new password. Also, if you’re able to login into the board, make sure pynq-remote is up and running using `sudo systemctl status pynq-remote` You can find more information about the login credentials here: [https://docs.amd.com/r/2024.1-English/ug1144-petalinux-tools-reference-guide/Login-Changes](https://docs.amd.com/r/2024.1-English/ug1144-petalinux-tools-reference-guide/Login-Changes) ---
**Author:** ![ismail](https://avatars.discourse-cdn.com/v4/letter/i/779978/32.png) [@ismail](https://discuss.pynq.io/u/ismail)\ **Post date:** [January 22, 2026, 1:31pm UTC](https://discuss.pynq.io/t/rfsoc4x2-pynq-remote-issue/8970/3 "2026-01-22T13:31:20Z")
Hi @Ironmanna Thank you for your advice. I have successfully logged into Petalinux on the RFSoC board using the username you provided. I now have jupyter lab running on a host machine and connected to the RFSoC4x2 board. ---
**Author:** ![drewphysics](https://avatars.discourse-cdn.com/v4/letter/d/87869e/32.png) [@drewphysics](https://discuss.pynq.io/u/drewphysics)\ **Post date:** [January 25, 2026, 2:59am UTC](https://discuss.pynq.io/t/rfsoc4x2-pynq-remote-issue/8970/4 "2026-01-25T02:59:14Z")
I had this same problem using the version 3.0.1 and also the newer version 3.1.1 from [PYNQ supported boards and PYNQ pre-built images | PYNQ](http://www.pynq.io/boards.html). Curiously, it didn’t seem to effect using the PYNQ servers over the USB3 cable, but I did not do any excessive testing. After going around with people at RealDigital, I finally got the answer: there’s a new USB chip I think for the usb3 port, and RealDigital had to make a patch to 3.0.1. Here’s the patched image: > **[Microsoft OneDrive](https://onedrive.live.com/?cid=50290cbc7c0f3b24&id=50290CBC7C0F3B24%21s8d71bfc3513b460099a61a2cc99899e4&resid=50290CBC7C0F3B24%21s8d71bfc3513b460099a61a2cc99899e4&e=xZ1Lj3&migratedtospo=true&redeem=aHR0cHM6Ly8xZHJ2Lm1zL3UvYy81MDI5MGNiYzdjMGYzYjI0L0VjT19jWTA3VVFCR21hWWFMTW1ZbWVRQkdLNmpsbEdFVWI2QjlhZDZtNGgwamc_ZT14WjFMajM)** It’s a patched 3.0.1 image. When RealDigital ships a new board, the image on the SD card that comes with it will have this patch. As of last Dec, the images on the [PYNQ.io](http://PYNQ.io) web site does NOT have the patch (although maybe they fixed it by now). I guess you will need their patch, so maybe contact RealDigital and see if they will help. Good luck!