Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Waiting for Amlogic device to be connected... #7

Open
jersobh opened this issue Apr 30, 2019 · 5 comments
Open

Waiting for Amlogic device to be connected... #7

jersobh opened this issue Apr 30, 2019 · 5 comments

Comments

@jersobh
Copy link

jersobh commented Apr 30, 2019

Hi, please, it wont find the device.. I'm stuck at Waiting for Amlogic device to be connected...

@drewferagen
Copy link

manually execute the tools/update command. I did an it turns out this needs libusb 0.1 so on ubuntu I had to run:
sudo apt install libusb-0.1-4

to install the right version.

@probonopd
Copy link

For me this worked:

sudo apt-get -y install libusb-dev git
git clone https://github.com/khadas/utils
cd utils/aml-flash-tool
git checkout 7c25838 # Later ones fail with: ERR: AmlUsbBulkCmd failed!
sudo ./INSTALL
update identify

Later ones fail with: ERR: AmlUsbBulkCmd failed!

@kitkw
Copy link

kitkw commented May 16, 2022

manually execute the tools/update command. I did an it turns out this needs libusb 0.1 so on ubuntu I had to run: sudo apt install libusb-0.1-4

to install the right version.

sudo apt install libusb-dev
finished

but always "Waiting for Amlogic device to be connected... "
how to fix

@drewferagen
Copy link

I like to watch lsusb to show all my connected devices in a terminal, then plug it in and see if it is showing up. I think the port you use matters, mine had two and only one of them would show up when I plugged into my PC. It should show up as AMlogic something or other.

Also, after you create the udev rule, it's usually a good idea to reboot just to make sure it is in place.

@kitkw
Copy link

kitkw commented May 19, 2022

I like to watch lsusb to show all my connected devices in a terminal, then plug it in and see if it is showing up. I think the port you use matters, mine had two and only one of them would show up when I plugged into my PC. It should show up as AMlogic something or other.

Also, after you create the udev rule, it's usually a good idea to reboot just to make sure it is in place.

root@kitman-Aspire-4749:/home/kitman/aml-linux-usb-burn# ./aml-flash --img=aml_upgrade_package.img --soc=gxl --wipe --reset=n --parts=all --debug

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null identify 7

  • Results ---------------------------------------------------
    AmlUsbIdentifyHost
    This firmware version is 3-0-0-0-0-1-0

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null identify 7

  • Results ---------------------------------------------------
    AmlUsbIdentifyHost
    This firmware version is 3-0-0-0-0-1-0

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null bulkcmd " echo 12345"

  • Results ---------------------------------------------------
    AmlUsbBulkCmd[ echo 12345]
    [AmlUsbRom]Err:return len=0 < strLenBusy 11
    [AmlUsbRom]Err:bulkInReply=[]
    ERR: AmlUsbBulkCmd failed!

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null identify 7

  • Results ---------------------------------------------------
    AmlUsbIdentifyHost
    This firmware version is 3-0-0-0-0-1-0

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null rreg 4 0xc8100228

  • Results ---------------------------------------------------
    [update]Total tansfer size 0x4

C8100228: 00000000

0xc8100228 = 0x00000000
Secure boot bit = 0
Unpacking image
[Msg]Image package version 0x2
[Msg]Unpack item [USB , DDR] to (/tmp/aml-flash-tool-3fNa/DDR.USB) size:49152 bytes
[Msg]Unpack item [USB , UBOOT] to (/tmp/aml-flash-tool-3fNa/UBOOT.USB) size:631296 bytes
[Msg]Unpack item [PARTITION , _aml_dtb] to (/tmp/aml-flash-tool-3fNa/_aml_dtb.PARTITION) size:47525 bytes
[Msg]Unpack item [UBOOT , aml_sdc_burn] to (/tmp/aml-flash-tool-3fNa/aml_sdc_burn.UBOOT) size:680960 bytes
[Msg]Unpack item [ini , aml_sdc_burn] to (/tmp/aml-flash-tool-3fNa/aml_sdc_burn.ini) size:602 bytes
[Msg]Unpack item [PARTITION , bootloader] to (/tmp/aml-flash-tool-3fNa/bootloader.PARTITION) size:680448 bytes
[Msg]Unpack item [PARTITION , impdata] to (/tmp/aml-flash-tool-3fNa/impdata.PARTITION) size:4395192 bytes
[Msg]Unpack item [PARTITION , logo] to (/tmp/aml-flash-tool-3fNa/logo.PARTITION) size:7122224 bytes
[Msg]Backup item [dtb , meson1] backItemId[2][PARTITION, _aml_dtb]
[Msg]Unpack item [conf , platform] to (/tmp/aml-flash-tool-3fNa/platform.conf) size:202 bytes
[Msg]Unpack item [PARTITION , recovery] to (/tmp/aml-flash-tool-3fNa/recovery.PARTITION) size:16312320 bytes
[Msg]Unpack item [PARTITION , rootsys] to (/tmp/aml-flash-tool-3fNa/rootsys.PARTITION) size:8495104 bytes
[Msg]Unpack item [PARTITION , system] to (/tmp/aml-flash-tool-3fNa/system.PARTITION) size:1081169968 bytes
[Msg]Unpack item [PARTITION , tclconfig] to (/tmp/aml-flash-tool-3fNa/tclconfig.PARTITION) size:10611136 bytes
[Msg]Unpack item [PARTITION , userdata] to (/tmp/aml-flash-tool-3fNa/userdata.PARTITION) size:4526264 bytes
[Msg]Write config file "/tmp/aml-flash-tool-3fNa/image.cfg" OK!
Image unpack OK!
[OK]

Parsing image configuration files

awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
platform_conf_name = platform.conf
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
ddr_filename = DDR.USB
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
uboot_filename = UBOOT.USB
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
uboot_comp_filename =
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
dtb_meson_filename =
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
dtb_meson1_filename = _aml_dtb.PARTITION
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
dtb_meson1_enc_filename =
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
ddr_enc_filename =
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
uboot_enc_filename =
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
keys_filename =
platform = 0x0811
bin_params =
ddr_load = 0xfffc0000
ddr_run = 0xfffc0000
uboot_down =
uboot_decomp =
uboot_enc_down =
uboot_enc_run =
uboot_load = 0x200c000
uboot_run = 0xfffc0000
bl2_params = 0xfffcc000
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
nb_partitions = 9
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符
awk: 命令行:1: 警告: 正则表达式中的转义序列“"”不是有效的操作符

Partition list

0 _aml_dtb.PARTITION _aml_dtb normal
1 bootloader.PARTITION bootloader normal
2 impdata.PARTITION impdata sparse
3 logo.PARTITION logo normal
4 recovery.PARTITION recovery normal
5 rootsys.PARTITION rootsys normal
6 system.PARTITION system sparse
7 tclconfig.PARTITION tclconfig sparse
8 userdata.PARTITION userdata sparse

Bootloader/DTB files

bootloader_file = /tmp/aml-flash-tool-3fNa/bootloader.PARTITION
dtb_file = /tmp/aml-flash-tool-3fNa/_aml_dtb.PARTITION

Initializing ddr
Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null cwr /tmp/aml-flash-tool-3fNa/DDR.USB 0xfffc0000

  • Results ---------------------------------------------------
    ................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
    Transfer Complete! total size is 49152 Bytes

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null write /home/kitman/aml-linux-usb-burn/tools/usbbl2runpara_ddrinit.bin 0xfffcc000

  • Results ---------------------------------------------------
    ..
    Transfer Complete! total size is 32 Bytes

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null run 0xfffc0000

  • Results ---------------------------------------------------
    [update]Run at Addr fffc0000
    AmlUsbRunBinCode:ram_addr=fffc0000

........
Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null identify 7

  • Results ---------------------------------------------------
    AmlUsbIdentifyHost
    This firmware version is 3-0-0-0-0-1-0

[OK]
Running u-boot
Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null write /tmp/aml-flash-tool-3fNa/DDR.USB 0xfffc0000

  • Results ---------------------------------------------------
    ..
    Transfer Complete! total size is 49152 Bytes

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null write /home/kitman/aml-linux-usb-burn/tools/usbbl2runpara_runfipimg.bin 0xfffcc000

  • Results ---------------------------------------------------
    ..
    Transfer Complete! total size is 48 Bytes

Command -> /home/kitman/aml-linux-usb-burn/tools/update 2>/dev/null write /tmp/aml-flash-tool-3fNa/UBOOT.USB 0x200c000

  • Results ---------------------------------------------------
    ERR: write data to device failed

[KO]

Cleanup

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants