Error on the new CH570D-R0-1v0 board

[notthetup]

Hello. I got my hands on the new CH570D-R0-1v0 from WCH.

Running wchisp on it I get.

 ❯ wchisp -V
wchisp 0.3.0
 ❯ wchisp -v info
05:31:13 [INFO] Opening USB device #0
05:31:13 [DEBUG] (1) wchisp::transport::usb: Found USB Device Bus 000 Device 001: ID 1a86:55e0
05:31:13 [DEBUG] (1) wchisp::transport: => a11200   00004d4355204953502026205743482e434e
05:31:13 [DEBUG] (1) wchisp::transport: <= a1000200 7013
05:31:13 [DEBUG] (1) wchisp::transport: => a11200   00004d4355204953502026205743482e434e
05:31:13 [DEBUG] (1) wchisp::transport: <= a1000200 7013
Error: Cannot find chip with id 0x70 device_type 0x13

I know this is a new board and a new IC. I will be happy to help test any builds/branches.

[biemster]

People are slowly starting to receive these boards, is anyone working on this?

[sw]

I've managed to flash @biemster's blink example from this PR with some changes to the YAML file.

At this point I don't think it's ready for a PR because EEPROM (data flash) access doesn't work and it's not tested at all on the CH572.

WCH doesn't seem to have updated any of their tooling for the CH570/572, at least not on the english or chinese website.

$ cargo run -- info
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.04s
     Running `target/debug/wchisp info`
17:35:04 [INFO] Opening USB device #0
17:35:04 [INFO] Chip: CH570[0x7013] (Code Flash: 240KiB, Data EEPROM: 8KiB)
17:35:04 [INFO] Chip UID: 95-47-21-62-32-DC-E8-85
17:35:04 [INFO] BTVER(bootloader ver): 02.30
17:35:04 [INFO] Current config registers: a55affffffffffff4800ff40000203009547216232dce885
USER_CFG: 0x40FF0048
  [2:0]   RESERVED 0x0 (0b0)
    `- Default
  [3:3]   CFG_RESET_EN 0x1 (0b1)
    `- Enable
  [4:4]   CFG_RST_PIN_EN 0x0 (0b0)
    `- PA8
  [5:5]   CFG_IWDG_EN 0x0 (0b0)
    `- Disable
  [6:6]   CFG_BOOT_EN 0x1 (0b1)
    `- Enable
  [15:7]  RESERVED 0x0 (0b0)
    `- Default
  [23:16] CFG_ROM_READ 0xFF (0b11111111)
    `- Disable 2-wire debug to read out, and keep the program secret
  [27:24] RESERVED 0x0 (0b0)
    `- Default
  [31:28] VALID_SIG 0x4 (0b100)
    `- Valid

[biemster]

I've managed to flash @biemster's blink example from this PR with some changes to the YAML file.

you mean the blinky actually works? that's awesome!

I'm currently using chprog.py to flash, but having control of the config bytes using your yaml would be great actually.

[dquadros]

I've got one of this boards (without the extra chips). Information on them from WCH seems chaotic.

As shown in the photo above, the board is marked as CH570D-R0-1v0 and the chip as CH570D. Had no luck with the WCH-LinkUtility V2.40 (the latest I could find) and the official WCH-LinkE dongle.

There is a github named https://github.com/openwch/ch570, but its contents refer to a CH572D-R0-1v2 board with a CH572D chip.

[biemster]

WCH very often pairs two chips in the ch5xx series, with one being a cheaper and stripped down version of the other. In this case 572 is the "full" version and 570 the cheaper stripped version. Confusingly the 570 is marketed the most currently because it tries to take the crown as cheapest RF mcu. And even more confusing there is already a 571/573 pair from a couple years ago.

The linkE should be able to work with the 570 on the latest firmware. There is some amazing reverse engineering of the linkE firmware underway and it has already shown that the 570 starts showing up in there from version 2.16 (my linkE arrived just a couple weeks ago with 2.12)

edit for future newcomers: the linkE does not work with the code in this repo of course, this code is for ISP flashing over USB/UART and is not using the debug interface