tooz
-
Content Count
627 -
Joined
-
Last visited
-
Days Won
42
Everything posted by tooz
-
hello @giseleznev, i didn't see anything that relates to i2c-6 from your dmesg result. have you used 1. another device and see if the 40 pin header works? 2. check the hardware signal? i don't have the a si5351 so i use a rtc for testing, vcc3.3v=pin1, sda=pin3, scl=pin5, gnd=pin9 sudo vim /boot/config.txt intf:i2c6=on save and reboot sudo i2cdetect -y 6
-
hello @giseleznev, 1. have you made a reboot after saving the config.txt? 2. what's the result of this command? 3. by empty, does it mean that only slave address is shown but the device is not found?
-
hello @giseleznev, what's the config.txt that you modified and what's the i2c device you connected to?
-
hello @manaasch and @roro, please try using the latest android 11 os v.2.0.14: Tinker Board 2 Android 11 V2.0.14
-
hello @Yakiug, sorry for the hassles. looks like tinker board 2s' been recognised as a ums device, which is correct, my guess is that the .img might be broken, i've sent the download link of v.2.0.14 (debian 10, kernel 4.4) via dm, please try using the .img and see if it can be flashed onto sd/ tinker board 2s correctly the os download list issue is now fixed: Tinker Board (asus.com)
-
hello @Yakiug, how are you using the board? we can try reproduce the issue there seems to be an issue on our website, please select 'tinker board 2' first instead, will update when it's fixed: https://tinker-board.asus.com/download-list.html?product=tinker-board-2
-
hello @snk, it's not supported on tinker board r2.0
-
hello @timharron, the standard rate: 115200 and the maximum rate is 1500000
-
hello @Hashimoto Kenichi, both devtype and devnum need to be set, please try using the uboot sources from: TinkerBoard2/u-boot (github.com) TinkerBoard2/u-boot at linux4.19-rk3399-debian10 (github.com) kernel base = 4.19
-
hello @Suntech, i don't think it's related to the dd cloning, i'd suggest to check the dns settings and see if there's anything wrong. or maybe the external networks are blocked by your company, which you can check with sudo ping 8.8.8.8 if there's no package sent/ received it's likely that your company network is restricted
-
hello @Hashimoto Kenichi, devnum and devtype are set by default if you're using tinker os, may i know what's the source code you're using for compiling os/ uboot, so we can have a look at the configs?
-
hello @snk, the miniloader has detected the partition table that's got uboot and trust: so the boot process from micro sd continued, and eventually led to boot failed. please try format and delete the partitions in the micro sd so the partition table can be loaded from emmc
-
@Hashimoto Kenichi, one possible reason might be broken emmc, but we'll need more information to confirm if it's the cause 1, what are the results of: printenv devnum and printenv devtype ? 2. where was the uboot flashed onto? (such as emmc/ sd card/ other storage ... etc) 3. is there any other storage (such as sd card/ usb flash storage ... etc) attached to tinker board 2s?
-
hello @btwin, please check inbox for the firmware
-
hello @snk, please try: su linaro export DISPLAY=:0 xrandr --output HDMI-1 --off or you can disable hdmi in kernel: sudo su echo off > /sys/class/drm/card0-HDMI-A-1/status (if you'd like to enable it, then it's echo on > /sys/class/drm/card0-HDMI-A-1/status )
-
hello @snk, you can turn it off with xrandr: xrandr --output HDMI-1 --off
-
hello @snk, the boot sequence is sd card -> emmc; if you have a sd card in the slot it's likely that the board will boot from sd. if you'd like to keep the micro sd card inserted, you have to either 1. format it, or 2. un-partition the sd card -- the easiest way would be just leave the sd card slot empty so the system boots from emmc.
-
hello @Hashimoto Kenichi, 1. are you using tinker os? 2. what's the error you encountered? to write in uboot: 1. connect tinker board 2s to an ubuntu machine (tinker board 2s should be in ums mode while connecting) 2. press any key during booting to enter u-boot 3. here's an example using setenv/ printenv, and then savenv 4. saveenv and reboot, printenv test and it returns the right value
-
hello @sk109sk, please add it in /boot/cmdline.txt instead sudo vim /boot/cmdline.txt add this line, save and reboot spidev.bufsiz=65536 you can check the value with: cat /sys/module/spidev/parameters/bufsiz
- 2 replies
-
- 1
-
-
- tinkerboards2s
- spi
- (and 1 more)
-
hello @btwin, this issue can be reproduced on our side and we're working on it, will keep you updated when it's fixed
-
hello @manaasch, have you tried using a newer os? does this persist in every version of the os you're using?
-
hello @Yakiug, 1. tinker board 2s might be in maskrom mode, please check if you have a jumper attached, if so, please remove it so the board stays in normal mode 2. another possibility is using an incompatible os, tinker board and tinker board 2s have separate img files and they can't be mixed used https://tinker-board.asus.com/download-list.html?product=tinker-board-2s
-
Disabling boot log levels on Tinker Edge R running Debian 10 (Buster)
tooz replied to saeed soleimanifar's topic in Software
hello @saeed soleimanifar, the fastest way to remove the 6 logos while booting, without re-compiling the kernel is to add quiet in /boot/cmdline.txt: consoleblank=1 quiet you can change it in monitor setting: toolbar >preferences> monitor settings -
Disabling boot log levels on Tinker Edge R running Debian 10 (Buster)
tooz replied to saeed soleimanifar's topic in Software
hello @saeed soleimanifar, you can get the console log disabled by modifying the /boot/cmdline.txt: console= save and then reboot -
hello @KMO, you can get it working properly by removing the ntp package: sudo apt-get remove ntp if you do not wish to remove ntp, you can comment out the line below in /lib/systemd/system/systemd-timesyncd.service.d/disable-time-daemon.conf # ConditionFileIsExecutable=!/usr/sbin/ntpd reboot and then update the system with sudo apt-get update check jobs with: systemctl list-jobs