All Activity
This stream auto-updates
- Today
-
Mooh joined the community
- Yesterday
-
Bruno C. joined the community
-
hello @lloydhussell, for more about can-utils: https://github.com/linux-can/can-utils it's supported on android debug build, it's not available on user build
- Last week
-
hello @wahaha, bootargs can specify the location of the ramdisk (initrd); however, for initramfs, you need to load the initramfs into memory and pass its address to the kernel. If the initramfs is built into the kernel image, then there is no need for separate loading or bootargs configuration
-
[Tinker Board 3S]Windows Laptop doesn’t recognize TinkerBoard3S
ryo replied to ryo's topic in General Discussion
hello @tooz, Thank you so much for your kind message and help. I was able to burn the OS using the method you answered. Thank you so much for your prompt response. Best regards, -
Hi, I recently bought a Tinker board Edge R and noticed with amazement that it hadn't received updates for two years. Has support been dropped? Other boards with the rk3399pro chip have received newer kernels. Could I know if there are any updates planned and the time frame? If not, could you point me to some material to port the kernel?
-
Gino joined the community
-
hi @DaveWK, I managed to resolve this with ideas about your post. you'll have to rebuild idbloader, uboot, kernel. and put them in the correct sector location. # Partition format to follow | Partition No. | Name | Sector Start | Sector End | Size | Comments | |---------------|-----------|--------------|------------|-------|--------------------------| | - | idbloader | 64 | 16383 | | first stage boot loader | | 1 | uboot | 16384 | 24575 | 4mb | second stage boot loader | | 2 | trust | 24576 | 32767 | 4mb | linux / android trust | | 3 | misc | 32768 | 40959 | 4mb | for misc inputs | | 4 | boot | 40960 | 172031 | 64mb | linux kernel boot | | 5 | userdata | 172032 | 303103 | 64mb | for kernel boot elements | | 6 | rootfs | 303104 | ~ | ~ | core linux OS | Then use dd command to extract out fedora rootfs from .raw file into an image file (similar to what you have done above) Note: when compiling uboot, you'll need to amend the hardcoded section where it looks for rootfs. see this: here Finally, use dd to write them all in. and it'll boot up perfectly!
-
[Tinker Board 3S]Windows Laptop doesn’t recognize TinkerBoard3S
tooz replied to ryo's topic in General Discussion
hello @ryo, since you have sd image ready, you can flash tinker board 3's emmc in ums mode. please keep the sd card in the board and 1. switch all the dip switches to off 2. connect tinker board 3 and laptop with micro usb cable 3. power on, open device manager and see if the board is recognised as 'ASUS Tinker UMS USB Device' 4. use balena etcher to flash it -
[Tinker Board 3S]Windows Laptop doesn’t recognize TinkerBoard3S
ryo replied to ryo's topic in General Discussion
Thank you so much for your kind message and help. I tried with both dip switches turned off as shown in the picture, but the result was the same. Is there anything else I should check? Anyway, I burn the OS to the SD card. I succeed to run OS from the SD card. I am not sure that it shows the recognition result of the emmc, but the results of "fdisk -l" is below: linaro@linaro-alip:~$ sudo fdisk -l Disk /dev/ram0: 4 MiB, 4194304 bytes, 8192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mmcblk0: 14.56 GiB, 15634268160 bytes, 30535680 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mmcblk1: 28.82 GiB, 30945574912 bytes, 60440576 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 73987B6B-4974-4C94-A3E8-58AB2EB7A946 Device Start End Sectors Size Type /dev/mmcblk1p1 16384 24575 8192 4M unknown /dev/mmcblk1p2 24576 32767 8192 4M unknown /dev/mmcblk1p3 32768 163839 131072 64M unknown /dev/mmcblk1p4 163840 294911 131072 64M unknown /dev/mmcblk1p5 294912 360447 65536 32M unknown /dev/mmcblk1p6 360448 393215 32768 16M unknown /dev/mmcblk1p7 393216 524287 131072 64M unknown /dev/mmcblk1p8 524288 60440511 59916224 28.6G unknown The size of SD card is 32GB. I also attached the screenshot of the desktop. I would like to note that, we have not recognize the tinker from the windows laptop yet. Best regards, -
Hi @tooz, Ah okay. Because I see that within uboot `make menuconfig`, there is [*] Enable boot arguements () Boot arguements Even if I specify the location within `Boot arguements` by part-UUID to tell it which partition ramfs is located at It won't work? Thank you
-
hello @wahaha, unfortunately there's no specific config to define ramdisk partition. verifying and loading kernel and ramfs both by default start from fit image. to load ramfs only you will need to use a command such as ex2load or fatload manually.
-
[Tinker Board 3S]Windows Laptop doesn’t recognize TinkerBoard3S
tooz replied to ryo's topic in General Discussion
hello @ryo, have you adjusted the dip switches to 1 and 2 so the board is in emmc mode? (on the other hand if you set them to 'on', it would be in sd card mode) -
Hello, I am trying to burn DebianOS into TinkerBoard3S(not Tinker3). I connected the Tinker to my Windows Laptop(Windows11) with a USB-MicroB cable as described in the instructions in this manual(https://tinker-board.asus.com/download/E22692_Tinker_Board_3_UM_WEB.pdf), but the Laptop does not recognize it.(Also, it is not recognized as a target by balenaEtcher). ・Current Status The Red LED on the back is on. When I connected the 3S via USB to Laptop, the device is listed as “unknown device” in the device manager of the windows Laptop. I tried the following, but the results were the same. ・Replace the USB cable. ・Change the USB port(of laptop) ・Connecting to other windows laptop ・Update and Reboot Windows. Is there anything else I need to do regarding the setup?
-
SUper Kodomo changed their profile photo
-
Is the can-utils even available on the Android build?
-
Hello. It has been a while, but I am soon to purchase the 3N. But I need a better understanding of how to utilise CAN. I don't see what you mean by can-utils. Prior to this, I have always used libmraa for UART comm on my tinkerboard 2.
- Earlier
-
I am trying to load initramfs into a dedicated partition, instead of packaging it together with kernel. My understanding is that I will need to define the location within uboot (so that it can be loaded into memory together with kernel as 2 separate objects). Within the kernel i will then need to make this change: General setup ---> () Initramfs source file(s) [*] Support initial ramdisk/ramfs compressed using gzip [ ] Support initial ramdisk/ramfs compressed using bzip2 [ ] Support initial ramdisk/ramfs compressed using LZMA [ ] Support initial ramdisk/ramfs compressed using XZ [ ] Support initial ramdisk/ramfs compressed using LZO [ ] Support initial ramdisk/ramfs compressed using LZ4 My question is, within `uboot`, how do i specify that i have placed the `initramfs.cpio.gz` file into partition 5 of my SD Card?
-
Dear everyone, I was wondering how to use the SPI of the ASUS Tinker V board. Is there any example code available? Any help is highly appreciated.
-
Dear everyone, I was wondering how to use any UART of the ASUS Tinker V board. Any UART (e.g. UART4 at PIN 6 and 8 of the 20-pin GPIO header) but the one connected to USB would be fine. Is there any example code available? Any help is highly appreciated.
-
macandcheese joined the community
-
kazu joined the community
-
The problem was with the monitor. After trying this out on a newer version everything is fine.
-
hello @shizimi, no, it will not be able to power since it needs 12v - 19v power via dc jack. please refer to the block diagram ch.1.6.1 on page 12: E22692_Tinker_Board_3_UM_WEB.pdf (asus.com)
-
Will the Tinkerboard 3 not work if I supply 5V from the GPIO header? There is no DC jack on the circuit diagram, so I can't tell.
-
ryo joined the community
-
hello @shizimi, the user manual/ quick start guide of tinker board 3 & tinker board 3s is released: https://tinker-board.asus.com/download/E22692_Tinker_Board_3_UM_WEB.pdf
-
hello @wahaha, please add the overlay to /boot/config.txt, save and reboot and see if the overlay comes effective sudo vi /boot/config.txt overlay=console-uart0-overlay
-
I am trying to view the uboot and boot messages on the tinkerboard 2s as it boots up, but it is failing to print out the message to computer terminal (via screen). I have connected the cables to gpio pins 6, 8, 10. (gnd, uart0_tx, uart0_rx) as per image below. from there, i plug it into the computer and used the below code to get the usb device that it is connected to sudo dmesg | grep tty Result : [21875.686247] cdc_acm 1-4:1.0: ttyACM0: USB ACM device From there, I used: sudo screen /dev/ttyACM0 115200` to launch screen with baud rate of 115200.. But there is no output on the screen. Not sure what is wrong? is Uart enabled by default?
-
hello @shizimi, we're planning to update the documentation next week, i'll put the link on here once it's ready. sorry for the inconvenience
-
hello @Dominik, 1. did the panel: go completely blank or show 'no signal'? 2. what's the powering sequence? is it panel ->tinker board 3n, or the other way round? was the hdmi cable connected between the panel and tinker board 3n the whole time? 3. could you collect logs via adb so we can have a little big more information for debugging, to collect logs using adb commands: ./adb root ./adb shell dmesg > dmesg.log ./adb shell "echo 0x0c > /sys/module/drm/parameters/debug" ./adb shell dmesg -C ##please unplug and re-plug the hdmi cable## ./adb shell dmesg > dmesg_drm.log
-
I want to connect Tinker Board 3N with a DWIN HDW156-001L monitor using "Tinker Board 3N Android 12 V1.0.19" OS but it doesn't work. I've checked if it's the monitors fault, but it works fine with PC (using the same HDMI cable). Other monitors work properly with the Tinker Board. There's a problem only when Tinker Board and DWIN are connected. I've tried flashing OS on the chip (instead of using SD card), flashing previous versions of the Android for Tinker Board. I've checked if Raspberry Pi 4 with Emteria's Android 14 would have the same issue but it worked properly. Is there a way to identify and fix the problem?
