Re: CDC/ACM console data to NuttX corrupted.

Thanks Greg, this helps me understand better how it all hangs together. Regards, Tim. > On 17 Aug 2023, at 21:33, Gregory Nutt wrote: > >  >> On 8/17/2023 10:34 AM, Tim Hardisty wrote: >> I have concluded that CDC/ACM will NOT play alongside SYSLOG - most likely >> on the SAMA5D2 device, or

Re: CDC/ACM console data to NuttX corrupted.

On 8/17/2023 10:34 AM, Tim Hardisty wrote: I have concluded that CDC/ACM will NOT play alongside SYSLOG - most likely on the SAMA5D2 device, or possibly just on my board for some reason. Whatever I choose as the SYSLOG output (/dev/ttyS0, ttyS1, ttyFC0 and ttyFC1 all of which are working fi

Re: CDC/ACM console data to NuttX corrupted.

I have concluded that CDC/ACM will NOT play alongside SYSLOG - most likely on the SAMA5D2 device, or possibly just on my board for some reason. Whatever I choose as the SYSLOG output (/dev/ttyS0, ttyS1, ttyFC0 and ttyFC1 all of which are working fine, or even /dev/null) it just ends up garblin

Re: CDC/ACM console data to NuttX corrupted.

OK...progress. CDC/ACM console behaves like this if CONFIG_CDCACM_NRDREQS is left at the default 4. It needs a given keyboard key to be pressed 4 times to work, and/or garbles the text sent. I also found that usbserial example app misbehaves in the same way - I thought it was working since ran

Re: CDC/ACM console data to NuttX corrupted.

Hi Adam, You are right - wasn't at my dev PC and was going from memory. The FUSB302 does of course only manage PD and CC pullup/pulldowns - I know I got confused at some point when I was doing the driver and had a resurgence of that confusion last night! D+/D- go straight to the processor so

Re: CDC/ACM console data to NuttX corrupted.

Tim, I may be misunderstanding what you are saying– but it may be that you are confusing USB C Power Delivery host or device functionality with USB 2.0 / USB 3.0 data host or device functionality. See this StackExchange question and answer

Re: CDC/ACM console data to NuttX corrupted.

Just FUSB302. It uses the toggle mode to work out a device or host attach and the driver (yes, I authored/submitted that) handles the necessary reconfiguration of the pull ups/downs and then signals, via a poll, to the application layer (or, in my case, board-level driver code) what has occurre

Re: CDC/ACM console data to NuttX corrupted.

Are you using an FUSB302 with an FUSB340 (USB Switch)? My understanding is that the FUSB302 only provides USB C power delivery along with a USB2.0/USB 3.0 connection. That chip doesn't do anything to allow host and device on the same port. As far as I know that's a function of the SAMA5D27 and the

Re: CDC/ACM console data to NuttX corrupted.

Hi Adam, My board is pushing many boundaries as it allows usb host and device to coexist on a single physical port using an FUSB302 controller. It means it can never be as clear cut as it being a bug to report! If you happen to have a config that works for this it would be useful for sure,

Re: CDC/ACM console data to NuttX corrupted.

Tim, I used the CDC/ACM as the console device. Will you file a bug and put all that in the bug, and then we can communicate there? -adam On Wed, Aug 16, 2023 at 12:25 PM Tim Hardisty wrote: > Thanks for replying Adam. > > Did you try CDC/ACM for console, or just CDC/ACM itself? CDC/ACM does w

Re: CDC/ACM console data to NuttX corrupted.

Thanks for replying Adam. Did you try CDC/ACM for console, or just CDC/ACM itself? CDC/ACM does work fine using the usbserial example app, it's just using it as a console that's tripping me up. I was drafting a different email before this topic, and may have missed some relevant information

Re: CDC/ACM console data to NuttX corrupted.

Hi Tim and Alan, I tested CDC/ACM when I was doing the CDC/ECM performance increases about 18 months ago. It seemed like everything worked fine on the Jupiter Nano, the SAMA5D2-XULT. I can put together a config for this again and test it... or send me yours, and I will adapt to Jupiter Nano. If we

Re: CDC/ACM console data to NuttX corrupted.

Hi Tim, On 8/16/23, Tim Hardisty 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

CDC/ACM console data to NuttX corrupted.

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 a