Ian Pat

Amlogic released a new kernel source (S905X) on 15.05.2017, pushed it to github for those interested, also attached the readme for this. Linux_BSP_Kernel4.9_Buildroot_OpenLinux_Release_Notes_V20170515.pdf

i managed to compile 4.9 from amlogic and i have all the stuff i need for using this a95x box as a tvheadend headless server for my dvb-c usb tuner (astrometa, mn88473 only supported for digital cable in kernels > 4.7). working usb, sd, emmc, ethernet (those were the only i tested/needed, others might or might not work, worked from uart until network was configured), now lets add a minimal linux userspace to that kernel and forget about it. that's it! bye bye Arm world dmesg.log

Internal eMMC working?

few questions regarding A95X on my quest to a Linux from scratch Is it possible to modify the partitions layout? I would like to keep a minimum number of them, what are the mandatory ones? I see cache and others i would like to get rid off and get the space. I decompiled the dtb for my device and found the list, if i modify that is it enough or is the partition layout stored someplace else (U-Boot for eg.)? How safe is to play around with the eMMC from a bricking perspective? Can the device be rescued with a defective partition layout or none at all? If i do for eg a dd if=/dev/zero of=/dev/mmcblk0 completely zeroing the eMMC can i still un-brick? This would mean U-Boot would be missing completely and everything else, but what will happen at start time? Will he still try to boot from an alternate storage (SD-Card or USB) or just simply halt and that's all. What are the scenarios under which one needs to to that ugly fix of shorting the pins on the eMMC in order to unbrick? Darn, i hate this ARM stuff (or ARM hates me)... x86, x86 where are thee?

Yes, the message was the same line, only difference was in the LOOP number. Meanwhile I managed to un-brick it with the USB Burning tool/male to male USB cable/original firmware (once plugged in it detected the device and i was able eventually to flash the original firmware). Was wondering... the fallback of shorting the pins of the eMMC makes sense, enforcing the boot to fallback to SD/USB and since i have the "feeling" i will soon need it... , how can I identify what pins to short? Everywhere (and not so many places available) i read about this, there was only the generic "short pins" advice... but what pins? I know it will be device-specific, but in my case the eMMC (Samsung KLMAG2WEPD-B031) is soldered with ball pins, meaning none are visible, so what to short? An electrical diagram/schematic would bring light to this or how? Congrats on your work, great stuff... maybe you should give me the 1-2-3 steps on how to make/install a custom linux (i want to make one from scratch, with minimal overhead) this way i won't brick it anyomore!

I want to install a very light headless linux on my A95X (2G/16G), images found here are fine (great work btw!), but i wish i had more control over what my installation will be. Any advice on: - steps for making my own image? (was thinking on simple kernel + initrd that already has the tools i need, self-contained) - what should i compile and from where for my specific device? - how can it be deployed? Thanks!

So, i managed to .... my box A95X, S905X, 2GB/16GB, I wrongly flashed to the internal the sd-card variant u-boot bin from the original firmware, on the serial console all i see is looping this message "EMMC:0;VEAD:0;CHK:AA;SD:800;USB:8;LOOP:7" Anyone can advice on what do to next (beside the obvious "buy another one") ? Thank you.