Replies: 2 comments 5 replies
-
Thanks for sharing these findings. I'm particularly interested in your observations on Windows; they should help us with #126. Generally, I wouldn't be surprised if our driver isn't configured properly. The Linux issues are new to me. I'll see if I can reproduce this myself when I get some time. In the mean time, here's a few things I'm curious about.
|
Beta Was this translation helpful? Give feedback.
-
Update for future readers: The patch described below is available in 0.1.1 of imxrt-log. I reproduced some of these logging issues on a Linux host (5.15 kernel). I use I'm noticing much better behavior with this commit in the [patch.crates-io.imxrt-log]
git = "https://github.com/mciantyre/imxrt-hal"
branch = "log-fixes" Some extra notes:
|
Beta Was this translation helpful? Give feedback.
-
Hi,
first of all, I am quite new to Rust, so bear with me. I do seem to have some problems running the template. I am using teensy41.
I created my project using the generator, and after flashing I do seem to be unable to properly open the usb serial port (the led is properly blinking and I can change the frequency of the blink in the code).
cargo generate --git https://github.com/mciantyre/teensy4-rs-template --name cando
When connecting/restarting the device I get the following in dmesg (same in kernel 5.15 an 6.1, I dont see any warnings in dmesg for teensyduino):
Trying picocom or screen, results in a freeze usually (with no output at all, I need to kill them, cannot exit normally). Also I don't see any output in Arduino IDE serial monitor. Once or twice it properly started showing the output.
I do see some output if i disconnect the usb cable and picocom errors out. Exmaple (there was no output until the cable was unplugged):

I know that baud should not matter in usb native mode, but I had tried with multiple baud rates nonetheless, without success.
If I flash Teensyduino everything works correctly. Is there a special command needed to open serial?
EDIT:
I actually adjusted locally MAX_PACKET_SIZE to 512 (in usbd.rs) and maxpacket warnings from dmesg are gone, but the behavior is the same.
EDIT2:
It does seem to work fine from Windows + PuTTY...
EDIT3:
I had some problems enumerating the device on Windows, it seems I do need to have the MAX_PACKET_SIZE = 512 for it to work. On Linux I saw that every time the device is connected mtp-probe is doing something with it, so I removed libmtp, now I do seem to have a better chance of connecting to serial. But when it IS working, it seems to skip some lines (on windows it does not skip anything):
But when I type/send any character, minicom just freezes again.
Beta Was this translation helpful? Give feedback.
All reactions