Jump to content

Single Armbian image for RK + AML + AW (aarch64 ARMv8)


Recommended Posts

Posted
4 minutes ago, dante6913 said:

yes you are right, but I'm tring what you said about the usb number because there where a lot of dongles and I have changed the order, so I'm going to try it with the usb armbian pen only

either you need to add more lines to poll all USB ports (you can do this via the "for" loop, or just add more lines with a direct number).

 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

fatload usb 1 1020000 s905_autoscript

autoscr 1020000

fatload usb 2 1020000 s905_autoscript

autoscr 1020000

fatload usb 4 1020000 s905_autoscript

autoscr 1020000

Posted

By the way, for today, I have already turned on and rebooted the system more than 30 times in Android on the SD card and in different systems on USB, everything works without errors, the file (boot.ini) is not overwritten and saves the added settings.

Posted
Just now, balbes150 said:

By the way, for today, I have already turned on and rebooted the system more than 30 times in Android on the SD card and in different systems on USB, everything works without errors, the file (boot.ini) is not overwritten and saves the added settings.

Yes same is hapenig here, but just boots in android,

No luck with 

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

fatload usb 1 1020000 s905_autoscript

autoscr 1020000

fatload usb 2 1020000 s905_autoscript

autoscr 1020000

fatload usb 4 1020000 s905_autoscript

autoscr 1020000

Going to try another usb stick

Posted
4 minutes ago, balbes150 said:

Show the file contents (uEnv.txt) on a USB flash drive

LINUX=/zImage
INITRD=/uInitrd

# rk-3399
#FDT=/dtb/rockchip/rk3399-rock-pi-4.dtb
#FDT=/dtb/rockchip/rk3399-nanopc-t4.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# rk-3328
#FDT=/dtb/rockchip/rk3328-box-trn9.dtb
#FDT=/dtb/rockchip/rk3328-box.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# aw h6
#FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e

# aml s9xxx
#FDT=/dtb/amlogic/meson-g12a-x96-max-no-cvbs.dtb
#FDT=/dtb/amlogic/meson-g12b-ugoos-am6-no-cvbs.dtb
FDT=/dtb/amlogic/meson-gxbb-odroidc2.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

Posted
1 minute ago, dante6913 said:

# rk-3399
#FDT=/dtb/rockchip/rk3399-rock-pi-4.dtb
#FDT=/dtb/rockchip/rk3399-nanopc-t4.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff1a0000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# rk-3328
#FDT=/dtb/rockchip/rk3328-box-trn9.dtb
#FDT=/dtb/rockchip/rk3328-box.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=uart8250,mmio32,0xff130000 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

# aw h6
#FDT=/dtb/allwinner/sun50i-h6-tanix-tx6.dtb
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0
#APPEND=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mem=2048M video=HDMI-A-1:e

# aml s9xxx
#FDT=/dtb/amlogic/meson-g12a-x96-max-no-cvbs.dtb
#FDT=/dtb/amlogic/meson-g12b-ugoos-am6-no-cvbs.dtb

This can be deleted

 

Show the file contents (boot.ini)

Posted
5 minutes ago, balbes150 said:

This can be deleted

 

Show the file contents (boot.ini)

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

fatload usb 1 1020000 s905_autoscript

autoscr 1020000

fatload usb 2 1020000 s905_autoscript

autoscr 1020000

fatload usb 4 1020000 s905_autoscript

autoscr 1020000
# Resolution Configuration
# 'hdmimode' must be one of below to configure display resolution within
# supported by your TV or monitor.
#    Symbol             | Resolution
# ----------------------+-------------
#    "480x320p60hz"     | 480x320 Progressive 60Hz
#    "480p60hz"         | 720x480 Progressive 60Hz
#    "576p50hz"         | 720x576 Progressive 50Hz
#    "720p60hz"         | 1280x720 Progressive 60Hz
#    "720p50hz"         | 1280x720 Progressive 50Hz
#    "1080p60hz"        | 1920x1080 Progressive 60Hz
#    "1080p50hz"        | 1920x1080 Progressive 50Hz
#    "1080p30hz"        | 1920x1080 Progressive 30Hz
#    "1080p24hz"        | 1920x1080 Progressive 24Hz
#    "1080i60hz"        | 1920x1080 Interlaced 60Hz
#    "1080i50hz"        | 1920x1080 Interlaced 50Hz
#    "2160p60hz"        | 3840x2160 Progressive 60Hz
#    "2160p50hz"        | 3840x2160 Progressive 50Hz
#    "2160p30hz"        | 3840x2160 Progressive 30Hz
#    "2160p25hz"        | 3840x2160 Progressive 25Hz
#    "2160p24hz"        | 3840x2160 Progressive 24Hz
#    "2160p60hz420"     | 3840x2160 Progressive 60Hz YCbCr 4:2:0
#    "2160p50hz420"     | 3840x2160 Progressive 50Hz YCbCr 4:2:0
#    "640x480p60hz"     | 640x480 Progressive 60Hz
#    "800x480p60hz"     | 800x480 Progressive 60Hz
#    "800x600p60hz"     | 800x600 Progressive 60Hz
#    "1024x600p60hz"    | 1024x600 Progressive 60Hz
#    "1024x768p60hz"    | 1024x768 Progressive 60Hz
#    "1280x800p60hz"    | 1280x800 Progressive 60Hz
#    "1280x1024p60hz"   | 1280x1024 Progressive 60Hz
#    "1360x768p60hz"    | 1360x768 Progressive 60Hz
#    "1440x900p60hz"    | 1440x900 Progressive 60Hz
#    "1600x900p60hz"    | 1600x900 Progressive 60Hz
#    "1600x1200p60hz"   | 1600x1200 Progressive 60Hz
#    "1680x1050p60hz"   | 1680x1050 Progressive 60Hz
#    "1920x1200p60hz"   | 1920x1200 Progressive 60Hz
#    "2560x1080p60hz"   | 2560x1080 Progressive 60Hz
#    "2560x1440p60hz"   | 2560x1440 Progressive 60Hz
#    "2560x1600p60hz"   | 2560x1600 Progressive 60Hz
#    "3440x1440p60hz"   | 3440x1440 Progressive 60Hz
setenv hdmimode "1080p60hz"

setenv rootopt "root=/dev/mmcblk0p2 rw init=/init rootwait"
setenv consoleopt "console=ttyS0,115200"
setenv androidopt "androidboot.hardware=odroidc2 androidboot.serialno=${fbt_id#}"
setenv logoopt "osd1,loaded,${fb_addr},${hdmimode}"
setenv selinuxopt "androidboot.selinux=disabled"

# HDMI/DVI Mode Configuration
# This will enforce the signal type of display
# "hdmi" - For HDMI interface
# "dvi" - For DVI interface
setenv vout_mode "hdmi"

# Display Auto Detection
# "false" or "true"
setenv display_autodetect "true"

# HPD enable/disable option
setenv disablehpd "false"

# Overscan offset configuration
# All offsets are zero and can be tuned by manual or ODROID Utility
setenv overscan_top "0"
setenv overscan_left "0"
setenv overscan_bottom "0"
setenv overscan_right "0"
setenv led_onoff "on"
suspend_hdmiphy=0

# Force HDMI to use RGB colorspace regardless of TV request
setenv hdmi_forcergb "0"      # Disabled
# setenv hdmi_forcergb "1"        # Enabled

# max cpu frequency in dvfs table / in MHz unit
# setenv max_freq "2016"  # 2.016GHz
# setenv max_freq "1944"  # 1.944GHz
# setenv max_freq "1920"  # 1.920GHz
# setenv max_freq "1896"  # 1.896GHz
# setenv max_freq "1752"  # 1.752GHz
# setenv max_freq "1680"  # 1.680GHz
# setenv max_freq "1656"  # 1.656GHz
# setenv max_freq "1536"  # 1.536GHz
setenv max_freq "1536"

# max cpu-cores
# setenv maxcpus "1"
# setenv maxcpus "2"
# setenv maxcpus "3"
setenv maxcpus "4"

# disable vu7
setenv disable_vu7 "false"

# invert touch screen x,y
setenv touch_invert_x "false"
setenv touch_invert_y "false"

# gpio power key : J2 (2x20) Pin#35, GPIOY.BIT3
#setenv gpiopower "214"

# usb timing tweak
setenv usbmulticam "false"

setenv hdmitx "hdmitx=${cecconfig}"
if test "${hdmi_forcergb}" = "1"; then setenv hdmitx "hdmitx=forcergb"; fi

if test "${display_autodetect}" = "true"; then usb pwren; hdmitx edid; fi
if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi

# Enable backlight_pwm
# disable : backlight "no"
# ODROID-VU5/7 : backlight "yes"
# ODROID-VU8 : backlight "invert"
setenv backlight_pwm "no"

