A strange problem of Chipscope

Hi, The problem may be the different versions: EDK 8.1.02i, ISE 8.1.03i, chipscope 8.2.02i.

They must be the same version: 8.1 or 8.2 and cannot be mixed. It is my guess!

Weng

Oh, that's also possible.

I installed chipscope 8.1i instead of 8.2i. but It's the same.

/Wayne

Weng Tianxiang wrote:

Make sure you rebuild everything. If you work entirely in XPS environment do Hardware/Clean Hardware before rebuilding.

/Mikhail

Hi Mikhai,

Thanks. I tried but it doesn't work either.

/Wayne

MM wrote:

Post your MHS file...

/Mikhail

Hi, Here is a file I recorded for use by myself after I have successfully inserted debuging information into a *.cdc file and used ChipScope correctly without error.

How to start ChipScope procedure correctly:

1. Generate a project as usually, including all files containig signals you want to debug;
2. Synthesize it without errors;
3. Start ChipScope Pro Core Insert;
4. Edit clock channel and trigger/data channels without errors: it means that the number of signals must be the same as you set in the previous page that leads you to go back to several pages to see if they are met: black font is OK, read font is an error. You cannot go forward until you correct the error.
5. Quit "ChipScope Pro Core Insert" software, then click 'Save' button to save the edit file as *.cdc. 'NEVER CLICK INSERT BUTTON', otherwise it would generate double insertion error problem later.
6. Insert *.cdc file into the project by adding source file into the project;
7. Run synthesis only;
8. Double click *.cdc file in the project and check if any signals are needed to change;
9. 6-7 can be skipped if all debug signals are included in *.cdc.
10. Compile to generate bit stream file as usually.

Then a bitstream containing debugging informatin is generated.

ChipScope has some limits on how signals are accessed:

1. Input pin must be accessed through its registered values;
2. Output pin should be accessed through its internal drive signal;
3. All extra debugging signals, i.e., the signals that are added for debugging, must be linked to an extra output pin to avoid them from being optimized out. The extra output pin must be added in *.puf for debugging use only.

A lesson: Never put more than 10 signals at the first time and try the ChipScope successfully. It is a very complex system and every step has a chance to trigger a miner over there. After you clear the way first time, you may add as many signals as you want to.

Especially it is lucky and better if you have an helper who has experiences.

Its manual is too detailed to start for a newbie.

Weng