It’s claimed there’s an Armbian image for the VIM3, but I can’t find it anywhere. @balbes150?
You can chck here: https://yadi.sk/d/pHxaRAs-tZiei/20.02/20200205
Thank you very much!
Is there a reason Armbian doesnt list/host the board yet, though?
It is a general version, you need to setup the DTB yourself.
All images are now universal.
The link provided isn’t allowing me to download it as due to some internal link problem,It says disk is full and won’t permit me to download the images
(p.s. disk as in online storage not my computer storage)
I just downloaded from one of the Yadi links. Are you using the “Download” button as opposed to the “Save to Yandex.disk”?
Ok, I checked it out it and now I can download, Thank you
Hey, @balbes150; I can’t get the image (bullseye no desktop) to boot on my VIM3 Pro; I just get the following:
bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 no sdio debug board detected L0:00000000 L1:20000703 L2:00008067 L3:14000000 B2:00402000 B1:e0f83180 TE: 235590 BL2 Built : 10:47:19, Jan 14 2019. g12b g152d217 - guotai.shen@droid11-sz Board ID = 8 Set A53 clk to 24M Set A73 clk to 24M Set clk81 to 24M A53 clk: 1200 MHz A73 clk: 1200 MHz CLK81: 166.6M smccc: 0003e0d3 DDR driver_vesion: LPDDR4_PHY_V_0_1_11 build time: Jan 14 2019 10:47:15 board id: 8 Load FIP HDR from SD, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 fw parse done Load ddrfw from SD, src: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0 Load ddrfw from SD, src: 0x00038200, des: 0xfffd0000, size: 0x00004000, part: 0 PIEI prepare done Cfg max: 2, cur: 1. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz Load ddrfw from SD, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : STREAM 0x00690001 - 0x00000000 INFO : STREAM 0x04020000 - INFO : ERROR : Training has failed! 1D training failed Cfg max: 2, cur: 2. Board id: 255. Force loop cfg DDR4 probe ddr clk to 1320MHz Load ddrfw from SD, src: 0x00014200, des: 0xfffd0000, size: 0x0000c000, part: 0 Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : STREAM 0x00490002 - 0x00000000 0x00000000 INFO : STREAM 0x04020000 - INFO : ERROR : Training has failed! 1D training failed All ddr config failed... Reset...
and it loops forever.
Which image you use ? Seems the DDR initialize failed, and the DDR driver version is old
Armbian_20.02.0-rc1.038_Aml-s9xxx_bullseye_current_5.5.0-rc6_20200205.img from @balbes150’s Yandex Disk account. (Which itself is rather out of date, as Armbian 20.02 is out of RC now.)
Show the full description of the steps, the firmware version in eMMC, and what was run earlier on this firmware.
Wrote SD card with dd, tried to boot. eMMC is blank.
As part of universal images there is no u-boot for AML. Either restore the regular firmware and use universal multi-boot , or additionally write u-boot to the SD card.
How would I go about writing U-Boot to the SD Card after writing the Armbian image? Can I take the U-Boot from the VIM3 Rescue image?
(I had cleared the bootloader from the eMMC due to the purple screen bug it introduced into the official Ubuntu image (which I won’t be using due to its lack of 3D acceleration as the panfrost driver is not present.))
Why are no prebuilt images provided for things like U-Boot?
my opinion system must work stand alone, why not prepare it for users ?
I wrote the mainline UBoot via KRescue then attempted to boot the Armbian image. It failed.
mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot.cmd 840 bytes read in 2 ms (410.2 KiB/s) [w] Script a:08000000 l:32768 c:1 - wrong header! script - # run plain script from memory Usage: script [addr|check] [bytes] [nochk] [silent] - run script starting at addr bytes - read bytes (hex) limit nochk - no check #!script header silent - be silent SCRIPT FAILED: continuing... Found U-Boot script /boot.scr 912 bytes read in 2 ms (445.3 KiB/s) [w] mkimage Script a:08000000 l:32768 - s:840 [#] Script a:08000000 l:4294967236 c:0 s:0 - run SCRIPT FAILED: continuing...
yes its my mistake wait a moment i will fix it
The U-Boot that gets installed by krescue also has the purple/green screen bug when booting krescue. >o<
YES! becouse we have 6 combinations
- mainline uboot + patched mainline kernel => GREEN
- mainline uboot + mainline kernel => OK
- legacy uboot + patched mainline kernel => OK
- legacy uboot + mainline kernel => GREEN
- mainline uboot + legacy kernel => GREEN
- legacy uboot + legacy kernel => OK
if u write uboot to emmc VIM3 VIM3L start always uboot from emmc if it presented on emmc
green screen not big problem for Krescue all other function works same well and if u install images its must be same ok