<![CDATA[PINE64 - Linux on PINE A64-LTS / SOPINE]]> https://forum.pine64.org/ Thu, 21 May 2026 18:13:20 +0000 MyBB <![CDATA[7 inch touch panel patches]]> https://forum.pine64.org/showthread.php?tid=20082 Mon, 17 Nov 2025 06:57:54 +0000 mkjmkj]]> https://forum.pine64.org/showthread.php?tid=20082
I have tried porting Alpine Linux 3.22.2 to my Pine64 A64 LTS v2 board using only packages from Alpine communities, which works reasonable except for sound, ethernet device is weird (have to ethtool it to 100mbit for it to work). I also have a 7 inch panel https://pine64.com/product/7-lcd-touch-screen-panel/ which doesn't work at all. 

I found from the Armbian community patches to DTS overlays that should enable it (pine64_lcd=on). Latest Armbian images doesn't work either, their u-boot breaks my Pine64 board (doesn't detect RAM and demands reset), and the panel only backlights up (no image), though HDMI works,. The touchscreen does produce output when running libinput debug-events.

I have tried experimenting with dts patches to the 6.12 kernel source tree, and got the touchpanel discovered but still broken, while the kernel panics and oops every so often.

I'd like to ask the Pine64 community if anyone have an overview of which patches are needed for the 7 inch panel to work on a 6.12 kernel?]]>
I have tried porting Alpine Linux 3.22.2 to my Pine64 A64 LTS v2 board using only packages from Alpine communities, which works reasonable except for sound, ethernet device is weird (have to ethtool it to 100mbit for it to work). I also have a 7 inch panel https://pine64.com/product/7-lcd-touch-screen-panel/ which doesn't work at all. 

I found from the Armbian community patches to DTS overlays that should enable it (pine64_lcd=on). Latest Armbian images doesn't work either, their u-boot breaks my Pine64 board (doesn't detect RAM and demands reset), and the panel only backlights up (no image), though HDMI works,. The touchscreen does produce output when running libinput debug-events.

I have tried experimenting with dts patches to the 6.12 kernel source tree, and got the touchpanel discovered but still broken, while the kernel panics and oops every so often.

I'd like to ask the Pine64 community if anyone have an overview of which patches are needed for the 7 inch panel to work on a 6.12 kernel?]]> <![CDATA[Uboot says bad image magic - mainline kernel]]> https://forum.pine64.org/showthread.php?tid=19460 Sun, 13 Oct 2024 19:17:14 +0000 lash]]> https://forum.pine64.org/showthread.php?tid=19460
When booting the kernel, I get "Bad ARM64 Image Magic" I can't figure out what this means, and why it is happening. Sources I have searched seem to be board specific, and found nothing on this board. I've arrived at a point where I cannot find a way to reason further about it, so thus I am reaching out.

I am currently loading the kernel and dtb manually at the uboot prompt:

setenv bootargs loglevel=7 earlyprintk
fatload mmc 0:1 0x42000000 boot/vmlinux
fatload mmc 0:1 0x4a000000 boot/u-boot.dtb
booti 0x42000000 - 0x4a000000

My current configuration is:

        - linux 5.14 from mainline (git:7d2a07b769330c34b4deabeed939325c77a7ec2f)
        - u-boot v2024.10 from https://source.denx.de/u-boot/u-boot (git:f919c3a889f0ec7d63a48b5d0ed064386b0980bd)
        - dtb from the u-boot build
        - bl31.bin from PLAT=sun50i_a64 https://git.trustedfirmware.org/TF-A/tru...ware-a.git lts-v2.10.6 (git:f2aebf361050d69176d60016170291efa9e08a68)
        - scp.bin from https://github.com/crust-firmware/crust 0.6 (git:ffe9f1ac9c675e6e67db9084bd19fbdeffd8e162)
        - u-boot-sunxi-with-spl.bin written to offset 8k
        - tried sd and emmc vfat single partition (whole disk) with
                * boot/vmlinux
                * boot/u-boot.dtb

Files:
    - uboot defconfig: https://g33k.holbrook.no/c36cab0e6a15127...7b25f71bdd
    - uboot environment (saved from soc): https://g33k.holbrook.no/1c4d93e6510eb49...2329468b73
    - linux defconfig: https://g33k.holbrook.no/5bde4487e333f5a...19beb3382f]]>
When booting the kernel, I get "Bad ARM64 Image Magic" I can't figure out what this means, and why it is happening. Sources I have searched seem to be board specific, and found nothing on this board. I've arrived at a point where I cannot find a way to reason further about it, so thus I am reaching out.

I am currently loading the kernel and dtb manually at the uboot prompt:

setenv bootargs loglevel=7 earlyprintk
fatload mmc 0:1 0x42000000 boot/vmlinux
fatload mmc 0:1 0x4a000000 boot/u-boot.dtb
booti 0x42000000 - 0x4a000000