setenv test_mt_vid "0000"
setenv test_mt_pid "0000"

showddrclk

setenv bootargs "${rootopt} ${consoleopt} hdmimode=${hdmimode} ${cmode} ${hdmitx} vout=${vout_mode} disablehpd=${disablehpd} logo=${logoopt} ${androidopt} ${selinuxopt} suspend_hdmiphy=${suspend_hdmiphy} led_onoff=${led_onoff} max_freq=${max_freq} maxcpus=${maxcpus} disable_vu7=${disable_vu7} touch_invert_x=${touch_invert_x} touch_invert_y=${touch_invert_y} usbmulticam=${usbmulticam} gpiopower=${gpiopower} backlight_pwm=${backlight_pwm} ddrclock=${ddrclock} test_mt_pid=${test_mt_pid} test_mt_vid=${test_mt_vid}"

save

showlogo ${hdmimode}
#usb pwren

movi read dtb 0 ${dtbaddr}
# load kernel from vat or boot partition.
movi read boot 0 ${loadaddr}
#fatload mmc 0:1 ${loadaddr} Image_android
booti ${loadaddr} - ${dtbaddr}

Posted

There don't seem to be any errors. For today, there are no ideas yet, except for the failure of the media (it's time to sleep).

When the HK screen is displayed, the USB indicator should be flashing actively.

Posted
2 minutes ago, balbes150 said:

There don't seem to be any errors. For today, there are no ideas yet, except for the failure of the media (it's time to sleep).

When the HK screen is displayed, the USB indicator should be flashing actively.

tried now with an old usb 2 but got the same result.

Maybe is time to stop and try it another day.

I'm worry about the amount of time that I have taken from you.

Thank you for everything

Posted

Hi Fellow AML Armbian users

 

I tried to install the current version of this Armbian from Yandex Disk on my X92.

 

I tried to install the zip from OTA App as well as with toothpick, with both methods I can reach the recovery and choose the USB with the ZIP file but I get the error "cannot load volume /misc" is this a known problem? has anyone ever seen this?

 

Thanks for your help

Posted
On 5/10/2020 at 10:29 AM, balbes150 said:

Show the output of the "printenv" and "help" commands from u-boot

 

@balbes150Re: Beelink GT-King, unstable when copying files etc... (sorry it took a while to get back to you).  This is off a fresh imaged disk for "Armbian_20.05.4_Arm-64_bionic_current_5.7.0-rc4_desktop_20200510"

 

Printenv

Spoiler

1080p60hz_deepcolor=444,8bit
EnableSelinux=permissive
Irq_check_en=0
active_slot=normal
aml_dt=g12b_w400_a
avb2=0
baudrate=115200
bcb_cmd=get_avb_mode;get_valid_slot;
boot_part=boot
bootargs=init=/init console=ttyS0,115200 no_console_suspend earlycon=aml-uart,0xff803000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 otg_device=1 reboot_mode_android=normal logo=osd0,loaded,0x3d800000 vout=576cvbs,enable panel_type=lcd_1 hdmitx=,444,8bit hdmimode=1080p60hz frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs osd_reverse=0 video_reverse=0 irq_check_en=0 androidboot.selinux=permissive androidboot.firstboot=0 jtag=disable androidboot.hardware=amlogic androidboot.serialno=1234567890
bootcmd=run start_autoscript; run storeboot
bootdelay=1
bootup_offset=0x1160d60
bootup_size=0x5eec38
cmdline_keys=if keyman init 0x1234; then if keyman read usid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.serialno=${usid};setenv serial ${usid};else setenv bootargs ${bootargs} androidboot.serialno=1234567890;setenv serial 1234567890;fi;if keyman read mac ${loadaddr} str; then setenv bootargs ${bootargs} mac=${mac} androidboot.mac=${mac};fi;if keyman read deviceid ${loadaddr} str; then setenv bootargs ${bootargs} androidboot.deviceid=${deviceid};fi;fi;
colorattribute=444,8bit
cvbs_drv=0
cvbsmode=576cvbs
display_bpp=24
display_color_bg=0
display_color_fg=0xffff
display_color_index=24
display_height=576
display_layer=osd0
display_width=720
dtb_mem_addr=0x1000000
ethact=dwmac.ff3f0000
ethaddr=02:00:00:15:21:01
factory_reset_poweroff_protect=echo wipe_data=${wipe_data}; echo wipe_cache=${wipe_cache};if test ${wipe_data} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; if test ${wipe_cache} = failed; then run init_display; run storeargs;if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;fi; 
fb_addr=0x3d800000
fb_height=1080
fb_width=1920
fdt_high=0x20000000
fdtaddr=1000000
firstboot=0
frac_rate_policy=1
fs_type=rootfstype=ramfs
gatewayip=10.18.9.1
hdmi_read_edid=1
hdmimode=1080p60hz
hostname=arm_gxbb
identifyWaitTime=750
init_display=get_rebootmode;echo reboot_mode:::: ${reboot_mode};if test ${reboot_mode} = quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;osd open;osd clear;else if test ${reboot_mode} = recovery_quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;osd open;osd clear;else setenv reboot_mode_android normal;run storeargs;hdmitx hpd;hdmitx get_preferred_mode;osd open;osd clear;imgread pic logo bootup $loadaddr;bmp display $bootup_offset;bmp scale;vout output ${outputmode};vpp hdrpkt;fi;fi;
initargs=init=/init console=ttyS0,115200 no_console_suspend earlycon=aml-uart,0xff803000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 
initrd_high=7f800000
ipaddr=10.18.9.97
irremote_update=if irkey 2500000 0xe31cfb04 0xb748fb04; then echo read irkey ok!; if itest ${irkey_value} == 0xe31cfb04; then run update;else if itest ${irkey_value} == 0xb748fb04; then run update;\
fi;fi;fi;
jtag=disable
loadaddr=1080000
lock=10001000
netmask=255.255.255.0
osd_reverse=0
otg_device=1
outputmode=576cvbs
panel_type=lcd_1
preboot=run bcb_cmd; run factory_reset_poweroff_protect;run upgrade_check;run init_display;run storeargs;forceupdate;bcb uboot-command;run switch_bootmode;
reboot_mode=cold_boot
reboot_mode_android=normal
recovery_from_flash=get_valid_slot;echo active_slot: ${active_slot};if test ${active_slot} = normal; then setenv bootargs ${bootargs} ${fs_type} aml_dt=${aml_dt} recovery_part={recovery_part} recovery_offset={recovery_offset};if imgread kernel ${recovery_part} ${loadaddr} ${recovery_offset}; then wipeisb; bootm ${loadaddr}; fi;else setenv bootargs ${bootargs} ${fs_type} aml_dt=${aml_dt} recovery_part=${boot_part} recovery_offset=${recovery_offset};if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;fi;
recovery_from_sdcard=if fatload mmc 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload mmc 0 ${loadaddr} recovery.img; then if fatload mmc 0 ${dtb_mem_addr} dtb.img; then echo sd dtb.img loaded; fi;wipeisb; setenv bootargs ${bootargs} ${fs_type};bootm ${loadaddr};fi;
recovery_from_udisk=if fatload usb 0 ${loadaddr} aml_autoscript; then autoscr ${loadaddr}; fi;if fatload usb 0 ${loadaddr} recovery.img; then if fatload usb 0 ${dtb_mem_addr} dtb.img; then echo udisk dtb.img loaded; fi;wipeisb; setenv bootargs ${bootargs} ${fs_type};bootm ${loadaddr};fi;
recovery_offset=0
recovery_part=recovery
rpmb_state=1
saradc_val=0x3fe
sdc_burning=sdc_burn ${sdcburncfg}
sdcburncfg=aml_sdc_burn.ini
sdr2hdr=2
serial=1234567890
serverip=10.18.9.113
start_autoscript=if mmcinfo; then run start_mmc_autoscript; fi; if usb start; then run start_usb_autoscript; fi; run start_emmc_autoscript
start_emmc_autoscript=if fatload mmc 1 1020000 emmc_autoscript; then autoscr 1020000; fi;
start_mmc_autoscript=if fatload mmc 0 1020000 s905_autoscript; then autoscr 1020000; fi;
start_usb_autoscript=for usbdev in 0 1 2 3; do if fatload usb ${usbdev} 1020000 s905_autoscript; then autoscr 1020000; fi; done
stderr=serial
stdin=serial
stdout=serial
storeargs=setenv bootargs ${initargs} otg_device=${otg_device} reboot_mode_android=${reboot_mode_android} logo=${display_layer},loaded,${fb_addr} vout=${outputmode},enable panel_type=${panel_type} hdmitx=${cecconfig},${colorattribute} hdmimode=${hdmimode} frac_rate_policy=${frac_rate_policy} hdmi_read_edid=${hdmi_read_edid} cvbsmode=${cvbsmode} osd_reverse=${osd_reverse} video_reverse=${video_reverse} irq_check_en=${Irq_check_en}  androidboot.selinux=${EnableSelinux} androidboot.firstboot=${firstboot} jtag=${jtag}; setenv bootargs ${bootargs} androidboot.hardware=amlogic;run cmdline_keys;
storeboot=boot_cooling;get_system_as_root_mode;echo system_mode: ${system_mode};if test ${system_mode} = 1; then setenv bootargs ${bootargs} ro rootwait skip_initramfs;else setenv bootargs ${bootargs} ${fs_type};fi;get_valid_slot;get_avb_mode;echo active_slot: ${active_slot};if test ${active_slot} != normal; then setenv bootargs ${bootargs} androidboot.slot_suffix=${active_slot};fi;if test ${avb2} = 0; then if test ${active_slot} = _a; then setenv bootargs ${bootargs} root=/dev/mmcblk0p23;else if test ${active_slot} = _b; then setenv bootargs ${bootargs} root=/dev/mmcblk0p24;fi;fi;fi;if imgread kernel ${boot_part} ${loadaddr}; then bootm ${loadaddr}; fi;run storeargs; run update;
switch_bootmode=get_rebootmode;if test ${reboot_mode} = factory_reset; then setenv reboot_mode_android normal;run storeargs;run recovery_from_flash;else if test ${reboot_mode} = update; then setenv reboot_mode_android normal;run storeargs;run update;else if test ${reboot_mode} = quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;else if test ${reboot_mode} = recovery_quiescent; then setenv reboot_mode_android quiescent;run storeargs;setenv bootargs ${bootargs} androidboot.quiescent=1;run recovery_from_flash;else if test ${reboot_mode} = cold_boot; then run try_auto_burn; setenv reboot_mode_android normal;run storeargs;else if test ${reboot_mode} = fastboot; then setenv reboot_mode_android normal;run storeargs;fastboot;fi;fi;fi;fi;fi;fi;
try_auto_burn=update 700 750;
update=run usb_burning; run sdc_burning; if mmcinfo; then run recovery_from_sdcard;fi;if usb start 0; then run recovery_from_udisk;fi;run recovery_from_flash;
upgrade_check=echo upgrade_step=${upgrade_step}; if itest ${upgrade_step} == 3; then run init_display; run storeargs; run update;else fi;
upgrade_key=if gpio input GPIOAO_3; then echo detect upgrade key; run update;fi;
upgrade_step=2
usb_burning=update 1000
video_reverse=0
wipe_cache=successful
wipe_data=successful

