Jump to content

Armbian for Amlogic S805 and S802/S812


masteripper

Recommended Posts

Bad news. My boxes provide no UART output. Listened while full boot to Android, to LibreELEC, recovery, SD boot try. 100% good converter, settings and pinout and absolutely no echo.

Is it end of the story? Or I could do anything more to try to boot your image? Really like to use Armbian on my M8.

Link to comment
Share on other sites

To run the image without UART. But it will take more time and tests to find a working configuration.

 

Try to run it from a USB flash drive LE from this directory. They used to run using script multi-boot (s805_autoscript). If you start at least one of the options, it will simplify the launch Armbian.

 

https://yadi.sk/d/J9pHkMo0uHcKU

Link to comment
Share on other sites

It seems that multiupload is not activated. Write down the way with Armbian on the SD card and activate the multiboot. Then the system will run from a USB flash drive. After activating multi-boot, this line needs to change.

 

bootcmd=run storeboot

Link to comment
Share on other sites

Hi, i am new here, this device MXIII-G 1000m

Have logs in putty:

 

Without dtb.img (Screen blackscreen in HDMI after logo power)

http://pastebin.com/Kq2BER3A

 

With dtb.img extract my device ... (Screen blackcreen in hdmi after logo power)

http://pastebin.com/3xEHTPQQ

 

With meson8m2_n200_2G_MIIIPlus.dtb (screen ok, but without wifi, bluetooth detected...)
http://pastebin.com/aTHZxGQB

Link to comment
Share on other sites

j0fhhh.jpg

 

33fdnjo.jpg

 

With meson8m2_n200_2G_MIIIPlus.dtb this run screen ok, but, without bluetooth, wifi, ethernet.
 

2hn3nfn.jpg

 

262sil2.jpg

 

This is Netxeon M82G V2.0 S812/2G/8G/AP6330, but pcb say M82G_V1.0_20150324.

 

Chipset ethernet Realtek RTL8211F.

 

Need more information? =)

 

Very thank you.

 

Link to comment
Share on other sites

For what would a network need to update the kernel to support new version of dtb data. But I do not have time for this. I hope that in the near future I will be able to return to this issue.

Link to comment
Share on other sites

Updated version Armbian 5.27 for s802\s812. Running a wired network. For network card you need to use the right dtb file prefix for 1000 is a Gigabit network card. Tested on Tronsmart MIII Plus.

 

https://yadi.sk/d/QCGU0PIv3G5kEa

 

Update

The dtb files MIII_Plus M8S_Plus is NOT working.

 

To use the WiFi on the Ubuntu Mate (until I have time to add support for Wi-Fi only in this way). Connect the dhd module or other suitable part of the image. On Tronsmart MIII Plus the Wifi network (after activation of the module dhd) works.

Edited by balbes150
Link to comment
Share on other sites

Updated version Armbian 5.27 for s802\s812. Running a wired network. For network card you need to use the right dtb file prefix for 1000 is a Gigabit network card. Tested on Tronsmart MIII Plus.
 
https://yadi.sk/d/QCGU0PIv3G5kEa
 
Update
The dtb files MIII_Plus M8S_Plus is NOT working.
 
To use the WiFi on the Ubuntu Mate (until I have time to add support for Wi-Fi only in this way). Connect the dhd module or other suitable part of the image. On Tronsmart MIII Plus the Wifi network (after activation of the module dhd) works.


It works on my Minix x8-h (s802) with k200b_2G dtb. Bluetooth is not working. I'll test more soon.

It's great seeing the device revived with Armbian

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk

Link to comment
Share on other sites

Wired network works ? You have a 100 MB network ? Wi-Fi did not try to include ? BT is not yet working in almost all the images for s8xxx and s9xxx. BT for me it is not the most important thing you need to spend scarce time, which is not enough. If there are users who will deal with this question and give me a solution - I will include this solution in all the images.

Link to comment
Share on other sites

Update images (20170322). Fixed "poweroff". Added all the images support WiFi. Removed from the images are not working dtb. Updated part of the packages from online repositories.


OK. Thanks! I'll give it a try soon. Is there something you would like to know or have tested on a Minix x8-h?

Verstuurd vanaf mijn ONEPLUS A3003 met Tapatalk

Link to comment
Share on other sites

If possible, check these items.

1. Work wired network

2. Work WiFi

3. The script backups dd_backup_x (when you create a compressed copy). Check recovery, no real need to do.

4. The sound quality (is or is not rattling and interference)

5. Show the output of the command "fw_printenv" and "fdisk -l"

Link to comment
Share on other sites

hi guys,

I have a Minix X8-H with a broken emmc and I'm in need of a Linux image that I can boot and run from SDcard.

can you please point me in the right direction?

I tried Armbian_5.27_S812_Ubuntu_xenial_3.10.99_server_20170322.img.xz but it doesn't seem to work, it gets stuck on u-boot after the Hardkernel banner.

EEEE I3000000032940xf100110003877500EEEE I400000004294_M8_BL1_10221D113B323EEEE I3000000032940xbbbb000126B22525

-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)

 

I think this is an S802 or similar:

[    0.000000@0] Machine: Amlogic Meson8 platform, model: AMLOGIC

[    0.000000@0] Total memory is 2048 MiB

 

I have access to UART console and I have a working U-boot for it.

I tried LibrELEC but after loading the kernel it gets stuck on unable to mount /dev/system because it seems it is trying to mount the broken flash.

 

thanks in advance

Link to comment
Share on other sites

54 minutes ago, balbes150 said:

You want to run Armbian or LE from the media ?

any of them for this matter.

my board is unusable as of right now.

so I'll take anything you'd recommend.

 

thanks!

Link to comment
Share on other sites

Hi, Balbes150, two versions 22 march and 17 march not worked cable HDMI after bootlogo Google TV.
20170309 this version work no problem HDMI.

 

Have log running ssh new version if you need. =)

Link to comment
Share on other sites

15 minutes ago, balbes150 said:

In the next few days, I'll try to get u-boot to s812.

thank you, sir!

I've tried building this one http://openlinux.amlogic.com/wiki/index.php/Arm/Buildroot/buildroot-3.10/buildroot-2015-01-20

after building u-boot (used make meson8_k200b_release_defconfig) and tried it, interestingly enough I've got the same error:

EEEE I3000000032940xf100110003877500EEEE I400000004294_M8_BL1_10221D113B323EEEE I400000004294enter usb bootA1A13697EEEE I3000000032940xf100110003877500EEEE I400000004294_M8_BL1_10221D113B323EEEE I5
-----------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (Built at 19:33:00 Dec  8 2014) *
-----------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
 

so, I'm back to square 1

Link to comment
Share on other sites

scratch that.

it seems the u-boot is fine. managed to start the board with it

EEEE I3000000032940xf100110003877500EEEE I400000004294_M8_BL1_10221D113B323EEEE I400000004294enter usb bootA1A13697EEEE I3000000032940xdd00000103974545EEEE I600000006294No boot up devic5
no sdio debug board detected
TE : 472102
BT : 19:06:30 Apr  4 2017
PMU:rn5t618
DC01 v:1100, 0x[36]: 18 -> 28
DC02 v:1150, 0x[37]: 18 -> 2c
DC03 v:1500, 0x[38]: 38 -> 48
LDO01 v:2900, 0x[4c]: 4e -> 50
LDO02 v:1800, 0x[4d]: 24 -> 24
LDO03 v:1800, 0x[4e]: 30 -> 30
LDO04 v:2850, 0x[4f]: 4e -> 4e
LDO05 v:1800, 0x[50]: 24 -> 24
LDO0a v:2700, 0x[56]: 28 -> 28
LDO0b v:900, 0x[57]: 00 -> 00

CPU clock is 1200MHz

CPU type: M8
DDR info: 2GB(auto) @ 792MHz(1T)
DDR channel: DDR 0 + DDR 1

DDR init use : 12123 us

HHH
0x0000008d
check SD_boot_type:0x1   card_type:0x1
ucl decompress...pass
0x12345678
Boot from external device
TE : 805512

System Started


U-boot(m8_k200_v1@) (Apr 04 2017 - 19:06:21)

clr h-ram
DRAM:  2 GiB
 

-- so, u-boot seems fine there.

there's still a long way to having a system up and running (with XBMC, for example) so I'm still hoping you could help.

let me know if you need any info .

cheers

Link to comment
Share on other sites

2 hours ago, balbes150 said:

In the next few days, I'll try to get u-boot to s812.

so after I replaced the bootloader on the Armbian_5.27_S812_Ubuntu_xenial_3.10.99_server_20170322.img with the one I built, I managed to boot the system with Linux.

--

Ubuntu 16.04.2 LTS vegas812 ttyS0

vegas812 login:
--

what's the user/pass?

now if I'll only manage to run an image with a desktop..

Link to comment
Share on other sites

58 minutes ago, lmirel said:

so after I replaced the bootloader on the Armbian_5.27_S812_Ubuntu_xenial_3.10.99_server_20170322.img with the one I built, I managed to boot the system with Linux.

--

Ubuntu 16.04.2 LTS vegas812 ttyS0

vegas812 login:
--

what's the user/pass?

now if I'll only manage to run an image with a desktop..

after I RTFM I managed to log in

tried to boot the xfce image with no luck.

anyway, life it is already better now ;)

Link to comment
Share on other sites

Here all supported Libreelec granted you =)

 

LibreELEC:~ # fw_printenv
baudrate=115200
bcb_cmd=bcb uboot-command;
boardname=m8_board
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
check_rebootmode=get_rebootmode; clear_rebootmode; echo reboot_mode=${reboot_mode};if test ${reboot_mode} = factory_reset; then defenv; fi;
chipname=8726m8
console=ttyS0,115200n8
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_format_index=24
display_height=1080
display_layer=osd2
display_width=1920
ethaddr= xxx
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run prepare; run storeargs; run recovery;fi; if test ${wipe_cache} = failed; then run prepare; run storeargs; run recovery;fi;
fb_addr=0x07900000
fb_height=720
fb_width=1280
firstboot=1
gatewayip=10.18.9.1
get_dt=checkhw
hdmimode=1080p
hostname=arm_m8
initargs=rootfstype=ramfs init=/init console=ttyS0,115200n8 no_console_suspend earlyprintk ramoops.mem_address=0x04e00000 ramoops.mem_size=0x100000 ramoops.record_size=0x8000 ramoops.console_size=0x4000 androidboot.selinux=permissive storage=2
initrd_high=60000000
ipaddr=10.18.9.97
loadaddr=0x12000000
loadaddr_logo=0x13000000
netmask=255.255.255.0
normalsize=400000
normalstart=1000000
outputmode=1080p
p0path=uImage
p0size=400000
p0start=1000000
p1path=android.rootfs
p1size=8000000
p1start=1400000
partnum=2
preboot=run factory_reset_poweroff_protect;if itest ${upgrade_step} == 3; then run prepare; run storeargs; run update; fi; if itest ${upgrade_step} == 1; then  defenv_reserve_env; setenv upgrade_step 2; saveenv;fi; run check_rebootmode;run prepare;run storeargs;run update_key; run switch_bootmode
preloaddtb=imgread dtb boot ${loadaddr}
prepare=logo size ${outputmode}; video open; video clear; video dev open ${outputmode};imgread res logo ${loadaddr_logo}; unpackimg ${loadaddr_logo}; logo source ${outputmode}; bmp display ${bootup_offset}; bmp scale;
reboot_mode=normal
recovery=echo enter recovery;run bcb_cmd; setenv bootargs ${bootargs} wipeinstaboot;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
store=2
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=if test ${reboot_mode} = charging; then run try_auto_burn; fi;secukey auto;secukey write keyexample 1234567890; echo Booting...; run bcb_cmd; if unifykey get usid; then  setenv bootargs ${bootargs} androidboot.serialno=${usid};fi;if unifykey get mac; then  setenv bootargs ${bootargs} mac=${mac};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
try_auto_burn=update 700 750;
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 saradc 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=0x10
video_dev=tvout
wipe_cache=successful
wipe_data=successful

 

Link to comment
Share on other sites

3 hours ago, Vitus said:

User: root

Pass: 1234

thanks

 

took a stab at running kodi

 

mirel@vegas812:~$ kodi
/usr/lib/arm-linux-gnueabihf/kodi/kodi-xrandr: Failed to get size of gamma for output default
libEGL warning: DRI2: failed to authenticate
Segmentation fault
Crash report available at /home/mirel/kodi_crashlog-20170405_050451.log
 

it reports some errors and it doesn't start

05:04:50 T:2942435936   ERROR: DBus: Error org.freedesktop.DBus.Error.InvalidArgs - No such property 'OnLowBattery'

05:04:51 T:2942435936   ERROR: CWinSystemX11::XErrorHandler: BadAtom (invalid Atom parameter), type:0, serial:33, error_code:5, request_code:18 minor_code:0
05:04:51 T:2942435936 WARNING: Visual 0x21 of the SDL window is not suitable, looking for another one...
05:04:51 T:2942435936   ERROR: Failed to determine egl config for visual info
05:04:51 T:2942435936   ERROR: Previous line repeats 236 times.
05:04:51 T:2942435936   ERROR: EGL/GLX Error: vInfo is NULL!

 

looks like it is missing some things.

I'm running Armbian_5.27_S812_Ubuntu_xenial_3.10.99_mate_20170322.img

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines