Jump to content

Search the Community

Showing results for tags 'mangopi-mq'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Community
    • Announcements
    • Feature Requests
  • Using Armbian
    • Beginners
    • Software, Applications, Userspace
    • Advanced users - Development
  • Upcoming Hardware
    • News
    • RISC-V
  • Maintained Hardware
    • Board does not start
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families
  • Community maintained / Unmaintained
    • TV boxes
    • Off-topic
    • Amlogic meson
    • Allwinner sunxi
    • Marvell mvebu
    • Rockchip
    • Other families


  • Official giveaways
  • Community giveaways

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start






Website URL







Found 8 results

  1. Added alpha version of image build support for RISC-V. 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/
  2. Hello, 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.
  3. Hi everyone! I tried to boot both Lunar and Sid and got similar UART-console output: 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?
  4. Hi Guys! 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. SPI_INT PD17 SPI_SCK PD11 SPI_SI PD12 SPI_SO PD13 SPI_CS PD10 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# 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!
  5. Hello everyone 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?:(
  6. Downloaded Armina 23.8 Lunar CLI version and used the Raspberry Pi imager to push it to a 32G SD card. (I use a mac). It still does not boot, here is the log file that it produces.... Can't find a valid device tree. MangoPiBootlog.txt
  7. I have recently taken on the somewhat challenging task of creating a power monitoring system similar to an IoTaWatt. I have been doing research on the topic and have concluded that a RISC V Mango Pi Pink V1.4 would be a viable board to get the job done. However I still need some assistance from people with more knowledge than me on the topic. I have several questions that i would greatly appreciate if answered. Is the RISC V Mango Pi Pink V1.4 capable of running Armbian with processing power to spare? Is the RISC V Mango Pi Pink V1.4 a powerful enough computer to take several inputs and graph them? Does anyone have any tips on how you would go about making a system similar to IoTaWatt? 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.
  8. Hi all, 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
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines