aarch64 mtk/mstar soc

[exkc]

Hi all i have digged up some into on aarch64 on mtk/mstar SoC.
Known mstar soc fmaily :
Muji <- device tree : https://github.com/opensource-hisense/SmartTV-SeriesM64/blob/master/Kernel/linaro/arch/arm64/boot/dts/muji.dts
Monet <- device tree : https://github.com/opensource-hisense/SmartTV-SeriesM64/blob/master/Kernel/linaro/arch/arm64/boot/dts/monet.dts
Mainz <- device tree :
mainz.txt
Also mtk/mstar use drectfb i found fusion module in their kernel (drectfb use fusion kernel module)

mtk/mstar uboot/kernel is quirky it require some odd kernel flag to boot

https://github.com/opensource-hisense/SmartTV-SeriesM64/ <- pre mtk it contained code for some mstar aarch64 soc
https://github.com/TCLOpenSource/mt9221/ <- It seem from the time after mtk has bought mstar (it contain code for some mtk/mstar soc (see drivers/mstar2/hal) and it had some heritage from mstar)
https://github.com/TCLOpenSource/mt9653/ <- newest kernel (a lot of heritage has been removed(drivers/mstar2 is gone))

both mtk kernel has missing some device tree for soc that released b4 mstar got bought by mtk.

[exkc]

i have a mainz board (SoC : msd6a358)

It run android 6 and here is the boot log : mainz.txt

https://wiki.postmarketos.org/wiki/KTC_msd6a358m2c1_(ktc-msd6a358m2c1)

Also it has boot/recovery partition just like typical android but mstar used standard u multi image instead of boot img.Dumping the dtb is quite easy there are a partition call dtb which just like dtbo parttion in typical android but mstar use dtb format instead of dtbo .

[exkc]

should i make pr to put those info on site.yeah i finally think about doing that lol

[exkc]

i found some guide on how to compile the mstar sdk

https://download.csdn.net/download/lxy1979/13126258 (mooney)

https://wenku.csdn.net/doc/58s1u4hnnb (muji)

https://wenku.csdn.net/doc/5w74x9u3fg (nike)

https://wenku.csdn.net/doc/qkrwrn5ar2 (maserati)

https://download.csdn.net/download/lxy1979/13126268 (napoli)

https://download.csdn.net/download/lxy1979/13126248 (monet)

https://download.csdn.net/download/lxy1979/13126266 (edison)

https://download.csdn.net/download/lxy1979/13126275 (madison)

https://download.csdn.net/download/lxy1979/13126273 (madison)

(they are locked by paywall but the preview of the guide has gave me enough info on that)
acc to those those guide it seem

MSD6A901 is edison

MSD6A648 is mooney

MSD6A638 is monet

MSD6A828 is Muji

MSD6A818 is nike

MSD6A938 is maserati

MSD6A918 is napoli

MSD628VXM/MSD628VX is madison

[exkc]

acc to the code found in https://github.com/hradec/mstar6a918/ it seem Nike edison Madison are arm32

[exkc]

ah Napoli as well

[fifteenhex]

Hi,

This is all good info. If you create pages I'll merge them. I don't think I ever got dumps from a 64bit mstar chip. In your log it looks like its running a 32bit kernel so maybe they never managed to actually get it working properly.

[exkc]

its running a 32bit kernel so maybe they never managed to actually get it working properly.

actually the kernel is 64 bit but the uimage is 32bit they packed 64 bit kernel image into a 32bit uimage.

(uimage is just file with uboot header added on top so the uimage marked the kernel as 32 bit but kernel is 64 bit)

(uh it use quirky uboot that only take uimage that packaged like that.)

pmOS on the stock kernel :

[fifteenhex]

Crazy, they really did as much as they possibly could to avoid upgrading their stuff.

[exkc]

some are device boot as 32bit
and uboot would filp the soc to 64 when booting the kernel
https://patchwork.ozlabs.org/project/uboot/patch/1480902750-839-12-git-send-email-andre.przywara@arm.com/#1528602

idk why it do that in this hacky way

i think the uboot is too old for filping 64bit in normal way (taking aarch64 uimage and filp the soc to 64bit)

[exkc]

https://documents.cdn.ifixit.com/KXHVwUgKCBW2fW4I.pdf
https://fcc.report/FCC-ID/2A3YB-YSBG1PLUS/6451340.pdf
some schematic

[exkc]

https://bbs.elecfans.com/jishu_1958058_1_1.html

i am dumping evey shit i find i will proby tidy em into a page