Fu-.

hello @tooz 1.Tinker_Board_2-Debian-Bullseye-v3.0.20-20240527 2.No. A notice point: I checked I/O status with io command. io -4 0xff77e008 ff77e008: 00000000 both pins are GPIO. io -4 0xff760334 ff760334: 0000e233 clk_spi5_src_en is set, seems to disable SPI clock

hello @tooz Yes, I've changed /boot/config.txt Before: #intf:spi5=off After: intf:spi5=off gpioall says GPIO2C6 and C7 are GPIO, also I can control the signals HIGH,and LOW. When signal is HIGH, the voltage is lower than other GPIO pins. It is only about 1.95V. Moreover, I 've confirmed that the waveform was going up and down like an SPI clock even though it was holding HIGH. I wonder why signal is oscllating? and why the voltage is too low?

hello @tooz I tried setting via sysfs gpio, it seemed to be the same behavor.

hello @tooz I'm setting both pins as GPIO. I don't want these pin as using SPI, just only GPIO.

Question about GPIO2C6 and GPIO2C7 pins. It is possible to set them to GPIO using wiringPi, but the voltage at HIGH output is lower than other GPIO pins. It is only about 1.95V. Upon further investigation, I found that a clock-like waveform is output during HIGH output. GPIO2C6 is exclusive with SPI5_CLK and GPIO2C7 is exclusive with SPI5_CSN, but it appears that the SPI5 clock continues to be output when each pin is set as a GPIO. Any suggestions?

Hello @tooz, I'm using a different YOLO onnx. This input size is 640x640. It's not sample onnx(convertimg from yolov7l), this takes about 10sec per inference. Regards,

Hello @tooz, Thank you. I hope you can find a good solution. Regards,

Hello @tooz. The zip archive contains to build the sample sources and Makefile. So, extract zip to /home/linaro/, Please make here. Regards,

Hi, tooz. I'll provide a test environment where the problem occurs. Please download from below. https://drive.google.com/file/d/1222dOTwmF18_-sgBqk_YtPRJfL-DzPN4/view?usp=drive_link Regards,

I've tested on the latest debian 11, but it seems to look like nothing to do with debian version. The inference is too slow.

Hi, I'm using yolo v7. I've just noticed that the debian 11 was released. I'll try the new image and test. Regards,

Hi, I am challenging image judgment using OpenCV and YOLO. When I ran libmali using OpenCL, multiple threads took the form of one mutex, and the operation speed was abnormally slow. The expected speed is about 100ms per judgment, but it takes more than 10 seconds when it actually works. Is there any way to solve this? I'm using the latest Tinker2S debian image and OpenCV 4.8.0. Regards,

I want to use Pin #7(GPIOB0) as 1-wire like a RaspberryPi. Drivers(wire,w1-gpio,w1-therm) are loaded. But, Pin #7 does not appear to be working correctly. I modified a little on rk3399-tinker_board_2.dts like this: / { : (SNIPPED) : w1 { compatible = "w1-gpio"; pinctrl-names = "default"; pinctrl-0 = <&w1_pin>; gpios = <&gpio0 RK_PB0 GPIO_ACTIVE_HIGH>; status = "okay"; }; }; &pinctrl { pinctrl-0 = <&gpio_init &test_clkout2 &w1_pin>; : (SNIPPED) : w1pin { w1_pin: w1-pin { rockchip,pins = <RK_GPIO0 RK_PB0 RK_FUNC_3 &pcfg_pull_up>; }; }; }; --- dmesg says, [ 5.245994] Driver for 1-wire Dallas network protocol. No devices detected. gpio readall says Pin#7(GPIO 8) is GPIOB0, NOT CLKOUT. Does anyone know a better way? Regards,

After further investigation, it seems that GPIO#15 (gpio2c_4) is correctly set to pull-down GPIO mode. read GRF_GPIO2C_IOMUX: io -4 -r 0xff77e008 ff77e008: 00000000 bits 9:8 is 2'b00 = GPIO read GRF_GPIO2C_P: io -4 -r 0xff77e048 ff77e048: 0000fd3f bits 9:8 is 2'b01 = weak 0(pull down) Nevertheless, once the input changes from Low->High and the High input is nothing, GPIO#15 continues to stay High. Is there something else I should be setting? From these conditions, it does not seem to be a problem with wiringPi. Is this not a problem with RK3399, but a specification of Tinker2S?

> 4. GPIO #15 (wiring Pi #3) pulled down <-> up switch How to do this?