Should I flash latest Android Pie and try on top of it?
As far as I noticed, uboot is being updated during the installation to emmc.
What was the result, USB devices work or not ?
No
Usb devices do not work. Any of them. Pendrive blinked and silence. Same for the UZB. Keyboard didnāt responded with leds, no keypress reaction
This is the result of running Armbian from a USB stick on VIM1. If you do not work, then the problem with the hardware on your instance.
You use the same dtb?
File uEnv.ini
dtb_name=/dtb/amlogic/meson-gxl-s905x-khadas-vim.dtb
Hi,
I have a problem with ethernet on Vim3 Pro - Armbian Linux aml 5.3.0-aml-g12 #5.98 SMP on eMMC.
No link like below
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: ug
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: no
ifup/ifdown nothing help - I can see connection on the switch (led) - port,cable checked ā¦
[ 1.952138] meson8b-dwmac ff3f0000.ethernet: no reset control found
[ 1.958703] meson8b-dwmac ff3f0000.ethernet: User ID: 0x11, Synopsys ID: 0x37
[ 1.965417] meson8b-dwmac ff3f0000.ethernet: DWMAC1000
[ 1.970585] meson8b-dwmac ff3f0000.ethernet: DMA HW capability register supported
[ 1.978003] meson8b-dwmac ff3f0000.ethernet: RX Checksum Offload Engine supported
[ 1.985420] meson8b-dwmac ff3f0000.ethernet: COE Type 2
[ 1.990592] meson8b-dwmac ff3f0000.ethernet: TX Checksum insertion supported
[ 1.997579] meson8b-dwmac ff3f0000.ethernet: Wake-Up On Lan supported
[ 2.003977] meson8b-dwmac ff3f0000.ethernet: Normal descriptors
[ 2.009829] meson8b-dwmac ff3f0000.ethernet: Ring mode enabled
[ 2.015612] meson8b-dwmac ff3f0000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[ 5.084877] dm9601 1-1.2:1.0 eth1: register ādm9601ā at usb-xhci-hcd.3.auto-1.2, Davicom DM96xx USB 10/100 Ethernet, 00:e0:13:00:32:a3
[ 5.380111] meson8b-dwmac ff3f0000.ethernet eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet]
[ 5.380118] meson8b-dwmac ff3f0000.ethernet eth0: phy: setting supported 00,00000000,000062ef advertising 00,00000000,000062ef
[ 5.398244] meson8b-dwmac ff3f0000.ethernet eth0: No Safety Features support found
[ 5.398254] meson8b-dwmac ff3f0000.ethernet eth0: PTP not supported by HW
[ 5.398261] meson8b-dwmac ff3f0000.ethernet eth0: configuring for phy/rgmii link mode
[ 5.398269] meson8b-dwmac ff3f0000.ethernet eth0: phylink_mac_config: mode=phy/rgmii/Unknown/Unknown adv=00,00000000,000062ef pause=10 link=0 an=1
[ 5.400048] meson8b-dwmac ff3f0000.ethernet eth0: phy link down rgmii/Unknown/Unknown
Android working OK I have no problem (same port , same cable) ā¦ only with Armbian,Libreelec ā¦
Any help would be appreciated.
Show the contents of the file (uEnv.ini)
Hi,
uEnv.ini
dtb_name=/dtb/amlogic/meson-g12b-a311d-khadas-vim3.dtb
bootargs=root=LABEL=ROOT_EMMC rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
extlinux/extlinux.conf
LABEL Armbian
LINUX /zImage
INITRD /uInitrd
FDT /dtb/amlogic/meson-g12b-a311d-khadas-vim3.dtb
APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
Check the Mac address bindings on the router. Check the WOL settings or whatever else you changed. Remove the USB network card. I have a wired network normally works on two VIM3 (s922x and a311d) in all images of Armbian and Libreelec.
im trying to install on vim3 (Android Pie Latest) using above procedure but its always grey screen (no errors or anything) when i enter into boot mode.
dtb in uEnv and extlinux is : /dtb/amlogic/meson-g12b-a311d-khadas-vim3.dtb
Using 5.98_20191025 Ubuntu Disco
I didnāt change anything. On Libreelec with 5.3 kernel same story link is down ā¦ no connection at all.
With kernel 5.3 I have 02:00:00:1b:12:01 mac after start ā¦ but with 4.9.190 c8:63:14:70:45:e0.
seems like mac parameters from āKernel command lineā is ignored ā¦"
Tried to play in cli with add correct mac , enable wol , ip link up ā¦and sometimes works but after restart again no link.
With Ubuntu started from SD kernel 4.9.190 all working ok ā¦ link is up and working.
Hi, my Wetek Play 2 experience. Iāve instaled Ubuntu image first (last one, disco) and it worked nice, samba share on lan stable 32+ MiB/s transfer. Then I decide to check Debian, (Iāve never used Debian, using Manjaro normally) and in Armbian configuration app Iāve started some script which actually copied everything on eMMC. O.K. Removed sd card to check if it boot from EMMC my device ended in loop. Used usb/rs232 serial comm to check whatās going on and : LOOP EMMC 0 USB 0 and something like that endlessly repeating. The real problem is that now I canāt break boot with CTRL +C to reinstall Android recovery. So, no display, no recoveryā¦
Anyone with similar experience?
Not really , maybe the image during download got corrupt, can you try entering bootloader mode by pressing just Enter Key? or try burning the official images
Thanx for quick response. Usb burning tool is no go for Wetek play 2. Like Iāve metioned no display. The only way I can monitor boot is through putty with serial connection. And the only way to interrupt the boot with serial is ctrl+c for my Wetek. So Iām helpless now. So maybe somebody else has knowledge how to break boot loop. Wetek is just another s905W device. And, yes, maybe bad download, bad format on sd card or else.
;LOOP:9;EMMC:0;READ:0;CHK:17A;SD:800;USB:8;LOOP:A;EMMC:0;READ:0;CHK:17A;SD:800;USB:8; is what shows up via putty and rs232. if sounds familiar to anyone. And number after LOOP is increasing.
Just to report back. Iām writing this from Armbian.
The story: Iāve bricked my Wetek play 2. Despite the recommendation not to use Usb burning tool on Wetek Iāve succeed to back android on device. If anyone has bricked WP 2 use the youtube, search for Recovery Wetek Play 2 and youāll find solution.
So, happy again, Iām asking if somebody knows exact way to flash Armbian on eMMC, please, give me a guide. Iāve read the thread several times but itās confusing for newbie like me.
https://test.libreelec.tv/LibreELEC-AMLGX.arm-9.80-nightly-20191029-708dbf9-box.img.gz
The factory WeTek u-boot needs to find boot.ini in the root folder of the boot media or it will not boot. See the ^ above image to see what LE is using to initiate the usual āmultibootā process that LE and Armbian otherwise share.
Thanx for response , I thought that this thread is dead. So, copying my existing boot.ini from sd card to eMMC will do the thing?
OK. I just check LE image. Understand.
What about the procedure of flashing the eMMC? Can you point me some post or thread. Existing thread is confusing about 2018 and 2015 versions of boot. Or I am not quite smart to understand.
Iām no expert on emmc flashing ā¦ but basically youāll need to create new filesystems avoiding the first ~2MB or so that contains the factory u-boot. Mainline u-boot doesnāt have āboardā support for WeTek devices so unless youāre volunteering to add that youāll need to stick with the factory (2015) u-boot.