All Activity
This stream auto-updates
- Today
-
ArthurH. joined the community
- Yesterday
-
MinaKONO joined the community
-
SUper Kodomo changed their profile photo
- Last week
-
earv joined the community
-
drevetph joined the community
-
Bill M joined the community
-
mortgagedoves joined the community
-
Thank you for answer. I am using Debian 2.0.0 Release Version.
-
hello @ken, tinker board 2s will shut down if the cpu is overheated i'm not sure whether there's an issue with cpu or ddr, seems like both can be the possible cause. it'd be helpful to have the console log for debugging. are you running the system with os release from tinker board? if so, what's the version of the os?
-
The environmental temperature is around 25 to 30 degrees and a heat sink is attached. If the CPU temperature is overheated, will it automatically reboot? Or does it shut down? When the system is stopped, only the power LED on and the LAN port lamps all remain OFF. There are 240 identical systems in operation, but only an unspecified unit has occasional problems. (4 ~ 5EA)
-
Well, if SSH is not working in linux system then there are some steps that you can follow to resolve this issue. 1. Check SSH serice status 2. Check SSH port 3. Check SSH configuration 4. Check SSH logs 5. Check disk space 6. Check network connectivity Thanks
-
hello @ken, the hardware watchdog is enabled by default. from what you've described sounds like the system shut down because of overheating -- what's the enviornment and was the heatsink attached? please connect tinker board 2s with a usb to ttl serial cable to collect serial logs (instruction can be found here: https://tinker-board.asus.com/forum/index.php?/topic/14971-how-to-enable-serial-console-in-2s/&do=findComment&comment=15287 ) so we know what causes the trouble
-
Tinkerboard2 runs 24 hours a day, but sometimes goes down. Is there a Hardware Watchdog feature? I would like to get setup information about WatchDog.
- Earlier
-
hello @minami, it's been updated to github: TinkerBoard-Android/rockchip-android-manifest (github.com) sorry for the inconvenience
-
Hi @tooz I got it, please share if you have information.
-
thank you for your answer tooz
-
hello @haonc, i don't think this camera module is on the qualified vendor list nor been calibrated yet. i will let you know once i have more information from my colleagues.
-
hello @Tolga, please refer to the setting below. It’s not necessary to use uart1, uart2 or uart4 can be used, too. Using uart3 however is not suggested, since it’s used for uart log output https://github.com/TinkerBoard/TinkerBoard/wiki/User-Guide#gpio-config-table-for-tinker-board-and-tinker-board-s First, modify the /boot/config.txt file as follows, and then reboot to enable I2C1 and I2C4. ##### Hardware Interface Config ####### Note: fiq_debugger and uart3 use the same pin. Set fiq_debugger first while bb oth 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=on intf:i2c4=on #intf:spi0=off #intf:spi2=off #intf:pwm2=off #intf:pwm3=off intf:pcm_i2s=on intf:uart1=on #intf:uart2=off #intf:uart3=off #intf:uart4=off Chip,line Device Path GPIO number Function2 Function1 GPIO Pin# Pin# GPIO Function1 Function2 GPIO number Device Path Chip,line --- --- --- --- VCC3.3V_IO --- 1 2 --- VCC5V_SYS --- --- --- --- 8,4 GPIO:/sys/class/gpio/gpio252 I2C:/dev/i2c-1 252 --- I2C1_SDA GPIO8_A4 3 4 --- VCC5V_SYS --- --- --- --- 8,5 GPIO:/sys/class/gpio/gpio253 I2C:/dev/i2c-1 253 --- I2C1_SCL GPIO8_A5 5 6 --- GND --- --- --- --- 0,17 GPIO:/sys/class/gpio/gpio17 17 --- TEST_CLKOUT GPIO0_C1 7 8 GPIO5_B1 UART1_TXD --- 161 GPIO:/sys/class/gpio/gpio161 UART:/dev/ttyS1 5,9 --- --- --- --- GND --- 9 10 GPIO5_B0 UART1_RXD --- 160 GPIO:/sys/class/gpio/gpio160 UART:/dev/ttyS1 5,8 5,12 GPIO:/sys/class/gpio/gpio164 SPI:/dev/spidev0 UART:/dev/ttyS4 164 UART4_CTSN SPI0_CLK GPIO5_B4 11 12 GPIO6_A0 I2S_SCLK --- 184 GPIO:/sys/class/gpio/gpio184 6,0 5,14 GPIO:/sys/class/gpio/gpio166 SPI:/dev/spidev0 UART:/dev/ttyS4 166 UART4_TXD SPI0_TXD GPIO5_B6 13 14 --- GND --- --- --- --- 5,15 GPIO:/sys/class/gpio/gpio167 SPI:/dev/spidev0 UART:/dev/ttyS4 167 UART4_RXD SPI0_RXD GPIO5_B7 15 16 GPIO5_B2 UART1_CTSN --- 162 GPIO:/sys/class/gpio/gpio162 UART:/dev/ttyS1 5,10 --- --- --- --- VCC3.3V_IO --- 17 18 GPIO5_B3 UART1_RTSN --- 163 GPIO:/sys/class/gpio/gpio163 UART:/dev/ttyS1 5,11 8,9 GPIO:/sys/class/gpio/gpio257 SPI:/dev/spidev2 257 --- SPI2_TXD GPIO8_B1 19 20 --- GND --- --- --- --- 8,8 GPIO:/sys/class/gpio/gpio256 SPI:/dev/spidev2 256 --- SPI2_RXD GPIO8_B0 21 22 GPIO5_C3 --- --- 171 GPIO:/sys/class/gpio/gpio171 5,19 8,6 GPIO:/sys/class/gpio/gpio254 SPI:/dev/spidev2 254 --- SPI2_CLK GPIO8_A6 23 24 GPIO8_A7 SPI2_CSN0 --- 255 GPIO:/sys/class/gpio/gpio255 SPI:/dev/spidev2.0 8,7 --- --- --- --- GND --- 25 26 GPIO8_A3 SPI2_CSN1 --- 251 GPIO:/sys/class/gpio/gpio251 SPI:/dev/spidev2.1 8,3 7,17 GPIO:/sys/class/gpio/gpio233 I2C:/dev/i2c-4 233 --- I2C4_SDA GPIO7_C1 27 28 GPIO7_C2 I2C4_SCL --- 234 GPIO:/sys/class/gpio/gpio234 I2C:/dev/i2c-4 7,18 5,13 GPIO:/sys/class/gpio/gpio165 SPI:/dev/spidev0.0 165 UART4_RTSN SPI0_CSN0 GPIO5_B5 29 30 --- GND --- --- --- --- 5,16 GPIO:/sys/class/gpio/gpio168 SPI:/dev/spidev0.1 168 --- SPI0_CSN1 GPIO5_C0 31 32 GPIO7_C7 UART2_TXD PWM 239 GPIO:/sys/class/gpio/gpio239 UART:/dev/ttyS2 PWM:/sys/class/pwm/pwmchip3 7,23 7,22 GPIO:/sys/class/gpio/gpio238 UART:/dev/ttyS2 PWM:/sys/class/pwm/pwmchip2 238 PWM2 UART2_RXD GPIO7_C6 33 34 --- GND --- --- --- --- 6,1 GPIO:/sys/class/gpio/gpio185 185 --- I2S_LRCKRX GPIO6_A1 35 36 I2S_LRCKRX UART3_RXD --- 233 GPIO:/sys/class/gpio/gpio223 UART:/dev/ttyS3 7,7 7,8 GPIO:/sys/class/gpio/gpio224 UART:/dev/ttyS3 224 --- UART3_TXD GPIO7_B0 37 38 GPIO6_A3 I2S_SDI --- 187 GPIO:/sys/class/gpio/gpio187 6,3 --- --- --- --- GND --- 39 40 GPIO6_A4 I2S_SDO0 --- 188 GPIO:/sys/class/gpio/gpio188 6,4
-
Hi All, I'm currently porting IMX477 HQ Camera from Raspberry Pi on my Android 11 Tinker Board 2s. I could preview image by camera app, but color was not ok now. It seems that calib iq-file was missing, right? How can i able to get this file? Or what can i do to get correct color? Thanks, haonc
-
Wayne joined the community
-
Hello friends, We are trying to connect rs232 ( weight bridge ) with PIN. We use debian software for Tinker board S. We have to read COM Port. We successful if we use USB cable.
-
Tolga joined the community
-
emma32 joined the community
-
billm joined the community
-
[Release] Tinker Board 3N Debian 11 (kernel 5.10) v.1.0.0
tooz replied to Tinker Board's topic in Software
hello @Shtrihcode, this will be fixed in the next release, thanks for letting us know and sorry for the inconvenience -
[Release] Tinker Board 3N Debian 11 (kernel 5.10) v.1.0.0
Shtrihcode replied to Tinker Board's topic in Software
Doker not start linaro-alip systemd[1]: docker.service: Failed with result 'exit-code'. root@linaro-alip:/usr/src# iptables -L iptables v1.8.9 (legacy): can't initialize iptables table `filter': Table does not exist (do you need to insmod?) root@linaro-alip:/usr/src# iptables -t nat -N DOCKER iptables v1.8.9 (legacy): can't initialize iptables table `nat': Table does not exist (do you need to insmod?) -
hello @User 604, 1. did you get camera preview sucessfully when you executed command? gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink 2. seems like the cameras you use don't support NV12 format, also the cameras used are not specified in the commands. please use this command to check the cameras' video nodes: v4l2-ctl --list-devices and then use this commend to check if you can get a preview smoothly: gst-launch-1.0 v4l2src device=/dev/videoN ! videoconvert ! autovideosink ^ /dev/videoN -- please change the 'N' to the actual # of the video node you're using
-
unlike ov5647 and imx219, imx477 still needs some refinement and calibration to be fully supported. Hi Tooz, we understood this, can you support us to do it by ourselves, or what is your plan to support IMX477?
-
A simple command like "gst-launch-1.0 pylonsrc ! fakesink" (to probe list of installed cameras, as suggested here: https://github.com/basler/gst-plugin-pylon#getting-started ) took me 6 min!
-
$ gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink Setting pipeline to PAUSED ... No protocol specified No protocol specified arm_release_ver of this libmali is 'r18p0-01rel0', rk_so_ver is '4'.Using mplane plugin for capture Pipeline is live and does not need PREROLL ... Got context from element 'autovideosink0': gst.gl.GLDisplay=context, gst.gl.GLDisplay=(GstGLDisplay)"\(GstGLDisplayGBM\)\ gldisplaygbm0"; Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Failed to allocate required memory. Additional debug info: ../sys/v4l2/gstv4l2src.c(700): gst_v4l2src_decide_allocation (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Buffer pool activation failed ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Internal data stream error. Additional debug info: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: streaming stopped, reason not-negotiated (-4) Execution ended after 0:00:00.038114558 Setting pipeline to NULL ... Freeing pipeline ... The command completed immediately.
-
4 Basler USB3 Vision cameras are connected, but during our testing, we only started gs-launch-1.0 using the camera [0] and [1]: [0]: 23298703 acA2440-35um [1]: 23299426 acA2440-35um [2]: 23844311 daA2500-14um [3]: 40120759 daA3840-45um We use the official power adapter that comes with Tinker Board 2s.
-
hello @User 604, 3x USB A ≈13.5W, USB C ≈7.5W; please make sure the adapter that you use provides sufficient power. OTG for USB C means both host mode and device mode are supported at the same time, so no need for extra configuration, if the camera that connects to the USB C port's been detected/ recognized. However please keep in mind that the 4 USB A ports use the same host controller via an usb hub so they share the same bandwith; the USB C uses another host controller and therefore doesn't share the same bandwith with the 4 USB A ports. please try this command and see if the issue still persists: gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw,format=NV12,width=640,height=480 ! videoconvert ! autovideosink reference: https://tinker-board.asus.com/doc_tb.html#camera/
-
hello @gigigagagogo, this forum is dedicated to tinker series (single board computers); for laptop related questions please visit: https://zentalk.asus.com/t5/laptop/ct-p/Laptop
-
TinkerOS Upgrade to Latest Version of Debian
tooz replied to whocares256's topic in General Discussion
hello @Unbroken, the new tinkeros (debian 11) was released: Tinker Board (asus.com) ; the system should be more compatible imo -
hello @User 604 do you have the product name/ serial of the basler usb3 cameras you're using so i can have a look at the specifications and support?
-
Hi, Just got my new Tinker Board 2S and installed the Debian 11 image (v3.0.6-20230627) on the emmc. All seems to be working. I need to connect 4x Basler USB3 cameras using the USB A. Since 2S has 3 USB A ports, I used a USB A to USB C adapter for the 4th camera. Tinker Board doc says the USB C port is OTG. Do I need to change any configuration to disable OTG for my use case? I tried gstreamer plugin (https://github.com/basler/gst-plugin-pylon) to capture from the cameras, but everything seems extremely slow. A simple command line "gst-launch-1.0 pylonsrc ! fakesink" even takes a long time, feels like hanging. Any thoughts?
