Solutions
Update history
Date | Version | Author | Update content |
---|---|---|---|
2023-05-18 | v0.3 | wonder |
|
Here are some normal questions.
Programmer
Make sure there are 2 converter
and COM
device, this means the debugger works well.
The debugger can be used for Jtag and UART, when using its uart function, Jtag is disabled. To solve this, replug the TypeC cable of your board to disconnect the uart connection.
No COM
devices
If there is no COM
device but 2 converter
devices, right click converter B
-> Properties
-> Advanced
-> Load VCP
, then Click OK
and reconnect your USB device.
No convertor
device
It takes 10 seconds for debugger loading the driver. And you can install the driver manually. Click me to download driver
Download frequency
Make sure the frequency is equal or lower than 2.5MHz
, otherwise it may lead some troubles like burning bitstream file really slow or failed burning bitstream file.
Choose Frequency equal to or lower than 2.5MHz
Then cilck Save
Error found
This error means the Programmer application does detect debugger or your driver is wrong.
Visit this programmer compressed file, download it and extract it, replace the programmer folder install with GOWIN IDE by this extracted file.
If you don't know how to replace the programmer folder, just execute the programmer application in the extracted folder to download bitstream file instead of the programmer application installed with GOWIN IDE.
If this problem still occurs after you use our recommended programmer application, try to rerun this application. If all attempts fail, see the begin of this documents about converter
.
Cable lost
Reflash bitstream to solve this. This occurs when flashing bitstream, board and computer does not well disconnected.
Cable open failed
This means the programmer application does not detect the debugger, try this programmer application mentioned in Error found.
If this problem still occurs after you use our recommended programmer application, try to rerun this application. If all attempts fail, see the begin of this documents about converter
.
No Gowin devices found
This means the debugger does not detect the FPGA chip, you can use the latest GOWIN Programmer to solve this problem.
Nano 9K
Because the FPGA JTAG_SEL pin is routed to Key S2, from the GOWIN manual we can see when JTAGSEL_N=0 (Active low), Jtag is enabled.
For Nano 9K, hold S2 key to solve the trouble caused by JTAGSEL_N and JTAG pins are being used as I/O.
Primer 20K
For 20K Dock kits, it's necessary to enable the core board before using debugger debug the chip, just put the 1 switch on the dip switch down, otherwise this error occurs.
Enable Core Board | Disable state | Additional comments |
---|---|---|
When disabled, the LDE0 and LED1 is on, and core board doesn't work. |
When using RV Debugger Plus burning firmware into 20K core board this error occurs, possibly the order of connecting wire is wrong, make sure your connecting order is same as following sheet, or you can check your core board jtag connector inside pins, make sure none of them are crooked(One time we get problem connecting Debugger with core board and finally check out that there is a crooked pin in the jtag connector, this maybe because of doing wrong connection operations when connecting)
The JTAG pin orders can be found in the back of 20K core board.
Core Board | 5V0 | TMS | TDO | TCK | TDI | RX | TX | GND |
Debugger | 5V0 | TMS | TDO | TCK | TDI | TX | RX | GND |
ID code mismatch
This means the selected device in the project mismatch your burning chip. All that refers chip model(The project device, pin constrain, IP modules and programmer device choose) need to be reset.
Board name | Series | Device | Package | Speed |
---|---|---|---|---|
Tang Nano | GW1N | GW1N-1 | QN48 | C6/I5 |
Tang Nano 1K | GW1NZ | GW1NZ-1 | QN48 | C6/I5 |
Tang Nano 4K | GW1NSR | GW1NSR-4C | QN48P | C6/I5 or C7/I6 |
Tang Nano 9K | GW1NR | GW1NR-9C | QN88P | C6/I5 |
Tang Nano 20K | GW2AR | GW2AR-18C | QN88 | C8/I7 |
Tang Primer 20K | GW2A | GW2A-18C | PBGA256 | C8/I7 |
spi flash selected mismatch
The board using GOWIN Semiconductor LittleBee product family (Series of chip names beginning with GW1N) incorporates embedded FLASH in main chip, so when burning firmware we burn into embedded FLASH, and regard the external FLASH as a peripheral.
The board using GOWIN Semiconductor Arora product family (Series of chip names beginning with GW1N) does not incorporate embedded FLASH, so when burning firmware we burn into external FLASH, and the operations are as followed .
Operation isexFlash Erase,Program thru GAO-Bridge |
|
Flash Device we choose Generic Flash |
Download slowly
Don't choose Operation containing Verify
Make sure the frquency is equal or lower than 2.5MHz
, normally 2.5MHz
everything is ok.
Choose Frequency equal to or lower than 2.5MHz
Then click Save
Directory *** has null character.
Error character of the project path.
- Close IDE.
- Check project path, only English works and
_
are Ok, take care of the blank characterin the path.
- Reopen the project, clean and rerun your project.
Can't find bitstream file
Normally the bitstream file with extension name .fs
is in the impl/pnr folder under the project path.
From the picture above we can know the of this bitstream file path is fpga_project1/impl/pnr/fpga_project1.fs
The fpga_project1 is the project directory, the impl folder is generated by IDE, and the download is in the pnr folder.
The file with extension name .fs
is the firmware we will burn into fpga.
IDE
See IP manual
In the IP Core generate interface of IDE, click your target IP, then choose your language reference to see the IP manual.
Click to see instructions
Reconfigure generated IP
In the IP Core generate interface of IDE, click the folder icon next to device selection at the top to open the generated IP configuration interface.
Click to see instructions
Set top module
For project that contains multiple-projects, if you succeed generating your module, right-click the module you want to set as the top module IDE -> Hierarchy interface.
If your Hierarchy interface is the same as what is in the left picture, this means there are logic errors in the code, such as syntax errors or generate errors. Click 'RTL Analysis Error' in the upper right corner then you can see the error type code and location of the error in the dialog box that pops up, as shown in the right picture in the following table.
RTL Analysis Error | Error type and details |
Using GAO
GAO is Gowin Analyzer Oscilloscope, its document can be found in the path like what is shown below
Using this programmer application instead of the programmer application installed with, then you can use GAO.(GAO need run by IDE, so you need to replace the Programmer bin folder by your downloaded one)