Jump to content

Recommended Posts

Posted
  On 2/4/2018 at 6:03 PM, Jose Deras said:
Expand  

Yes, I've seen this and tried but when I put 'console=both' or 'console=serial' into armbianEnv.txt the system won't boot up anymore, so I figured I might be doing something wrong. The docs aren't really "guiding" in that particular case.

Maybe I misunderstood the instructions? The - or + console is confusing to me at least and since it explicitly says "either boot.cmd OR armbianEnv.txt" I decided to not touch boot.cmd and stick to armbianEnv.txt, but yea... above happened.

Posted
  On 2/5/2018 at 9:21 PM, HackXIt said:

Maybe I misunderstood the instructions? The - or + console is confusing to me at least and since it explicitly says "either boot.cmd OR armbianEnv.txt" I decided to not touch boot.cmd and stick to armbianEnv.txt, but yea... above happened.

Expand  

 

You can edit boot.cmd (and recompile to boot.scr), but it is not recommended if you are not confident in what you are doing. 

 

It is possible that this feature is broken for this board. Since this is nothing critical, I guess nobody pays attention.

 

Thanks for pointing this out. Will be checked why is this so.

Posted

Tinkerboard Onboard audio is now available out of the box for build-it-yourself enthusiasts on default kernel.  :beer: New image should be ready in the following days.

Posted

Congrats, now let's fix the CSI support. :P According to  this issue, OV5647 (RPi 5MP cam) and IMX219 (RPI 8 MP cam) should work with upstream drivers.  The Rockchip ISP1 driver which was merged to 4.4 kernel in january should do the job and the Asus workaround with RK CIF ISP10 should no longer be needed. Unfortunately I fail when I compile a kernel with the needed drivers. 

When I adjust the kernel to activate the needed drivers, the board doesn't come up. 

 CONFIG_REGULATOR_TPS65910=y
 CONFIG_MEDIA_SUPPORT=y
 CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+CONFIG_VIDEO_V4L2_SUBDEV_API=y
 CONFIG_MEDIA_USB_SUPPORT=y
 CONFIG_USB_VIDEO_CLASS=y
 # CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV is not set
 # CONFIG_USB_GSPCA is not set
 CONFIG_V4L_PLATFORM_DRIVERS=y
+CONFIG_VIDEO_ROCKCHIP_ISP1=y
 CONFIG_SOC_CAMERA=y
 CONFIG_VIDEO_RK_CIF_ISP10=y
 CONFIG_V4L_MEM2MEM_DRIVERS=y
 CONFIG_VIDEO_ROCKCHIP_RGA=y
 CONFIG_VIDEO_ROCKCHIP_VPU=y
 CONFIG_V4L_TEST_DRIVERS=y
+# CONFIG_MEDIA_SUBDRV_AUTOSELECT is not set
+CONFIG_VIDEO_TC35874X=y
+CONFIG_VIDEO_IMX219=y
+CONFIG_VIDEO_OV5647=y
 CONFIG_DRM=y
 CONFIG_DRM_ROCKCHIP=y
 CONFIG_ROCKCHIP_DW_HDMI=y

Bootlog from serial console:

  Reveal hidden contents

 

