[S812] MIII Plus 2Gb\16Gb eMMC

Mick84 · March 1, 2017 at 12:04 AM

Akaso m8s (s812, 2GB RAM, 8 GB Flash): Installed latest Krypto version internally. Works some minutes, then freezes and has to power cycled.
Probably overheating ? Maybe also fake 2 Ghz like s905x ?

Code

akaso:~ # fw_printenv
aml_dt=m8m2_n200_2G
baudrate=115200
bootargs=init=/init console=ttyS0,115200n8 no_console_suspend storage=1 cvbsdrv=0 vdaccfg=0xa000 logo=osd1,loaded,0x15100000,720p,full hdmimode=720p cvbsmode=576cvbs androidboot.firstboot=1 hdmitx=
bootcmd=run start_autoscript; run storeboot
bootdelay=1
bootfile=boot.img
bootfromnand=0
bootfromrecovery=0
bootm_low=0x00000000
bootm_size=0x80000000
bootpath=u-boot.bin
bootsize=100000
bootstart=0
bootup_offset=0x136177d0
bootup_size=0x3f4c8
chipname=8726m8
console=ttyS0,115200n8
cvbs_drv=0
cvbsmode=576cvbs
digitaudiooutput=PCM
display_bpp=16
display_color_bg=0
display_color_fg=0xffff
display_color_format_index=16
display_height=720
display_layer=osd2
display_width=1280
ethact=Meson_Ethernet
ethaddr=00:15:18:01:81:31
fb_addr=0x15100000
fb_height=720
fb_width=1280
filesize=250
firstboot=1
gatewayip=10.18.9.1
get_dt=checkhw
has.accelerometer=false
hdmimode=720p
hostname=arm_m8
initargs=init=/init console=ttyS0,115200n8 no_console_suspend storage=1
initrd_high=60000000
ipaddr=10.18.9.97
loadaddr=0x12000000
loadaddr_logo=0x13000000
mmcargs=setenv bootargs console=${console} boardname=m8_board
netmask=255.255.255.0
normalsize=400000
normalstart=1000000
outputmode=720p
p0path=uImage
p0size=400000
p0start=1000000
p1path=android.rootfs
p1size=8000000
p1start=1400000
partnum=2
preboot=if itest ${upgrade_step} == 3; then run prepare; run storeargs; run update; fi; if itest ${upgrade_step} == 1; then  defenv; setenv upgrade_step 2; saveenv;fi; run prepare;run storeargs;get_rebootmode; clear_rebootmode; echo reboot_ mode=${reboot_mode};run update_key; run switch_bootmode
preloaddtb=imgread dtb boot ${loadaddr}
prepare=logo size ${outputmode}; video open; video clear; video dev open ${outputmode};imgread pic logo bootup ${loadaddr_logo}; bmp display ${bootup_offset}; bmp scale;
reboot_mode=charging
recovery=echo enter recovery;if mmcinfo; then if fatload mmc 0 ${loadaddr} recovery.img; then bootm;fi;fi; if usb start 0; then if fatload usb 0 ${loadaddr} recovery.img; then bootm; fi;fi;if imgread kernel recovery ${loadaddr}; then bootm;else echo no recovery in flash; fi;
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
serverip=10.18.9.113
start_autoscript=if mmcinfo; then run start_mmc_autoscript; fi; if usb start; then run start_usb_autoscript; fi
start_mmc_autoscript=if fatload mmc 0 11000000 s805_autoscript; then autoscr 11000000; fi
start_usb_autoscript=if fatload usb 0 11000000 s805_autoscript; then autoscr 11000000; fi
stderr=serial
stdin=serial
stdout=serial
store=1
storeargs=setenv bootargs ${initargs} cvbsdrv=${cvbs_drv} vdaccfg=${vdac_config} logo=osd1,loaded,${fb_addr},${outputmode},full hdmimode=${hdmimode} cvbsmode=${cvbsmode} androidboot.firstboot=${firstboot} hdmitx=${cecconfig}
storeboot=secukey auto;secukey write keyexample 1234567890; echo Booting...; if unifykey get usid; then  setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;imgread kernel boot ${loadaddr};bootm;run recovery
switch_bootmode=if test ${reboot_mode} = factory_reset; then run recovery;else if test ${reboot_mode} = update; then run update;else if test ${reboot_mode} = usb_burning; then run usb_burning;else if test ${wipe_data} = failed; then echo wipe_data=${wipe_data}; run recovery;else fi;fi;fi;fi
testaddr=0x12400000
update=run usb_burning; if mmcinfo; then if fatexist mmc 0 ${sdcburncfg}; then run sdc_burning; else if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;run recovery;fi;else run recovery;fi;
update_key=saradc open 0; if saradc get_in_range 0 0x50; then msleep 50; if sara dc get_in_range 0 0x50; then echo update by key...; run update; fi;fi
upgrade_step=0
us_delay_step=1
usb_burning=update 1000
vdac_config=0xa000
video_dev=tvout
wipe_data=success

Display More

Hi mate

If you dont mind asking, how do you generate this code. I would appreciate if you could share

Thanks

MihalacheM · March 1, 2017 at 6:05 AM

You need to SSH your box. More info in this link Accessing LibreELEC - LibreELEC. Check the first video.
[hr]

Quote from balbes150

Test version 20170228.

Still not working wifi and bluetooth on MINIX NEO X8-H PLUS. (S812H, 2GB, ANDROID 4.4)

Arnozzy · March 1, 2017 at 8:13 AM

where can I find build 20170228?

MihalacheM · March 1, 2017 at 8:59 AM

Quote from Arnozzy

where can I find build 20170228?

Here: Yandex.Disk

maxpower · March 1, 2017 at 12:36 PM

Quote from Mick84

Hi mate

If you dont mind asking, how do you generate this code. I would appreciate if you could share

Thanks

ssh into your box (enable ssh service) login: root password: libreelec then execute fw_printenv.

**balbes150** · March 1, 2017 at 2:39 PM Official Post

Test 20170301

Gato Felix · March 1, 2017 at 5:53 PM

Quote from balbes150

Test 20170301

Tested 20170301 on minix x8H (S802) and minix X8H Plus (S812)

Wifi works on S802 but signal is not optimal (but acceptable). Bluetooth works for me with an speaker.

wifi and bluetooth don't works on S812. At first it seems to works. The networks are listed and you can connect and appears a correct IP.
But when you try to access the net don't work.

I think minix x8h (s802) uses an AP6330 chip and minix x8h plus (s812) uses an Ap6335 chip. I don't know if this is useful for you...

Skripo · March 1, 2017 at 11:13 PM

Balbes, do you want me to test these also or are is the BCM4335 not included?

Thanks.

e123enitan · March 3, 2017 at 1:38 AM

@ Balbes, I just tried this image on Tronsmart S82, using the tar file, in the process of updating the file stopped, error the hardware for 802 is not compatible with 812.

Thanks

roel · March 3, 2017 at 7:24 AM

Quote from e123enitan

@ Balbes, I just tried this image on Tronsmart S82, using the tar file, in the process of updating the file stopped, error the hardware for 802 is not compatible with 812.

Thanks

You have to unpack the tar file and copy the files from the target folder to the update folder of your libreelec device. Files are kernel.img, kernel.md5, system.img and system.md5. Should work for updating without the error.

e123enitan · March 3, 2017 at 3:19 PM

Quote from roel

You have to unpack the tar file and copy the files from the target folder to the update folder of your libreelec device. Files are kernel.img, kernel.md5, system.img and system.md5. Should work for updating without the error.

Got U, I shall give it a go tonight and report back.

maxpower · March 3, 2017 at 11:08 PM

Quote from roel

You have to unpack the tar file and copy the files from the target folder to the update folder of your libreelec device. Files are kernel.img, kernel.md5, system.img and system.md5. Should work for updating without the error.

I doubt that: Update

Ozcube · March 3, 2017 at 11:19 PM

Quote from maxpower

I doubt that: Update

I also thought that it was unnecessary to extract the .tar file. All that is required is to copy the .tar file to the update folder or am I wrong?
[Edit] I just did an update by putting the .tar file into the update directory. On reboot the .tar was automatically extracted and installed.

e123enitan · March 4, 2017 at 4:52 AM

Quote from e123enitan

Got U, I shall give it a go tonight and report back.

I just unpacked the tar. inside are three folders (3rdparty, Licenses and target) Inside the target are the files that you referenced to. In addition are Change log, Readme.md and Release. So to be clear the only file that are needed are those in the target and should be to be copy into Userfolder>update of the Libreelec.

PhoenixKopf · March 4, 2017 at 11:39 AM

LibreElec 8 works good on M8S with ap6330 Lan broken because of 100mbit not 1000mbit but it's ok WLAN working good Installed on emmc

roel · March 4, 2017 at 12:12 PM

Quote from e123enitan

I just unpacked the tar. inside are three folders (3rdparty, Licenses and target) Inside the target are the files that you referenced to. In addition are Change log, Readme.md and Release. So to be clear the only file that are needed are those in the target and should be to be copy into Userfolder>update of the Libreelec.

Indeed only the kernel and system files should be copied to the update folder of libreelec.

Arcee · March 5, 2017 at 7:44 AM

Quote from balbes150

Test 20170301

I've just tried installing this firmware onto my Minix X8-H Plus and unfortunately, Wi-Fi is still not working and selecting 4K resolution gives me only the top quarter of the screen.

The requested output from my Minix is as follows:

First, the output of execute fw_printenv is:

Code

[b]LibreELEC-MinixX8HP:[/b][b]~ [/b]# fw_printenvWarning: Bad CRC, using default environmentbootargs=console=ttyAMA0,115200n8 root=/dev/mmcblk0p9 rwbootcmd=run distro_bootcmdbootdelay=2baudrate=115200arch=armcpu=armv8board=hikeyboard_name=hikeyvendor=hisiliconsoc=hi6220kernel_name=Imagekernel_addr_r=0x00080000fdt_name=hi6220-hikey.dtbfdt_addr_r=0x02000000fdt_high=0xffffffffffffffffinitrd_high=0xffffffffffffffffmmc_boot=if mmc dev ${devnum}; then setenv devtype mmc; run scan_dev_for_boot_part; fiboot_net_usb_start=usb startusb_boot=usb start; if usb dev ${devnum}; then setenv devtype usb; run scan_dev_for_boot_part; fiboot_prefixes=/ /boot/boot_scripts=boot.scr.uimg boot.scrboot_script_dhcp=boot.scr.uimgboot_targets=usb0 mmc1 dhcp boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}extlinux/extlinux.confscan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}extlinux/extlinux.conf; then echo Found ${prefix}extlinux/extlinux.conf; run boot_extlinux; echo SCRIPT FAILED: continuing...; fiboot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source ${scriptaddr}scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${script}; then echo Found U-Boot script ${prefix}${script}; run boot_a_script; echo SCRIPT FAILED: continuing...; fi; donescan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_prefixes}; do run scan_dev_for_extlinux; run scan_dev_for_scripts; donescan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setenv devplist 1; for distro_bootpart in ${devplist}; do if fstype ${devtype} ${devnum}:${distro_bootpart} bootfstype; then run scan_dev_for_boot; fi; donebootcmd_usb0=setenv devnum 0; run usb_bootbootcmd_mmc1=setenv devnum 1; run mmc_bootbootcmd_dhcp=run boot_net_usb_start; if dhcp ${scriptaddr} ${boot_script_dhcp}; then source ${scriptaddr}; fidistro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done

Then, the output of the udevadm info /sys/bus/sdio/devices/sdio* is:

Code

[b]LibreELEC-MinixX8HP:[/b][b]~ [/b]# udevadm info /sys/bus/sdio/devices/sdio*P: /devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1E: DEVPATH=/devices/platform/aml_sdio.0/mmc_host/sdio/sdio:0001/sdio:0001:1E: DRIVER=bcmsdh_sdmmcE: MODALIAS=sdio:c00v02D0d4335E: SDIO_CLASS=00E: SDIO_ID=02D0:4335E: SUBSYSTEM=sdio

I hope it helps to get things working in a next test build. Thanks for the efforts so far!

hscotty55 · March 5, 2017 at 9:14 PM

LibreELEC-S812.Minix.arm-8.0.1.img.gz seems to be working good on Tronsmart MXIII plus 2G/16G on sd card. LAN and WIFI all work. I will try to install on internal and check.

Thanks again for your work!