lmirel
-
Posts
11 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by lmirel
-
-
3 hours ago, balbes150 said:
1. If eMMC is missing\faulty\completely erased - in these cases always need u-boot on SD card (run u-boot from a USB drive is possible, but I still know of only one manufacturer, which is implemented Khadas VIM on all the other TV boxes there is only a boot loader for the SD card).
2. All I know of u-boot in update mode have the option of running the script with the default name aml_autoscript.
3. Therefore, it is sufficient to write to the SD card standard u-boot and slip him the right script aml_autoscript (using as a basis a ready skriti s905_autoscript for the desired systems.
After recording of the image Armbian scripts aml_autoscript and s805_autoscript used for their own purposes. aml_autoscript is a script activate the multi-boot. S805_autoscript the script is a startup script system from external media.
thanks! I'll take a closer look at 'aml_autoscript' upon my return.
-
6 hours ago, balbes150 said:
2. What exactly You are interested in the script ?
the regular use case for when the eMMC fails on these boards (this is the one requiring intervention) is that we end up with an empty flash, unable to boot.
the preloader is looking for boot code on SD, USB device and serial.
the SD script would have to be prepared in such a way that it sets-up the bootloader to boot from SD each of the OSs: armbian, lakka.tv and LibreELEC.
Armbian uses 'aml_autoscript' and 's805_autoscript' but I didn't observe these to be executed at all.
this is the case where we can't rely on the existing Android system to help us boot from SD (since the eMMC is broken).
-
19 hours ago, balbes150 said:
Please check out these options from u-boot using to run from the SD card.
https://yadi.sk/d/CUHySrWd3GgpqZ
I saw that You have already compiled your version, but I have a request, check these files to run. I need to make sure they work and you can include them in the Assembly of the image Armbian for s812.
thanks very much.
I hope is not urgent as I'm travelling for the next couple weeks and can't try them yet.
have you any experience with the bootloader script for AMLogic?
I used the following scripts to boot:
- armbian
setenv condev "console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0"
setenv bootargs "root=LABEL=ROOTFS rootflags=data=writeback rw ${condev} fsck.repair=yes net.ifnames=0 mac=${mac}"
setenv kernel_loadaddr "0x14000000"
setenv dtb_loadaddr "0x11800000"
setenv initrd_loadaddr "0x15000000"
setenv boot_start bootm ${kernel_loadaddr} ${initrd_loadaddr} ${dtb_loadaddr}
mmcinfo
fatload mmc 0 ${initrd_loadaddr} uInitrd
fatload mmc 0 ${kernel_loadaddr} uImage
fatload mmc 0 ${dtb_loadaddr} dtb/meson8_k200b_2G_emmc_sdhc.dtb
run boot_start
- lakka.tv and LibreELEC.tv
setenv condev "console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0"
setenv bootargs "${condev} bootfromsd"
mmcinfo
fatload mmc 0 ${loadaddr} kernel
bootm
I'm thinking these could be used to prep the script for booting from SD.
thanks again!
-
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
-
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
-
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..
-
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 -> 00CPU clock is 1200MHz
CPU type: M8
DDR info: 2GB(auto) @ 792MHz(1T)
DDR channel: DDR 0 + DDR 1DDR init use : 12123 us
HHH
0x0000008d
check SD_boot_type:0x1 card_type:0x1
ucl decompress...pass
0x12345678
Boot from external device
TE : 805512System 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
-
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
-
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!
-
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
Armbian for Amlogic S805 and S802/S812
in Amlogic CPU Boxes
Posted
I couldn't get any of the builds to boot the board.
I used the usual approach with the BootcardMaker from @mlogic.
it boots fine with the Android bootloader.img and the one I built from the @mlogic buildroot.