see config file in attachment to reproduce it.  The LED on the tinkercam shines during boot (it doesn't do it with normal armbian Image).  Any suggestions to solve it are appreciated. :)

 

linux-rockchip-default.configFetching info...

Posted

Hello Bluetooth.  Thanks @Igor for the services help, loading on boot no problem.  Played some music through the board from my phone over Bluetooth, nice and smooth.

 

DWsMtcRVwAAgtKx.jpg:large

Posted
  On 2/23/2018 at 3:58 AM, TonyMac32 said:

Hello Bluetooth.  Thanks @Igor for the services help, loading on boot no problem.  Played some music through the board from my phone over Bluetooth, nice and smooth.

Expand  

Does this improve the chances of my wireless keyboard working? It's not bluetooth exactly, it's got it's own proprietary dongle. It works on the mainline kernel, but not 4.4, even though the keyboard is ancient. I wonder if there are some kernel config options that are needed to support USB interfaces that are enabled in the mainline, but not in 4.4? I'm really looking forward to the new image, even if I have to bring my keyboard home from work to test!

Posted
  On 2/23/2018 at 7:59 PM, bedalus said:
Does this improve the chances of my wireless keyboard working? It's not bluetooth exactly, it's got it's own proprietary dongle. It works on the mainline kernel, but not 4.4, even though the keyboard is ancient. I wonder if there are some kernel config options that are needed to support USB interfaces that are enabled in the mainline, but not in 4.4? I'm really looking forward to the new image, even if I have to bring my keyboard home from work to test!
Are there Linux drivers for that keyboard? I feel like we talked about that before, do you have the lsusb output while it's plugged in?

Sent from my Pixel using Tapatalk

Posted
  On 2/23/2018 at 8:15 PM, TonyMac32 said:

Are there Linux drivers for that keyboard? I feel like we talked about that before, do you have the lsusb output while it's plugged in?

Expand  

Good memory, yes I tried to diff the config on the page 14, but page 15:

...is where I detailed most of my findings. Looks like the dongle started working between 4.11 and 4.12

Posted
  On 2/21/2018 at 3:28 AM, TonyMac32 said:

Tinkerboard Onboard audio is now available out of the box for build-it-yourself enthusiasts on default kernel.  :beer: New image should be ready in the following days.

Expand  

I've downloaded the "Ubuntu desktop - legacy kernel" from the armbian main page and flashed it, did "apt update && apt upgrade" and yet the sound doesn't seem to be working for me.
So I'm guessing the "default" kernel is something else?

BTW
Sound once worked when I did the fix in the Tinkerboard Sound Post of yours. I'm simply wondering what you're referring to, since I'm not the brightest linux kid around and I tend to get confused by all the kernel terminology.

I'm trying to hop onto the tinkerboard train again to use it as my main development station for µController related stuff and would certainly like to help here with any testing or such, as long as I know what I am doing.

Posted
  On 2/27/2018 at 6:59 PM, HackXIt said:
I've downloaded the "Ubuntu desktop - legacy kernel" from the armbian main page and flashed it, did "apt update && apt upgrade" and yet the sound doesn't seem to be working for me.
So I'm guessing the "default" kernel is something else?

BTW
Sound once worked when I did the fix in the Tinkerboard Sound Post of yours. I'm simply wondering what you're referring to, since I'm not the brightest linux kid around and I tend to get confused by all the kernel terminology.
The image hasn't been updated yet, the changes are primarily in asound.conf and default.pa, which don't get touched on package upgrades. If you have a kernel dated after my update, then you can modify those with

https://github.com/armbian/build/blob/master/packages/bsp/rockchip/pulseaudio.txt

*Insert in where it lists modules*

and

https://github.com/armbian/build/blob/master/packages/bsp/rockchip/asound.conf

*Copy/add depending on if you have one or not*

Sent from my Pixel using Tapatalk

Posted
  On 2/27/2018 at 7:07 PM, TonyMac32 said:

The image hasn't been updated yet, the changes are primarily in asound.conf and default.pa, which don't get touched on package upgrades. If you have a kernel dated after my update, then you can modify those with

https://github.com/armbian/build/blob/master/packages/bsp/rockchip/pulseaudio.txt

*Insert in where it lists modules*

and

https://github.com/armbian/build/blob/master/packages/bsp/rockchip/asound.conf

*Copy/add depending on if you have one or not*

Sent from my Pixel using Tapatalk
 

Expand  

I see. Great, I'll do that, thanks for the hint.

On another topic:

There is one thing that NEVER worked for me, which is "dpkg-reconfigure keyboard-configuration". That command changes the keyboard configuration, but the system either forgets or resets back to US keyboard-configuration after every reboot.
I honestly don't know why, I was mostly busy with other stuff.
If anyone got a hint as to why this happens, I would greatly appreciate it :)

Posted
  On 2/27/2018 at 7:13 PM, HackXIt said:

On another topic:

There is one thing that NEVER worked for me, which is "dpkg-reconfigure keyboard-configuration". That command changes the keyboard configuration, but the system either forgets or resets back to US keyboard-configuration after every reboot.
I honestly don't know why, I was mostly busy with other stuff.
If anyone got a hint as to why this happens, I would greatly appreciate it

Expand  

 

Posted

I've inserted the modules from the provided .txt and also added the file asound.conf to /etc/ with the contents from github.
However, after restarting now the pulseaudio sound server won't function properly anymore ("Connection refused" upon trying to connect)
Must have done something wrong somewhere?

Posted
  On 2/27/2018 at 8:10 PM, HackXIt said:
I've inserted the modules from the provided .txt and also added the file asound.conf to /etc/ with the contents from github.
However, after restarting now the pulseaudio sound server won't function properly anymore ("Connection refused" upon trying to connect)
Must have done something wrong somewhere?
Then the kernel must be older than the update. I patched in a rename of the soundcard I/O channels to make it match ASUS and make sense (spdif, headphone, BT VoIP). Let me get back to you when I have access to my machine. Worst case I'll upload a deb for you to install the new kernel if you can't build yourself.

Sent from my Pixel using Tapatalk

Posted
  On 2/27/2018 at 9:02 PM, TonyMac32 said:

Then the kernel must be older than the update. I patched in a rename of the soundcard I/O channels to make it match ASUS and make sense (spdif, headphone, BT VoIP). Let me get back to you when I have access to my machine. Worst case I'll upload a deb for you to install the new kernel if you can't build yourself.

Sent from my Pixel using Tapatalk
 

Expand  

How do I update the armbian kernel? I doubt I could build it myself, definitly don't have the skillset.

Sorry for the late reply, been a busy week.

 

About the keyboard configuration, I've settled with the fact to use the rather simple command: `setxkbmap at`
It's an easy one liner and I only have to do it once per boot.. Only works once x-environment has booted, so no init.d scripts for that simple command. But I'll see if there's another way to script it sometime. For now it will work, been distracting me with this for too long anyways.

Posted
  On 3/7/2018 at 6:42 PM, HackXIt said:
How do I update the armbian kernel? I doubt I could build it myself, definitly don't have the skillset.
Sorry for the late reply, been a busy week.
 
About the keyboard configuration, I've settled with the fact to use the rather simple command: `setxkbmap at`
It's an easy one liner and I only have to do it once per boot.. Only works once x-environment has booted, so no init.d scripts for that simple command. But I'll see if there's another way to script it sometime. For now it will work, been distracting me with this for too long anyways.
New 4.4 based images were released containing the updates.

Sent from my Pixel using Tapatalk

Posted
  On 3/7/2018 at 6:59 PM, TonyMac32 said:

New 4.4 based images were released containing the updates.

Sent from my Pixel using Tapatalk
 

Expand  

From the main armbian page or on github? I've used the armbian mainline download (from the armbian website)... But I guess I gotta redo ? Is there no way to not use a complete new image? Kinda tough to reconfigure everything now.

Posted

If you are using mainline kernel (4.14) you have to follow the instructions detailed in the thread dedicated to Tinker Board sound, that update has not been rolled out yet. If you are using 4.4 kernel you should, after installing all the files, simply have to apt update and upgrade now.

Sent from my Pixel using Tapatalk

Posted
  On 3/7/2018 at 7:59 PM, HackXIt said:
uname -r
4.4.112-rockchip

I guess I have it. I'll try copying the files again.
 

Expand  

Nope. Still same result, no audio. No pulse server.
Maybe I didn't delete some lines that should have been deleted? Here's my default.pa:

#!/usr/bin/pulseaudio -nF
#
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2 of the License, or
# (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.

# This startup script is used only if PulseAudio is started per-user
# (i.e. not in system mode)

.nofail

### Load something into the sample cache
#load-sample-lazy x11-bell /usr/share/sounds/freedesktop/stereo/bell.oga
#load-sample-lazy pulse-hotplug /usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy pulse-coldplug /usr/share/sounds/freedesktop/stereo/device-added.oga
#load-sample-lazy pulse-access /usr/share/sounds/freedesktop/stereo/message.oga

.fail

### Automatically restore the volume of streams and devices
load-module module-device-restore
load-module module-stream-restore
load-module module-card-restore

### Automatically augment property information from .desktop files
### stored in /usr/share/application
load-module module-augment-properties

### Should be after module-*-restore but before module-*-detect
load-module module-switch-on-port-available

### Load audio drivers statically
### (it's probably better to not load these drivers manually, but instead
### use module-udev-detect -- see below -- for doing this automatically)
#load-module module-alsa-sink
load-module module-alsa-sink device=OnBoard_D0 sink_properties=device.description="BT_VOIP-Output"
load-module module-alsa-sink device=OnBoard_D1 sink_properties=device.description="SPDIF-Output"
load-module module-alsa-sink device=OnBoard_D2 sink_properties=device.description="Headset-Output"
#load-module module-alsa-source device=hw:1,0
load-module module-alsa-source device=OnBoard_D0 source_properties=device.description="BT_VOIP-Input"
load-module module-alsa-source device=OnBoard_D1 source_properties=device.description="Headset-Input"


### Automatically load driver modules depending on the hardware available
.ifexists module-udev-detect.so
load-module module-udev-detect tsched=0
.else
### Use the static hardware detection module (for systems that lack udev support)
load-module module-detect
.endif

### Automatically connect sink and source if JACK server is present
.ifexists module-jackdbus-detect.so
.nofail
load-module module-jackdbus-detect channels=2
.fail
.endif

### Automatically load driver modules for Bluetooth hardware
.ifexists module-bluetooth-policy.so
load-module module-bluetooth-policy
.endif

.ifexists module-bluetooth-discover.so
load-module module-bluetooth-discover
.endif

### Load several protocols
.ifexists module-esound-protocol-unix.so
load-module module-esound-protocol-unix
.endif
load-module module-native-protocol-unix

### Network access (may be configured with paprefs, so leave this commented
### here if you plan to use paprefs)
#load-module module-esound-protocol-tcp
#load-module module-native-protocol-tcp
#load-module module-zeroconf-publish

### Load the RTP receiver module (also configured via paprefs, see above)
#load-module module-rtp-recv

### Load the RTP sender module (also configured via paprefs, see above)
#load-module module-null-sink sink_name=rtp format=s16be channels=2 rate=44100 sink_properties="device.description='RTP Multicast Sink'"
#load-module module-rtp-send source=rtp.monitor

### Load additional modules from GConf settings. This can be configured with the paprefs tool.
### Please keep in mind that the modules configured by paprefs might conflict with manually
### loaded modules.
.ifexists module-gconf.so
.nofail
load-module module-gconf
.fail
.endif

### Automatically restore the default sink/source when changed by the user
### during runtime
### NOTE: This should be loaded as early as possible so that subsequent modules
### that look up the default sink/source get the right value
load-module module-default-device-restore

### Automatically move streams to the default sink if the sink they are
### connected to dies, similar for sources
load-module module-rescue-streams

### Make sure we always have a sink around, even if it is a null sink.
load-module module-always-sink

### Honour intended role device property
load-module module-intended-roles

### Automatically suspend sinks/sources that become idle for too long
load-module module-suspend-on-idle

### If autoexit on idle is enabled we want to make sure we only quit
### when no local session needs us anymore.
.ifexists module-console-kit.so
load-module module-console-kit
.endif
.ifexists module-systemd-login.so
load-module module-systemd-login
.endif

### Enable positioned event sounds
load-module module-position-event-sounds

### Cork music/video streams when a phone stream is active
#load-module module-role-cork

### Modules to allow autoloading of filters (such as echo cancellation)
### on demand. module-filter-heuristics tries to determine what filters
### make sense, and module-filter-apply does the heavy-lifting of
### loading modules and rerouting streams.
load-module module-filter-heuristics
load-module module-filter-apply

# X11 modules should not be started from default.pa so that one daemon
# can be shared by multiple sessions.

### Load X11 bell module
#load-module module-x11-bell sample=x11-bell

### Register ourselves in the X11 session manager
#load-module module-x11-xsmp

### Publish connection data in the X11 root window
#.ifexists module-x11-publish.so
#.nofail
#load-module module-x11-publish
#.fail
#.endif

### Make some devices default
#set-default-sink output
#set-default-source input



 

Posted

I think running apt update and apt upgrade should give you 4.4.117 or 119 since the new image came out. @Igor the repo was updated, correct?

If not, the link I shared in the new kernel testing thread has the most recent kernel packages in it, with the audio updates. Install those, verify you have 4.4.(newer than 112), then reinstall all the files you deleted, they are necessary.

(I'm working off my phone at the moment, I apologize for curtness or spelling errors)

Sent from my Pixel using Tapatalk

Posted

Does Bluetooth Audio only work on the 4.4 default kernal? Or is it working on the new 4.14 mainline kernel? .. I spent all weekend configuring a new 4.14 install and now want to send audio to a bluetooth speaker (Amazon Echo).

Posted
  On 3/11/2018 at 6:31 PM, mfarley said:

Does Bluetooth Audio only work on the 4.4 default kernal? Or is it working on the new 4.14 mainline kernel? .. I spent all weekend configuring a new 4.14 install and now want to send audio to a bluetooth speaker (Amazon Echo).

Expand  

 

I'm afraid at present it only works with 4.4.  I can't give you a very good reason for this, the rtk_hciattach program simply refuses to function properly with the Tinkerboard on 4.14.  @Myy and myself spent some time working on it https://github.com/Miouyouyou/MyyQi/issues/7, I got some progress toggling the BT gpio's manually, Myy wrote a driver to help, but in the end it simply refused.  Now, I lost track of it long before the conversation was over, and I will be trying to move some of the progress from the default image to the Next image, so I will have another go of it, and I know there were some efforts to make it mainline without needing that attach tool at all, I'll have to see what became of that.

Posted

You can always contribute to the project (big "Donate Now" button at the bottom right of this page), I know that Myy has some links in Github for donations, as for myself I have an amazon wishlist for those interested (only shared on request), it's how I get some hardware for support purposes that I wouldn't buy on my own (like the RPi touchscreen).

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

Important Information

Terms of Use - Privacy Policy - Guidelines