Author Topic: I'd like to know your experience with Gowin FPGAs  (Read 7292 times)

darkspr1te and 1 Guest are viewing this topic.

Offline betocoolTopic starter

  • Regular Contributor
  • *
  • Posts: 162
  • Country: au
I'd like to know your experience with Gowin FPGAs
« on: May 25, 2026, 01:35:29 pm »
Hey all,

The title says it all. After the probable Vivado non-Linux release of 2026+, I thought it might be a good idea to look elsewhere. Other than Altera, Gowin seems to come up as a close alternative to the Artix-7 series, and I'd be willing to give them a try. Might get a 20K dev kit to start with.

Any comments, gotchas, caveats, experience you'd be willing to share?

Cheers,

Alberto
 

Offline kicktostart

  • Newbie
  • Posts: 5
  • Country: us
Re: I'd like to know your experience with Gowin FPGAs
« Reply #1 on: May 25, 2026, 03:19:06 pm »
Hi Alberto,

While I prefer AMD/Xilinx, my experience with Gowin has been decent. For smaller, quick-turn, internal R&D designs, I would likely prototype using a Gowin FPGA nowadays (or at least try it first if it makes sense).

I find there are a few bells and whistles in the Xilinx ecosystem that you cannot get with Gowin yet. If you are using the RFSoCs, or the SERDES to go really fast, I don't see Gowin as a viable replacement.

Also, in terms of DSP development, the Xilinx ecosystem contains bit-accurate models that make testing and validating those pipelines easier. That said, Gowin does have these features: https://www.gowinsemi.com/upload/database_doc/605/document/60700307ee366.pdf

Place and route using the Gowin tools is noticeably faster than Vivado. Dev iteration times are also faster. Also on the price side, Gowin is very competitive.

For a quick test and bring-up of the 20K, this repo might have something: https://github.com/yuri-panchul/basics-graphics-music/tree/main/boards

Also, it feels to me like the Gowin ecosystem is growing. That is: there is a lot more open source development happening that uses these FPGAs.

Hope this helps.
 

Offline asmi

  • Super Contributor
  • ***
  • Posts: 3324
  • Country: ca
Re: I'd like to know your experience with Gowin FPGAs
« Reply #2 on: May 25, 2026, 03:40:04 pm »
These devices are definitely on a single end of FPGA spectrum. To me personally Efinix look a lot more appealing.

Offline zapta

  • Super Contributor
  • ***
  • Posts: 6585
  • Country: 00
Re: I'd like to know your experience with Gowin FPGAs
« Reply #3 on: May 25, 2026, 04:43:03 pm »
Do you plan to use just board or also get bare Gowin chips for your custom boards? IIRC, Gowin bare chips are hard to find.

I have experience with the Sipeed Tang Nano 9k and 20k and the open source toolchain (via Apio), they are priced very reasonably and work as expected.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 30126
  • Country: nl
    • NCT Developments
Re: I'd like to know your experience with Gowin FPGAs
« Reply #4 on: May 27, 2026, 11:17:13 pm »
I used Gowin FPGAs in a design a couple of years ago. I didn't bother getting a dev board or a programmer. The SPI programming protocol is super easy to implement and the tools provided by Gowin work well. Mouser and LCSC carry a decent range of Gowin FPGAs (in stock). Availability of the Gowin devices during the chip shortage was also good.
« Last Edit: May 27, 2026, 11:24:32 pm by nctnico »
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline marshallh

  • Supporter
  • ****
  • Posts: 1472
  • Country: us
    • retroactive
Re: I'd like to know your experience with Gowin FPGAs
« Reply #5 on: May 30, 2026, 08:27:01 am »
I've watched a few people get started on them. They do work, but there seem to be some gotchas that probably are only an issue if you want to ship a product with them:

1. Guy found that his 138k? started to have bitflips in the fabric when packing enough logic in the die and at fast enough speeds. Huge problem.
2. Guy found that the DDR3 IP failed to initialize when much other logic was in the design
3. Guy found that both 60k and 138k had instability in the fabric and increasing Vcore was enough to fix it

