hey, im trying to make the duo s connect to the arduino ide as per the official guide (Introduction | Milk-V).
i did everything by the guide up to this part
Search for "duo", select Duo Dev Module for Duo, select Duo256 Dev Module for Duo256M, select the corresponding serial port in the port and click OK.
this is where im stuck. i can select the board but not the port. i have the latest arduino ide (2.3.6), i tried different usb ports and different cables, i tried different duo s images, v1.1.4 and also via buildroot sdk1. i also tried to connect to the arduino ide with both windows and linux. all of the above yield the same result.
am i missing something?
if you need any more details let me know.
any help is welcome, thank you!
This doesn’t seem normal. Does your board get recognized over USB? Can you connect to it via SSH over RNDIS networking?
If the board boots the OS and you can access it, which serial port is emulated on your computer by the USB-to-TTL converter that interfaces your PC and the board?
Which branch and commit did you use to build the firmware?
1 Like
the board connects and works normally via ssh.
i havent used a usb-to-ttl converter at all. am i supposed to use a usb-to-ttl?
i used milkv-duos-emmc-v1.1.4.zip from here (Releases · milkv-duo/duo-buildroot-sdk · GitHub), and with buildroot i followed the docker guide (Introduction | Milk-V) and pulled the sdk from here (GitHub - milkv-duo/duo-buildroot-sdk: Milk-V Duo Official buildroot SDK).
i lack experience in this stuff so tell me if i missed something from your questions
1 Like
So which branch and commit you used, again? If you used some other than mentioned in the guide, it isn’t you following the guide, I guess.
1 Like
well in the guide they point out this:
The latest available Arduino firmware version is Duo-V1.1.2.
DuoS does not currently provide a ready-to-use Arduino version of the firmware. Please go to Buildroot SDK , clone it and switch to the arduino branch to compile.
as of now version 1.1.4 states that it supports arduino for the duo s, which is what i used as well.
1 Like
Ah, cool. So does it provide a CDC (serial over USB) interface as well? I haven’t assembled the V1 images for quite a while, what do you see in the log of the main PC when Duo S starts up?
1 Like
this is after i run # sudo dmesg -w
its what you see when i disconnect the duos and connect it back
[14929.159530] usb 2-1: USB disconnect, device number 13
[14929.159671] cdc_ncm 2-1:1.0 enx8eb1a982c379: unregister 'cdc_ncm' usb-0000:00:14.0-1, CDC NCM (NO ZLP)
[14930.464765] usb 2-1: new high-speed USB device number 14 using xhci_hcd
[14930.598772] usb 2-1: New USB device found, idVendor=3346, idProduct=1000, bcdDevice= 2.00
[14930.598782] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=XXXXXXXXXXXX
[14930.598786] usb 2-1: Product: USB Com Port
[14930.598789] usb 2-1: Manufacturer: CVITEK
[14930.598792] usb 2-1: SerialNumber: XXXXXXXXXXXX
[14930.602251] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[14931.604395] usb 2-1: USB disconnect, device number 14
[14948.306964] usb 2-1: new high-speed USB device number 15 using xhci_hcd
[14948.440973] usb 2-1: New USB device found, idVendor=3346, idProduct=1000, bcdDevice= 2.00
[14948.440984] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=XXXXXXXXXXXX
[14948.440988] usb 2-1: Product: USB Com Port
[14948.440991] usb 2-1: Manufacturer: CVITEK
[14948.440994] usb 2-1: SerialNumber: XXXXXXXXXXXX
[14948.445779] cdc_acm 2-1:1.0: ttyACM0: USB ACM device
[14949.446398] usb 2-1: USB disconnect, device number 15
[14959.627092] usb 2-1: new high-speed USB device number 16 using xhci_hcd
[14965.235158] usb 2-1: device descriptor read/64, error -110
[14965.471778] usb 2-1: New USB device found, idVendor=3346, idProduct=100c, bcdDevice= 5.10
[14965.471789] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=XXXXXXXXXX
[14965.471793] usb 2-1: Product: NCM
[14965.471796] usb 2-1: Manufacturer: Cvitek
[14965.471799] usb 2-1: SerialNumber: XXXXXXXXXX
[14965.499041] cdc_ncm 2-1:1.0: MAC-Address: xx:xx:xx:xx:xx:xx
[14965.499874] cdc_ncm 2-1:1.0 eth0: register 'cdc_ncm' at usb-0000:00:14.0-1, CDC NCM (NO ZLP), xx:xx:xx:xx:xx:xx
[14965.552625] cdc_ncm 2-1:1.0 enxdeb989d48771: renamed from eth0
1 Like
Yes, it is being announced on the bus as /dev/ttyACM0. Yet, later I’m worried seeing this: