I’m trying to build an internet radio and spotify client using volumio. For this I want to use following hardware:
ODROID C2 with 8GB eMMC
HiFi Shield+ (Hardkernel)
7" capacitive touch display type C from waveshare
Edimax WiFi stick
Volumio 2.344 for ODROID C2
However, after installing volumio I stumbled in to several problems:
The volume can not be changed. After setting the volume in the web interface to e.g. 50% the system sets it back to 100%.
The touch plugin does not work. During installation it gets stuck at the step Disabling Kiosk service (I waited more than half an hour…). However, if I reboot the system the display shows the frontend of volumio but the touch function is not working.
I also tried to realize this with a raspberry pi 3 type B and the HifiBerry DAC+ and in this setting everything works fine. However, this system is very slow. Booting takes about the 1 minute and 20 seconds whereas the ODROID C2 only needs 35 seconds to boot. For 1 minute boot time is too long, so that is no option for me.
Does anyone have any idea what I could do to get this run with ODROID C2?
I would really be grateful for some help.
I’ve had a good search through the forum and I can’t see anything relevant to your situation. You might have more success with a larger audience on the HardKernel forums? Let us know how you get on though please.
The HiFi Shield+ seems to be using PCM5102 DAC chip and it doesn’t have hardware volume control. You will have to select software volume control to get that to work.
if test “${mesontimer}” = “0”; then fdt rm /meson_timer; fdt rm /cpus/cpu@0/timer; fdt rm /cpus/cpu@1/timer; fdt rm /cpus/cpu@2/timer; fdt rm /cpus/cpu@3/timer; fi
if test “${mesontimer}” = “1”; then fdt rm /timer; fi
if test “${nographics}” = “1”; then fdt rm /reserved-memory; fdt rm /aocec; fi
if test “${nographics}” = “1”; then fdt rm /meson-fb; fdt rm /amhdmitx; fdt rm /picdec; fdt rm /ppmgr; fi
if test “${nographics}” = “1”; then fdt rm /meson-vout; fdt rm /mesonstream; fdt rm /meson-fb; fi
if test “${nographics}” = “1”; then fdt rm /deinterlace; fdt rm /codec_mm; fi
@KKMan:
I did not realize that the HiFi Shield+ has no hardware volume setup control. However, if I set the Mixer Type to software the system freezes and I have to restart it. After restart, the Mixer Type is set to none again. Anyhow, if I can solve this problem by using the HiFi Shield 2 or another soundcard that is fine for me.
@brachiopode:
I already used an adapted boot.ini. And the display works already. What does not work is the touch function. Unfortunately my odroid doesn’t start up with your boot.ini. I do not know the reason. The only differences I can see is the HDMI BPP Mode.
Here a snippet of your boot.ini
[code]# HDMI BPP Mode
setenv m_bpp “32”
setenv m_bpp “24”
setenv m_bpp “16”[/code]
And here a snippet of my boot.ini
[code]# HDMI BPP Mode
setenv m_bpp “32”
setenv m_bpp “24”
setenv m_bpp “16”[/code]
The rest is identical. Maybe I will flash my the eMMC again and try it from scratch.
@chsims1:
I already had look at Hardkernel forums and I also have found a thread about pretty much the same problem regardin touch functionality: https://forum.odroid.com/viewtopic.php?t=24651
However, I could not get it running on my system, yet. Don’t know what I am doing wrong. The good news is that this problem seems to be already addressed to volumio and there will be an update with a new release as I read this thread correctly. Anyhow, I would like to get this running already without new software release.
the Odroid Image has a few boot.ini’s for various Hardkernel displays (VU5/VU7/VU7+)
As the display was already working, you had it figured out.
boot.ini is irrelevant for the touch part, expect perhaps for the disable_VU7 part.
The HK displays need a corresponding hid touch driver, this display also gets connected to the usb otg port.
Our image uses the hid driver which was inserted into the Volumio-specific kernel.
As for the waveshare display, you should check the Hardkernel forum as chsims1 suggested.
There are some discussion regarding waveshare, perhaps you can get help there.
Maybe a silly question. If you have connected the monitor only with HDMI. For the touch function, the monitor must also be connected via the Micro USB socket.
The disable_VU7 part in the boot.ini was a good hint I think. If I understand this right, the following snippets show that the dwav_usb_mt driver is loaded for the touch screen, which is intended vor the vu7 display and does not work with the waveshare display.
volumio@volumio:~$ lsusb -t
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=dwav_usb_mt, 12M
...
volumio@volumio:~$ dmesg|grep 'usb\|hid'
...
[ 5.695450] input: WaveShare WaveShare Touchscreen as /devices/platform/dwc2_a/usb2/2-1/2-1:1.0/input/input2
[ 5.701668] dwav_usb_mt 2-1:1.0: ODROID VU7 MultiTouch(800x480)
...
With Ubuntu and disable_VU7 set to “true” in boot.ini a hid-multitouch driver is loaded:
odroid@odroid64:~$ dmesg|grep 'usb\|hid'
...
[ 11.277563] input: WaveShare WaveShare Touchscreen as /devices/platform/dwc2_a/usb2/2-1/2-1:1.0/0003:0EEF:0005.0001/input/input2
[ 11.277848] hid-multitouch 0003:0EEF:0005.0001: input,hidraw0: USB HID v1.11 Device [WaveShare WaveShare Touchscreen] on usb-dwc2_a-1/input0
...
However, adding the line
setenv disable_vu7 "true"
to boot.ini has no effect with volumio. It seems like this software switch, as it is available for android and ubuntu for the odroid c2, is not implemented in volumio. So now I need to find out how to load the correct driver for the display but I could not find the answer, yet.
Hi,
this could be, I have not pulled the kernel from the Hardkernel repo for ages.
There was never a real reason for it, because nothing big “audio”-related ever changed.
So now there is a reason to.
According to Murphy’s law I just built a new version yesterday, of course without Hardkernel changes.
Need to schedule a new build.
Meanwhile I will move this topic to the Community Portings Odroid section and follow up there
@rusty: Time frame?
Sorry, we never give time frames unless nearly finished.
Your are talking to volunteers with jobs and family.
Consider it done when finished :mrgreen:
OK, thank you again for your help.
I’m already grateful, that you plan to resolve this issue. That is already a big help for me.
I did not want to act pushy.