The third one might have been the fault of Sipeed for not having a good enough PDN. But the first two were fairly spooky and I wouldn't want to be stuck trying to deal with that situation.
Verilog tips
BGA soldering intro

11:37 <@ktemkin> c4757p: marshall has transcended communications media
11:37 <@ktemkin> He speaks protocols directly.
 

Offline nctnico

  • Super Contributor
  • ***
  • Posts: 30126
  • Country: nl
    • NCT Developments
Re: I'd like to know your experience with Gowin FPGAs
« Reply #6 on: May 30, 2026, 02:45:49 pm »
I've watched a few people get started on them. They do work, but there seem to be some gotchas that probably are only an issue if you want to ship a product with them:

1. Guy found that his 138k? started to have bitflips in the fabric when packing enough logic in the die and at fast enough speeds. Huge problem.
2. Guy found that the DDR3 IP failed to initialize when much other logic was in the design
3. Guy found that both 60k and 138k had instability in the fabric and increasing Vcore was enough to fix it

The third one might have been the fault of Sipeed for not having a good enough PDN. But the first two were fairly spooky and I wouldn't want to be stuck trying to deal with that situation.
1 and 2 sound like a lack of timing constraints. Typically this is overlooked but proper timing constraints are as necessary as applying power to an FPGA.
There are small lies, big lies and then there is what is on the screen of your oscilloscope.
 

Offline Shalomie42

  • Contributor
  • Posts: 15
  • Country: us
Re: I'd like to know your experience with Gowin FPGAs
« Reply #7 on: May 31, 2026, 05:02:30 pm »
I recently did a production design with a GOWIN LittleBee and I think I am going to continue with it.

What drew me towards the LittleBee was:
  • Come with internal LDO. We are using the UV variant. You can power the whole chip by 3V3 if you want. We are using 1V8 for VCORE and 3V3 for everything else to get lower power
  • Come in LQFP package
  • Dual purpose for JTAG pins.
  • Largest amount of logic on the market given the above constraints

On the first rev of my board I made a mistake with the DONE and RDY pins. The intention was to put a jumper on the board to ground the DONE pin on POR so that it would stay in configuration mode so we could use the JTAG to program the chip. Then once you reboot, the JTAG pins can be used as I/O. The datasheet stated that if you ground the DONE pin it keeps it in configuration mode. It does not. In fact, it basically does nothing. I reached out to the GOWIN FAE and he said it did what I wanted. I told him it did not. I went ahead and tested using the RDY pin instead and it was the pin I actually wanted to use for this purpose. I ended up with:

  • DONE pin straight connection to an LED with a pull up, just because apparently. The LED indicates that the chip has booted, configured, and gone to user mode
  • RDY pin pullup with a jumper to ground it for POR programming

I have been eyeballing the Efinix Trions, because you can actually buy them for cheap on digikey. I see they have "twice" the amount of logic of the LittleBee. However, my gut has been telling me to stay away. It feels like I would need twice the amount of logic to match a 9K LittleBee or normal FPGA, because half of the logic on the chip would have to be used for routing since no dedicated routing. Additionally, it requires 1V1 and a specific power sequence, which is very annoying. Funny thing is that the power sequence is explicitly called out as being required in the documentation but their dev kit reference designs just apply power without a sequence using LDOs. Go figure. I also heard some stories of them having a very naive implementation for the internal buffer to pin routing causing 10ns of extra delay out of nowhere. Kaizo block out of nowhere!

I have experience with Lattice; however, they have been aggravating me for years. I know an important sales guy from Lattice who I query professionally. However, if you are not ordering high volume, it is very apparent he wants to and does shrug you off. My last few interactions with him have not been great. Additionally, I am actually quite sick of Lattice sitting on their Laurels for years and years. Where are new modern ice40 replacements? They were introduced in 2009? The new MachXO(x) chips are a joke as not only are these based on an old node but they keep making the same mistake over and over again of not offering their high logic variants in QFP. In my industry (industrial) we never want to use BGA type packages. I would love to stay on the western side because I am based in the US and the Lattice tools are better. However, they are just asking for smaller players to come and eat their lunch when they stagnate for so many years. Give me an FPGA in QFP with a dense amount of logic. I don't particularly understand why more vendors can't do this. It can't be a die size problem can it? The QFP package is many times as large as the denser packages. Lattice has the ECP5, but that thing is really showing its age.
« Last Edit: May 31, 2026, 05:14:41 pm by Shalomie42 »
 

Offline asmi

  • Super Contributor
  • ***
  • Posts: 3324
  • Country: ca
Re: I'd like to know your experience with Gowin FPGAs
« Reply #8 on: June 01, 2026, 02:56:32 am »
The new MachXO(x) chips are a joke as not only are these based on an old node but they keep making the same mistake over and over again of not offering their high logic variants in QFP. In my industry (industrial) we never want to use BGA type packages. I would love to stay on the western side because I am based in the US and the Lattice tools are better. However, they are just asking for smaller players to come and eat their lunch when they stagnate for so many years. Give me an FPGA in QFP with a dense amount of logic. I don't particularly understand why more vendors can't do this. It can't be a die size problem can it? The QFP package is many times as large as the denser packages. Lattice has the ECP5, but that thing is really showing its age.
Nobody is making FPGAs is QFP because it's terrible for singal integrity, so you can't really make anything even moderately fast in that package. Not to mention it's just too damn large. BGAs are objectively superior in every aspect, so I suggest you to look at a calendar and embrace modern technology. QFP are quickly going the way of dodo, so you'd better keep up with time if you don't want to be left behind. I personally would take BGA over just about any other package any day.
 
The following users thanked this post: glenenglish

Offline Shalomie42

  • Contributor
  • Posts: 15
  • Country: us
Re: I'd like to know your experience with Gowin FPGAs
« Reply #9 on: June 01, 2026, 11:44:08 am »
A lot of applications don't need the speed, including most of mine. We don't need any of the fancy interfaces, just a lot of low power logic.

The choice between QFP & BGA is not mine. However, I would highly suggest you don't try and assume and draw conclusions on why people need to use QFP over BGA. A lot of our boards have to use 2oz copper, which can be difficult for BGA soldering. We have a few extremely experienced hardware engineers who have told us BGA would be very difficult on such boards given our boards are also extremely cost sensitive.
 

Offline asmi

  • Super Contributor
  • ***
  • Posts: 3324
  • Country: ca
Re: I'd like to know your experience with Gowin FPGAs
« Reply #10 on: June 01, 2026, 01:05:51 pm »
A lot of applications don't need the speed, including most of mine. We don't need any of the fancy interfaces, just a lot of low power logic.
That's a very niche use case, and the one that wouldn't look good in marketing ("We just released a brand new FPGA which can't even do DDR2 - not to mention DDR3/DDR4 or super-fancy LPDDR4, but it's got LOGIC!" :-DD ). Nobody is going to take seriously an FPGA with considerable amount of logic which can't even talk to DRAM nowadays, so a vendor would have to add some memory inside the package to compensate for meager IO abilities, which would drive up cost. The reality is IO needs of FPGA design usually are proportional to the amount of logic resources, hence why devices with lots of logic tend to be in a big BGA packages with lots of balls.
I'm not saying your usecase does not exist or is invalid somehow, I'm just telling you how FPGA vendors themselves explain why no modern FPGAs are released in anything but BGA packages (I asked that quesion to Xilinx engineers during one of webinars a few years back when they were introducing Spartan-7 devices which were initially announced in QFP package among others, but that was quietly dropped somewhere along the way and never saw the light of day), and even those tend to become smaller the more modern FPGAs are. Everybody want to make their products smaller and lighter - not bigger and heavier. And as a side effect of reducing size you also improve both power and signal integrity because shorter (or ideally non-existant in case of chip-scale packages) bond wires have both shorter impedance discontinuity (improving signal integrity) and less inductance (improving power integrity). This allows ever faster signals to still have enough loss margin to be useful.

The choice between QFP & BGA is not mine. However, I would highly suggest you don't try and assume and draw conclusions on why people need to use QFP over BGA. A lot of our boards have to use 2oz copper, which can be difficult for BGA soldering. We have a few extremely experienced hardware engineers who have told us BGA would be very difficult on such boards given our boards are also extremely cost sensitive.
This problem is typically solved by using modules - when you have a small hi-tech multilayer board with all high-speed stuff, and a low-tech carrier board with all that power stuff. Alternatively, instead of 2oz copper you can simply route the same net over multiple layers in parallel, achieving the same result as thicker copper - this is often used if you only need a few high-power traces. This is routinely done on a lot of FPGA and higher-end SoC boards - with ever shrinking Vccint voltages modern FPGAs and SoCs draw ever higher currents, so in order for all that current to be delivered to device and not lost along the way you have to have multiple power planes in parallel. As a side effect, such arrangement reduces inductance of a PDS which allows for a faster step response and thus better power/ground stability, also contributing to improving signal integrity because bouncing ground/power rails make for bad reference planes.
As for the cost - BGA typically allow making boards much smaller than any other package, and a size is a big driver of price - because not only bigger PCB cost more to manufacture, it also requires bigger enclosure, which also cost more as material cost is the primary cost factor when we're talking about production volume.
« Last Edit: June 01, 2026, 06:04:08 pm by asmi »
 
The following users thanked this post: glenenglish

Offline glenenglish

  • Frequent Contributor
  • **
  • Posts: 556
  • Country: au
  • RF engineer. AI6UM / VK1XX . Aviation pilot. MTBr
Re: I'd like to know your experience with Gowin FPGAs
« Reply #11 on: August 17, 2026, 09:38:51 am »
you can do 0.8mm BGA on a $5 4 layer JLC PCB.....  and you can hand place it.
0.2mm hole   / 0.4mm diameter vias are  base level capability these days.....

In microcontrollers, I actually choose the 10x10 100ball  0.8mm BGA over a 100 lead 0.5mm QFN....
and ANY DAY over any 0.4mm QFN

anyway, suggest Efinix. San Jose company, software is OK, devices fast if only LUT4s.....
« Last Edit: August 17, 2026, 09:42:02 am by glenenglish »
 

Offline K9DTV

  • Contributor
  • Posts: 30
  • Country: us
Re: I'd like to know your experience with Gowin FPGAs
« Reply #12 on: Yesterday at 11:15:54 am »
Not been on in some time and just happened a cross this, as I was look for Gowin posts.

I have worked with Gals/Pals and CPLDs before but never a FPGA, so I have picked up Intel and  Xilinx boards, but just never got started with them.
I think the reason was that the boards (Chip) were just way to big and the software had a steep learning curve.
Then I ran in to GOWIN and there stuff was CHEAP and picked up some of their boards.
In three days I had a working video game and used up all the LUT and ram.
This was the Sipeed Tang Primer 20K Dock, I think I paid $22 for it (before Tariffs).
The software was easy to use and there was an example on using the LCD (I would not of known the timming) that got me started.
So, for me they opened a door that I was not willing to open before.

Anyway my site is K9DTV.COM, there is noting for sale there (and there never will be) and everything there is open source.
P.S. The (NEW) site is not even a week old, so it is not done and I am working on it!
« Last Edit: Yesterday at 11:35:02 am by K9DTV »
 

Offline zapta

  • Super Contributor
  • ***
  • Posts: 6585
  • Country: 00
Re: I'd like to know your experience with Gowin FPGAs
« Reply #13 on: Yesterday at 06:59:34 pm »
Anyway my site is K9DTV.COM, there is noting for sale there (and there never will be) and everything there is open source.

Very nice site.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf