Installation on Magicsee N5 Plus (S905X3) Failed

Hi,

I’m trying to install Manjaro on a TV box Magicsee N5 Plus (Amlogic S905X3).
But the boot failed (toothpick methode), after some seconds, I have the recovery display.

System : Manjaro-ARM-minimal-generic-22.06.img.xz
Support : SD Card 32GB (Sandisk Ultra A1)
DTB File : dedicated file which have created on this box.
Log file : can’t join it ?

Could you help me ?

Ok, step by step so ^^

Is that normal this error :

Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SD32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SD32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading aml_autoscript
** Unable to read file aml_autoscript **
reading recovery.img
** Unable to read file recovery.img **
(Re)start USB…

And some lines later, I have this. Is this Manjaro starting ?

Booting Android Image at 0x01080000 …

Kernel command line: androidboot.dtbo_idx=0 --cmdline root=/dev/mmcblk0p18 buildvariant=userdebug
Start read misc partition datas!
info->magic =
info->version_major = 1
info->version_minor = 0
info->slots[0].priority = 15
info->slots[0].tries_remaining = 7
info->slots[0].successful_boot = 0
info->slots[1].priority = 14
info->slots[1].tries_remaining = 7
info->slots[1].successful_boot = 0
info->crc32 = -1075449479
active slot = 0
active_slot is normal
load dtb from 0x1000000 …
Amlogic multi-dtb tool
Single dtb detected
find 1 dtbos
dtbos to be applied: 0
Apply dtbo 0
Loading Kernel Image(COMP_NONE) … OK
kernel loaded at 0x01080000, end = 0x01997420
Loading Ramdisk to 099a0000, end 09fffb2e … OK
Loading Device Tree to 0000000009987000, end 000000000999f7eb … OK

Starting kernel …

uboot time: 7974902 us
[ 0.000000@0] Booting Linux on physical CPU 0x0
[ 0.000000@0] Linux version 4.9.113 (lidaojun@ubuntu) (gcc version 6.3.1 20170109 (Linaro GCC 6.3-2017.02) ) #2 SMP PREEMPT Thu Oct 31 22:25:34 CST 2019
[ 0.000000@0] CPU: ARMv7 Processor [411fd050] revision 0 (ARMv7), cr=10c5383d
[ 0.000000@0] CPU: div instructions available: patching division code
[ 0.000000@0] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000@0] OF: fdt:Machine model: Amlogic

You can try one of the Odroid C4 images instead, as that has the same SoC, so might work.

Unfortunately, I have the same result :sleepy:

Do you have any firmware on SPI or eMMC?

Because you’re using the wrong image.

Use either am6 or GT-King pro image.
Then change dtb name in uEnv.ini

You should be able to boot into manjaro atleast.

I have the initial android system.

This 2 board didn’t have the same MCU … Is it not a problem ??? → Bad asnwer, this is dtb file which match the MCU …

So, hem … I have an interesting result : No box reset, but stay freeze on Amlogic boot logo …

log :

[mmc_startup] mmc refix success
init_part() 274: PART_TYPE_EFI
[mmc_init] mmc init success
Device: SDIO Port B
Manufacturer ID: 3
OEM: 5344
Name: SD32G
Tran Speed: 50000000
Rd Block Len: 512
SD version 3.0
High Capacity: Yes
Capacity: 29.7 GiB
mmc clock: 40000000
Bus Width: 4-bit
reading s905_autoscript
930 bytes read in 3 ms (302.7 KiB/s)
## Executing script at 01020000
reading u-boot.ext
** Unable to read file u-boot.ext **
** Bad device usb 0 **
reading uImage
28762688 bytes read in 1549 ms (17.7 MiB/s)
reading uInitrd
8306954 bytes read in 451 ms (17.6 MiB/s)
reading uEnv.ini
314 bytes read in 2 ms (153.3 KiB/s)
mac=06:8E:B2:13:60:89
reading /dtbs/amlogic/meson-sm1-magicsee_n5_plus.dtb
88435 bytes read in 12 ms (7 MiB/s)
avb2: 0
ee_gate_off ...
avb2: 0
## Booting kernel from Legacy Image at 01080000 ...
   Image Name:   uImage
   Image Type:   AArch64 Linux Kernel Image (uncompressed)
   Data Size:    28762624 Bytes = 27.4 MiB
   Load Address: 01080000
   Entry Point:  01080000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 13000000 ...
   Image Name:   uInitrd Image
   Image Type:   AArch64 Linux RAMDisk Image (uncompressed)
   Data Size:    8306890 Bytes = 7.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
Start read misc partition datas!
info->magic =
info->version_major = 1
info->version_minor = 0
info->slots[0].priority = 15
info->slots[0].tries_remaining = 7
info->slots[0].successful_boot = 0
info->slots[1].priority = 14
info->slots[1].tries_remaining = 7
info->slots[1].successful_boot = 0
info->crc32 = -1075449479
active slot = 0
active_slot is normal
load dtb from 0x1000000 ......
      Amlogic multi-dtb tool
      Single dtb detected
## Flattened Device Tree blob at 01000000
   Booting using the fdt blob at 0x1000000
find 1 dtbos
No androidboot.dtbo_idx configured
And no dtbos will be applied
   Loading Kernel Image(COMP_NONE) ... OK
   kernel loaded at 0x01080000, end = 0x02bee200
   Loading Ramdisk to 7f013000, end 7f7ff0ca ... OK
   Loading Device Tree to 000000001ffe7000, end 000000001ffffa28 ... OK

Starting kernel ...

uboot time: 5964625 us

And after … nothing …

This is some progress though.

Now the boot process is correct. It reads uEnv.ini , uImage and uInitrd.

Still it is trying to fall back to Android. You should try some other generic dtb.

Good luck

You’re right !!! I tried the file meson-sm1-x96-air-gbit.dtb , and it’s start !!! Thanks a lot !!! :slight_smile:

Starting kernel ...

uboot time: 6000206 us
[    1.004578] meson-drm ff900000.vpu: Failed to find CVBS Connector bridge
[    3.965015] systemd-fstab-generator[278]: Failed to create unit file /run/systemd/generator/boot.mount, as it already exists. Duplicate entry in /etc/fstab?
[    4.060710] systemd[274]: /usr/lib/systemd/system-generators/systemd-fstab-generator failed with exit status 1.
[    6.675024] panfrost ffe40000.gpu: dev_pm_opp_set_regulators: no regulator (mali) found: -19
[   11.032289] meson8b-dwmac ff3f0000.ethernet: Failed to reset the dma
[   11.033076] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_hw_setup: DMA engine initialization failed
[   11.042041] meson8b-dwmac ff3f0000.ethernet eth0: stmmac_open: Hw setup failed

Manjaro Linux 5.18.1-1-MANJARO-ARM-KHADAS (ttyAML0)

manjaro-arm login:

Ethernet problem solved with dtb without gbit version

1 Like

Hi is onboard wifi working for you or only the Ethernet?

I have F3 Air with similar processor, intrested to know if wifi and Bluetooth working.

I think no … :cry:

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.