Is there a simple CDC example?

[greenscreenflicker]

Hello,
i'm looking for a very basic CDC example, ideally only printing "Hello world" on the console.
Is there such examples? All i find are such complex...
Michael

[tyustli]

examples/device/cdc_dual_ports

[dragonlock2]

I use the nanoCH32V203 personally so not sure about this board's connectors. PA11/12 should be USBD. PB6/PB7 should be USBFS

[ddB0515]

Checked schematic and same pins are on both boards and I'm using PA11/12 for USBD. Does example works on your board normally? No issues?

[dragonlock2]

Looking at the schematic CH32V203C8T6-R0.pdf, PA11/PA12 are actually on the P6 connector, labeled USB2(Host) in the image. You'll need a USB-A to USB-A cable or something similar.

On the other hand, the USB-C connector has R22/R23 DNP by default so you can't even test the USBFS (using the USB-C connector) without soldering them on or using a USB-A to USB-C cable.

[ddB0515]

OMG you are right, so all this time it was working just used wrong USB port 🤦‍♂️
Connected using USB-A to USB-A it's working...

[31890.237801] input: miscboards mouse_jiggler as /devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:0c.0/0000:15:00.0/usb3/3-7/3-7.4/3-7.4.1/3-7.4.1:1.0/0003:CAFE:0069.003E/input/input56
[31890.300626] hid-generic 0003:CAFE:0069.003E: input,hidraw8: USB HID v1.11 Mouse [miscboards mouse_jiggler] on usb-0000:15:00.0-7.4.1/input0

And mouse is recognized by Hidviz

Next task is to try CH32V203G6U6 and this one should be easier as is only USBD without USBFS and having only 1 USB :)
Will post here update/progress once I manage to change linker/size and try...
Thanks a lot for support 🍻

[ddB0515]

WOW

This was so easy for CH32V203G6U6 (changed Linker script to 32K/10K)
Deleted build folder, clean build and flash

[35443.850672] usb 3-7.2: new full-speed USB device number 39 using xhci_hcd
[35444.053768] usb 3-7.2: New USB device found, idVendor=cafe, idProduct=0069, bcdDevice= 0.00
[35444.053774] usb 3-7.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35444.053777] usb 3-7.2: Product: mouse_jiggler
[35444.053778] usb 3-7.2: Manufacturer: miscboards
[35444.053780] usb 3-7.2: SerialNumber: 69420
[35444.068302] input: miscboards mouse_jiggler as /devices/pci0000:00/0000:00:02.1/0000:04:00.0/0000:05:0c.0/0000:15:00.0/usb3/3-7/3-7.2/3-7.2:1.0/0003:CAFE:0069.0048/input/input64
[35444.068397] hid-generic 0003:CAFE:0069.0048: input,hidraw8: USB HID v1.11 Mouse [miscboards mouse_jiggler] on usb-0000:15:00.0-7.2/input0

Also nice show of usage and plenty of room :)
Memory region Size Region Size %age Used
ROM: 23684 B 32 KB 72.28%
RAM: 7044 B 10 KB 68.79%

Such nice to have this working on both WCH chips

@dragonlock2 you have a 🍺 or 🍻

[HiFiPhile]

https://googlethatforyou.com?q=how%20do%20i%20transfer%20files%20from%20wsl%20to%20windows

[ilg-ul]

xpm does not add anything to the PATH, since, by design, the xPack framework allows to use different versions of a toolchain in different projects.

Instead xpm adds links to the xpacks/.bin folder, which you should add to the local project PATH.

You can automate this by using xPack actions, which are invoked via xpm run <name>; in this case xpacks/.bin is automatically added to the PATH.

There is also a VS Code extension allowing to conveniently run these actions with a click of the mouse.

If you save package.json to your repository, if you clone it on another machine, you can install exactly the same version of the toolchain via xpm install. This also works on Windows directly, you don't have to use WSL. Actually it works the same on all platforms, Windows, macOS and Linux.