Jovan

If you think about this: I'd say this is release notes for the Debian OS release, not for hardware revision. I've also found this: But this is drawing and schematics, again without release notes about the differences between the hardware revisions. Thanks @tooz

@tooz We've: * installed software from official debian repository * updated default network netplan configuration * copied our binaries Nothing that would affect boardinfo. btw, /proc/boardinfo content on both boards is: Tinker Board 2S - 16GB however, /proc/boardid on "master" board is "1", but on new board is "3". Just to mention, restoring "master" image to TInkerBoard R1.02 still works properly.

During the production, we create the master image (based on Debian 11, v3.0.20) on one tinkerBoard 2S, and then clone it on other boards. That worked for some time, until recently it stopped working, meaning that restoring the same image does not end up in working/bootable TinkerBoard 2S device. Only thing we found is that new boards are TinkerBoard 2S R1.03, but the master image was created on TinkerBoard 2S R1.02. @tooz Is there a way to make the image work on all hardware revisions? Please check the photos below for revision info:

@tooz thanks for quick responses and valuable support you're providing. Maybe I'm checking it on wrong place, but those are release notes for Software OS releases, right? I was asking for release notes for hardware revisions, ie. changes in hardware between the different revisions of PCB.

Hello, Are there release notes available for TInkerBoard 2S board, to check what was updated/upgraded/fixed between the revisions. We have in production boards, some of them are marked as R1.02 and some of them are R1.03, and we were wondering about the difference now. Thanks @tooz (or anybody else of course)

@tooz thanks for the prompt response. Tried and tested it, and yes, it solved our issue. ?

Hello, We're having issues with reading date&time from RTC clock. Battery is connected, voltage is measured and is ok. We can set the date&time in RTC clock using command "hwclock --systohc" as you can see in screenshot below: But our issue is that after the reboot, only the date is read from RTC clock. After the reboot, time starts every time at 00:00:00 even though it was written to RTC before the reboot. This is plain vanilla Debian OS and we're having this issue consistently on more than one device. Any ideas? Thanks a lot.

Hello, Is there any way to read voltage level of the installed CMOS battery within the Debian OS? Purpose is to signal the operator when there is a need for battery replacement before it becomes dead and unusable. Thanks

I can, just to know the behaviour, but in production we deliver it to customer without the SD Card with the OS on the eMMC ?

I just got and tried a new, second one (same model, Tinker Board 3N). Removed the jumper cap, plugged into the mac and it immediately recognized and works like a charm. Looks like the first one needs to be RMA. Thanks

Thanks for all the great feedback. There is always an option it's a faulty one.

I'm not sure I understand the last question, but I've never "used" the board in term of booting the OS. As soon as I plug in the power supply, red led turns on. It was on also before I've removed the mask2 jumper. So, it's always on when I connect the power supply, no matter if USB cable is connected or not.

I've attached the latest setup photo for reference. Red light is there, USB-C -> USB-A, but nothing detected by Win, and nothing in device manager.

I've done all that, both jumper caps removed, except Macbook does not have USB-A port, so have to use USB hub for that. Also tried on Windows, which now does not recognize anything at all ?

Thanks for really fast answers. Unfortunatelly... still nothing. So, I've removed jumper from Mask2 pins. What about the Recovery pins, should I have the jumper there ON or no)? And also the Mask1 dip-switch?

Thanks for the feedback. On Mac I had to use USB Hub to get USB-A port. Tried two without any success. Result is the same. Then I tried on the Windows machine and it got recognized, but not as a storage device, but as "Unknown Device", which then was not available for flashing in BalenaEther as it's not recognized as a storage device. Any further help please? Is there any drivers I should install on Win? Thanks again

After successfully using TinkerBoard 2S in production, we wanted to evaluate TinkerBoard 3N and bought it. However, using the same setup (macOS and USB-C <-> USB-C cable directly connected to the mac laptop), we cannot get it to be recognized as a storage device. We're following the same procedure as we do with the TinkerBoard 2S (unplug everything from TinkerBoard, connect the USB-C cable to board and laptop using the OTG port and then connecting the power supply. But nothing happens when we connect the board... Can you suggest what can we try to resolve the issue? Photo of the board itself is attached if that helps in any way... Thanks

Yup, my question is kinda pointless... we are changing the baudrate in user space, and it's working properly. The issue was somewhere else, not related to TinkerBoard itself (we've resolved that). Thanks

Thanks for prompt reply. I'll check the fix and get back here with the result. Hopefully we will have this fix included in next official Debian11 image too.

Thanks for the response. These are exact steps for reproduction: 1) burn official 3.0.11 image (Tinker_Board_2-Debian-Bullseye-v3.0.11-20231024-release.img) 2) change intf:fiq_debugger to OFF 3) change intf:uart0 to ON 4) remove wifi/bt card that was shipped with the TinkerBoard 5) Reboot When I put back the WiFi/BT card in, then I can see the line: cfg80211: failed to load regulatory.db but without wireless card, it's stuck on boot just before that line (as shown on photo). Best regards

Hello, When. in /boot/config.txt I enable uart0 and uart4 and define them with different baud rates, both are always initialized with 1500000 baudrate. intf:fiq_debugger=on intf:uart0=on intf:uart4=on #intf:i2c6=off #intf:i2c7=off #intf:i2s0=off #intf:spdif=on #intf:spi1=off #intf:spi5=off #intf:pwm0=off #intf:pwm1=off #intf:pwm3a=off #intf:test_clkout2=off uart0 = Serial("/dev/ttyS0", 115200) uart4 = Serial("/dev/ttyS4", 1000000) then after the boot I get: linaro@linaro-alip:~$ sudo dmesg | grep tty [ 4.664967] Kernel command line: storagemedia=emmc androidboot.storagemedia=emmc androidboot.mode=normal androidboot.verifiedbootstate=orange androidboot.serialno=b6977d7c12b9a2e5 root=/dev/mmcblk0p8 rw rootwait console=tty0 earlycon=uart8250,mmio32,0xff1a0000 console=ttyFIQ0 rootfstype=ext4 coherent_pool=1m [ 5.325828] printk: console [tty0] enabled [ 5.681796] Registered FIQ tty driver [ 6.876158] printk: console [ttyFIQ0] enabled [ 6.890795] Registered fiq debugger ttyFIQ0 [ 7.667771] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 45, base_baud = 1500000) is a 16550A [ 7.668238] ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 47, base_baud = 1500000) is a 16550A [ 14.656870] ttyFIQ ttyFIQ0: tty_port_close_start: tty->count = 1 port count = 2 How to change baudrate this? Thanks

Hello, When we put "intf:fiq_debugger=off" line to config.txt and removed WiFi card (as the device we're sending to our customers does not require WiFi/BT, TInkerBoard simply won't boot. It's stuck after the messages about cfg80211 loading certificates (as shown in the attached photo). Do you have maybe any solution or workaround for this issue? Best regards, Jovan