We also tried using another SD card with same v3.0.1 image downloaded from pynq.io. It did not work. Is there a defect in reading the uboot from the sd card? Do we need to flash v2.7 into the board?
So what we mean is even after flashing the SD card again with the 3.0.1 image, the sequence of LEDs lighting up got stuck at the ‘INT’ LED and is not proceeding to the ‘DONE’ LED and further. So, should we try downloading the image again in a new SD card and start the board again?
Does the OLED turn on/print anything? I would open up a serial terminal and watch the boot sequence where it is failing. If the sd card got corrupted somehow, worth trying to burn a new one.
Yes, the display showed ‘Test Failed’ when we switched the board ON for the first time. Maybe it showed that because we didn’t connect the ethernet cable. After that we connected the ethernet and other required cables but everytime it got stuck on the ‘INT’ LED. No further LED lit up.
If you flash the latest v3.0.1 pynq image, there is not selftest being run on it so you shouldn’t see any “test fail” messages with that image. If you are seeing “test fail” it is the wrong image.
I would make sure v3.0.1 is definitely loaded on your sd card, on successful boot an IP address should appear on the OLED, if not then I would use a serial terminal to debug what is going on.
We tried everything, flashed a new sd card with the recent PYNQ image, also flashed another sd card with an older version of image but still we have the same problem. The LED sequence stops at INT red LED.
No, there is no display in the OLED. But, we are observing red LEDs glowing under the ‘USB FAULT’ named ‘TOP’ and ‘BOT’. Is this normal for these LEDs to glow up first?
No the usb fault leds shouldn’t be on, my bet is there is something wrong with the sd card. It seems to me like you’re having a similar issue to this post RFSoC 4x2 Does not show any IP address in the Display - #10 by kulla002, the author of that post had a screenshot with the usb fault leds on as well, reflashing the sd card solved their issue.
The fact that you managed to get a “test failed” on the OLED the first time you booted the board with the shipped sd card image means the board is certainly functional enough to boot. What method are you using to flash your sd card?
For flashing a new SD card we used dd command in linux, macOS, BalenaEtcher, Rufus, Win32. But every time it is getting stuck at the same LED. Can the format of SD card create issues. Right now the format is FAT16. In my laptop MS-DOS(FAT) is not getting selected. Is there anyway to download the bitstream using UART port?
We used 3 new SD cards and tried flashing both v3.0.1 and v2.7 version of the image. Also in the terminal emulator (MacWise), there is no recognition of the serial port. We tried Teraterm also, but got the same issue.
We are connecting both the ethernet and USB 3.0 cable to the board and the laptop. But only the ethernet is recognised, no sign of USB cable being detected.
We were testing our new RFSoC 4x2 board. The board is working fine with the windows system but showing some problems with Mac. When we are connecting the board to a Mac system, it is showing the IP address but the jupyter lab is not loading. Are there any other additional requirements that we should be aware of for using the board with mac?
I’ve noticed some weirdness with my 4x2 boot procedure when I have multiple cables plugged into it during the boot. Have you tried turning on the board with only ethernet plugged in? Make sure the board is in “boot from SD Card mode”. You should be able to plug in the USB micro here after it’s fully booted and see a device recognized: