Posts by roel

roel · [S812] MIII Plus 2Gb\16Gb eMMC roel March 19, 2017 at 11:14 AM

Thanks a lot Balbes, I really appreciate your work. As your LibreElec runs fine on my Eny M8S, I don't really need the testing, but I definitely will try you armbian version.

roel · [S812] MIII Plus 2Gb\16Gb eMMC roel March 6, 2017 at 8:23 PM

My recovery firmware comes from the ENY site (search for EM8S): EM8-M8C and M8S Amlgoic S812 Support Firmware-Android TV Box , Android TV Sitck,Google TV Box, Google TV Stick, China Manufacturer Supplier

This is the content of my remote.conf (copy and paste it in a text file and rename it to remote.conf):

# ZAP-A10 NEC remote
factory_code = 0xfe010001
work_mode = 0
repeat_enable = 1
release_delay = 121
debug_enable = 1
reg_control = 0xfbe40

key_begin
0x4e 2 ;NUM_1
0x0d 3 ;NUM_2
0x0c 4 ;NUM_3
0x4a 5 ;NUM_4
0x09 6 ;NUM_5
0x08 7 ;NUM_6
0x46 8 ;NUM_7
0x05 9 ;NUM_8
0x04 10 ;NUM_9
0x01 11 ;NUM_0
0x42 111 ;DEL
0x51 105 ;LEFT
0x16 103 ;UP
0x50 106 ;RIGHT
0x1a 108 ;DOWN
0x13 28 ;OK
0x10 74 ;VOL-
0x41 66 ;MUTE
0x11 172 ;HOME
0x4c 46 ;MENU
0x18 78 ;VOL+
0x19 14 ;EXIT
0x40 116 ;POWER

0x5a 119
0x59 122
0x52 128
0x58 123
0x54 120
0x55 121
0x45 130
0x49 134
0x0a 133
0x48 138
0x4d 70
0x0e 136
0x0f 135
0x43 132
0x03 127
0x06 139
0x44 140
0x00 63
key_end

roel · [S812] MIII Plus 2Gb\16Gb eMMC roel March 6, 2017 at 9:49 AM

Quote from wowwoo

My M8S seems ENY's M8S 2GB/8GB. I try Libreelec 8.0 I could install and works. But remote couldn't work only I can use for power off.
And problem with reboot, I had to re plug always. I think it's dtb problem where can I found my device tree?

6330 ap+2GB/8GB+10/100 Fastethernet version

Thank you so much your great job! balbes150

I'm running Balbes latest lan1000 version on my ENY M8S just fine. No problems with the remote or power on/off. I will post my remote.conf this evening.

roel · [S812] MIII Plus 2Gb\16Gb 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.

roel · S802/S812-Libreelec images for 7/8/9 roel March 3, 2017 at 11:06 AM

Probably he tried it with the aml_autoscript so now it is booting from SD as it sees a kernel.img. Try it with copying the unextracted zip to the sd-card and boot the device with the toothpick method with the SD-card in the SD slot.
BTW, Did you login as root through ssh

roel · [S812] MIII Plus 2Gb\16Gb eMMC 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.

roel · Dual booting possible from SD or nand roel February 27, 2017 at 11:07 AM

Hello,

a few years ago, always-innovating had the option to dual boot on their touchbook. I wonder if it could also be done, for example 2 different versions of LibreElec or Lakka and LibreElec or Ubuntu and LibreElec. Maybe it's possible to do it on a SD-card and with a s805_autoscript?

Here is the link to sources from always-innovating:
git.alwaysinnovating.com Git - ai.tools/tree - ai-launcher/

roel · [S812] MIII Plus 2Gb\16Gb eMMC roel February 24, 2017 at 11:16 AM

Quote from t.michele

Burn the image on a usb stick and boot from usb.

roel · img for booting from SD roel February 22, 2017 at 8:22 PM

Thanks for that, I found the platform_ini on your github page. I will recompile with these settings.

-> Where do you learn these things?

roel · img for booting from SD roel February 22, 2017 at 7:41 PM

This is the content of mu s805_autoscript:if test ${bootfromrecovery} = 1; then setenv bootfromrecovery 0; saveenv; run update; fi;
if test ${bootfromnand} = 1; then setenv bootfromnand 0; saveenv; run storeboot; fi;
setenv bootrootfs " boot=LABEL=LIBREELEC disk=LABEL=LIBREELEC_DISK BOOT_IMAGE=kernel.img "
setenv cecconfig cecf
setenv bootargs ${bootrootfs} ${bootargs}
setenv le_usb "if fatload usb 0 ${loadaddr} kernel.img; then bootm ${loadaddr}; fi;"
setenv le_sd "if fatload mmc 0 ${loadaddr} kernel.img; then bootm ${loadaddr}; fi;"
run le_usb
run le_sd

compiled with:
mkimage -C none -A arm -T script -d s805_autoscript.txt s805_autoscript

This is the output from 'cat s805_autoscript':

'V��2X��"��E�if test ${bootfromrecovery} = 1; then setenv bootfromrecovery 0; saveenv; run update; fi;
if test ${bootfromnand} = 1; then setenv bootfromnand 0; saveenv; run storeboot; fi;
setenv bootrootfs " boot=LABEL=LIBREELEC disk=LABEL=LIBREELEC_DISK BOOT_IMAGE=kernel.img "
setenv cecconfig cecf
setenv bootargs ${bootrootfs} ${bootargs}
setenv le_usb "if fatload usb 0 ${loadaddr} kernel.img; then bootm ${loadaddr}; fi;"
setenv le_sd "if fatload mmc 0 ${loadaddr} kernel.img; then bootm ${loadaddr}; fi;"
run le_usb
run le_sd

roel · Leelbox M9S with s812 chip help needed roel February 22, 2017 at 4:00 PM

I should start trying the sd-card version from Balbes150. You can't do anything wrong with that version. Just check if you can enable multiboot. Read through the thread for all the information: thread-1506.html

roel · img for booting from SD roel February 21, 2017 at 1:12 PM

I use the LE8 sources from Demetris and used your s805_autoscript, replacing the LABEL's to LIBREELEC and LIBREELEC_DISK. I use the mkimage command as mentioned on your github page.
I'm not at home now, I can specify this evening.

roel · img for booting from SD roel February 21, 2017 at 11:05 AM

Balbes,

I tried different sd-card readers, different sd-cards and different ways, burning with dd, burning with etcher, etc.

The strange thing is that your builds work on the same sd-cards with the same readers and the same burning tools. I even burned your image to sd, booted from it and upgraded it with my KERNEL and SYSTEM files. result -> 2nd partition is corrupted. Regarding me there is some setting that is wrong, at the other side its strange it doesn't happen with the usb drive.

I'm checking my scripts and patches vs yours to see if there is something different that can explain it.

roel · img for booting from SD roel February 20, 2017 at 9:36 PM

Seems it just the same image, due to some reason it works with a usb stick and not with a SD-card. I tried different SD-cards with all the same result. Somebody an idea why I get a filesystem corruption error on a SD-card and with the same image on a usb stick I don't have the error and the device boots fine.

roel · S802/S812-Libreelec images for 7/8/9 roel February 20, 2017 at 9:22 PM

Indeed, for some stupid reason it boots from usb but not from SD-card. Ona SD-card you get an error of filesystem corruption. What could be the reason of this.
By the way, I didn't need the recovery way (didn't work on a M8S), it works with a s805_autoscript.

So Demetris just to let you know, I booted your latest lakka build for the M8 on my M8S on a USB stick with the s805_autoscript in attachement (unzip first). It's the s805_autoscript from Balbes150 with the BOOT changed to LAKKA an DISK changed to LAKKA_DISK

roel · [S812] MIII Plus 2Gb\16Gb eMMC roel February 20, 2017 at 9:01 PM

Balbes,

the DVD works OK with your 'standard kernel'. I could pair bluetooth devices also, that's OK to.

I saw on your github account you made a branch for the Khadas Vim is it still WIP or can it be compiled?

roel · S802/S812-Libreelec images for 7/8/9 roel February 20, 2017 at 8:54 PM

I'm getting a file system corrupted also on my m8s when trying to boot from SD-card. I don't know what you mean with booting into recovery and then reboot from usb. Did you burn the image to usb or copy the img file to usb. In the last case, I think you already installed it on your internal nand.
I'm compiling the sources now myself with the S805_autoscript build in and the dtb file for my box, see if it works then.

roel · img for booting from SD roel February 20, 2017 at 11:11 AM

I have a question about amlogic images for booting from SD. Is the image different then those to flash your firmware.

I tried to boot a regular image (for flashing) from SD, so not the sd-images from Kszaq or Balbes150. I get the kernel booting, but then it complaints about the the fact the 2nd partition is corrupted and it needs to do a chkfs, what doesn't work as the filesystem is read only. I tried with different sd cards even a new one and it's all the same. My filesystem is fat16 for the BOOT partition and ext4 for the DISK partition. If I do the md5sum check, the md5sum is correct.

I checked Balbes sources on github and don't see any differences in the mkimage script, or it should be another script that I don't know. I build the sources using 'make amlpkg', or should I use 'make image'? According me it shouldn't be different or does it?

My s805_autoscript works as if I leave the disk=LABEL=DISK away, the kernel boots and then complaints about not finding the 2nd partition. With the disk=LABEL=DISK, it does find the 2nd partition (mmvblk0p2) and complaints about the fact the filesystem is corrupted.

The only thing I assume can be the problem is the fact I copy the s805_autoscript to the sd-card after burning the image to it.