Jump to content

ryo

Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello @tooz, Thank you so much for your kind message and help. I have checked the questions you asked. 1. checked /boot/config.txt and confirmed that pwm=0,1,2,5 are all off 2. confirmed that /dev/ttyS0 exists. Therefore, the answers to both questions are yes, but MCU does not work with UART0. I will describe the details of the problem. I think this is confusing. I apologize. I still cannot send or receive messages to a specific MCU. To check the communication status, I connected a USB-UART (FTDI) to a Windows OS laptop and was able to communicate accurately with the Windows console (Teraterm) via UART0. [Windows] - [USB] - [USB-UART] - [GPIO] This made me think that it was a problem with the MCU software, but I was able to communicate accurately with the MCU via UART1, 4, and 9. I thought that there might be a difference in the hardware between UART0 and UART1, 4, and 9, but if there is no difference, I will investigate whether communication is possible with MCUs from different manufacturers. The version information of the Kernel and OS currently used is as follows. linaro@linaro-alip:~$ uname -a Linux linaro-alip 5.10.209 #1 SMP Wed Oct 30 10:46:21 UTC 2024 aarch64 GNU/Linux linaro@linaro-alip:~$ cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)” NAME="Debian GNU/Linux” VERSION_ID="11” VERSION="11 (bullseye)” VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/” SUPPORT_URL="https://www.debian.org/support” BUG_REPORT_URL="https://bugs.debian.org/” BUILD_INFO="root@16c4f514c5ab Wed Oct 30 11:31:37 UTC 2024” ID_LIKE="debian” RK_BUILD_INFO="root@16c4f514c5ab Wed Oct 30 11:35:04 UTC 2024” Best regards,
  2. Hello, I am trying to connect an UART device (MCU) to a TinkerBoard3S. I have confirmed that UART1, 4, and 9 work correctly, but it does not work with UART0. Is there any difference between UART0 and UART1,4,9? I have checked the performance with baudrates of 9600, 115200. I assume that UART0 has CTS and RTS pins. Therefore, I have set the CTS and RTS pins to not be used in the software. I attached sample python code with pyserial module. >>> import serial >>> ser = serial.Serial("/dev/ttyS0", 9600, timeout=1) >>> ser.rtscts=False >>> ser.dsrdtr=False >>> ser.rts=False >>> ser.dtr=False Are there any other necessary settings?
  3. (Sorry for posting so many times, I think it was due to my operation error) hello @tooz, Thank you so much for your kind message and help. I followed the steps for the link you shared, and was able to use the GPIO. FYI, I think the results of the gpio readall does not match what you want to show. I attached the screen shots of the results of gpio readall. (the pictures of the previous post, when I enable UART0 from tinker-config) Best regards,
  4. Hello, I am currently trying to check GPIO control with TinkerBoard3S. ・Environment  TinkerBoard3S OS:Tinker Board 3 Debian 11 (kernel 5.10) V.1.0.1(The results were the same with 1.0.4) I tried to check the LED blinking with pin108 using the following sample code, but it doesn't work.(there is no import error) import ASUS.GPIO as GPIO import time GPIO.setmode(GPIO.ASUS) GPIO.setwarnings(False) GPIO.setup(108, GPIO.OUT) while True: GPIO.output(108, GPIO.HIGH) time.sleep(0.2); GPIO.output(108, GPIO.LOW) time.sleep(0.2); The result of "gpio readall" before executing sample code is bellow, but after executing the 108 pin mode remained IN. Also, to check UART communication, I enabled UART communication from tinker-config, but there was no change in "gpio readall" results. Is there anything else I need to do regarding the GPIO control?  linaro@linaro-alip:~$ gpio readall +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+ | CPU | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | CPU | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | | | 3.3v | | | 1 || 2 | | | 5v | | | | | | GPIO8A4 | | | 3 || 4 | IN | 5v | 146 | 146 | | 105 | 105 | GPIO8A5 | IN | 5 || 6 | IN | 0v | 147 | 147 | | 106 | 106 | GPIO0C1 | IN | 7 || 8 | IN | GPIO5B1 | 148 | 148 | | 107 | 107 | 0v | IN | 9 || 10 | IN | GPIO5B0 | 149 | 149 | | 108 | 108 | GPIO5B4 | IN | 11 || 12 | IN | GPIO6A0 | 150 | 150 | | | | GPIO5B6 | | | 13 || 14 | | | 0v | | | | | | GPIO5B7 | | | 15 || 16 | | | GPIO5B2 | | | | | | 3.3v | | | 17 || 18 | | | GPIO5B3 | | | | | | GPIO8B1 | | | 19 || 20 | | | 0v | | | | | | GPIO8B0 | | | 21 || 22 | | | GPIO5C3 | | | | | | GPIO8A6 | | | 23 || 24 | | | GPIO8A7 | | | | | | 0v | | | 25 || 26 | | | GPIO8A3 | | | | | | GPIO7C1 | | | 27 || 28 | | | GPIO7C2 | | | | | | GPIO5B5 | | | 29 || 30 | | | 0v | | | | | | GPIO5C0 | | | 31 || 32 | | | GPIO7C7 | | | | | | GPIO7C6 | | | 33 || 34 | | | 0v | | | | | | GPIO6A1 | | | 35 || 36 | | | GPIO7A7 | | | | | | GPIO7B0 | | | 37 || 38 | | | GPIO6A3 | | | | | | 0v | | | 39 || 40 | | | GPIO6A4 | | | +-----+-----+---------+------+---+----++----+---+------+---------+-----+-----+ | CPU | wPi | Name | Mode | V | Physical | V | Mode | Name | wPi | CPU | +-----+-----+---------+------+---+--Tinker--+---+------+---------+-----+-----+
  5. 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,
  6. 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,
  7. 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?
×
×
  • Create New...