root@orangepirv2:~# uname -a
Linux orangepirv2 6.6.63-current-ky #1 SMP PREEMPT Tue Mar 18 02:29:27 UTC 2025 riscv64 GNU/Linux
root@orangepirv2:~# cat /etc/os-release 
PRETTY_NAME="Armbian-unofficial 26.02.0-trunk trixie"
NAME="Debian GNU/Linux"
VERSION_ID="13"
VERSION="13 (trixie)"
VERSION_CODENAME=trixie
DEBIAN_VERSION_FULL=13.2
ID=debian
HOME_URL="https://www.armbian.com/"
SUPPORT_URL="https://forum.armbian.com"
BUG_REPORT_URL="https://www.armbian.com/bugs"
ARMBIAN_PRETTY_NAME="Armbian-unofficial 26.02.0-trunk trixie"

This is not ready for prime time now. Needs a bit cleanup b/c I pulled in binaries and private project stuff not meant for armbian-build. Currently resides in this fork https://github.com/sven-ola/armbian-build/tree/orangepi-rv2. If you want to give it a try: it's compile.sh opirv2 after checkout. I've also managed to boot from the top 2230 M.2 SSD but this is also handmade (I'm pretty sure there is a script in here that copies the SD card boot blobs to SPI flash, will try before doing the MR).

Best // Sven-Ola

Issues:  
. Missing Wacom tablet driver support at opening of the Ubuntu GNOME environment, the Stylus pen was not detected as pointer device.  
. Instability at the Firefox Web browser when opening of the start screen.
. Chrome browser also shows issues with Google page display. My bypass solution is to use the startpage.com as default entry portal.  
. Slowness and strange blockings when switching the login to GNOME on Xorg. Xorg mode on Ubuntu. It could give support  to the xinput setup commands.  

I appreciate some guidance how to activate those missing features at the Orange Pi RV2 board. Further test reports are welcome. 

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

So far, this is an early version and some of the functions do not work in it.

Currently, support has been added for the StarFive model.

https://rvspace.org/

Details can be seen in this topic.

https://forum.rvspace.org/t/armbian-for-starfive-build-system-ubuntu-debian/468

Added support for Nezha D1 and Lichee RV (Dock) with Allwinner D1 RISC-V chip. To start the system. Download the image, unpack it, burn it to the SD card.  Connect the SD card to the device and turn on the power. Further steps for initial setup are similar for all Armbian systems.

For the Nezha D1 model, HDMI, LAN, USB, analog audio via 3.5 jack works.

For Lichee RV Dock  works HDMI WiFi USB USB-LAN

Link to download images.

https://disk.yandex.ru/d/da8qJ8wyE1hhcQ

https://www.cnx-software.com/2021/12/30/sipeed-lichee-rv-risc-v-module-gets-5-carrier-board-with-hdmi-and-usb-ports-optional-wifi/

forum MangoPI

https://forum.mangopi.org/

I tried to load the latest armbian builds but I couldn't boot. As for performance, I have to say that with the official sipeed image I'm not bad even if it's not a distro but a debian image optimized by the sipeed team. I also believe in this case that there are no maintainers who can follow the armbian community release of this board, what a pity.

What other image could I use? Thanks to everyone

I would like to know if anyone is still playing with this board and what image they are using and if starting from an old armbian image I can restart somehow.

I know that the graphics without hardware acceleration are really poor and the packages should not be updated at the risk of losing optimizations or serious problems such as turning off the video interface on hdmi.

Sorry for the long rant but I'm sorry I can't play on this board, thanks everyone.

BOARD=bananapif3
BOARD_NAME="BananaPi BPI-F3"
BOARDFAMILY=spacemit
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=2f1fa5f40
LINUXFAMILY=spacemit
ARCH=riscv
BOOT_SOC=
IMAGE_TYPE=nightly
BOARD_TYPE=csc
INITRD_ARCH=riscv
KERNEL_IMAGE_TYPE=Image
KERNEL_TARGET=current
KERNEL_TEST_TARGET=
FORCE_BOOTSCRIPT_UPDATE=
FORCE_UBOOT_UPDATE=
OVERLAY_DIR=""
VENDOR="Armbian"
VENDORDOCS="https://docs.armbian.com"
VENDORURL="https://www.armbian.com/"
VENDORSUPPORT="https://forum.armbian.com"
VENDORBUGS="https://www.armbian.com/bugs"
VERSION=25.5.0-trunk.52
REVISION=25.5.0-trunk.52
BRANCH=current

I tried to enbale the I2C bus according followig documentation - but it didn't work for me.
 

https://forum.banana-pi.org/t/bananapif3-gpio-wiringpi-gpiod-python3-periphery-adafruit-blinka-and-luma-examples/18948

https://paste.armbian.de/furuzimipu

 

[    0.535367] /soc/i2c@d401d800/spm8821@41: Fixed dependency cycle(s) with /soc/i2c@d401d800/spm8821@41/regulators/DCDC_REG5
[    0.558741] raid6: int64x8  gen()  1179 MB/s
[    0.559346] spacemit-regulator spacemit-regulator@spm8821: DMA mask not set
[    0.599031] /soc/i2c@d401d800/spm8821@41: Fixed dependency cycle(s) with /soc/i2c@d401d800/spm8821@41/regulators

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

https://disk.yandex.ru/d/eEC4riP1jBWCeg

Important. For the system to work correctly, you need to update the bootloader once. To do this, download the image from the link

https://disk.yandex.ru/d/zsqznfa1ySI2gw

 burn it to the SD card, connect it to Star64 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 Star64 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.

root@192.168.1.51's password: 
 ____  _              __   _  _   
/ ___|| |_ __ _ _ __ / /_ | || |  
\___ \| __/ _` | '__| '_ \| || |_ 
 ___) | || (_| | |  | (_) |__   _|
|____/ \__\__,_|_|   \___/   |_|  
                                  
Welcome to Armbian 23.06 Jammy with Linux 5.15.115-star64

System load:   3%           	Up time:       3 min	
Memory usage:  3% of 3.80G  	IP:	       192.168.1.51
CPU temp:      39°C           	Usage of /:    17% of 7.1G   	
RX today:      19.4 KiB  	

[ 10 security updates available, 12 updates total: apt upgrade ]
Last check: 2023-06-22 12:32

[ General system configuration (beta): armbian-config ]

Last login: Thu Jun 22 12:32:24 2023
root@star64:~# cat /proc/cpuinfo 
processor	: 0
hart		: 1
isa		: rv64imafdc
mmu		: sv39
isa-ext		: 
uarch		: sifive,u74-mc

processor	: 1
hart		: 2
isa		: rv64imafdc
mmu		: sv39
isa-ext		: 
uarch		: sifive,u74-mc

processor	: 2
hart		: 3
isa		: rv64imafdc
mmu		: sv39
isa-ext		: 
uarch		: sifive,u74-mc

processor	: 3
hart		: 4
isa		: rv64imafdc
mmu		: sv39
isa-ext		: 
uarch		: sifive,u74-mc

root@star64:~# neofetch 
            .-/+oossssoo+/-.               root@star64 
        `:+ssssssssssssssssss+:`           ----------- 
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 22.04.2 LTS riscv64 
    .ossssssssssssssssssdMMMNysssso.       Host: Pine64 Star64 
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.15.115-star64 
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 4 mins 
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 509 (dpkg) 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.1.16 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Resolution: 1920x1080 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   Terminal: /dev/pts/0 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   CPU: (4) @ 1.500GHz 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Memory: 118MiB / 3893MiB 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/                            
  +sssssssssdmydMMMMMMMMddddyssssssss+                             
   /ssssssssssshdmNNNNmyNMMMMhssssss/
    .ossssssssssssssssssdMMMNysssso.
      -+sssssssssssssssssyyyssss+-
        `:+ssssssssssssssssss+:`
            .-/+oossssoo+/-.

root@star64:~# 

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.

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?

hastebin - iqolofuzis (armbian.com)

That is my hastebin paste made from a recently built BeagleV-Ahead board that has a four core, RISCV processor. The TH1520 or four c910 processors make up the bulk of the board with some extra functionality. I have been trying to build for this board recently and again.

Anyway, there is a u-boot function in the mix of building an Armbian Jammy image that is called /dev/loop.

It seems this is where my current errors are located in the build. Please send some advice.

Seth

P.S. Here is what I think makes up the main issue:

[💲|🌱] Writing u-boot bootloader [ /dev/loop2 ]
/home/karlth/build_armbian/lib/functions/image/loop.sh: line 89: write_uboot_platform: command not found

There is a new BeagleV-Ahead I would like to see have Armbian support. 

* T-Head TH1520 (quad-core Xuantie C910 processor) and etc...

I was trying to get support and I wanted to reach out. So, here I am. I am making a .csc file now which hopefully one day will be a full-blown .conf file w/ xxx_defconfig support.

Seth

P.S. Please let me know what steps I need to take to get support. 

Armbian_23.09_Starfive2_lunar_current_6.1.31.img.xz

Which is from https://disk.yandex.ru/d/YDBZD53WnCk1Ig/ArmbianTV/20231123-current

So the board works, but there seems to be no USB support?

I tried to boot from the image from the Armbian site https://www.armbian.com/star64/

But it will not boot at all. What am I doing wrong?

I have compiled a boot image for MangoPi Pro D1 from the source code at the link

https://github.com/chainsx/armbian-riscv-build

these sources, as I understand it, are based on:
https://github.com/150balbes/build

The image is working, but I can't install Kernel Headers

Console displays me the following message:

max@nezha:~$ sudo apt install linux-headers-$(uname -r)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package linux-headers-5.19.17-d1
E: Couldn't find any package by glob 'linux-headers-5.19.17-d1'

Which way should we move and dig to resolve the issue?

cat /proc/version

Linux version 5.19.17-d1 (root@jammy-vm) (riscv64-unknown-linux-gnu-gcc (Xuantie-900 linux-5.10.4 glibc gcc Toolchain V2.6.1 B-20220906) 10.2.0, GNU ld (GNU Binutils) 2.35) #riscv Sun Jan 14 14:33:15 +04 2024

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.

• BeagleV: Beta version has been delivered to developers. Now runs Fedora. Price: 150 USD.
• Nezha RISC-V SBC: Seems available, see https://www.cnx-software.com/2021/05/20/nezha-risc-v-linux-sbc/ . 99 USD. OS: "Tina, a fork of OpenWrt, officially supported by Allwinner, " ...
• D1 Linux RISC-V SBC: promised for May, but we have to wait and see. https://www.cnx-software.com/2021/04/13/allwinner-d1-linux-risc-v-sbc-processor/

If it helps, I'm willing to do a small donation.

I've been trying MangoPi MQ Pro images for a couple weeks now, it always fails booting with same behaviour, with the same error message.

To me, the most important lines are those:

ERROR: Did not find a cmdline Flattened Device Tree
Could not find a valid device tree
SCRIPT FAILED: continuing...

With my limited knowledge, my understanding is that the memory where the devicetree file is loaded gets overwritten by something else, or is loaded in memory address higher than the 512MB available on this device.

I understand that MangoPi MQ Pro images are based on the Nezha D1 board witch is comes with 1GB of memory.

So I decided to mess a little bit with u-boot variables to confirm my assumptions. (Again I am not a developer and I'm a bit clueless on how to deal with these numbers correctly.)

Booting this image Armbian_23.8.0-trunk.52_Mangopi-mq_lunar_edge_6.1.0-rc3.img with the default settings, I get the same invalid devicetree error.

But with the following parameters I manage to boot the kernel, well not really but the kernel at least try to start.

etenv fdt_high 0xffffffffffffffff
setenv initrd_high 0xffffffffffffffff
setenv scriptaddr 0x88100000
setenv script_offset_f 0x1fff000
setenv script_size_f 0x1000
setenv kernel_addr_r 0x84000000
setenv kernel_comp_addr_r 0x90000000
setenv kernel_comp_size 0x10000000
setenv fdt_addr_r 0x88000000
setenv ramdisk_addr_r 0x88300000
setenv distro_bootpart 1
run mmc_boot

Result:

=> run mmc_boot
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
1:      Armbian
Retrieving file: /boot/uInitrd
Retrieving file: /boot/Image
append: root=UUID=6aabfef8-4a9a-4cc5-8504-710ab6b18516 console=ttyS0,115200n8 console=tty0 earlycon=sbi cma=96M rootflags=data=writeback stmmaceth=chain_mode:1 rw rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnams
Retrieving file: /boot/dtb/allwinner/sun20i-d1-nezha.dtb
## Loading init Ramdisk from Legacy Image at 88300000 ...
   Image Name:   uInitrd
   Image Type:   RISC-V Linux RAMDisk Image (gzip compressed)
   Data Size:    20125415 Bytes = 19.2 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
sun4i_usb_phy phy@4100400: PHY: Failed to power off phy@4100400: -38.
device_remove: Device 'usb@4200400' failed to remove, but children are gone
   Using Device Tree in place at 0000000088000000, end 0000000088009963

Starting kernel ...

[    0.000000] Linux version 6.1.0-rc3-d1 (armbian@next) (riscv64-linux-gnu-gcc (Ubuntu 11.3.0-1ubuntu1~22.04.1) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 Thu Nov  3 04:50:15 UTC 2022
[    0.000000] Machine model: Allwinner D1 Nezha
[    0.000000] earlycon: sbi0 at I/O port 0x0 (options '')
[    0.000000] printk: bootconsole [sbi0] enabled
[    0.000000] efi: UEFI not found.
[    0.000000] INITRD: 0x88300000+0x01332000 is not a memory region - disabling initrd
[    0.000000] Unable to handle kernel paging request at virtual address ffffffd80186cae8
[    0.000000] Oops [#1]
[    0.000000] Modules linked in:
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 6.1.0-rc3-d1 #1
[    0.000000] Hardware name: Allwinner D1 Nezha (DT)
[    0.000000] epc : vmalloc_fault.constprop.0+0x64/0x168
[    0.000000]  ra : do_page_fault+0x60/0x39e
[    0.000000] epc : ffffffff80008d1e ra : ffffffff80008e82 sp : ffffffff81603d10
[    0.000000]  gp : ffffffff8185da58 tp : ffffffff8160aac0 t0 : ffffffff80008e22
[    0.000000]  t1 : ffffffff80e002b0 t2 : ffffffff80e00330 s0 : ffffffff81603d30
[    0.000000]  s1 : ffffffd77c000001 a0 : ffffffff8185d2a8 a1 : ffffffff811c0970
[    0.000000]  a2 : ffffffff8186cae8 a3 : 0000000000000000 a4 : 0000000000000ae8
[    0.000000]  a5 : ffffffd80186cae8 a6 : 0000000000000000 a7 : 0000000000000018
[    0.000000]  s2 : ffffffff81603db0 s3 : 000000000000000d s4 : 0000000000000000
[    0.000000]  s5 : ffffffff8160aac0 s6 : 0000000000000000 s7 : 0000000000000000
[    0.000000]  s8 : 000000007ff1d180 s9 : 000000007ffb69c0 s10: 0000000000000001
[    0.000000]  s11: 0000000000000002 t3 : 7000000000000000 t4 : ffffffff80c117a0
[    0.000000]  t5 : ffffffff80c117a0 t6 : ffffffff80c117d0
[    0.000000] status: 0000000200000100 badaddr: ffffffd80186cae8 cause: 000000000000000f
[    0.000000] [<ffffffff80008e82>] do_page_fault+0x60/0x39e
[    0.000000] [<ffffffff800037c8>] ret_from_exception+0x0/0xc
[    0.000000] ---[ end trace 0000000000000000 ]---
[    0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[    0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the idle task! ]---

I hope this can help someone more knowledgeable than me to figure out better numbers that could lead to a fully booting MangoPI MQ Pro.

Armbian_23.05.0-trunk-e33842ef2_Mangopi-mq_lunar_edge_6.1.0-rc3.boot.log

 I noticed that "/boot/dtb/allwinner/sun20i-d1-nezha.dtb" is wrong choise, found it in extlinux.conf and changed it like this(hope commenting out strings works here):

label Armbian
  kernel /boot/Image
  initrd /boot/uInitrd
#  fdt /boot/dtb/allwinner/sun20i-d1-nezha.dtb
  fdt /boot/dtb/allwinner/sun20i-d1-mangopi-mq-pro.dtb
  append root=UUID=5e7413f7-b308-4843-b9a9-063d99cb1700 console=ttyS0,115200n8 console=tty0 earlycon=sbi cma=96M rootflags=data=writeback stmmaceth=chain_mode:1 rw rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles

the result was like this(this is just a tail of log):

lunar_edge_tail.log

Am I on the right path?

This is my fist post on this forum. I have been spending a lot of time these days to make the MCP2515 CAN Controller on the RISCV computer, but I am not able to make it work even if everything seems to be on place. It is obvious that I am not understanding something correclty and that is why is not working. I am using the MangoPi Mqpro that has the SPI port on the 40 pin connector.

Right now is not possible to add overlays on mangopi with the arbiam, but I managed to upload my custom overlays using the grub and Ubuntu, that part is not relevant for the topic. Let's assume for the topic that I am able to upload overlays and they are correctly applied on device tree.

### Connections

The SPI interface is defined as follows, extracted from /sys/kernel/debug/pinctrl/2000000.pinctrl/pinmux-pins:

pin 106 (PD10): device 4026000.spi function spi1 group PD10
pin 107 (PD11): device 4026000.spi function spi1 group PD11
pin 108 (PD12): device 4026000.spi function spi1 group PD12
pin 109 (PD13): device 4026000.spi function spi1 group PD13
pin 110 (PD14): device 4026000.spi function spi1 group PD14
pin 111 (PD15): device 4026000.spi function spi1 group PD15
pin 112 (PD16): device 2000c00.pwm function pwm group PD16
pin 113 (PD17): device spi1.0 function irq group PD17

Basically is connected to the SPI interface of the MCP2515, and the interrupt is connected to PD17.

The overlay that I am applying is the next one:

/dts-v1/;
/plugin/;

/ {
	compatible = "allwinner,d1-nezha\0allwinner,sun20i-d1";

	fragment@0 {
		target-path = "/clocks";
		__overlay__ {
			#address-cells = <1>;
			#size-cells = <1>;
            /* External crystal oscillator on the board */
			can0_osc_fixed: can0_osc_fixed {
				compatible = "fixed-clock";
                #clock-cells = <0>;
                clock-frequency  = <8000000>;
                phandle = <0x81>;
			};
		};
	};

	fragment@1 {
		target = <&pinctrl>; // pinctrl@2000000
		__overlay__ {
			can0_pin_irq: can0_pin_irq {
				pins = "PD17";
                function = "irq";
                phandle = <0x85>;
			};
		};
	};

	fragment@2 {
		target = <&spi>;   //spi@4026000
		__overlay__ {
			#address-cells = <1>;
			#size-cells = <0>;
			status = "okay";
			mcp2515 {
				reg = <0>;		// SPI 1
                compatible = "microchip,mcp2515";
                pinctrl-names = "default";
                pinctrl-0 = <0x85>;
                spi-max-frequency = <10000000>;
                interrupt-parent = <0x22>; // pinctrl@2000000
                interrupts = <0 113 2>; // IRQ LINE, try with <0 65 2>
                clocks = <0x81>;
                status = "okay";
			};
		};
	};
};

However when I boot up I look to the interrupts and there is nothing related to the irq line for the CAN/spi, output of /proc/interrupts:

           CPU0       
  2:      79503  sun20i-intc  75 Edge      timer@2050000
  3:          0  sun20i-intc 109 Edge      5500000.hdmi, dw-hdmi-cec
  4:          0  sun20i-intc  25 Edge      mv64xxx_i2c
  5:          0  RISC-V INTC   5 Edge      riscv-timer
  6:         14  sun20i-intc  68 Edge      sun8i-ce-ns
  7:          0  sun20i-intc  47 Edge      ohci_hcd:usb3
 74:          0  sun20i-intc  31 Edge      sun6i-spi
 78:       5926  sun20i-intc  74 Edge      ths
 79:          0  sun20i-intc  50 Edge      ohci_hcd:usb4
 80:          0  sun20i-intc  46 Edge      ehci_hcd:usb1
 81:       1336  sun20i-intc  18 Edge      ttyS1
 82:     189890  sun20i-intc  57 Edge      sunxi-mmc
 83:          0  sun20i-intc  82 Edge      1c0e000.video-codec
 84:          0  sun20i-intc  80 Edge      2010000.iommu
 85:          0  sun20i-intc 107 Edge      5470000.lcd-controller
 88:          0  sun20i-intc  49 Edge      ehci_hcd:usb2
 89:          0  sun20i-intc 160 Edge      7090000.rtc
 90:          2  sun20i-intc  27 Edge      mv64xxx_i2c
 98:          0  sun20i-intc  45 Edge      musb-hdrc.2.auto
101:       8630  sun20i-intc  56 Edge      sunxi-mmc
109:          0  sun20i-intc  66 Edge      3002000.dma-controller
111:          4  sun20i-intc  32 Edge      sun6i-spi
112:          0  sun20i-intc  77 Edge      sun4i-a10-lradc-keys
113:          0  sun20i-intc 106 Edge      5461000.lcd-controller
114:          7  sun20i-intc 167 Edge      sunxi-ir
119:          0  sun20i-intc  36 Edge      2008000.led-controller
204:          1  sunxi_pio_edge  84 Edge      usb0-vbus-det
205:          1  sunxi_pio_edge  85 Edge      usb0-id-det
254:          1  sunxi_pio_edge 134 Edge      4020000.mmc cd
IPI0:         0  Rescheduling interrupts
IPI1:         0  Function call interrupts
IPI2:         0  CPU stop interrupts
IPI3:         0  IRQ work interrupts
IPI4:         0  Timer broadcast interrupts

Some outputs from the Kernel:

[   52.133406] CAN device driver interface
[   52.918270] mcp251x spi1.0 can0: MCP2515 successfully initialized.
[ 1163.417322] IPv6: ADDRCONF(NETDEV_CHANGE): can0: link becomes ready
[ 1182.919088] can: controller area network core
[ 1182.919249] NET: Registered PF_CAN protocol family
[ 1183.000429] can: raw protocol

And after booting I run the next:

$ sudo ip link set can0 up type can bitrate 500000
$ sudo ifconfig can0 up
$ sudo cansend can0 5A1#00.01.02.03.04

This configuration is not working because when I try to connect, I am not receiving anything.

I suppose that I am not configuring correctly the interrupt line of the IRQ of SPI. My knowledge on this is very narrow, and I am not able to understand what is failing. All the feedback is totally welcome. I can give more documentation if my explanation is not complete enought.

Thanks!

I have some trouble with device tree from Mango Pi. There is no overlays in Mango Pi D1: armbian-add-overlay file.dts => output: D1 is not support for overlays.

When start board, command dmesg | grep serial output: @2500000.serial and @2500400.serial. It's okay.

When I decompiled sun20i-d1-nezha.dtb file I saw that serial@2500000 and serial@2500400 status = "okay", other serials status = "disable". There are serials: 2500000,2500400,2500800,2500c00,2501000,2501400.

So I try, for example, to change status for serial@2500800 from disable to okay. After dtc -I dts -O dtb to the /boot/dtb/allwiner then I did reboot and dmesg | grep serial output only serial@2500000 and serial@2500400, there is no 2500800.

What's the problem?:(

It still does not boot, here is the log file that it produces.... 

Can't find a valid device tree.

MangoPiBootlog.txt

Can anyone explain what is really being said on the git hub? I have never used it and have on idea what is what.

IoTaWatt Homepage - https://iotawatt.com/

IoTaWatt Github - https://github.com/boblemaire/IoTaWatt

 

Thank you to anyone who can help.

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.

won't boot directly from microSD, switches   01 SD

I'm trying to build @balbes150's risc-v branch of Armbian and put it into /dev/sdb 32GB SD card.

I'm using Ubuntu 22.04.

./compile.sh BOARD=nezha BRANCH=current RELEASE=sid BUILD_MINIMAL=no BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no CARD_DEVICE="/dev/sdb"

It went well, the card seems OK to me.

$ lsblk
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda       8:0    0 931,5G  0 disk
└─sda1    8:1    0 931,5G  0 part
sdb       8:16   1  28,9G  0 disk
├─sdb1    8:17   1   256M  0 part
└─sdb2    8:18   1   2,7G  0 part /media/slavek/c4be3c21-ec0c-4ccb-a9ec-f310583febf9

When I try to boot my MangoPi Pro (D1) from it, I see no output on HDMI.

I might need to add a bootloader to the card? How do I do it?

Could some of Armbian gurus help me please?

Thank you, JP