Hi Tim, On 8/16/23, Tim Hardisty <t...@jti.uk.com.invalid> wrote: > I am trying to get CDC/ACM working on my custom board so I can have a > USB console. I have finally worked out the arcane set of CONFIG options > needed, found the to-be-expected bugs/inconstencies with some of the > SAMA5 code, that I have worked around for now (most are covered by > disabling debug assertions for now)...and...finally get an NSH prompt on > a Minicom terminal. > > Yay! > > But data transmission TO the board from Minicom is behaving very strangely. > > If I want to send '?' - to see what built-in apps I have, I need to type > the '?' four times followed by 4 ENTERs, then I get the expected > response. Eh? > > Tried Minicom on Windows/WSL or Ubuntu, and PuTTY. Minicom has been my > console of choice, via serial, for ages. > > This seems very odd - it's 100% OK to the PC but 100% not OK from PC to > board. > > In case it's related...SYSLOG to the original /dev/ttyS1 no longer > works, and playing with SYSLOG configuration, seems to interfere with > the CDC/ACM usb functionality as well by stopping it working if I dare > to try to log to /dev/console! > > Anyone got any suggestions before I scream even louder!!!??? >
I never saw this behavior before! Since you also tested on Windows, it is not something in the computer messing with /dev/ttyACM0. The first thing I noticed is that none board has usbnsh inside boards/arm/sama5/xxxxx/configs/ so probably you are the first one to test this feature. So, start looking what the boards from other arch enable to get USB CDC/ACM working as console. And because there is no usbnsh board config for this chip, maybe it needs more investigation. I'm CC Adam, maybe he already tested it on Jupiter Nano board. BR, Alan