My current configuration is:

        - linux 5.14 from mainline (git:7d2a07b769330c34b4deabeed939325c77a7ec2f)
        - u-boot v2024.10 from https://source.denx.de/u-boot/u-boot (git:f919c3a889f0ec7d63a48b5d0ed064386b0980bd)
        - dtb from the u-boot build
        - bl31.bin from PLAT=sun50i_a64 https://git.trustedfirmware.org/TF-A/tru...ware-a.git lts-v2.10.6 (git:f2aebf361050d69176d60016170291efa9e08a68)
        - scp.bin from https://github.com/crust-firmware/crust 0.6 (git:ffe9f1ac9c675e6e67db9084bd19fbdeffd8e162)
        - u-boot-sunxi-with-spl.bin written to offset 8k
        - tried sd and emmc vfat single partition (whole disk) with
                * boot/vmlinux
                * boot/u-boot.dtb

Files:
    - uboot defconfig: https://g33k.holbrook.no/c36cab0e6a15127...7b25f71bdd
    - uboot environment (saved from soc): https://g33k.holbrook.no/1c4d93e6510eb49...2329468b73
    - linux defconfig: https://g33k.holbrook.no/5bde4487e333f5a...19beb3382f]]> <![CDATA[Wifi not recognized - Pine64+ / Debian Bullseye]]> https://forum.pine64.org/showthread.php?tid=19384 Tue, 13 Aug 2024 16:09:56 +0000 coredumpster]]> https://forum.pine64.org/showthread.php?tid=19384
Have successfully installed Debian 11 ( Bullseye ) and have that running, but cannot for the life of me seem to get the wifi/bt module enabled.

I have installed the firmware-realtek package, which should have the right firmware bits, but something else appears to be missing, and I'm at a loss.

Code:
cparker@pine64:~$ uname -a
Linux pine64 5.10.0-32-arm64 #1 SMP Debian 5.10.223-1 (2024-08-10) aarch64 GNU/Linux
cparker@pine64:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye

The Realtek FW .bin files are in /usr/lib/firmware/rtlwifi  for the rtl8723bs.

Modprobe doesn't appear to do anything.

Is it an issue with Debian / Bullseye?  Would Bookworm be different, or Armbian?  Not stuck with this version, but it's the first one I was able to get to boot properly, with everything else working.]]>
Have successfully installed Debian 11 ( Bullseye ) and have that running, but cannot for the life of me seem to get the wifi/bt module enabled.

I have installed the firmware-realtek package, which should have the right firmware bits, but something else appears to be missing, and I'm at a loss.

Code:
cparker@pine64:~$ uname -a
Linux pine64 5.10.0-32-arm64 #1 SMP Debian 5.10.223-1 (2024-08-10) aarch64 GNU/Linux
cparker@pine64:~$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye

The Realtek FW .bin files are in /usr/lib/firmware/rtlwifi  for the rtl8723bs.

Modprobe doesn't appear to do anything.

Is it an issue with Debian / Bullseye?  Would Bookworm be different, or Armbian?  Not stuck with this version, but it's the first one I was able to get to boot properly, with everything else working.]]> <![CDATA[PINE A64-LTS enable I2S on Linux]]> https://forum.pine64.org/showthread.php?tid=19382 Thu, 08 Aug 2024 18:09:57 +0000 toadShepard]]> https://forum.pine64.org/showthread.php?tid=19382 https://forum.pine64.org/showthread.php?tid=6906

But after modifying the equivalent .dts file overlay (mine is sun50i-a64-pine64-lts.dts) I am able to see i2s0 under /sys/firmware/devicetree/base/soc/i2s@1c22000/status is set to "okay". But when I run "aplay -l" I get the response "no soundcards found...". 

Any help is appreciated.]]> https://forum.pine64.org/showthread.php?tid=6906

But after modifying the equivalent .dts file overlay (mine is sun50i-a64-pine64-lts.dts) I am able to see i2s0 under /sys/firmware/devicetree/base/soc/i2s@1c22000/status is set to "okay". But when I run "aplay -l" I get the response "no soundcards found...". 

Any help is appreciated.]]> <![CDATA[Armbian for Pine64 LTS]]> https://forum.pine64.org/showthread.php?tid=19207 Sat, 04 May 2024 17:18:12 +0000 Mark88]]> https://forum.pine64.org/showthread.php?tid=19207
i have an LTS board and i am trying to find a way to install Armbian on it.
I was using this board since more than 5 years now without any issue or update, but now i need to use it on a different project and i need something more fresh than Bionic.

I was trying to install something newer but actually the only working version of Armbian i found is Armbian_21.02.1_Pine64so_bionic_current_5.10.12.
Is there any way to install something newer on this board or is time to became a paper holder?

I have tryed newer version but the board can't boot.

Thanks in advice for any help.]]>
i have an LTS board and i am trying to find a way to install Armbian on it.
I was using this board since more than 5 years now without any issue or update, but now i need to use it on a different project and i need something more fresh than Bionic.

I was trying to install something newer but actually the only working version of Armbian i found is Armbian_21.02.1_Pine64so_bionic_current_5.10.12.
Is there any way to install something newer on this board or is time to became a paper holder?

I have tryed newer version but the board can't boot.

Thanks in advice for any help.]]> <![CDATA[Can't boot from eMMc with Armbian 23.8 Bookworm]]> https://forum.pine64.org/showthread.php?tid=18844 Tue, 07 Nov 2023 08:50:49 +0000 francoispawlus]]> https://forum.pine64.org/showthread.php?tid=18844
I try to evaluate the platform based on:
  • Sopine Baseboard model A
  • Sopine A64 compute module
  • Armbian 23.8 Bookworm

There is no issue with SDCard boot.

But when I try to boot the same image from eMMC (32G), the process stopped when the kernel start.

Here is an extract of the log from the serial console:
Please go to the last line to see the last operation.

Code:
[10:40:49:671] U-Boot SPL 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000)
[10:40:49:695] DRAM: 2048 MiB
[10:40:49:695] Trying to boot from MMC2
[10:40:50:402] NOTICE:  BL31: v2.9(debug):armbian
[10:40:50:402] NOTICE:  BL31: Built : 08:27:02, Aug 31 2023
[10:40:50:402] NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
[10:40:50:402] NOTICE:  BL31: Found U-Boot DTB at 0x20ab818, model: SoPine with baseboard
[10:40:50:402] INFO:    ARM GICv2 driver initialized
[10:40:50:402] INFO:    Configuring SPC Controller
[10:40:50:402] INFO:    PMIC: Probing AXP803 on RSB
[10:40:50:402] INFO:    PMIC: dcdc1 voltage: 3.300V
[10:40:50:402] INFO:    PMIC: dcdc5 voltage: 1.200V
[10:40:50:402] INFO:    PMIC: dcdc6 voltage: 1.100V
[10:40:50:402] INFO:    PMIC: dldo1 voltage: 3.300V
[10:40:50:402] INFO:    PMIC: dldo2 voltage: 3.300V
[10:40:50:448] INFO:    PMIC: dldo4 voltage: 3.300V
[10:40:50:448] INFO:    PMIC: fldo1 voltage: 1.200V
[10:40:50:448] INFO:    PMIC: Enabling DC SW
[10:40:50:448] INFO:    BL31: Platform setup done
[10:40:50:448] INFO:    BL31: Initializing runtime services
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
[10:40:50:448] SCP/INF: Crust v0.5.10000
[10:40:50:448] INFO:    PSCI: Suspend is available via SCPI
[10:40:50:448] INFO:    BL31: Preparing for EL3 exit to normal world
[10:40:50:468] INFO:    Entry point address = 0x4a000000
[10:40:50:468] INFO:    SPSR = 0x3c9
[10:40:50:961] ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
[10:40:50:961]
[10:40:50:961]
[10:40:50:961] U-Boot 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000) Allwinner Technology
[10:40:50:961]
[10:40:50:961] CPU:   Allwinner A64 (SUN50I)
[10:40:50:961] Model: SoPine with baseboard
[10:40:50:961] DRAM:  2 GiB
[10:40:51:022] Core:  73 devices, 22 uclasses, devicetree: separate
[10:40:51:022] WDT:   Not starting watchdog@1c20ca0
[10:40:51:022] MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
[10:40:51:045] Loading Environment from FAT... Unable to use mmc 1:1...
[10:40:52:787] In:    serial
[10:40:52:787] Out:   serial
[10:40:52:787] Err:   serial
[10:40:52:803] Net:   eth0: ethernet@1c30000
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] starting USB...
[10:40:52:843] Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus
[10:40:52:881] USB EHCI 1.00
[10:40:52:881] Bus usb@1c1a400: USB OHCI 1.0
[10:40:52:897] Bus usb@1c1b000: USB EHCI 1.00
[10:40:52:924] Bus usb@1c1b400: USB OHCI 1.0
[10:40:52:924] scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
[10:40:54:067] scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
[10:40:55:194] scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
[10:40:56:329] scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
[10:40:57:468]        scanning usb for storage devices... 0 Storage Device(s) found
[10:40:57:468] Autoboot in 1 seconds, press <Space> to stop
[10:40:58:507] switch to partitions #0, OK
[10:40:58:523] mmc1(part 0) is current device
[10:40:58:523] Scanning mmc 1:1...
[10:40:58:555] Found U-Boot script /boot/boot.scr
[10:40:58:602] 3259 bytes read in 5 ms (635.7 KiB/s)
[10:40:58:602] ## Executing script at 4fc00000
[10:40:58:602] U-boot loaded from eMMC or secondary SD
[10:40:58:602] Boot script loaded from mmc
[10:40:58:602] 155 bytes read in 4 ms (37.1 KiB/s)
[10:40:58:602] MMC: no card present
[10:40:58:602] ** Bad device specification mmc 0 **
[10:40:58:642] 41715 bytes read in 11 ms (3.6 MiB/s)
[10:40:58:642] Working FDT set to 4fa00000
[10:40:58:642] 3821 bytes read in 5 ms (746.1 KiB/s)
[10:40:58:642] Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
[10:40:58:642] ## Executing script at 45000000
[10:40:59:041] 18215274 bytes read in 395 ms (44 MiB/s)
[10:40:59:533] 22390792 bytes read in 476 ms (44.9 MiB/s)
[10:40:59:533] Moving Image from 0x40080000 to 0x40200000, end=417d0000
[10:40:59:733] ## Loading init Ramdisk from Legacy Image at 4ff00000 ...
[10:40:59:733]    Image Name:   uInitrd
[10:40:59:733]    Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
[10:40:59:733]    Data Size:    18215210 Bytes = 17.4 MiB
[10:40:59:733]    Load Address: 00000000
[10:40:59:733]    Entry Point:  00000000
[10:40:59:733]    Verifying Checksum ... OK
[10:40:59:861] ## Flattened Device Tree blob at 4fa00000
[10:40:59:861]    Booting using the fdt blob at 0x4fa00000
[10:40:59:882] Working FDT set to 4fa00000
[10:40:59:882]    Loading Ramdisk to 48ea0000, end 49fff12a ... OK
[10:40:59:912]    Loading Device Tree to 0000000048e2d000, end 0000000048e9ffff ... OK
[10:40:59:912] Working FDT set to 48e2d000
[10:41:00:344]
[10:41:00:344] Starting kernel ...
[10:41:00:344]
[10:41:03:989] <0x1b>[2J<0x1b>[3J<0x1b>[-1;-1fdone.
[10:41:04:014] Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[10:41:04:014] Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems


It would be helpfull if somebody have any idea to solved this .

thanks for the support,
BR]]>
I try to evaluate the platform based on:
  • Sopine Baseboard model A
  • Sopine A64 compute module
  • Armbian 23.8 Bookworm

There is no issue with SDCard boot.

But when I try to boot the same image from eMMC (32G), the process stopped when the kernel start.

Here is an extract of the log from the serial console:
Please go to the last line to see the last operation.

Code:
[10:40:49:671] U-Boot SPL 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000)
[10:40:49:695] DRAM: 2048 MiB
[10:40:49:695] Trying to boot from MMC2
[10:40:50:402] NOTICE:  BL31: v2.9(debug):armbian
[10:40:50:402] NOTICE:  BL31: Built : 08:27:02, Aug 31 2023
[10:40:50:402] NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
[10:40:50:402] NOTICE:  BL31: Found U-Boot DTB at 0x20ab818, model: SoPine with baseboard
[10:40:50:402] INFO:    ARM GICv2 driver initialized
[10:40:50:402] INFO:    Configuring SPC Controller
[10:40:50:402] INFO:    PMIC: Probing AXP803 on RSB
[10:40:50:402] INFO:    PMIC: dcdc1 voltage: 3.300V
[10:40:50:402] INFO:    PMIC: dcdc5 voltage: 1.200V
[10:40:50:402] INFO:    PMIC: dcdc6 voltage: 1.100V
[10:40:50:402] INFO:    PMIC: dldo1 voltage: 3.300V
[10:40:50:402] INFO:    PMIC: dldo2 voltage: 3.300V
[10:40:50:448] INFO:    PMIC: dldo4 voltage: 3.300V
[10:40:50:448] INFO:    PMIC: fldo1 voltage: 1.200V
[10:40:50:448] INFO:    PMIC: Enabling DC SW
[10:40:50:448] INFO:    BL31: Platform setup done
[10:40:50:448] INFO:    BL31: Initializing runtime services
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 843419 was applied
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 855873 was applied
[10:40:50:448] INFO:    BL31: cortex_a53: CPU workaround for 1530924 was applied
[10:40:50:448] SCP/INF: Crust v0.5.10000
[10:40:50:448] INFO:    PSCI: Suspend is available via SCPI
[10:40:50:448] INFO:    BL31: Preparing for EL3 exit to normal world
[10:40:50:468] INFO:    Entry point address = 0x4a000000
[10:40:50:468] INFO:    SPSR = 0x3c9
[10:40:50:961] ns16550_serial serial@1c28000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19
[10:40:50:961]
[10:40:50:961]
[10:40:50:961] U-Boot 2023.07.02-armbian (Aug 31 2023 - 08:27:25 +0000) Allwinner Technology
[10:40:50:961]
[10:40:50:961] CPU:   Allwinner A64 (SUN50I)
[10:40:50:961] Model: SoPine with baseboard
[10:40:50:961] DRAM:  2 GiB
[10:40:51:022] Core:  73 devices, 22 uclasses, devicetree: separate
[10:40:51:022] WDT:   Not starting watchdog@1c20ca0
[10:40:51:022] MMC:   mmc@1c0f000: 0, mmc@1c11000: 1
[10:40:51:045] Loading Environment from FAT... Unable to use mmc 1:1...
[10:40:52:787] In:    serial
[10:40:52:787] Out:   serial
[10:40:52:787] Err:   serial
[10:40:52:803] Net:   eth0: ethernet@1c30000
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] MMC: no card present
[10:40:52:843] ** Bad device specification mmc 0 **
[10:40:52:843] Couldn't find partition mmc 0
[10:40:52:843] starting USB...
[10:40:52:843] Bus usb@1c1a000: sun4i_usb_phy phy@1c19400: External vbus detected, not enabling our own vbus
[10:40:52:881] USB EHCI 1.00
[10:40:52:881] Bus usb@1c1a400: USB OHCI 1.0
[10:40:52:897] Bus usb@1c1b000: USB EHCI 1.00
[10:40:52:924] Bus usb@1c1b400: USB OHCI 1.0
[10:40:52:924] scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
[10:40:54:067] scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
[10:40:55:194] scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
[10:40:56:329] scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
[10:40:57:468]        scanning usb for storage devices... 0 Storage Device(s) found
[10:40:57:468] Autoboot in 1 seconds, press <Space> to stop
[10:40:58:507] switch to partitions #0, OK
[10:40:58:523] mmc1(part 0) is current device
[10:40:58:523] Scanning mmc 1:1...
[10:40:58:555] Found U-Boot script /boot/boot.scr
[10:40:58:602] 3259 bytes read in 5 ms (635.7 KiB/s)
[10:40:58:602] ## Executing script at 4fc00000
[10:40:58:602] U-boot loaded from eMMC or secondary SD
[10:40:58:602] Boot script loaded from mmc
[10:40:58:602] 155 bytes read in 4 ms (37.1 KiB/s)
[10:40:58:602] MMC: no card present
[10:40:58:602] ** Bad device specification mmc 0 **
[10:40:58:642] 41715 bytes read in 11 ms (3.6 MiB/s)
[10:40:58:642] Working FDT set to 4fa00000
[10:40:58:642] 3821 bytes read in 5 ms (746.1 KiB/s)
[10:40:58:642] Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
[10:40:58:642] ## Executing script at 45000000
[10:40:59:041] 18215274 bytes read in 395 ms (44 MiB/s)
[10:40:59:533] 22390792 bytes read in 476 ms (44.9 MiB/s)
[10:40:59:533] Moving Image from 0x40080000 to 0x40200000, end=417d0000
[10:40:59:733] ## Loading init Ramdisk from Legacy Image at 4ff00000 ...
[10:40:59:733]    Image Name:   uInitrd
[10:40:59:733]    Image Type:   AArch64 Linux RAMDisk Image (gzip compressed)
[10:40:59:733]    Data Size:    18215210 Bytes = 17.4 MiB
[10:40:59:733]    Load Address: 00000000
[10:40:59:733]    Entry Point:  00000000
[10:40:59:733]    Verifying Checksum ... OK
[10:40:59:861] ## Flattened Device Tree blob at 4fa00000
[10:40:59:861]    Booting using the fdt blob at 0x4fa00000
[10:40:59:882] Working FDT set to 4fa00000
[10:40:59:882]    Loading Ramdisk to 48ea0000, end 49fff12a ... OK
[10:40:59:912]    Loading Device Tree to 0000000048e2d000, end 0000000048e9ffff ... OK
[10:40:59:912] Working FDT set to 48e2d000
[10:41:00:344]
[10:41:00:344] Starting kernel ...
[10:41:00:344]
[10:41:03:989] <0x1b>[2J<0x1b>[3J<0x1b>[-1;-1fdone.
[10:41:04:014] Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
[10:41:04:014] Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems


It would be helpfull if somebody have any idea to solved this .

thanks for the support,
BR]]> <![CDATA[Try to boot armbian 22.02 on SoPine baseboard]]> https://forum.pine64.org/showthread.php?tid=17768 Sat, 31 Dec 2022 01:48:01 +0000 adjivas]]> https://forum.pine64.org/showthread.php?tid=17768
I try to boot Armbian on the SoPine with baseboard from a eMMC module.

From armbian/pine64, I try some Arbian images.
I get this error:
Quote:U-Boot SPL 2022.07-armbian (Nov 30 2022 - 10:45:59 +0000)
DRAM: 0 MiB
### ERROR ### Please RESET the board ###

So I try this specialized image Armbian_22.11.1_Pine64so_bullseye_current_5.15.80.img.xz.
But it's stuck at the `armbi_root: clean` line:
Quote:U-Boot 2022.07-armbian (Nov 30 2022 - 10:45:55 +0000) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  73 devices, 22 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface11
eth0: ethernet@1c30000
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
155 bytes read in 2 ms (75.2 KiB/s)
MMC: no card present
** Bad device specification mmc 0 **
41777 bytes read in 4 ms (10 MiB/s)
3821 bytes read in 3 ms (1.2 MiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
17114760 bytes read in 393 ms (41.5 MiB/s)
21934088 bytes read in 504 ms (41.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41750000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    17114696 Bytes = 16.3 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 48fad000, end 49fff648 ... OK
  Loading Device Tree to 0000000048f3a000, end 0000000048facfff ... OK

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
armbi_root: clean, 69593/130816 files, 435596/523264 blocks

My questions are:
- should I change any configuration files from the Armbian_22.11.1_Pine64so_bullseye_current_5.15.80.img.xz's image?
- should I try another image?

Thank's by advance]]>
I try to boot Armbian on the SoPine with baseboard from a eMMC module.

From armbian/pine64, I try some Arbian images.
I get this error:
Quote:U-Boot SPL 2022.07-armbian (Nov 30 2022 - 10:45:59 +0000)
DRAM: 0 MiB
### ERROR ### Please RESET the board ###

So I try this specialized image Armbian_22.11.1_Pine64so_bullseye_current_5.15.80.img.xz.
But it's stuck at the `armbi_root: clean` line:
Quote:U-Boot 2022.07-armbian (Nov 30 2022 - 10:45:55 +0000) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  73 devices, 22 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface11
eth0: ethernet@1c30000
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
155 bytes read in 2 ms (75.2 KiB/s)
MMC: no card present
** Bad device specification mmc 0 **
41777 bytes read in 4 ms (10 MiB/s)
3821 bytes read in 3 ms (1.2 MiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
17114760 bytes read in 393 ms (41.5 MiB/s)
21934088 bytes read in 504 ms (41.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41750000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    17114696 Bytes = 16.3 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 48fad000, end 49fff648 ... OK
  Loading Device Tree to 0000000048f3a000, end 0000000048facfff ... OK

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
armbi_root: clean, 69593/130816 files, 435596/523264 blocks

My questions are:
- should I change any configuration files from the Armbian_22.11.1_Pine64so_bullseye_current_5.15.80.img.xz's image?
- should I try another image?

Thank's by advance]]> <![CDATA[Manjaro won't boot from EmmC]]> https://forum.pine64.org/showthread.php?tid=17767 Sat, 31 Dec 2022 00:25:24 +0000 adjivas]]> https://forum.pine64.org/showthread.php?tid=17767
I have a Sopine Baseboard Model A
This board haven't a SD interface, it's has a eMMC interface.

I downloaded the last 22.06's image of Manjaro Arm from manjaro-arm/pine64-lts-images's repository.

I flashed my eMMC Module and mounted it on the Sopine baseboard, I connected my USB serial console/programmer and I power on the Sopine.

My problem is during the boot, nothing happen after the `Starting kernel ...` line.

Quote:% sudo screen /dev/ttyUSB0 115200
U-Boot SPL 2022.04-2 (May 05 2022 - 08:29:42 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.6(release):
NOTICE:  BL31: Built : 08:29:42, May  5 2022
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x209c938, model: SoPine with baseboard
SCP/INF: Crust v0.5.10000


U-Boot 2022.04-2 (May 05 2022 - 08:29:42 +0000) Manjaro Linux ARM

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  39 devices, 17 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface10
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      Manjaro ARM
Retrieving file: /initramfs-linux.img
Retrieving file: /Image
append: initrd=/initramfs-linux.img console=ttyS0,115200 root=PARTUUID=1f2fe968-00ee-4b00-ad77-12e7c5c80fac rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/allwinner/sun50i-a64-pine64-lts.dtb
Moving Image from 0x40080000 to 0x40200000, end=419e0000
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 497f6000, end 49fff57e ... OK
  Loading Device Tree to 00000000497e9000, end 00000000497f5dd7 ... OK

Starting kernel ...

My questions are:
- Manjaro Arm isn't yet compatible with Sopine Baseboard?
- Should I change any files of configuration from the Manjaro Arm image?

Thank's by advance!]]>
I have a Sopine Baseboard Model A
This board haven't a SD interface, it's has a eMMC interface.

I downloaded the last 22.06's image of Manjaro Arm from manjaro-arm/pine64-lts-images's repository.

I flashed my eMMC Module and mounted it on the Sopine baseboard, I connected my USB serial console/programmer and I power on the Sopine.

My problem is during the boot, nothing happen after the `Starting kernel ...` line.

Quote:% sudo screen /dev/ttyUSB0 115200
U-Boot SPL 2022.04-2 (May 05 2022 - 08:29:42 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.6(release):
NOTICE:  BL31: Built : 08:29:42, May  5 2022
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x209c938, model: SoPine with baseboard
SCP/INF: Crust v0.5.10000


U-Boot 2022.04-2 (May 05 2022 - 08:29:42 +0000) Manjaro Linux ARM

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  39 devices, 17 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface10
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      Manjaro ARM
Retrieving file: /initramfs-linux.img
Retrieving file: /Image
append: initrd=/initramfs-linux.img console=ttyS0,115200 root=PARTUUID=1f2fe968-00ee-4b00-ad77-12e7c5c80fac rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/allwinner/sun50i-a64-pine64-lts.dtb
Moving Image from 0x40080000 to 0x40200000, end=419e0000
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 497f6000, end 49fff57e ... OK
  Loading Device Tree to 00000000497e9000, end 00000000497f5dd7 ... OK

Starting kernel ...

My questions are:
- Manjaro Arm isn't yet compatible with Sopine Baseboard?
- Should I change any files of configuration from the Manjaro Arm image?

Thank's by advance!]]> <![CDATA[sopine-a64 yocto build running on SOPine Baseboard]]> https://forum.pine64.org/showthread.php?tid=16885 Thu, 23 Jun 2022 15:26:11 +0000 tderensis]]> https://forum.pine64.org/showthread.php?tid=16885
I have followed steps in the meta-pine64 repo here: https://github.com/alistair23/meta-pine64

The only exception is that I have specified the kirkstone branch where possible. I have also added console=tty0 to enable HDMI output.

Build Configuration:
BB_VERSION          = "2.0.0"
BUILD_SYS           = "x86_64-linux"
NATIVELSBSTRING     = "universal"
TARGET_SYS          = "aarch64-poky-linux"
MACHINE             = "sopine-a64"
DISTRO              = "poky"
DISTRO_VERSION      = "4.0.1"
TUNE_FEATURES       = "aarch64"
TARGET_FPU          = ""
meta
meta-poky
meta-yocto-bsp      = "kirkstone:4aeda14352a9fa9dd5ba50cf940a2b514fd1ac3c"
meta-oe
meta-python
meta-multimedia     = "kirkstone:fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7"
meta-arm-toolchain
meta-arm
meta-arm-bsp        = "kirkstone:a8cb33d5139e30b4a643da9a277487299c0e658f"
meta-pine64         = "master:96b5e55c25912c8bd80fbf0e537bf0d3519989ec"
meta-python2        = "kirkstone:f02882e2aa9279ca7becca8d0cedbffe88b5a253"


When I boot the resulting image (core-image-base), I see uboot text, then yocto splash screen. However, almost immediately the HDMI looses connection, but the board remains powered (LEDs on).

Has the kirkstone yocto build been verified with the meta-pine64 layer?]]>
I have followed steps in the meta-pine64 repo here: https://github.com/alistair23/meta-pine64

The only exception is that I have specified the kirkstone branch where possible. I have also added console=tty0 to enable HDMI output.

Build Configuration:
BB_VERSION          = "2.0.0"
BUILD_SYS           = "x86_64-linux"
NATIVELSBSTRING     = "universal"
TARGET_SYS          = "aarch64-poky-linux"
MACHINE             = "sopine-a64"
DISTRO              = "poky"
DISTRO_VERSION      = "4.0.1"
TUNE_FEATURES       = "aarch64"
TARGET_FPU          = ""
meta
meta-poky
meta-yocto-bsp      = "kirkstone:4aeda14352a9fa9dd5ba50cf940a2b514fd1ac3c"
meta-oe
meta-python
meta-multimedia     = "kirkstone:fcc7d7eae82be4c180f2e8fa3db90a8ab3be07b7"
meta-arm-toolchain
meta-arm
meta-arm-bsp        = "kirkstone:a8cb33d5139e30b4a643da9a277487299c0e658f"
meta-pine64         = "master:96b5e55c25912c8bd80fbf0e537bf0d3519989ec"
meta-python2        = "kirkstone:f02882e2aa9279ca7becca8d0cedbffe88b5a253"


When I boot the resulting image (core-image-base), I see uboot text, then yocto splash screen. However, almost immediately the HDMI looses connection, but the board remains powered (LEDs on).

Has the kirkstone yocto build been verified with the meta-pine64 layer?]]> <![CDATA[Armbian 22.02 Release Announcement]]> https://forum.pine64.org/showthread.php?tid=16184 Mon, 28 Feb 2022 23:00:54 +0000 TRS-80]]> https://forum.pine64.org/showthread.php?tid=16184 https://www.armbian.com/newsflash/armbia...ouncement/]]> https://www.armbian.com/newsflash/armbia...ouncement/]]> <![CDATA[SD memory corruption]]> https://forum.pine64.org/showthread.php?tid=16160 Fri, 25 Feb 2022 10:52:07 +0000 Baptiste]]> https://forum.pine64.org/showthread.php?tid=16160 I have some problems of memory corruption with sopine compute module. 

Memory corruption change content of file. 

We removed all hard shutdown to avoid corruption, and we shut down system with command shutdown -h now .


Have you already seen this issue ? What can be used to avoid memory corruption ? 

Thx.]]> I have some problems of memory corruption with sopine compute module. 

