Official list of Amlogic reference boards

[Guest]

When determining whether an Amlogic custom ROM is compatible with a particular model, the most important characteristic is the reference board. This is recorded in the build.prop as the "ro.product.board" property, and it usually takes the form of a string like "p212", "p230", or "q200" (which correspond to the S905X, S905D and S912 chipsets, respectively). This post lists the features and peripherals for these boards according to Amlogic, and it's my hope that it will become more complete as folks contribute information on their devices. (The original source was from an Amlogic document here.)


u221:

• Amlogic S922X CPU
• 4GB DDR4
• HDMI out x 1, MIPI-CSI/DSI
• TF Card x 1
• Ethernet with internal phy x 1
• MIMO 2T2R WiFi / BT5.0
• SPDIF x 1
• USB 3.0 x 1
• USB OTG x 1
• EMMC x 1

u211:

• Amlogic S905X2 CPU
• 4GB DDR4
• HDMI out x 1
• TF Card x 1
• Ethernet with internal phy x 1
• MIMO 2T2R WiFi / BT5.0
• SPDIF x 1
• USB 3.0 x 1
• USB OTG x 1
• EMMC x 1

q201:

• Amlogic S912 CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet 100M x 1, 1000M x 1
• SDIO WiFi/BT (AP6255) x 1
• SPDIF x 1
• USB hub x 2
• USB OTG x 1
• EMMC x 1

q200:

• Amlogic S912 CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet 100M x 1, 1000M x 1
• SDIO WiFi/BT (AP6356S) x 1
• SPDIF x 1
• USB hub x 2
• USB OTG x 1
• EMMC x 1

p281:

• Amlogic S905W CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet with internal phy x 1
• SDIO WiFi/BT (RTL8189ETV) x 1
• SPDIF x 1
• USB hub x 2
• USB OTG x 1
• EMMC x 1

p230:

• Amlogic S905D CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet 100M x 1, 1000M x 1
• SDIO WiFi/BT (AP6356S) x 1
• SPDIF x 1
• USB hub x 2
• USB OTG x 1
• EMMC x 1
• Video TS & DVP in, RGB out

p212:

• Amlogic S905X CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet with internal phy x 1
• SDIO WiFi/BT (RTL8189ETV) x 1
• SPDIF x 1
• USB hub x 2
• EMMC x 1

p201:

• Amlogic S905 CPU
• 1GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• SDIO WiFi/BT (brcm 40183) x 1
• USB hub x 1
• USB OTG x 1
• SPI & NAND x 1

p200:

• Amlogic S905 CPU
• 1GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• SDIO WiFi/BT (AP6354) x 1
• ADC key x 1
• YPbPr out x 1
• SPDIF(coaxial) x 1
• USB hub x 1
• USB OTG x 1

n200:

• Amlogic S812 CPU
• 2GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• USB WiFi/BT (AP6234) x 1
• SPDIF x 1
• CVBS out x 1
• USB hub x 1
• USB OTG x 1
• VGA x 1
• EMMC x 1

m201:

• Amlogic S805 CPU
• 1GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• USB WiFi/BT (AP6210) x 1
• USB hub x 2
• EMMC x 1

m200:

• Amlogic S805 CPU
• 1GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• USB WiFi/BT (AP6210) x 1
• SPDIF x 1
• USB hub x 2
• VGA x 1
• EMMC x 1

k200_B:

• Amlogic S802 CPU
• 1GB DDR3
• HDMI out x 1
• TF Card x 1
• Ethernet x 1
• USB WiFi/BT (8188eu) x 1
• SPDIF x 1
• CVBS out x 1
• USB hub x 2
• USB OTG x 1
• SPI & EMMC x 1

There are other permutations that have popped up on our radar, such as the q201_6377 (which does not always have the Qualcomm QCA9377 wireless chipset) and the p200_2G (second generation S905?), and m201_N (anyone have a guess what the N stands for?).

Also, Nougat releases have spawned the q20x and p21x, which are based on the q201 and p212, respectively. These reference board designations only seem to be used by VideoStrong, so I'm not entirely sure they're new hardware.

Finally, as a challenge: Who can suggest the quickest way to determine what reference board your model of Amlogic TV box has?

[calc]

One way if you have the aml_upgrade_package.img for your device is to unpack it and look at the device tree. It doesn't appear to be in the Android build.prop at least on my box.

http://freaktab.com/forum/tv-player-...ge-img-extract

If you don't have the image file then you can extract the device tree from the boot.img off the box itself.

To convert the device tree from blob to source text run the following:

dtc -O dts -o meson1.dts -I dtb meson1.dtb

My device for example shows the following:

model = "Amlogic";
compatible = "amlogic, Gxm";
amlogic-dt-id = "gxm_q200_2g";

[Guest]

Yes, the device tree from the factory firmware is probably the most reliable way to identify hardware.

If you don't have the OEM burn package, you can dump the boot partition using "dd if=/dev/block/boot of=boot.img" and then extract the bootheader (bootimg.cfg), kernel (zImage), RAMdisk (initrd.img), and dtb (stage2.img) using "abootimg -x boot.img".

Note that on Amlogic devices, the stage2.img usually has two copies of the dtb with a 0x800 header that has to be stripped before you can convert it to a dts with dtc. Look for the "D00DFEED" hex sequence, which marks the beginning.

[calc]

On my S912 there is only one copy of the dtb in stage2.img, it starts with D00DFEED, and dtc (v1.4.0) has no trouble converting it to text.

D00DFEED appears to mark the beginning of a dtb file in general, when converting dts back to dtb it wrote that at the beginning of the file. I guess if you see that twice in the file you will know it has two copies.

[ajiratech]

Does anyone know how to find source code for these reference boards ? I'm specifically looking for p200 and p201, but other boards will also work.

I'd like to build a custom linux firmware to run on it for a project of mine.

Thanks

[Guest]

Well, there are instructions on how to get the Amlogic SDK 7.1 here, but what we've discovered is that they won't grant access to anyone but the major OEMs. I've even offered to sign their NDA, but after that they still went dark on me.

[ajiratech]

Guest anz.

Thank you! I appreciate your response, I guess I should start looking for alternatives.

Would you know any good document to get Mali GPU to accelerate Video 1080p atleast and best case 4K? I'm not interested in 3D.

Thanks

Sorry, I don't have any expertise in that area.

[ajiratech]

Guest Thanks. No worries. I'll spend some time on this now.

[gary9872]

Trying to get the device tree but boot.img doesn't seem to contain it (stage2.img) This is for a 905W p281 board.

Did I do something wrong?


Android Boot Image Info:

* file name = boot.img

* image size = 33554432 bytes (32.00 MB)
page size = 2048 bytes

* Boot Name = ""

* kernel size = 7108500 bytes (6.78 MB)
ramdisk size = 1314728 bytes (1.25 MB)

* load addresses:
kernel: 0x01080000
ramdisk: 0x01000000
tags: 0x00000100

* cmdline = buildvariant=userdebug

* id = 0x6ada9134 0x52338adf 0x2fc3d2af 0xa81a6671 0x91a96e97 0x00000000 0x00000000 0x00000000

On Nougat builds the device trees are in the dtb.img (_aml_dtb.PARTITION). If there are multiple, you can unpack them with dtbSplit and repack with dtbTool. (https://github.com/Wilhansen/aml-dtbtools)

[shanx_verma]

Hi, I am a seasoned tweaker in case of android phones, but this smart Tv and TV Boxes is a completely new playing field, so kindly please, if I don't provide enough information, let me know how I can make it available you you. I have a SmartTV from the Kodak Brand, with the model number 32HDXSMART.
It has a p383 board as per CPU-Z (I suppose this is reference board, like your thread says) and I have been able to gather this info so far (from CPU-Z + DVDAndroid Xposed Installer + build.prop)
.
1. As per CPU-Z -
.
RAM - 1GB
ROM - 8GB
Manufacturer- amlogic
CPU Architecture- aarch64
Kernel Version - 3.14.29 (20170926)
BuildID - CV950H-A42_LSC320AN09_V20170926
Screen Size - 13.77 inches (although the smart TV is 32 inches)
Architecture Details -
4x ARM [email protected] GHz
Revision-r0p4
Clock Speed - 100MHz - 1.51 GHz
GPU Vendor-ARM
GPU Renderer - Mali-450 MP

.

2. As per Xposed Installer by DVDAndroid -
( https://forum.xda-developers.com/xpo...aller-t3137758 )
.
Lolipop 5.1.1 (API-22)
Manufacturer - Amlogic
Brand - Android
Model (and ROM) - AOSP (though its heavily skinned and modified)
Board - P383
CPU - AArch64 Processor rev 4 (aarch64) armeabi-v7a (arm)
.
.
3. As per Build.prop -
.
(So I scoured all possible and viewable folders with Amaze File Manager (this TV is surely very weirdly rooted, as enabling Root Access Mode in Amaze, I couldn't access the root path / However, in normal mode it could.) ).
.
So after all that searching, I found various files with the probability of helping me identify my SoC (but bad luck, Im unable to make much out of it.) . Im attaching those files here (was unable to upload directly, so zipped it together, plz rename extension to 'zip' to open it) in the hopes that someone more experienced will be able to see what I couldn't and probably point me out some general directions on how to proceed with tweaking...
.
Again, let me know if and what, further information is needed.
Please help!!

[soldiaz]

which ref board is u213? I know u211 though

[soldiaz]

wrong thread

[salehdeh76]

Anyone knows what is the difference between u212 and u211?

I know both should be S905X2 but where can I find more info?

[blust0ne]

I have a H96Max x2 with s905x2, android 9.0 and 4G LPDDR3 ram.

It seems to be incompatible with u211 device firmwares (maybe DDR4).

u-boot boot log says:

edwin--> select loc_name = g12a_u212_4g
edwin--> ddr_mode = <NULL>
Multi dtb tool version: v2 .
Support 4 dtbs.
aml_dt soc: g12a platform: u212 variant: 4g
dtb 0 soc: g12a plat: u212 vari: 1g
dtb 1 soc: g12a plat: u212 vari: 2g
dtb 2 soc: g12a plat: u212 vari: 4g
dtb 3 soc: sm1 plat: ac213 vari: 2g
Find match dtb: 2

AIDA64 says:

the board is amlogic franklin.

[Digidog1]

Guest

Finally, as a challenge: Who can suggest the quickest way to determine what reference board your model of Amlogic TV box has?

I installed a terminal while running android and on Nougat at least this location works just fine.

cat /proc/device-tree/amlogic-dt-id

Which in my case on a T95 S1 2/16 box returned gxl_p212_2g for the device tree used. Incidentally the terminal login was p282 lol I also confirmed it to be a p282 board with CPUZ i believe it was.