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!!!???

Reply via email to