I cannot write from the ArduinoIDE. about ch55xduino

[hexesdesu]

I think I might fix this problem by using libusb instead of Winusb Driver

Winusb
first time plugged in

second time plugged in

libusb
first time plugged in

second time plugged in ( •̀ ω •́ )y

[prosper00]

If it's been flashed before, you need to put it into DFU mode. Typically, you'd do this by disconnecting the device, connecting USB Data+ to 3.3V with a 10k resistor, and then powering it up. (you can remove the resistor at this point). That should put it in DFU mode, and you can upload to it again.

[ichirowo]

The previous image shows DFU mode.

It just looks like this when you turn it on

[ichirowo]

I don't need to configure the COM port, do I?
It is not recognized as a COM port in DFU mode of CH552

[prosper00]

I've never used the com port/CDC option, so I can't help you with that.

I've also noticed that I have to start programming very soon after entering DFU. If I enter DFU and leave it for more than a few seconds before I start programming, then it doesn't detect. I don't know why. It still shows as connected in DFU mode, but, programming doesn't work. However, if I start programming within a few seconds of connecting the device, then it all works

[DeqingSun]

@ichirowo If you see "USB module". It is likely the DFU mode is correct. It is likely a driver issue and the uploader can not communicate with hardware.

Did you use the Zadig software to install the driver? You should see something like this.

[ichirowo]

Thanks. It's resolved.

I didn't think it was important to install the driver in Zadig.

When I couldn't write, I had the following problem.

When I did the following, I was able to write with ArduinoIDE.

I could also confirm the symptom of not being able to write after about 10 seconds of entering DFU mode.
You should write as soon as you switch to it.

Thanks. I will introduce this great product and community to Japan.

[DeqingSun]

@ichirowo Great. If you use the default CDC setting, choose the correct COM port and the CDC code will enter DFU automatically when you upload the code.

[ichirowo]

Thanks. It's working fine.
I also installed the CDC driver.

[DeqingSun]

Seems you get it solved?

[hexesdesu]

I've got the same problem when using CH551G. And once I upload a stretch, then I have to ①unplug the USB connector ②reconnect the connector with BL button pushed ③find the device which has a yellow alert sign in device manager and choose automatically update device driver ④reinstall WinUSB driver in Zadig; Everytime！

I f your board is never used with ch55xduino before, you need to make the ch55x chip enter bootloader mode. You need to disconnect USB and unpower ch55x, connect the pull-up resistor on D+ line (generally a 10K resistor between D+ and 5V, controlled by a push-button or adjacent pads). Then you connect USB. and hit Upload. Also, a blank new chip will enter the bootloader automatically.
If you have used ch55xduino once and your code doesn't crash the USB subsystem, you can simply press Upload. Arduino and the firmware will kick the chip into the bootloader automatically.

Quite not same/(ㄒoㄒ)/~~

[DeqingSun]

@hexesdesu what version of Windows are you using? Also would you mind sharing a screen shot of the yellow alert sign, and the details (error code, etc) in that device? That will help me to troubleshoot it.

[SdtElectronics]

I have met the same issue as the one mentioned by @hexesdesu , however, I haven't solved it yet. My current Windows installation is 2004 (internal version 19041.804) but I have already encountered this issue for a long time, likely in version 190x.
The error reported is "Device USB\VID_4348&PID_55E0\5&92c31b4&0&9 had a problem starting" with error code 0xA. This only happens after I installed the WinUSB driver with Zadig. With the original driver provided by wch, the device can be recognized by the system.

On the other hand, the official flashing tool seems worked nicely with the original driver. I wonder whether there is an alternative way to download the bin generated by the arduino IDE, with the official flashing tool?

[DeqingSun]

@SdtElectronics I think there might be a conflict with the official driver, as the official driver is listed on Windows Hardware Compatibility List. I'll see if I can use the CH372 API (official one) in windows to solve this issue.

Before that, maybe you can try to remove the official driver completely and then use the Zadig, to see if it works.

The process should be similar to this one (remove the official driver, not your wireless card. This image is from internet).

[hexesdesu]

@SdtElectronics Maybe have a try?

[SdtElectronics]

@hexesdesu Whoa! This worked for me! That cursed WinUSB has bothered me for several months. I am really grateful to your help.

[DeqingSun]

@hexesdesu Thanks for the help, I'll update the readme

[HonghongLu]

I used mac 11.2.3, arduino 1.8.13, board ch554 and I cannot get it upload to it. I tried holding the reset button, and plug in the usb, then release the button, but it cannot upload.
error messages
dyld: Library not loaded: /usr/local/opt/libusb/lib/libusb-1.0.0.dylib
Referenced from: /Users/user/Library/Arduino15/packages/CH55xDuino/tools/MCS51Tools/2020.12.01/macosx/vnproch55x
An error occurred while uploading the sketch
Reason: Incompatible library version: vnproch55x requires version 3.0.0 or later, but libusb-1.0.0.dylib provides version 2.0.0

[DeqingSun]

vnproch55x.zip
@HonghongLu Please try this file. It has libusb statically linked. Replace the original file in the Arduino package. On my computer, it was in ~/Library/Arduino15/packages/CH55xDuino/tools/MCS51Tools/2020.12.01/macosx

Note you may need to allow the app in the security setting.

[HonghongLu]

vnproch55x.zip
@HonghongLu Please try this file. It has libusb statically linked. Replace the original file in the Arduino package. On my computer, it was in ~/Library/Arduino15/packages/CH55xDuino/tools/MCS51Tools/2020.12.01/macosx

Note you may need to allow the app in the security setting.

yes, I replaced and file and tried. here is another error.
CH55x Programmer by VNPro
Load file as hex
Loaded 4393 bytes between: 0000 to 1156
DeviceVersion of CH55x: 1.00
MCU ID: 00 00
Not support, family ID.
An error occurred while uploading the sketch

[DeqingSun]

@HonghongLu Unfortunately my tool does not support the old protocol. All chip I can get have a 2.3.1 or newer boot loader version. You can try with a new chip. Or you can use the upload tool from other people.

[AnonymousChatter]

@DeqingSun Just would like to chime in on this topic. I have been testing out the WebUSB uploading tool. As Chrome would only support WebUSB through WinUSB, so LibUSB option is out.
It works flawlessly with Windows 7 using Zadig's WinUSB driver.
But for Windows10, it work once after installing as observe by @hexesdesu , subsequent DFU mode would end up with a non operation device + driver.
Here is the funny part. If I forcibly use Zadig to use WinCDC with the DFU CH55x (Of course it will fail), then swap the driver back to WinUSB, it works again :)

[nulllaborg]

I find use WCHISPTool no this issue , not nedd using libusb instead of Winusb Driver，can we use "WCHISPTool way" to write hex with Arduino IDE

[nulllaborg]

Thanks. It's resolved.

I didn't think it was important to install the driver in Zadig.

When I couldn't write, I had the following problem.

When I did the following, I was able to write with ArduinoIDE.

I could also confirm the symptom of not being able to write after about 10 seconds of entering DFU mode. You should write as soon as you switch to it.

Thanks. I will introduce this great product and community to Japan.

i have the same problem. i know why have this problem
when install WCHISPTool we will install CH375_ usb driver ， so we will look like this:

maybe we can use CH375 usb driver to Upgrade program by Arduino @DeqingSun

[DeqingSun]

@nulllaborg You can use the CH375 driver now

ch55xduino/README.md

Line 56 in 80d298d

Added 2022/03/31, Please note, you can either following the Zadig instructions, or you can replace the tools in ```C:\Users\YOUR USER NAME\AppData\Local\Arduino15\packages\CH55xDuino\tools\MCS51Tools\2020.12.01\win``` with [this one](https://github.com/DeqingSun/ch55xduino/files/8390855/vnproch551_exe_20220331.zip). The newly compiled tool can use the default CH375 driver and co-exist with the offical WCHISPTool. Also it workes with 2.5.0 version of bootloader. The newly compiled tool will be de default tool in the next release.