Environment size: 8188/65532 bytes

 

Help Commands

Spoiler

?       - alias for 'help'
aml_sysrecovery- Burning with amlogic format package from partition sysrecovery
amlmmc  - AMLMMC sub system
amlnf   - aml mtd nand sub-system
autocali- auto cali    - auto set cali value for exphy

autoscr - run script from memory
avb     - avb
base    - print or set address offset
bcb     - bcb
bmp     - manipulate BMP image data
boot_cooling- cpu temp-system
booti   - boot arm64 Linux Image image from memory
bootm   - boot application image from memory
bootp   - boot image via network using BOOTP/TFTP protocol
cbusreg - cbus register read/write
chpart  - change active partition
clkmsr  - Amlogic measure clock
cmp     - memory compare
cp      - memory copy
crc32   - checksum calculation
cvbs    - CVBS sub-system
dcache  - enable or disable data cache
ddr_auto_fast_boot_check- ddr_fastboot_config cmd arg1 arg2 arg3...
ddr_auto_scan_drv- ddr_test_cmd cmd arg1 arg2 arg3...
ddr_auto_test_window- ddr_test_cmd cmd arg1 arg2 arg3...
ddr_cpu_test- ddr_test_cmd cmd arg1 arg2 arg3...
ddr_fast_boot- ddr_fastboot_config cmd arg1 arg2 arg3...
ddr_g12_offset_data- ddr_g12_offset_data  1 0  0 0  1 3
ddr_g12_override_data- ddr_g12_override_data  1 0  0 0  1 3
ddr_spec_test- DDR test function
ddr_test_cmd- ddr_test_cmd cmd arg1 arg2 arg3...
ddr_test_copy- ddr_test_copy function
ddrtest - DDR test function
defenv_reserv- reserve some specified envs after defaulting env
dhcp    - boot image via network using DHCP/TFTP protocol
dtimg   - manipulate dtb/dtbo Android image
echo    - echo args to console
efuse   - efuse commands
efuse_user- efuse user space read write ops
emmc    - EMMC sub system
env     - environment handling commands
ethloop - ethloop    - loopback test using ethernet test package

exit    - exit script
false   - do nothing, unsuccessfully
fastboot- use USB Fastboot protocol
fatinfo - print information about filesystem
fatload - load binary file from a dos filesystem
fatls   - list files in a directory (default /)
fatsize - determine a file's size
fdt     - flattened device tree utility commands
forceupdate- forceupdate
g12_d2pll- g12_d2pll 1300  1 0x10 0
get_avb_mode- get_avb_mode
get_rebootmode- get reboot mode
get_system_as_root_mode- get_system_as_root_mode
get_valid_slot- get_valid_slot
go      - start application at address 'addr'
gpio    - query and control gpio pins
gpt     - GUID Partition Table
guid    - GUID - generate Globally Unique Identifier based on random UUID
hdmitx  - HDMITX sub-system 20190123
help    - print command description/usage
i2c     - I2C sub-system
icache  - enable or disable instruction cache
img_osd - image osd sub-system
imgread - Read the image from internal flash with actual size
itest   - return true/false on integer compare
jtagoff - disable jtag
jtagon  - enable jtag
keyman  - Unify key ops interfaces based dts cfg
keyunify- key unify sub-system
lcd     - lcd sub-system
loadb   - load binary file over serial line (kermit mode)
loadx   - load binary file over serial line (xmodem mode)
loady   - load binary file over serial line (ymodem mode)
loop    - infinite loop on address range
macreg  - ethernet mac register read/write/dump
md      - memory display
mm      - memory modify (auto-incrementing address)
mmc     - MMC sub system
mmcinfo - display MMC info
mtdparts- define flash/nand partitions
mw      - memory write (fill)
mwm     - mw mask function
nand    - NAND sub-system
nboot   - boot from NAND device
nm      - memory modify (constant address)
open_scp_log- print SCP messgage
osd     - osd sub-system
phyreg  - ethernet phy register read/write/dump
ping    - send ICMP ECHO_REQUEST to network host
plltest - test pll
printenv- print environment variables
query   - SoC query commands
rarpboot- boot image via network using RARP/TFTP protocol
read_temp- cpu temp-system
reboot  - set reboot mode and reboot system
reset   - Perform RESET of the CPU
ringmsr - Amlogic measure ring
rpmb_state- RPMB sub-system
rsvmem  - reserve memory
run     - run commands in an environment variable
saradc  - saradc sub-system
saradc_12bit- saradc sub-system
saveenv - save environment variables to persistent storage
sdc_burn- Burning with amlogic format package in sdmmc 
sdc_update- Burning a partition with image file in sdmmc card
set_active_slot- set_active_slot
set_trim_base- cpu temp-system
set_usb_boot- set usb boot mode
setenv  - set environment variables
sf      - SPI flash sub-system
showvar - print local hushshell variables
sleep   - delay execution for some time
sspi    - SPI utility command
store   - STORE sub-system
systemoff- system off 
tee_log_level- update tee log level
temp_triming- cpu temp-system
test    - minimal test like /bin/sh
tftpboot- boot image via network using TFTP protocol
true    - do nothing, successfully
ubi     - ubi commands
ubifsload- load file from an UBIFS filesystem
ubifsls - list files in a directory
ubifsmount- mount UBIFS volume
ubifsumount- unmount UBIFS volume
ui      - ui sub-system
unpackimg- un pack logo image into pictures
update  - Enter v2 usbburning mode
usb     - USB sub-system
usb_burn- Burning with amlogic format package in usb 
usb_update- Burning a partition with image file in usb host
usbboot - boot from USB device
uuid    - UUID - generate random Universally Unique Identifier
version - print monitor, compiler and linker version
viu_probe- enable viu probe in no secure chip
vout    - VOUT sub-system
vout2   - VOUT2 sub-system
vpp     - vpp sub-system
vpu     - vpu sub-system
write_trim- cpu temp-system
write_version- cpu temp-system

 

Thanks for taking a look.

Posted
On 5/11/2020 at 5:03 PM, itchy'n'scratchy said:

Hi Fellow AML Armbian users

 

I tried to install the current version of this Armbian from Yandex Disk on my X92.

 

I tried to install the zip from OTA App as well as with toothpick, with both methods I can reach the recovery and choose the USB with the ZIP file but I get the error "cannot load volume /misc" is this a known problem? has anyone ever seen this?

 

Thanks for your help

Based on your question, I think you are doing something wrong.  With the toothpick method the steps described in the first post of this thread don't mention anything to do with recovery.  The steps sumarized are to prepare the image on an SD card, update uEnv.txt, install the SD card and boot while holding down the reset button with a toothpick.  Perhaps you need to provide more details on what you are trying to do.

Posted

Does anyone else have issues with booting from usb flash drive, everything is ok when booting from sd, but when trying with usb, it boots as server, but with start dependencies failed, and no desktop.

 

Device is kvim1, image is ubuntu focal desktop, kernel 5.7 rc4.

 

 

 

 

Posted
10 hours ago, SteeMan said:

Based on your question, I think you are doing something wrong.  With the toothpick method the steps described in the first post of this thread don't mention anything to do with recovery.  The steps sumarized are to prepare the image on an SD card, update uEnv.txt, install the SD card and boot while holding down the reset button with a toothpick.  Perhaps you need to provide more details on what you are trying to do.

When doing either of the methods in the first post tooth pick or updater app, I'm dropping into recovery, so I thought it might be clever to apply the aml_autoscript.zip via the recovery, but that seems to not work.

 

Later I realised the autoscript zip is 0b in size, I guess that's why it wont work...

Posted
17 hours ago, balbes150 said:

ver 20200514 kernel 5.7-rc5

Hi balbes150

 

I wasn't able to start multiboot even with the same usb configuration that I before had for a short period sucess . I'm starting to think tha I have some issue with my hardware.

So, I would like to ask you if is possible to boot your images without multiboot?

Thanks

Posted
35 minutes ago, dante6913 said:

I wasn't able to start multiboot even with the same usb configuration that I before had for a short period sucess . I'm starting to think tha I have some issue with my hardware.

So, I would like to ask you if is possible to boot your images without multiboot?

Yes, it is possible, which system option do you want to get ?

Posted (edited)
12 minutes ago, balbes150 said:

Yes, it is possible, which system option do you want to get ?

armbian bullsyey on the c2.

I'm following your c1 sub forum, I see that you made some changes on the boot.ini from the experimental images. I was thinking trying this changes on my C2. I know that they are diferent systems, but I am so frustated that I'm not able to multiboot that I'm willing to try anything.

Edited by dante6913
Posted
6 minutes ago, dante6913 said:

armbian, on the c2.

I'm following your c1 sub forum, I see that you made some changes on the boot.ini from the experimental images. I was thinking trying this changes on my C2. I know that they are diferent systems, but I am so frustated that I'm not able to multiboot that I'm willing to try anything.

What is your current configuration of eMMC + SD , eMMC + USB,  SD + USB media etc (which media do you want to run Armbian from) ?

Posted (edited)
4 minutes ago, balbes150 said:

What is your current configuration of eMMC + SD , eMMC + USB,  SD + USB media etc (which media do you want to run Armbian from) ?

Android 6 in emmc and have an sd and usb. Last Sunday I tried multiboot with usb

with boot.ini of the android

DROIDC2-UBOOT-CONFIG

usb start

fatload usb 0 1020000 s905_autoscript

autoscr 1020000

 

Managed to bootone time but after that allways failled to boot

Edited by dante6913
Posted (edited)

I tried an android image on a sd (fresh install) an armbian from an usb but that failed too. That why I'm thinking that maybe I have some issue with the hardware that doesn't let me use multiboot.  But as I said thats very strange because I was able to boot with android in the emmc and armbian in usb one time. But after reboot I couldn't boot anymore. 

 

So if I can't multiboot maybe I can install your ambian image on my emmc 

Edited by dante6913
Posted

Perhaps this command is the reason.

 

usbmulticam=${usbmulticam} gpiopower=${gpiopower}"

save

showlogo ${hdmimode}

 

 

Try temporarily replacing the entire file (boot.ini) with eMMC with this version. Write Armbian and configure (uEnv.txt) to the SD card. Connect the SD card and check the launch.

 

ODROIDN2-UBOOT-CONFIG

# set load addresses
setenv env_addr 0x10400000
setenv kernel_addr 0x11000000
setenv initrd_addr 0x13000000
setenv dtb_addr 0x1000000

#if test "${devtype}" = ""; then setenv devtype "mmc"; fi
setenv devtype "mmc"
setenv devnum "1"

# load uEnv.txt
load ${devtype} ${devnum} ${env_addr} uEnv.txt && env import -t ${env_addr} ${filesize}
setenv bootargs ${APPEND}

# Load kernel, dtb
load ${devtype} ${devnum} ${kernel_addr} ${LINUX}
load ${devtype} ${devnum} ${initrd_addr} ${INITRD}
load ${devtype} ${devnum} ${dtb_addr} ${FDT}
fdt addr ${dtb_addr}

# boot
booti ${kernel_addr} ${initrd_addr} ${dtb_addr}

 

Posted
1 hour ago, balbes150 said:

Perhaps this command is the reason.

 

usbmulticam=${usbmulticam} gpiopower=${gpiopower}"

save

showlogo ${hdmimode}

 

 

Try temporarily replacing the entire file (boot.ini) with eMMC with this version. Write Armbian and configure (uEnv.txt) to the SD card. Connect the SD card and check the launch.

 


ODROIDC2-UBOOT-CONFIG

# set load addresses
setenv env_addr 0x10400000
setenv kernel_addr 0x11000000
setenv initrd_addr 0x13000000
setenv dtb_addr 0x1000000

#if test "${devtype}" = ""; then setenv devtype "mmc"; fi
setenv devtype "mmc"
setenv devnum "1"

# load uEnv.txt
load ${devtype} ${devnum} ${env_addr} uEnv.txt && env import -t ${env_addr} ${filesize}
setenv bootargs ${APPEND}

# Load kernel, dtb
load ${devtype} ${devnum} ${kernel_addr} ${LINUX}
load ${devtype} ${devnum} ${initrd_addr} ${INITRD}
load ${devtype} ${devnum} ${dtb_addr} ${FDT}
fdt addr ${dtb_addr}

# boot
booti ${kernel_addr} ${initrd_addr} ${dtb_addr}

 

Thanks balbes150, 

I'm going to try when I'm home. Now I am at my working place (lunnch time). 

I will feed back the result.

Posted (edited)

Just to be clear? The boot.ini file to be replace is the one from the android in the emmc?

Edited by dante6913
Posted
12 minutes ago, dante6913 said:

Just to be clear? The boot.ini file to be replace is the one from the android in the emmc?

Yes, you need to replace the contents of the file (boot.ini) with eMMC (in android). It should only contain the lines I gave above.

 

Second check, check the launch from USB. Write an image USB and configure it (uEnv.txt) and replace this line in (boot.ini) with eMMC

 

setenv devtype "mmc"

setenv devnum "1"

 

to

 

usb start

setenv devtype "usb"

setenv devnum "0"

Posted
18 minutes ago, balbes150 said:

Yes, you need to replace the contents of the file (boot.ini) with eMMC (in android). It should only contain the lines I gave above.

 

Second check, check the launch from USB. Write an image USB and configure it (uEnv.txt) and replace this line in (boot.ini) with eMMC

 

setenv devtype "mmc"

setenv devnum "1"

 

to

 

usb start

setenv devtype "usb"

setenv devnum "0"

thanks, when I'm back home I will try it

Posted
42 minutes ago, dante6913 said:

thanks, when I'm back home I will try it

By the way, I noticed a difference

 

1 hour ago, dante6913 said:

DROIDC2-UBOOT-CONFIG

 

and correctly, as it should be

 

1 hour ago, dante6913 said:

ODROIDC2-UBOOT-CONFIG

 

Posted
7 minutes ago, balbes150 said:

By the way, I noticed a difference

 

 

and correctly, as it should be

 

 

you're damn right, since the beginning I had this error

Posted

This is the key string used by u-boot to determine whether to execute this file or not. :)

 

It must be strict

 

ODROIDC2-UBOOT-CONFIG

Posted (edited)
11 minutes ago, balbes150 said:

This is the key string used by u-boot to determine whether to execute this file or not. :)

 

It must be strict

 

ODROIDC2-UBOOT-CONFIG

On your image there are these files boot.ini and boot-emmc.ini that have the key string as ODROIDN2-UBOOT-CONFIG should I modify Them to ODROIDC2-UBOOT-CONFIG?

Edited by dante6913
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines