Add Blues Cygnet board

[maxgerhardt]

Board see here, STM32Duino variant here. Closes #821

Tested by Blues employees.

• we already have bw_swan_r5.json, "BluesWireless" seems to be the old name though? Now it's just "Blues"? (I named this file blues_cygnet.json)
  • added copy of Blues Swan as blues_swan_r5.json
• I activate the USB CDC by default because this board has no onboard USB-to-UART converter and can be flashed via USB by default, so users will expect Serial to also go via USB
• no on-board debugger probe: set DFU as default upload method for the same reason: Works by default with just USB cable
• No HWIDs, the code in main.py correctly selects 0x0483:0xDF11 (STM32 DFU) (Swan R5 also didn't set it)

[zfields]

In stm32duino, we allowed for both bw_swan_r5 as blues_swan_r5; see here. Does this mean, we also need a blues_swan_r5.json?

If so, would you mind to create a copy of bw_swan_r5.json that changes "Blues Wireless" references to "Blues" and add it to this PR?

I think it should look like this:

{
  "build": {
    "core": "stm32",
    "cpu": "cortex-m4",
    "extra_flags": "-DSTM32L4 -DSTM32L4xx -DSTM32L4R5xx",
    "f_cpu": "120000000L",
    "framework_extra_flags": {
      "arduino": "-DCUSTOM_PERIPHERAL_PINS"
    },
    "mcu": "stm32l4r5ziy6",
    "product_line": "STM32L4R5xx",
    "variant": "STM32L4xx/L4R5Z(G-I)Y_L4R9Z(G-I)Y_L4S5ZIY_L4S9ZIY"
  },
  "connectivity": [
    "can"
  ],
  "debug": {
    "jlink_device": "STM32L4R5ZI",
    "openocd_target": "stm32l4x",
    "svd_path": "STM32L4R5.svd"
  },
  "frameworks": [
    "arduino",
    "stm32cube"
  ],
  "name": "Swan R5",
  "upload": {
    "maximum_ram_size": 655360,
    "maximum_size": 2097152,
    "protocol": "stlink",
    "protocols": [
      "dfu",
      "blackmagic",
      "cmsis-dap",
      "jlink",
      "serial",
      "stlink",
      "mbed"
    ]
  },
  "url": "https://blues.io/products/swan",
  "vendor": "Blues"
}

[zfields]

See above: https://github.com/maxgerhardt/platform-ststm32/pull/2/files

[zfields]

Thank you for helping us with this work!

When do you expect it will be merged and released? We have a lot of customers who love PlatformIO, and we would like to let them know when it will support our new board.

[maxgerhardt]

I dunno. But for sure only after an employee reviewed it. CC @valeros

[valeros]

Thanks, added!