All Activity
This stream auto-updates
- Today
-
Jovan joined the community
-
android 11 [Release] Android 11 Tinkerboard (not R2.0)
Tom replied to denchakapon's topic in Android
I am trying to root this version per the procedure outlined by TOOZ on May 4 2022, but I can find no place to obtain the needed boot image or to extract it from the Android Image. I understand TWRP does not have a version for the Tinker board. I would be very grateful if someone could provide the boot image or a method that could extract it. In my testing so far Android 11 is very stable except for the usb cable connection to ADB which can be intermittent, but Fastboot works on cable works well as does ADB on Wi-Fi. Thank You - Yesterday
-
heikki.a.laurila@outlook.c joined the community
- Last week
-
petert joined the community
-
hello @DutchDev, aicc can be removed using command: sudo apt purge aiccagent no
-
Cliff changed their profile photo
-
Hi, Is it possible to remove the aicc service from the Tinker_Board-Debian-Buster-v3.0.23-20230426 image or are there constraints that prevent removal? Regards, Erik
-
DutchDev joined the community
-
ttquattroman joined the community
-
Autorunning an app at startup can be done in several ways depending on your operating system. Here are the general steps for some common platforms: Windows: Startup Folder: Press Win + R to open the Run dialog box. Type shell:startup and hit Enter. This opens the Startup folder. Copy a shortcut of the application into this folder. Task Scheduler: Search for "Task Scheduler" in the Start menu and open it. Click on "Create Basic Task" from the right-hand menu. Follow the wizard to set a name, trigger (choose "When the computer starts"), action (select "Start a program"), and browse to select the application's executable file. macOS: Login Items: Go to System Preferences > Users & Groups. Click on your username and go to the "Login Items" tab. Click the "+" button and add the application to the list. Launch Agents: Create a .plist file in /Library/LaunchAgents or ~/Library/LaunchAgents (for a specific user). Set the ProgramArguments key to the path of the application executable. Linux (Ubuntu): Startup Applications: Go to "Startup Applications" or search for it in the application menu. Click "Add" or "New" and add the application with its command or path. rc.local: Edit the /etc/rc.local file and add a line to start the application before the exit 0 line. Note: Ensure you have the necessary permissions to modify system startup settings. Always be cautious about what applications you set to autorun for security and performance reasons. Choose the method that best suits your preferences and system requirements.
-
Etrina joined the community
-
I went for a UVC camera with OV3660 sensor (HBVCAM-3M2111) to match the sensor on my MCU board. It actually worked really well. I did have to run, otherwise a probe would hang. Ideally, I think this could be disabled. I suppose it assumes Coral camera in use. sudo rm /dev/video0
- Earlier
-
bielolopez joined the community
-
igfuti joined the community
-
sputnik3 joined the community
-
cocolangot joined the community
-
can imx219 8MB be used on Tinkerboard or Tinkerboard S
tooz replied to captain kirk's topic in Hardware
hello @captain kirk, also please use sudo tinker-config -
can imx219 8MB be used on Tinkerboard or Tinkerboard S
tooz replied to captain kirk's topic in Hardware
hello @captain kirk, imx219 is supported on tinker board r2.0, i don't think you need to add an overlay, but if you must, try modify the last line: overlay=CSI0-IMX219 save and then reboot to test and see if the camera works: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink reference: Tinker Board (asus.com) -
Hello Has any one used IMX219 8MP camera with Tinkerboard or Tinkerboard S hardware? Please kindly provide me information about how to connect and use imx219 8MB camera., In my /boot/config.txt i haven't seen any info about how to set/activate camera on the device. There is a section for loading device tree overlays (I assume these are kind of device drivers) but could"n find any information on the internet, Even I do not know how to activate them there are "camera-ov5647-overlay.dts" and "camera-ov5647-overlay.dtbo" files In the /boot/overlays folder . There is no file for `imx219`, so does that mean tinkerboard and tinkerboard s do not support imx219 cameras at all? here is my boot config.txt: ##### Hardware Interface Config ##### ## Note: fiq_debugger and uart3 use the same pin. Set fiq_debugger first while both on. ## ## Note: uart4 and spi0 are the same pins. Set the latter one while both on. ## ## Note: uart2 is the same pins to pwm2 and pwm3. Set the latter one while both on. ## intf:fiq_debugger=on #intf:i2c1=off #intf:i2c4=off #intf:spi0=off #intf:spi2=off #intf:pwm2=off #intf:pwm3=off intf:pcm_i2s=on #intf:uart1=off #intf:uart2=off #intf:uart3=off #intf:uart4=off ##### Driver Config ##### ## Note: auto_ums: Auto enable ums mode while power on with USB connected. ## conf:auto_ums=on ##### Tinker Power Management ##### cpu_governor=ondemand a17_minfreq=126000 a17_maxfreq=1800000 gpu_governor=simple_ondemand t76x_minfreq=200000000 t76x_maxfreq=600000000 ##### List of device tree overlays to load. Format: overlay=<dtbo name, no extension> <dtbo2> ... ##### ## Note: Put dtbo files under the overlays folder. ## overlay= Any help is really appreciated
-
hello @Ethan_Lin, 1. from what you've described i'd suggest to check the devices (the dac, adc) 2. please collect the logs when the issue occurs, you can use adb with the command: adb shell su -c dmesg > dmesg.log
-
thanks for reply tooz I have connected ADC and DAC. Initially, they functioned properly, but after frequent input and output data operations, I noticed that the returned data became incorrect.
-
hello @Ethan_Lin, what's the os/ version and i2c bus you're using? did you connect it to other peripherals?
-
-
Devices :Tinker board 2s Sometimes, devices will block the I2C bus, but I want to resolve this issue through software without the need for a reboot or power cycling. I have some ideas, such as altering GPIO status, but this method has proven unsuccessful. I hope someone can provide a viable solution.
-
hello @gavin67890, for csi cameras, the coral camera is the only camera module supported on tinker edge t thus far: https://tinker-board.asus.com/download/Tinker_Edge_T_Device_QVL.pdf though there's no qvl for the uvc cameras, we use logictec c930e for testing
-
Coral Dev Board Camera? But I am struggling to locate any suppliers with stock, maybe heading towards EoL. I keep coming across this document quite a lot, but I can't see how it could be correct. Both the "Raspberry Pi CM1 Adaptors Adapter" and the Pi NoIR Camera V2 have different ribbon cable pins. Ideally, as you state, this document would be a good place to identify compatible cameras. "... for Coral Dev Board" and "... for Tinker Edge T" not in same place as Raspberry Pi or Jetson Nano. Perhaps UVC would be a solution to the camera above. This from Arducam looks encouraging. I'm going to try a UVC cam with my Coral Dev Board. This is maybe too adventurous/exotic.
-
hello @wahaha, sorry for the delay -- the sources of debian 11 for tinker board 2s have been uploaded repo init -u https://github.com/TinkerBoard-Linux/rockchip-linux-manifest.git -b linux5.10-rk3399-debian11 repo sync
-
Yea I think it'll work. I copied the modules over. Will enable it and try. But I believe it'll work. Thanks! Also, can I please trouble you to help upload the kernel resources for 5.10 to git so that I can customize my kernel and the modules?
-
hello @wahaha, looks like the driver isn't initialised, please try: sudo modprobe 8822ce uname -a
-
hi @tooz jakew@tk0:~$ lspci 00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter jakew@tk0:~$ sudo lsmod Module Size Used by jakew@tk0:~$ jakew@tk0:~$ ifconfig -a eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.50.146 netmask 255.255.255.0 broadcast 192.168.50.255 inet6 fe80::7e10:c9ff:feed:f504 prefixlen 64 scopeid 0x20<link> ether 7c:10:c9:ed:f5:04 txqueuelen 1000 (Ethernet) RX packets 416 bytes 37385 (37.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 386 bytes 228443 (228.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 35 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 84 bytes 6308 (6.3 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 84 bytes 6308 (6.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 jakew@tk0:~$ lspci 00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter jakew@tk0:~$ sudo lsmod Module Size Used by jakew@tk0:~$ seems like might be a driver issue? since lscpi is showing hardware results. Note: I used debian 11 v3.0.6 --> but I used debootstrap to install a variant of ubuntu instead. which probably didn't install the driver (i think?)
-
hello @wahaha, not sure if it's a hardware or driver issue, to get a little further: 1. what is the image version you're using? is it debian 11 v.3.0.6? 2. what are the results when you execute the commands: ifconfig -a sudo lspci sudo lsmod
-
I reinstalled debian onto the tinkeboard 2s, and added the below to /etc/network/interfaces # Add the following (for ethernet): auto lo eth0 allow-hotplug eth0 iface lo inet loopback iface eth0 inet dhcp However, when I did: ifconfig It produced the below result: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.50.146 netmask 255.255.255.0 broadcast 192.168.50.255 inet6 fe80::7e10:c9ff:feed:f504 prefixlen 64 scopeid 0x20<link> ether 7c:10:c9:ed:f5:04 txqueuelen 1000 (Ethernet) RX packets 1536 bytes 159578 (159.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 908 bytes 199763 (199.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 35 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 90 bytes 6869 (6.8 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 90 bytes 6869 (6.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 As you can see, wlan / wlp1s0 is not found in there. As such, I am unable to connect via wifi / bluetooth. Is there a driver / kernel / firmware that I can use to update the drivers so that the wifi and bluetooth modules are detectable?
-
I reinstalled debian onto the tinkeboard 2s, and added the below to /etc/network/interfaces # Add the following (for ethernet): auto lo eth0 allow-hotplug eth0 iface lo inet loopback iface eth0 inet dhcp However, when I did: ifconfig It produced the below result: eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.50.146 netmask 255.255.255.0 broadcast 192.168.50.255 inet6 fe80::7e10:c9ff:feed:f504 prefixlen 64 scopeid 0x20<link> ether 7c:10:c9:ed:f5:04 txqueuelen 1000 (Ethernet) RX packets 1536 bytes 159578 (159.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 908 bytes 199763 (199.7 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 35 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 90 bytes 6869 (6.8 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 90 bytes 6869 (6.8 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 As you can see, wlan / wlp1s0 is not found in there. As such, I am unable to connect via wifi / bluetooth. Is there a driver / kernel / firmware that I can use to update the drivers so that the wifi and bluetooth modules are detectable?