Memory corruption change content of file. 

We removed all hard shutdown to avoid corruption, and we shut down system with command shutdown -h now .


Have you already seen this issue ? What can be used to avoid memory corruption ? 

Thx.]]> <![CDATA[Change Ethernet LED behaviour]]> https://forum.pine64.org/showthread.php?tid=14893 Wed, 15 Sep 2021 10:41:03 +0000 pine_A64_user]]> https://forum.pine64.org/showthread.php?tid=14893
I am using a "Pine A64 LTS Version V2" with Armbian 21.08 and I would like to change the behaviour of the Ethernet Port LEDs.

At the moment the LEDs show the following behaviour:

Green: 
      ON,   if no cable is plugged in
      ON,   if cable with 1000 Mbit/s is connected 
      OFF,  if cable with 100 Mbit/s is connected
Orange:
      Flashing, if sending / receiving data


I would like to change that behaviour to the following:

Green:
     OFF, if no cable ist plugged in
     ON,  if cable is plugged in
Orange:
     Flashing, if sending / receiving data


Does anyone know how to achieve that?]]>
I am using a "Pine A64 LTS Version V2" with Armbian 21.08 and I would like to change the behaviour of the Ethernet Port LEDs.

At the moment the LEDs show the following behaviour:

Green: 
      ON,   if no cable is plugged in
      ON,   if cable with 1000 Mbit/s is connected 
      OFF,  if cable with 100 Mbit/s is connected
Orange:
      Flashing, if sending / receiving data


I would like to change that behaviour to the following:

Green:
     OFF, if no cable ist plugged in
     ON,  if cable is plugged in
Orange:
     Flashing, if sending / receiving data


Does anyone know how to achieve that?]]> <![CDATA[slarm64 (unofficial slackware) SOPINE A64 (aarch64)]]> https://forum.pine64.org/showthread.php?tid=14551 Fri, 30 Jul 2021 18:12:52 +0000 mara]]> https://forum.pine64.org/showthread.php?tid=14551 shelldweller,
this board has been added to the assembly slarm64_build_kit

kernel
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst.sha256]]> shelldweller,
this board has been added to the assembly slarm64_build_kit

kernel
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst
slarm64-current-aarch64-server-sopine-5.13.5-build-20210727.img.zst.sha256]]> <![CDATA[Kernel rebuild resources and process for pine64-LTS]]> https://forum.pine64.org/showthread.php?tid=14131 Mon, 07 Jun 2021 06:23:51 +0000 Atreyo tech]]> https://forum.pine64.org/showthread.php?tid=14131 Hi,
 
I am start using pine64-LTS board and currently installing new OS in SD card successfully. Please check below result of "uname -a" according to my board. 
"Linux pine64so 5.10.34-sunxi64 #21.05.1 SMP Fri May 7 15:50"19 UTC 2021 aarch64 GNU/Linux"
 
Now, I want to modify or add some features through kernel. Please guide me how to get kernel source and rebuild process.]]> Hi,
 
I am start using pine64-LTS board and currently installing new OS in SD card successfully. Please check below result of "uname -a" according to my board. 
"Linux pine64so 5.10.34-sunxi64 #21.05.1 SMP Fri May 7 15:50"19 UTC 2021 aarch64 GNU/Linux"
 
Now, I want to modify or add some features through kernel. Please guide me how to get kernel source and rebuild process.]]> <![CDATA[Development environment live-iso for cross compilation, etc?]]> https://forum.pine64.org/showthread.php?tid=14125 Sun, 06 Jun 2021 14:25:46 +0000 Daniel972]]> https://forum.pine64.org/showthread.php?tid=14125
Preferably without  GUI. Anybody? Any hints?]]>
Preferably without  GUI. Anybody? Any hints?]]>