35 35
Peba

Asus Tinkerboard

Recommended Posts

Hmmm, no idea, that doesn't actually look like a bluetooth keyboard, to be honest, it's just popping up as a standard generic HID device.

 

[    1.996363] usb 1-1.3: new low-speed USB device number 3 using dwc2
[    2.079542] usb 1-1.3: New USB device found, idVendor=046e, idProduct=5577
[    2.079556] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.079566] usb 1-1.3: Product: USB Multimedia Cordless Keyboard
[    2.079574] usb 1-1.3: Manufacturer: BTC
[    2.083962] input: BTC USB Multimedia Cordless Keyboard as /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0
[    2.135850] hid-generic 0003:046E:5577.0001: input,hidraw0: USB HID v1.11 Keyboard [BTC USB Multimedia Cordless Keyboard] on usb-ff540000.usb-1.3/input0
[    2.143143] input: BTC USB Multimedia Cordless Keyboard as /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:046E:5577.0002/input/input1
[    2.195087] hid-generic 0003:046E:5577.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [BTC USB Multimedia Cordless Keyboard] on usb-ff540000.usb-1.3/input1

perhaps if you could boot the other images that don't recognize it, with it plugged in, and do the same thing?  I'm kind of curious now...

Share this post


Link to post
Share on other sites

I would if I could, but I've no way to log into the device on the standard images as this is my only keyboard! Maybe they'd let me borrow one from work.

 

I have to say thanks thanks for all your work and input in this thread. When I got this device I was unaware of armbian, and happened to discover it because you posted a link in the asus forum: https://tinkerboarding.co.uk/forum/thread-330.html

 

I found armbian and its users so interesting I must have read this entire thread two or three times! If you follow the link above you can see how I followed your example with GPIO power and an uprated heatsink and was able to hacksaw a hole into my case and attach a little fan! You can even see my dongle :o

Share this post


Link to post
Share on other sites
On 7/25/2017 at 5:43 AM, RickyTerzis said:

external HDD's assuming they won't spin up on the USB alone.

I haven't had a problem powering a 2.5" hard drive from the USB port

 

It's much better than my Pine64 boards. They reboot when plugged in and the hard drive refuses to spin up.

Share this post


Link to post
Share on other sites

Try to execute lsmod on the working kernel. Since most drivers are compiled modules, that should tell you what is the driver, I think. Then, from the module name, you can retrace the config option required and its dependencies.

 

It might also be possible to determine the driver used using /sys nodes. But I don't know how exactly. udevadm can also help you.

 

But yeah, try lsmod first.

Share this post


Link to post
Share on other sites

But wait... you got Bluetooth working on 4.12 kernels ? Are you using an external Bluetooth dongle or did you just start your Bluetooth keyboard and it worked out the box ?

 

Edit : Ah, didn't read correctly, you're using an external dongle. Well given the bad feedback I got from the tinkering forum on the internal Bluetooth, I guess it's the best choice.

Share this post


Link to post
Share on other sites
root@tinkerboard:/home/bedalus# lsmod
Module                  Size  Used by
snd_soc_hdmi_codec     16384  0
r8723bs               552960  0
dw_hdmi_i2s_audio      16384  0
mali_kbase            319488  0

Nothing to see with lsmod. However, udevadm gives me:

root@tinkerboard:/home/bedalus# udevadm info --query=all /dev/input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd 
P: /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0/event0
N: input/event0
S: input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd
S: input/by-path/platform-ff540000.usb-usb-0:1.3:1.0-event-kbd
E: BACKSPACE=guess
E: DEVLINKS=/dev/input/by-path/platform-ff540000.usb-usb-0:1.3:1.0-event-kbd /dev/input/by-id/usb-BTC_USB_Multimedia_Cordless_Keyboard-event-kbd
E: DEVNAME=/dev/input/event0
E: DEVPATH=/devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0/event0
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_MODEL=USB_Multimedia_Cordless_Keyboard
E: ID_MODEL_ENC=USB\x20Multimedia\x20Cordless\x20Keyboard
E: ID_MODEL_ID=5577
E: ID_PATH=platform-ff540000.usb-usb-0:1.3:1.0
E: ID_PATH_TAG=platform-ff540000_usb-usb-0_1_3_1_0
E: ID_REVISION=0310
E: ID_SERIAL=BTC_USB_Multimedia_Cordless_Keyboard
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:030101:030102:
E: ID_USB_INTERFACE_NUM=00
E: ID_VENDOR=BTC
E: ID_VENDOR_ENC=BTC
E: ID_VENDOR_ID=046e
E: MAJOR=13
E: MINOR=64
E: SUBSYSTEM=input
E: USEC_INITIALIZED=4130433
E: XKBLAYOUT=us
E: XKBMODEL=pc105

So usbhid. I think I'll borrow a keyboard from work then we can find out for sure. IKONFIG is set, so if I'm able to use a different keyboard and log in, I can diff the exact config used against the nightly.

Share this post


Link to post
Share on other sites

My tinker board appears to have crashed again after 1.8 weeks of uptime.
Power supply is the micro-USB "official" RPi one, and it's rated at 2.5A , the SD card appears to be fine.

Symptoms:

  1. Only the red led was powered on, I had no green (I/O) or yellow led (heartbeat) activity.
  2. When removing the power cord and reinserting it, it would power-on for a couple of seconds and then it would power-off by itself.
  3. I left it powered-off for around 2 minutes and then powered it on and it's working ok so far.
  4. I checked my graphs and I see that over the course of the last 2 weeks, the CPU was sustaining temps between 61-65.5 °C.
  5. Right now I'm noticing a 74°C temperature spike, which is slowly coming down to the previously observed temperatures. (This graph displays the last 24h)
    Temps2.png.595a85548a1499807bfe50c8bbdf23c4.png

I'm not sure why the CPU raises it's temperature if the system has crashed. I've also reviewed the syslog and kernel logs, but I cannot find anything that would point me to the cause of the crash.

It also must've refused to start because it was overheated, but why does it always work fine for almost two weeks and then suddenly decides to die? I would appreciate any pointers to help me investigate.

Using mainline kernel.

root@Tuxbox:~# lsb_release -a && uname -r
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.2 LTS
Release:        16.04
Codename:       xenial
4.11.6-rockchip

 

Share this post


Link to post
Share on other sites

IIRC, because of Log2Ram it will not write to SDcard when it crashes. You would have to write the data/logs to another storage device USB-Stick or something externally.

Beside with RPi-Monitor you might also be able to collect some data - is WIP.

Share this post


Link to post
Share on other sites
17 minutes ago, Igor said:

Power via GPIO.


Are there any instructions available? Any precautions, etc? Thanks.
PS: In the meantime, can I somehow downclock the SoC a little bit? Would that help any?

Share this post


Link to post
Share on other sites
On 2017-7-26 at 5:53 AM, TonyMac32 said:

Hmmm, no idea, that doesn't actually look like a bluetooth keyboard, to be honest, it's just popping up as a standard generic HID device.

 


[    1.996363] usb 1-1.3: new low-speed USB device number 3 using dwc2
[    2.079542] usb 1-1.3: New USB device found, idVendor=046e, idProduct=5577
[    2.079556] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.079566] usb 1-1.3: Product: USB Multimedia Cordless Keyboard
[    2.079574] usb 1-1.3: Manufacturer: BTC
[    2.083962] input: BTC USB Multimedia Cordless Keyboard as /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.0/0003:046E:5577.0001/input/input0
[    2.135850] hid-generic 0003:046E:5577.0001: input,hidraw0: USB HID v1.11 Keyboard [BTC USB Multimedia Cordless Keyboard] on usb-ff540000.usb-1.3/input0
[    2.143143] input: BTC USB Multimedia Cordless Keyboard as /devices/platform/ff540000.usb/usb1/1-1/1-1.3/1-1.3:1.1/0003:046E:5577.0002/input/input1
[    2.195087] hid-generic 0003:046E:5577.0002: input,hiddev96,hidraw1: USB HID v1.11 Mouse [BTC USB Multimedia Cordless Keyboard] on usb-ff540000.usb-1.3/input1

perhaps if you could boot the other images that don't recognize it, with it plugged in, and do the same thing?  I'm kind of curious now...

 

Well, I was allowed to borrow a USB keyboard from work, and I flashed the standard version with the mainline kernel, and...

[    2.033927] usb 1-1.3: new low-speed USB device number 3 using dwc2
[    2.116818] usb 1-1.3: New USB device found, idVendor=046e, idProduct=5577
[    2.116831] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.116841] usb 1-1.3: Product: USB Multimedia Cordless Keyboard
[    2.116850] usb 1-1.3: Manufacturer: BTC
[    2.212636] usb 3-1: config 1 has an invalid interface number: 255 but max is 6
[    2.212648] usb 3-1: config 1 has no interface number 6
[    2.214117] usb 3-1: New USB device found, idVendor=0bda, idProduct=481a
[    2.214130] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    2.214139] usb 3-1: Product: USB Audio
[    2.214148] usb 3-1: Manufacturer: Generic
[    2.214156] usb 3-1: SerialNumber: 201405280001

...

[    4.333263] input: Generic USB Audio as /devices/platform/ff500000.usb/usb3/3-1/3-1:1.255/0003:0BDA:481A.0003/input/input1
[    4.385590] hid-generic 0003:0BDA:481A.0003: input,hiddev0,hidraw0: USB HID v1.11 Device [Generic USB Audio] on usb-ff500000.usb-1/input255

 

USB 1-1.3 never gets allocated as an input device, even though it's detected (USB 3-1 later gets a device, which are the bottom two lines after I cut an irrelevant section). So perhaps something to do with some hid options? I took the diff between the configs:

 

> CONFIG_HID_ACCUTOUCH=m
...
> CONFIG_HID_CP2112=m
...
> CONFIG_HID_NTI=m

Not sure if these are relevant, it's difficult for me to guess whether it was a config option that helped, maybe it was just some mainline commit that fixed something between 4.11 and 4.12. 

 

Anyway, if you want to pursue the reason, I've attached the output of armbianmonitor -u and the diff between the two kernel configs. I'm out of ideas, but happy and lucky to have a working cordless keyboard!

armhwinfo.log

config.diff

Share this post


Link to post
Share on other sites
On 16/05/2017 at 7:31 AM, tkaiser said:

minerd --benchmark

[...] I would recommend testing with cpuminer (minerd --benchmark) since this tool provides a khash/sec output so you're able to detect throttling pretty easy. [...] If you Tinkerboard owners are able to improve heat dissipation that much that you get a constant +8 khash/sec value then you start to test for powering problems on this board.

 

EDIT: I deleted a lot of the results I just posted after re-reading the thread... It's all been done before! I got similar resuls as others who've done the test, around 6.6khash/s followed five minutes later by a decline to around 6.1, caused by thermal throttling to ~1.7GHz.

 

At least I seem to have a stable setup. Any other tests I can run on armbian's behalf? Anything I can do to help, I'm happy to give it a go.

Share this post


Link to post
Share on other sites

Thanks for your hard work getting the Tinkerboard running Armbian guys!

On 17/07/2017 at 1:57 PM, lafalken said:

Sounds great! Would like to see an clean version without desktop too.  

 

I would like to use this card as webb server, but is it stable enough for such use? For that I would use a usb-hdd, network cable and power. All other things like wireless is of no use for me. But a reboot that does not work is not very good ;(

I'd like to use it headless as well running Debian instead of Ubuntu, transcoding would be a bonus, but not required!

 

I'm currently not using the board, waiting for things to stabilise a bit more..  I've set it up (with a 3amp PSU) & it's ready to go. I'm more than happy to test some images on it though if needed.

Share this post


Link to post
Share on other sites

I've been waiting for my Sentio Superbook to turn up (I think it will arrive in a month or two) so I haven't had much use for my tiny portable desktop, which has gathered some dust over the last few weeks. I've sneezed it off, and flashed the lastest nightly Armbian_5.32.170916_Tinkerboard_Ubuntu_xenial_dev_4.13.0_desktop.7z (2017-09-15 08:10 589.2 MB)

 

I'm happy to report that my bluetooth keyboard continues to work with the nightlies, and since the last version I tested, I'm extremely pleased to now find that there is a login screen. Also, Chromium now works again. Another thing that had bugged me, being prompted for admin password for wifi reconnect, has now been fixed. I'm well chuffed.

Share this post


Link to post
Share on other sites

I would recommend using the last 4.12 image for now, there is a bug messing up the thermals so I'm not sure if it's wholly safe.  There is a pointer error occurring while initializing the tsadc, and I've not been able to track it down yet.  

 

@Igor it would be best to pull the 4.13 images if possible, they don't actually provide any additional functionality, I was hoping to have this cleaned up yesterday, but it wasn't as simple as I thought.  With broken thermal zones and this board's garbage heatsink...

 

@Myy can you confirm that the tsadc is working on your 4.13 kernel?  I'm working my way through the patches/drivers/etc, but confirmation it is/isn't a 4.13 problem would be great.

Share this post


Link to post
Share on other sites
Just now, TonyMac32 said:

@Igor it would be best to pull the 4.13 images if possible, they don't actually provide any additional functionality, I was hoping to have this cleaned up yesterday, but it wasn't as simple as I thought.  With broken thermal zones and this board's garbage heatsink...

 

True. I removed old nightly builds and their creating until this is not solved.

Share this post


Link to post
Share on other sites
On 9/16/2017 at 9:25 AM, tkaiser said:

 

Can you please post the output of 'psd p' please (should look like https://wiki.archlinux.org/index.php/profile-sync-daemon#Preview_.28parse.29_mode and I'm interested in activation mode and overlayfs size) 

bedalus@tinkerboard:~$ psd p
Profile-sync-daemon v6.31 on Ubuntu 16.04.3 LTS

 Systemd service is currently inactive.
 Systemd resync-timer is currently inactive.
 Overlayfs v23 is currently active.

Psd will manage the following per /home/bedalus/.config/psd/psd.conf:

 browser/psname:  chromium/chromium
 owner/group id:  bedalus/1000
 sync target:     /home/bedalus/.config/chromium
 tmpfs dir:       /run/user/1000/bedalus-chromium
 profile size:    42M
 overlayfs size:  
 recovery dirs:   none

 

Share this post


Link to post
Share on other sites
1 minute ago, bedalus said:

Systemd service is currently inactive.
Systemd resync-timer is currently inactive.

 

Thank you, then it's not just me. And there is something wrong: https://github.com/armbian/build/blob/8d211eec2c15feb1e77d8dee7bf45ee7ef645eab/packages/bsp/common/etc/profile.d/check_first_login.sh#L13-L32

 

With psd active your Chromium performance will increase by magnitudes.

Share this post


Link to post
Share on other sites

Guys, does anyone know what's the deal with those 2x2 and 1x2 pin header placeholders? They must have some role yet I found nothing on the internet and the Asus support guys aren't much of a help, they keep referring to the GPIO headers :-)))

asustinker1.jpg

Share this post


Link to post
Share on other sites

The "outboard" 2 pins on the 2x2 are the power button inputs.  The other two on that connector, I've heard various things but haven't done anything with personally.  The 1x2 is S/PDIF I believe.

Share this post


Link to post
Share on other sites

Hello. I installed armbian on my tinkerboard but when I install packets python with PIP I have problems of access right. I also have problems with the Network Manager where I can not change connection. Everything is grayed out.

how to remedy these 2 problems of right of access that I think are related.

Share this post


Link to post
Share on other sites
3 minutes ago, dragonlost said:

when I install packets python with PIP I have problems of access right. I also have problems with the Network Manager where I can not change connection. Everything is grayed out.

 

What image did you use, and what did you use to flash it to the SD card?  I have not encountered any issues with network manager in my testing/use.  For Python I'm afraid I'm not the expert resource.  

Share this post


Link to post
Share on other sites

I use image : Armbian_5.33_Tinkerboard_Ubuntu_xenial_next_4.13.3_desktop . I use etcher for flash sdcard.

 

I have no problem with network manager just permission connection editing problem. What are permission for editing connection in network manger ?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
35 35