Jump to content

Search the Community

Showing results for tags 'visionfive2'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Armbian
    • Armbian project administration
  • Community
    • Announcements
    • SBC News
    • Framework and userspace feature requests
    • Off-topic
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Standard support
    • Amlogic meson
    • Allwinner sunxi
    • Rockchip
    • Other families
  • Community maintained / Staging
    • TV boxes
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Support

Product Groups

  • Misc
  • Support


  • Armbian
  • Armbian releases


  • Volunteering opportunities


  • Community Calendar


  • Official giveaways
  • Community giveaways


  • Members

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 9 results

  1. Visionfive2 booting spi version starfive 5.11.3 firmware. U-boot sees the 8GB RAM. I am using Armbian_community_24.5.0-trunk.433_Visionfive2_jammy_edge_5.15.0_xfce_desktop.img. I suspect there is something broken with the dtb file. I am loading this dtb: load nvme 0:1 ${fdt_addr_r} /boot/dtb/starfive/jh7110-visionfive-v2.dtb When I use OpenBSD 7.5 the 8GB is seen, but that is a different dtb file and EFI boot process. Is there a different dtb file to use?
  2. Hello there! Over the past month and more I have been making many experiments - and right now, I am waiting for a finished product; a Docker container with musl-libc and gcc to serve as a "clean slate build environment". Initially, I had intended for this to be the environment for Alpine Linux - because I want the `alpine:3.19` container so half my software, including k3s, stops complaining xD - but figured, I made all those configs and have gathered all of this experience AND have a board right here - which is where I am putting my container together, too. Yep, those four cores are working overtime, since a month straight, between dozen revisions and rebuilds. I still have to finalize my U-Boot and OpenSBI config; but this is what my kernel has right now: ``` # cat /boot/config-6.6.0-g076ede06c00a | grep -E "JH7110|JH7100|SIFIVE|STARFIVE|VISIONFIVE" # CONFIG_SOC_SIFIVE is not set CONFIG_ARCH_STARFIVE=y CONFIG_SOC_STARFIVE=y CONFIG_ERRATA_SIFIVE=y CONFIG_ERRATA_SIFIVE_CIP_453=y CONFIG_ERRATA_SIFIVE_CIP_1200=y CONFIG_PCIE_STARFIVE_HOST=y CONFIG_DWMAC_STARFIVE=y CONFIG_SERIAL_SIFIVE=y CONFIG_SERIAL_SIFIVE_CONSOLE=y CONFIG_HW_RANDOM_JH7110=y CONFIG_SPI_SIFIVE=m CONFIG_PINCTRL_STARFIVE_JH7100=y CONFIG_PINCTRL_STARFIVE_JH7110=y CONFIG_PINCTRL_STARFIVE_JH7110_SYS=y CONFIG_PINCTRL_STARFIVE_JH7110_AON=y # CONFIG_GPIO_SIFIVE is not set CONFIG_STARFIVE_WATCHDOG=y CONFIG_DRM_VERISILICON_STARFIVE_HDMI=y CONFIG_SND_SOC_STARFIVE=y CONFIG_SND_SOC_JH7110_PWMDAC=y CONFIG_SND_SOC_JH7110_TDM=y CONFIG_USB_CDNS3_STARFIVE=y CONFIG_MMC_DW_STARFIVE=y CONFIG_VIDEO_STARFIVE_CAMSS=y CONFIG_CLK_STARFIVE_JH71X0=y CONFIG_CLK_STARFIVE_JH7100=y CONFIG_CLK_STARFIVE_JH7100_AUDIO=y CONFIG_CLK_STARFIVE_JH7110_PLL=y CONFIG_CLK_STARFIVE_JH7110_SYS=y CONFIG_CLK_STARFIVE_JH7110_AON=y CONFIG_CLK_STARFIVE_JH7110_STG=y CONFIG_CLK_STARFIVE_JH7110_ISP=y CONFIG_CLK_STARFIVE_JH7110_VOUT=y CONFIG_STARFIVE_JH7110_TIMER=y CONFIG_SIFIVE_CCACHE=y # CONFIG_PWM_SIFIVE is not set CONFIG_SIFIVE_PLIC=y CONFIG_RESET_STARFIVE_JH71X0=y # CONFIG_RESET_STARFIVE_JH7100 is not set CONFIG_RESET_STARFIVE_JH7110=y CONFIG_PHY_STARFIVE_JH7110_DPHY_RX=y CONFIG_PHY_STARFIVE_JH7110_PCIE=y CONFIG_PHY_STARFIVE_JH7110_USB=y CONFIG_CRYPTO_DEV_JH7110=y ``` And those are required. There is a porting page about the currently outstanding patches that have yet to be accepted into mainline, so I am just effectively living on this: https://github.com/starfive-tech/linux/tree/JH7110_VisionFive2_upstream (note the branch). This is Linux 6.6.0. I am also working on merging Imaginary's GPU drivers - currently based on 6.6.0-rc1 - into this tree, but Github won't let me post it... Oh well; the merge is just four files. Aside from that, there are also repos for MESA and the linux-firmware; constituting two packages specific to this board - or rather, this GPU. I wish they had made the driver itself a DKIM one... would've been more portable, I suppose. Anyway; with all of this said, I have a few questions: 1. Where does one apply for maintainership? The VF2 currently has none. 2. How, in the automated build process (`compile.sh` in the `armbian/build` repo), do I specify config snippets for this specific soc/board for kernel, u-boot and openspi? 3. Anything else I need? Kind regards, Ingwie
  3. I wanted to ask you why the RISC-V images are missing and in particular in one case the previous ones are also missing, e.g. https://imola.armbian.com/archive/mangopi-mq/archive
  4. Images for Visionfive-2. https://disk.yandex.ru/d/YDBZD53WnCk1Ig Important. For the system to work correctly, you need to update the bootloader in SPI\flash once (the switch for selecting the device to run should be set to “qspi” 0,0 , this is the default state when delivered from the factory). To do this, download the image from the link https://disk.yandex.ru/d/zsqznfa1ySI2gw burn it to the SD card, connect it to VF2 and turn on the power, wait 2 minutes and turn off the power. After that, you can write an ArmbianTV image to the SD card, connect it to VF2 and the system will start automatically. The next steps are usually the initial setup of Armbian. In versions with DE (IceWM XFCE). even video playback in the window works (fullscreen mode does not work) through the Parole player. Analog audio output is enabled by default, to switch to HDMI audio, use the settings via Volume Control as usual.
  5. The RNNoise code and instructions for compiling it are located at https://gitlab.xiph.org/xiph/rnnoise and highlight the latest addition of Jean-Marc Valin, a developer who I can never thank enough for the work he has done. Two years have passed since the highlighted addition and therefore updated instructions on how to complete the compilation would be useful in general and not just for the hardware we have. This is the sequence of commands: sudo atp update sudo apt install autogen sudo apt install configure-debian sudo apt install dh-autoreconf ./autogen.sh ./configure make -j36 sudo make install -j36 You will now have the RNNoise libraries installed on your system and the demo program to try them in the examples folder. RNNoise is an audio noise suppression library based on a recurrent neural network and it cannot be missing on the hardware used to record the human voice. Those who don’t know it yet can find the documentation on Archiv website and further information on the Mozilla and Jean-Marc Valin's website. I’m sure someone will appreciate it.
  6. Hi, I'm testing a visionfive2 board with 8GB ram and I can only see 4GB in the armbian installed system. As far as I understand, the official image by StarFive has a extra u-boot partition on SD that tricks something to make the ram fully visible to the system. In fact I can see 8GB when using the official debian image but only 4 under armbian. Is there any way to fix this? I'd like to use the armbian environment while using the full ram available. I'm trying to mashup the two partition schemas but I'm probably doing someting wrong... Thank you in advance for any (very appreciated) help! -psi
  7. On Armbian_23.5.0-trunk.140_Visionfive2_lunar_edge_5.15.0.img.xz chrony fails to start: May 02 23:24:48 visionfive2 systemd[1]: Starting chrony.service - chrony, an NTP client/server... May 02 23:24:48 visionfive2 chronyd[1874]: chronyd version 4.3 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGN> May 02 23:24:48 visionfive2 chronyd[1874]: Using right/UTC timezone to obtain leap second data May 02 23:24:48 visionfive2 chronyd[1874]: Fatal error : Failed to load seccomp rules May 02 23:24:48 visionfive2 chronyd-starter.sh[1872]: Failed to load seccomp rules May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Control process exited, code=exited, status=1/FAILURE May 02 23:24:48 visionfive2 systemd[1]: chrony.service: Failed with result 'exit-code'. May 02 23:24:48 visionfive2 systemd[1]: Failed to start chrony.service - chrony, an NTP client/server. So I am using ntpdate (from ntpsec-ntpdate) at boot.
  8. I tried setting SKIP_BOOTSPLASH=yes from Hidden options for advanced users of the Build Options page, but the Armbian splash screen still appears. Since I have to ask here, I am obviously not an advanced user. 🙃 How do I eliminate the boot splash screen as I am building/testing images? ./compile.sh \ BOARD=visionfive2 \ BRANCH=edge \ RELEASE=lunar \ BUILD_MINIMAL=no \ BUILD_DESKTOP=no \ KERNEL_CONFIGURE=no \ SKIP_BOOTSPLASH=yes \ CARD_DEVICE="/dev/sdb"
  9. Works with flash boot select, switches 00 Flash won't boot directly from microSD, switches 01 SD
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines