Official list of Amlogic reference boards

[soldiaz]

Is it possible to build dtb/dts with DDR3/4 and LPDDR 3/4 support?

[ClarkKent]

Guest ,et al, Can I get a Reference board # for beelinks. mini2: 905x3 ??
~Thanks!

It's not in the build.prop files, but the dtb calls it an "ac213".

[ClarkKent]

Guest Thanks! I Noticed that too.. guess that's why I couldn't find ANY lead on the query.

[PrinceOfAbyss]

Hello guys. I have a box like this: https://sites.google.com/view/droid-...e-tv-australia

I read the 1st post of this topic, and the ro.product.board in my build.prop isn't mentioned at all. More specifically part of the build.prop is the following:

ro.build.id=NMF26Q
ro.build.display.id=NMF26Q.1.3.0-DTV.0411
ro.build.version.incremental=1.3.0-DTV.0411
ro.build.version.sdk=25
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.1.1
ro.build.version.security_patch=2019-03-01
ro.build.version.base_os=
ro.build.date=Thu Apr 11 16:20:12 CST 2019
ro.build.date.utc=1554970812
ro.build.type=user
ro.build.user=build
ro.build.host=ubuntu-68-82
ro.build.tags=release-keys
ro.build.flavor=uiw4030vha-user
ro.product.model=VODAFONE
ro.product.brand=Vodafone
ro.product.name=uiw4030vha
ro.product.device=uiw4030vha
ro.product.board=pearl
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Technicolor
ro.product.locale=en-US
ro.wifi.channels=11
ro.board.platform=gxl

The box is acting very strangely:

• Connected it with a Type-A to Type-A USB cable to my computer
• Enabled Developer options
• Enabled USB debugging
• Disabled the USB Host mode (so that the USB port wouldn't act as a port for reading USB sitcks, but rather as a port to connect the box to another host - my computer in this case)
• Ran "adb reboot bootloader" command
• The box powered off, then powered on again and stayed in a screen showing the company's logo. During that time, it didn't accept any commands from the remote control, and the device under Device manager disappeared
• After unplugging and replugging the power cord, the box restarted normally
• This time I ran "adb reboot recovery" and indeed the box rebooted into the recovery screen
• There it showed the usual options, like any other Android device (Load from EXT, Load from ADB, Mount /system, etc), and there was the option to Reboot to bootloader. So I chose that option hoping it would work from that menu, but again the box hang at the company's logo screen

What do you gurus think of the above? Is it so locked up? Am I missing something obvious? Or what else? Any help would be very much appreciated.