Open gnocil opened 1 year ago
The reason I had this problem earlier was that the SD was locked, you can check SD card
The reason I had this problem earlier was that the SD was locked, you can check SD card
Hi, thanks for sharing your experience. I have checked the lock switch on my SD, but, unfortunately, it is not locked. I have tried to put it on lock mode, and I was having unable to mount error and kernel panic error.
Can you fill in all the info in our template?
Can you share the detailed info of all your operation from downloading the img to inserting the sd card on board? (The Linux commands and the outputs, the file operations, etc.)
Can you fill in all the info in our template?
Can you share the detailed info of all your operation from downloading the img to inserting the sd card on board? (The Linux commands and the outputs, the file operations, etc.)
Hi Dr Jiao,
Please see the updated post on the top with all requested info supplied.
Basically, I just flashed the .img into a 16GB SD card and have not done anything else. The UART prints Kernel panic errors, so haven't had the chance to input Linux commands yet. I also tried the SD card coming along with the FMCOMNNS2 board, and I can see the linux successfully running with root@analog: prompt.
I encountered the same issue. I suspect that the RTC is in an abnormal state. During initialization, Kuiper requests the clock, but it fails. The most apparent solution is to set CONFIG_RTC_DRV_ZYNQMP=n in the kernel configuration and then rebuild the kernel.
Could you send email to xianjun.jiao@ugent.be to introduce your self? Sent
Our image is used directly or you build your own image? I used the image "openwifi-1.4.0-notter.img" unzipped from "openwifi-1.4.0-notter.img.xz".
What is your own modification? No modification
Versions: OS, Vivado, openwifi/openwifi-hw repo branch and commit revision Ubuntu 22.04, using openwifi/openwifi-hw version in the quick instruction page, Vivado not used yet
Board/hardware type ZCU102, FMCOMMS2
WiFi channel number Not reach this step so far.
Steps to reproduce the issue, and the related error message, screenshot, etc I followed the quick start instruction : a. flash SD card with image openwifi-1.4.0-notter.img; b. copied all files in the folder Boot/openwifi/zcu102_fmcs2/* to Boot/;
Screenshot of Boot partition:
c. check these two folders rootfs/root/kernel_modules rootfs/etc/network/interfaces.new and confirm these two don't exist;
Screenshot of rootfs partition:
d. insert SD card to ZCU102 sd card slot with lock switched off; e. configure the boot switches to on-off-off-off to enable boot from SD card; f. connect the USB cable to PC and configure the UART console successfully; g. switch the ZCU102 board on and start seeing output as attached below.
Dear Dr. Jiao,
I built a bootable SD card for ZCU102+FMCOMMS2 using the latest image openwifi-1.4.0-notter.img.xz following the quick start instructions and I am able to see printouts from UART. However, the boot process stopped in the middle so I cannot get the OpenWiFi system running at the moment.
Please see the attached log from the UART. The booting ends with an error of [ end Kernel panic - not syncing] and I am unsure if it is caused by the bootable SD card files or something else as I didn't see any similar existing issues from the issue history.
Thank you for looking into the issue!