- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
error using chipscop pro
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-17-2012 06:23 AM
sir thankyou for your reply.
i have tried to read it using chipscope pro. but the error is coming like...
COMMAND: configure 2 "C:\Documents and Settings\Administrator\Desktop\FPGA_try\abc\cd.bit
INFO: Found 0 Core Units in the JTAG device Chain.
can i know due what is this?as iam new to chip scop pro analizer..hops ur reply
Re: error using chipscop pro
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-17-2012 07:11 AM
The "0 Core Units" info usually means that the bitstream loaded into the FPGA does
not contain the ChipScope ILA core (you mornally add these with the ChipScope inserter
or instantiate them directly in your design).
If your design has a ChipScope ILA core and you still see this message, it may be that
you have downloaded the wrong bitstream, or the FPGA has been loaded from an
attached PROM or Flash from a different bitstream.
By the way, I would suggest avoiding path names with spaces in them like "Documents an Settings" -
there are some portions of the ISE package that don't work well with them. Note that for the English
versions of Windows, this includes you desktop and "My Documents" folders. I normally keep
all Xilinx related stuff in a folder called "Projects" directly off the drive root like C:\Projects
-- Gabor
Re: error using chipscop pro
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-19-2012 02:08 PM
Yes, "0 core" means no chipscope
Lot of users (like me) cofuse the first time as if chipscope is a free hardware core always attached to the FPGA...that's not true, chipscope is part of user "FPGA design", it takes some resource CLB and BRAM... user has to add it in their design before using it
Very fun idea, you have to have your FPGA working first before you can debug it











