Threaded Mode | Linear Mode

Idnarn · 11-28-2024, 01:18 AM

(11-27-2024 07:35 PM)blackjetrock Wrote:
(11-27-2024 05:52 PM)Idnarn Wrote: The fact that it found the chip ID 0xab0a07e1 (Atmel ATSAM4LC2CA) suggests that USB communication is working fine. Can you strace the process and see where it's blocking?

Code:

write(1, "-I- Loading applet applet-flash-"..., 66-I- Loading applet applet-flash-sam4l4.bin at address 0x20002000 ) = 66 readlink("/home", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue/tree", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue/tree/hp15ce_programming", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue/tree/hp15ce_programming/sam-ba_cdc_linux", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue/tree/hp15ce_programming/sam-ba_cdc_linux/tcl_lib", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) readlink("/home/menadue/tree/hp15ce_programming/sam-ba_cdc_linux/tcl_lib/at91sam4l-ek", 0x7ffe2c341ce0, 1023) = -1 EINVAL (Invalid argument) openat(AT_FDCWD, "/home/menadue/tree/hp15ce_programming/sam-ba_cdc_linux/tcl_lib/at91sam4l-ek/applet-flash-sam4l4.bin", O_RDONLY) = 6 fcntl(6, F_SETFD, FD_CLOEXEC) = 0 ioctl(6, TCGETS, 0x7ffe2c343760) = -1 ENOTTY (Inappropriate ioctl for device) stat("/home/menadue/tree/hp15ce_programming/sam-ba_cdc_linux/tcl_lib/at91sam4l-ek/applet-flash-sam4l4.bin", {st_mode=S_IFREG|0644, st_size=2652, ...}) = 0 read(6, "\360\177\0 \t(\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 2652 write(5, "S20002000,a5c#\n", 15) = 15 write(5, "\360\177\0 \t(\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 2653) = 2653 close(6) = 0 write(5, "W20002040,0#\n", 13) = 13 write(5, "W20002048,0#\n", 13) = 13 write(5, "W2000204c,4#\n", 13) = 13 write(5, "W20002050,0#\n", 13) = 13 write(5, "G20002000#\n", 11) = 11 write(5, "w20002040,4#\n", 13) = 13 read(5,

What is fd=5 in the strace output? is it the opened USB device? It appears that a read() on it is blocking after several writes(). Perhaps something has changed in the USB driver in recent kernel versions, that's causing the change in behavior.