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

ARM/AARCH64 support? (RPi) #13

Open
klslz opened this issue Feb 14, 2021 · 7 comments
Open

ARM/AARCH64 support? (RPi) #13

klslz opened this issue Feb 14, 2021 · 7 comments

Comments

@klslz
Copy link

klslz commented Feb 14, 2021

Many users have the Tone 1 attached to the RPi.

I am wondering if you could provide binaries or even better the sources for the dfu tool.

I'd adapt the INSTALL scripts for RPiOS (Debian) myself.

THX

@numbqq
Copy link
Member

numbqq commented Feb 19, 2021

Hello @klslz

Yes you can build them from the source code here: https://github.com/numbqq/USB-Audio-2.0-Software-v6.1/tree/master/sc_usb_audio/module_dfu/host/xmos_dfu_linux

Simply type make to build.

@klslz
Copy link
Author

klslz commented Feb 19, 2021

Thx.

The sources on your link build a tone-dfu-tool.

What's the tone-burn-tool ? Which is used in the INSTALL script?

@klslz
Copy link
Author

klslz commented Feb 19, 2021

Now.

Despite the descriptions saying to use "tone-burn-tool -i xxx" on Linux - where I am not sure to find the sources , I tried the "tone-dfu-tool --download xxx" as being described for Mac_OS.

And it seems !?!? to have worked.
Toneboard 1 now shows up as Tone1 - as expected.

Bus 001 Device 003: ID 3353:a001  
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass          239 Miscellaneous Device
  bDeviceSubClass         2 
  bDeviceProtocol         1 Interface Association
  bMaxPacketSize0        64
  idVendor           0x3353 
  idProduct          0xa001 
  bcdDevice            2.00
  iManufacturer           1 Khadas
  iProduct                3 Tone1
  iSerial                 0 

@numbqq
Copy link
Member

numbqq commented Feb 20, 2021

Yes, it works.

@klslz
Copy link
Author

klslz commented Feb 20, 2021

Perhaps you should update the documentation. It's a bit confusing.

Anyhow.
The process also works on RPi4OS(Debian) (aarch64 ) and Fedora (x86_64).
I might release my own RPiOS installation script I wrote yesterday sooner or later. Let see.

Anyhow. Case close. Thx.

@ArtRoman
Copy link

I can't update VIM3 board on aarch64 linux host even after fixing dependencies in INSTALL script:
lib32z1 lib32stdc++6 lib32ncurses6 -> libz1 libstdc++6 libncurses6

update binary in aml-flash-tool/tools/linux-arm is 32-bit arm only and can't be run on 64-bit arm host:

aml-flash-tool/tools/linux-arm/update: cannot execute binary file: Exec format error

@poornimash
Copy link

poornimash commented Jun 9, 2023

I am having this issue, I am trying to update VIM3 device using another VIM3 device that is running Ubuntu18.04.
I edited the install script looking for 32 bit versions and I edited it to work on arm by changing
lib32z1 -> zlib1g
lib32stdc++6 -> libstdc++6
lib32ncurses5 -> libncurses5

I still got this error ./update: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory,
I then copied this file from my aarch64 folder to usr/lib folder and then get the error
./update: error while loading shared libraries: libusb-0.1.so.4: wrong ELF class: ELFCLASS64
Can you please advice on how to proceed?

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