1. 43
  1. 12

    $4.90 includes a 160x80 IPS RGB LCD and an acrylic transparent case. Not bad!

    1. 7

      That’s a lot of of onboard I/O for the price, too. No floating point, though. And I can’t tell what’s the cpu clock rate from that page or the first datasheet I clicked through to… but at that price, I’m almost sure to buy one or two just to play with.

      Really cool to see all these new RISC-V MCUs coming to market! Hopefully bigger computers aren’t too far behind; the HiFive Unleashed is still a little pricey for my taste.

      1. 3

        the cpu clock rate

        MCU data sheet says:

        The GD32VF103 device incorporates the RISC-V 32-bit processor core operating at 108 MHz frequency

    2. 4

      An interesting thing about the GD32VF103 microcontroller is that Gigadevice already sell the GD32F103 series which is the same chip with an ARM Cortex M3 CPU instead of RISC-V.

      Both chips’ peripheral interfaces are compatible with ST Micro’s STM32F103 series (also Cortex M3).

      (Which may sound dubious but compatible cloning has a long history in the semiconductor business, and as long as it’s done correctly and doesn’t infringe any patents then afaik it’s legal.)

      1. 2

        There is Zero, 0, -1+1 wrong with making something compatible with another interface. ST Micro or anyone else for that matter doesn’t own the memory offsets for peripherals, or the mix of peripherals or the pinouts for a chip. Not that you disagree with me in the slightest, but this needs to reiterated or we lose our basic technological rights.

        1. 2

          Yeah, 100%.

          I have often seen gigadevice mentioned in the same breath as “@$%@! Chinese copycats” so my comment was intended to preempt that. Because, as we know, it neglects a lot of semiconductor history including the history of some well established US companies.

          1. 3

            What if op-amp pinouts weren’t standardized? Linear regulators? Their interface forms a protocol, and protocols advance civilization. We need more standardization in semiconductors not less. The whole copycat thing perverts the discussion, and that path leads to Oracle owning APIs and preventing compatible but superior or cheaper workalikes. Without the ability to make compatible parts, we all die a swamp of lockin.

            What does come into play, is that when someone along the supply chain remarks product a to be product b, which is much much easier because of these standardized interfaces. Intent isn’t clear, and then FTDI went way off the rails. So much so that I still go out of my way to buy and use non-FTDI parts.

            Things should differ in only the areas that matter. Everything else is needless waste.