In an effort to improve our product FAQs, we’re putting together a new FAQ guide for each product.
You can ask us any question regarding the:
VIM3L
VIM3
VIM2
VIM1
Tone Board
Edge
Edge-V
Captain
Accessories (M2X, Edge-IO, etc, etc)
Even if the question is embarrassing, you can still ask it. Please do not create feature requests as those only apply to future products.
Our engineers will do their best to answer each question, when they have the time. Then I will compile the most important questions into an FAQ for each product, that would be put onto our website.
Hello mate,
My first question (and probably the last) is why is the GPIO on the VIM 3 not following with the raspberry pi standard ?
If it was that standard it would have allowed the usage of Pi hats and other accessories available on the market.
@ravelo You are right . The purpose of this post is to collect questions and put them into FAQ . @Electr1 But we also welcome more suggestions for improvement of our products . I think a new post should be created for this kind of problem. This post is use for collect problems.
in fenix 0.8.x
for being able to build a mainline linux kernel which is of a newer version than the one hard coded inside (currently: 5.5-rc2),
where to find the patch set to be applied to the Linus Torvald’s code tree ?
or how to create them ?
I do have a question, what about chromium os on Vim3, i believe that hardware is more than capable to run it, if chrome os runs on older rockchip soc’s, then it shouldn’t be impossible to run chromium os on vim3?
Maybe someone can explain me, is the bigger problem here Arm or Amlogic, or someone with enough knowledge and will needs to make it?
hi guys, for tone board using as stand alone :
i need to know where is pin for external supply (not from USB port), and the input port for iis(i2s) for use the dac on khadas board. which version of tone board i need, vim or generic?
the vim version Run on windows10?
Hello, for power input, have a look here.
For I2S, see here.
Electrically speaking, both Tone Board versions are the same. The VIMs version has headers mounted for mating to the VIM SBCs’ GPIO.
Both should work on Windows 10. I have the VIMs version, it works on Windows 10. Windows has a driver.
For more information on the Tone Board, see here, and here.
Are there Debian Buster images for VIM2 somewhere with Panfrost kernel drivers included ? By github activity it looks like it was recently enabled, but unfortunately Debian images are not uploaded to https://dl.khadas.com/Firmware/VIM2/Debian/
Also, i understand VIM1 should use Lima driver, and this looks like it should be more available and stable, can someone confirm if DRI2 works under X11 with VIM1 and “official” Ubuntu builds ?
EDIT: Nevermind, just got VIM2 debian-buster built, works fine, image here
DRI2 desktop works, GLES2 everything is up and running. Still need to figure out video decode, but it’s looking good
I doubt as panfrost support for amlogic device was just merged in 5.7 kernel. I was finally able to run display manager with fbturbo driver but still it is using llvmpipe instead is panfrost for rendering.
No, lima work well with Wayland as x11 support is not there yet.
Can you share some glmark results ?
Try glmark2 -s 1980x1080
Also glxgears and see what does it use to render?
There is a customer received his Tone Board and he have installed it into his tube headphone amp project. It sounds great! You can see it in my links below.
One problem he do have occasionally is that after waking my computer up from sleep, it will no longer output sound until he disconnect and reconnect the USB connection. Is there any way to fix this?
I do have one idea, what about a needed features topic, where we could discuss about software support, things that we want to see supported.
Like for example, chromium accelerated support, vpu support for boards, accelerated desktop, some piece of hardware to work with our board, some part of the board driver support, like things users need and want to see supportd, i hope you understood me.
These are just examples, it would be like feature request topic, then some users wouldn’t have to open many new topics for their needs.