lcapriotti

I kinda recall having wiped the emmc by mistake, and had to boot from SD on which I installed you mainline u-boot. I then recovered the emmc u-boot using the one on the SD, risky but hey it worked....

I took my time, apologies, but here is the boot log via serial. boot.txt

Keep in mind I have one of the first TX3 boxes, maybe HW changed between my version and newer ones.

There you go: https://www.dropbox.com/s/zq9sjetlb49wyc2/u-boot.zip?dl=0

1) I am using meson-sm1-sei610.dtb 2) I am using the default from Armbian_20.10_Arm-64_focal_current_5.9.0.img 3) my uboot.emmc is 765,142 bytes long

What I *think* I have done is: use sm1-u-boot.bin from https://github.com/hexdump0815/u-boot-misc/releases/tag/200926-01 dd the file to an SD card and boot from it dd the file to the emmc once booted from the SD card Not 100% sure though

Note that since then I was able to have a rock solid boot from emmc, but I lost track on how I was able to achieve it... If there is anything I can provide pls let me know

On my s905x3 (Tanix TX3) I have used sm1-u-boot.bin replacing u-boot.ext on the SD card, and have consistent success in booting from SD card - something that it not the case with the original u-boot from Armbian_20.10_Arm-64_focal_current_5.9.0.img. I can access the emmc once booted from the SD card. However, the box does not boot after installing into emmc, as the emmc is not recognised.

tks! There are two possible candidates: install-aml-s905-emmc.sh and install-aml.sh, which one shall be used on our box?

this is the driver I was referring to: openvfd

I figured out a combination of bad SD cards and possibly the CD card reader that is not 100% reliable is creating the above situation, hence I started investigating the install to emmc following the instructions available here BUT the install script seems to be missing from Armbian_20.10_Arm-64_focal_current_5.9.0.img.xz, am I mistaken? this would need these drivers, I wonder if they are available in armbian, there is also another thread in the forum but nobody answered.

I messed up my emmc and after having restored it using Burn_Card_Maker_V2.0.3 with both factory images and custom images (slimbox) I have lost ability to boot from SD and USB Is it because the u-boot is broken or not the one I had before? Does an armbian image that I could use with Burn_Card_Maker exist ?

can anyone confirm a "shutdown -h now" results in a reboot instead?

out of curiosity: is there any chance to interact with the front panel LCD and use it to display something more useful than "boot"?

Tanix TX3 comes in at least two versions, the QZ mentioned just above, and a BZ version. The name on the PCB is the only way to figure out. Maybe because I pre-ordered the box, I unfortunately got an even earlier version, my PCB says CS_905X3_TX95_B4_V1.1. This variant has 100M eth. On this box I followed Hannah's first post and got all working but the eth - no surprise The excerpt from boot log is the following: [ 3.523773] meson8b-dwmac ff3f0000.ethernet: IRQ eth_wake_irq not found [ 3.528711] meson8b-dwmac ff3f0000.ethernet: IRQ eth_lpi not found [ 3.534944] meson8b-dwmac ff3f0000.ethernet: PTP uses main clock [ 3.540791] meson8b-dwmac ff3f0000.ethernet: no reset control found [ 3.548747] meson8b-dwmac ff3f0000.ethernet: User ID: 0x11, Synopsys ID: 0x37 [ 3.554075] meson8b-dwmac ff3f0000.ethernet: DWMAC1000 [ 3.559232] meson8b-dwmac ff3f0000.ethernet: DMA HW capability register supported [ 3.566646] meson8b-dwmac ff3f0000.ethernet: RX Checksum Offload Engine supported [ 3.574061] meson8b-dwmac ff3f0000.ethernet: COE Type 2 [ 3.579238] meson8b-dwmac ff3f0000.ethernet: TX Checksum insertion supported [ 3.586223] meson8b-dwmac ff3f0000.ethernet: Wake-Up On Lan supported [ 3.592664] meson8b-dwmac ff3f0000.ethernet: Normal descriptors [ 3.598473] meson8b-dwmac ff3f0000.ethernet: Ring mode enabled [ 3.604250] meson8b-dwmac ff3f0000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 13.829376] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.1:08] driver [Meson G12A Internal PHY] (irq=34) [ 13.840836] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found [ 13.840849] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW [ 13.840859] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rmii link mode As I have built-in WiFi working (very poorly implemented) and also an external WiFi USB interface working great, eth is a low priority, yet it would be nice to figure it out.