Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Wrong memory detection T95MAX H616

Featured Replies

Hello!

I have a T95MAX ver 3 board with H616 / AXP313 / 4Gb RAM.
I've compiled an Armbian from Nick repo (https://github.com/NickAlilovic/build), branch v20251014 for Transpeed-8k618 with a little defconfig patch for TOC0 and DCDC3 voltage = 1.5V (extracted from Android native image DTB).

 

CONFIG_AXP_DCDC3_VOLT=1500
CONFIG_SPL_IMAGE_TYPE_SUNXI_TOC0=y

 

Image booting ok, but first UBoot stage found 4Gb and second stage found only 2Gb. Someone have any ideas for make 2nd stage and kernel detect full memory?

 

U-Boot SPL 2025.04-armbian-2025.04-S3482-Pfbbd-H8869-V9b5f-Bb703-R448a-dirty (Nov 13 2025 - 13:20:15 +0000)
DRAM:testing 32-bit width, rank = 2
read calibration failed!
testing 32-bit width, rank = 1
Store cfg
1st writing pattern
detected 11 columns
restore cfg
reconfigure for all active rows
store cfg
2nd writing pattern
detecting row address bits
detected 16 rows
restoring cfg
end of auto detect dram size
MBUS port 0 cfg0 0100000d cfg1 00640080
MBUS port 1 cfg0 06000009 cfg1 01000578
MBUS port 2 cfg0 0200000d cfg1 00600100
MBUS port 3 cfg0 01000009 cfg1 00500064
MBUS port 4 cfg0 20000209 cfg1 1388157c
MBUS port 5 cfg0 00640209 cfg1 00200040
MBUS port 6 cfg0 00640209 cfg1 00200040
MBUS port 8 cfg0 01000009 cfg1 00400080
MBUS port 11 cfg0 01000009 cfg1 00640080
MBUS port 14 cfg0 04000009 cfg1 00400100
MBUS port 16 cfg0 2000060d cfg1 09600af0
MBUS port 21 cfg0 0800060d cfg1 02000300
MBUS port 22 cfg0 01000009 cfg1 00640080
MBUS port 25 cfg0 0064000f cfg1 00200040
MBUS port 26 cfg0 20000209 cfg1 1388157c
MBUS port 37 cfg0 01000009 cfg1 00400080
MBUS port 38 cfg0 00640209 cfg1 00200040
MBUS port 39 cfg0 20000209 cfg1 1388157c
MBUS port 40 cfg0 00640209 cfg1 00200040
=> md.l 0x047FA000 
047fa000: 80000000 000009f4 0e40ff00 0000018f
047fa010: 00000010 00103040 00000000 00000000
047fa020: ffffffff 000007ff 0000ffff 00000000
...
04800b40: 00000000 00000000 00000000 00000000
04800b50: 00000000 00000000 00000000 00000000
04800b60: 00000000 00000000 00000000 00000000
04800b70: 00000000 00000000 00000000 00000000
 4096 MiB
Trying to boot from MMC1
NOTICE:  BL31: v2.13.0(debug):armbian
NOTICE:  BL31: Built : 10:39:26, Nov 13 2025
NOTICE:  BL31: Detected Allwinner H616 SoC (1823)
NOTICE:  BL31: Found U-Boot DTB at 0x4a0a4218, model: Transpeed 8K618-T
INFO:    ARM GICv2 driver initialized
INFO:    Configuring SPC Controller
INFO:    Probing for PMIC on I2C:
INFO:    PMIC: found AXP313
INFO:    BL31: Platform setup done
INFO:    BL31: Initializing runtime services
INFO:    BL31: cortex_a53: CPU workaround for erratum 855873 was applied
INFO:    BL31: cortex_a53: CPU workaround for erratum 1530924 was applied
INFO:    PSCI: Suspend is unavailable
INFO:    BL31: Preparing for EL3 exit to normal world
INFO:    Entry point address = 0x4a000000
INFO:    SPSR = 0x3c9
INFO:    Changed devicetree.
ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19


U-Boot 2025.04-armbian-2025.04-S3482-Pfbbd-H8869-V9b5f-Bb703-R448a-dirty (Nov 13 2025 - 13:20:15 +0000) Allwinner Technology

CPU:   Allwinner H616 (SUN50I)
Model: Transpeed 8K618-T
DRAM:  2 GiB
Core:  68 devices, 22 uclasses, devicetree: separate
WDT:   Not starting watchdog@30090a0
MMC:   mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1
Loading Environment from FAT... Unable to use mmc 0:1...
In:    serial@5000000
Out:   serial@5000000
Err:   serial@5000000
Net:   Could not get PHY for ethernet@5030000: addr 16
No ethernet found.

starting USB...
Bus usb@5101000: sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus
USB EHCI 1.00
Bus usb@5101400: USB OHCI 1.0
Bus usb@5200000: USB EHCI 1.00
Bus usb@5200400: USB OHCI 1.0
scanning bus usb@5101000 for devices... 1 USB Device(s) found
scanning bus usb@5101400 for devices... 1 USB Device(s) found
...

 

  • Author

 

Yes, i know, but i think this is mostly UBoot DRAM controller parameters problem. May be someone have any suggestions about it...

Edited by blackc

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.