[Gitalk:/hardware/en/lichee/th1520/lpi4a/3_images.html] 镜像集合 - Sipeed Wiki #449
Comments
|
Hello together, when is planned the next image release ? Damian |
|
Maybe middle in this month, decrease browser error. |
|
This page, https://wiki.sipeed.com/hardware/en/lichee/th1520/lpi4a/3_images.html, has a typo/error: "Account: root, debian, sipeed; passwords are all licheepi You can't have the account 'debian' have two different passwords :) |
|
Where is the link for Ubuntu project? |
|
I have the June 2023 image burned. Is keeping Debian up-to-date with apt update/upgrade sufficient, or should I be re-flashing the images instead? |
My guess is that it will appear here when it's alpha/beta quality: |
|
I am unable to flash any images as the device continuously connects and disconnects to any computer I connect to with any cable. Driver installation succeeded but flashing fails as the device is constantly connecting and disconnecting. Has anyone else encountered this issue? |
There is an OS in this board. Connect with HDMI monitor and boot board to check if it works well. |
It boots and successfully loads the desktop, though it is noted that Chromium cannot be opened and crashes on launch. After successfully booting, I have made additional attempts to image the board with the same result. The device is recognized by windows but disconnects and reconnects multiple times per second. Linux is unable to detect the device in imaging mode. |
Hi. |
|
Thank you for the response. The system exhibits the same behaviors when connected to the rear interface of the system, as well as when a 12V power supply or a 65W USB-C power supply is connected. It still connects and disconnects rapidly. |
Are u using the 8+8 version? |
|
Thank you for the excellent ideas. I figured it was some sort of power issue and began trying to remove everything from the rear interface of my pc. It seemed to reduce the frequency of the disconnects but not stop them completely. In further troubleshooting I realized the disconnects could be prevented by putting downward pressure on the USB-C cable. It appears that the USB-C connector on the board was faulty or maybe had some debris in it, because after cycling it many times it now works mostly normal and I was able to successfully flash an image. Thank you again! |
You're welcome, glad that ur problem is solved ^ ^ |
|
Highly need an official sipeed image without GUI. |
|
I've tried official images from 20231023, basic and full. Was able to burn and boot into basic image, everything work as expected. But got issue trying to boot full image, error reported in debug console: [ 5.198842] Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. Could anyone help to solve this issue? complete log is below: |
Your flash was corrupted somehow. I've had very little luck using the full image with included fastboot binary until I reboot my computer and it just decided to flash more than a few thousand little tiny packets at a time until it froze up. Using the new burn_tools_support_bigimage zip could solve this, though I haven't tried it. Also, giving us the console output of the flashing script would be more helpful. |
|
ok, thanks for info, good to know that no issues are expected in prebuilt image. I'll try reburn once again and report on results |
|
Hi, |
Maybe could have been a little bit cleaner by opening up a different issue, but I'll give you the benefit of the doubt here. Believe the Sipeed image is some combination of RevyOS kernel sources and T-Head Semi's Yocto toolchain sources. I don't expect much to change booting from an SD card other than making sure the DIP switches underneath are set right and using dd to write the images to the SD card. |
Thank you very much! This is the information I need. BTW, I am not familiar in how Sipeed expect on handling development question. I was entering my question from the wiki page, which in turn lead me to github. And still more question in the sense of your statement "Maybe could have been a little bit cleaner by opening up a different issue"? Where to create such issue? Should I always use the wiki github repo? or can I use licheepi4a github repo for general question about licheepi4a? |
If you were installing the bootloader and U-Boot to SPI flash, having the ability for whatever loads up from SPI to access filesystems on eMMC, etc would be necessary. Kind of want to do that, but at the same time don't since I don't know how accessible the SPI is on either the SOM or motherboard atm, nor my ability to program it even though I do have an Arduino. I didn't realize it at the time, but I now know that every page on the Sipeed wiki has it's own issue thread on GH and every comment on the wiki adds to that issue. So yeah, I guess that's my bad. The Wiki is pretty much the most accessible way to get questions answered, less so with the dedicated GH page. |
|
Hi, I have a 16g+128g lichee Pi4a board. I've downloaded the LPI4A_FULL_20231214.zip image and tried to flash the board to use latest image. I've tried several times, it always hangs at "Sending sparse 'root' 18/78 (110653 KB)", what could be the problem? |
|
I just tried image LPI4A_BASIC_20231023.zip, it can be flashed without issue. However, image LPI4A_BASIC_20231214.zip hangs when writing 'boot' section. Seems image from Dec., 2023 cannot work on my board (I have no idea which date my board is manufactured). |
|
make sure you use 'burn_tools_support_bigimage.zip' according to instructions on LicheePi Wiki site. |
This has been resolved. Please see vladimir-dudnik-1's reply above. |
|
Hi there, A have several questions though:
|
|
Hello, need help with board version: 51603 [ 5091.523274] usb 1-3: new high-speed USB device number 6 using xhci_hcd Host: Debian 12.7 I tried three USB cable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://wiki.sipeed.com/hardware/en/lichee/th1520/lpi4a/3_images.html
The text was updated successfully, but these errors were encountered: