- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-20-2011 09:33 AM
I have a Virtex6 design with multiple independent Picoblaze instances doing a variety of tasks for me. I encountered packing errors (Pack:2811) and eventually found that I must set KeepHierarchy to "Soft" in order to work around this bug. I have now added a Chipscope module and I am encountering the same packing errors. If I remove the Chipscope I eliminate the error.
I found a couple of threads that discuss these issues but I do not see any resolution to the problem. I have not yet tried placing registers between the PB and CS to see if the design will compile. Are these issues being addressed by Xilinx?
http://forums.xilinx.com/t5/PicoBlaze/Picoblaze-Ch
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-20-2011 09:35 AM
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-21-2011 08:00 PM
I found a couple of threads that discuss these issues but I do not see any resolution to the problem. I have not yet tried placing registers between the PB and CS to see if the design will compile. Are these issues being addressed by Xilinx?
Add the registers - this will fix it.
It sounded like it was being investigated, but the workaround is perfectly adequate for now.
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-24-2011 08:27 AM
The saga continues...
As I mentioned, I have multiple Picoblaze instances in my design. Using the registers between Picoblaze and Chipscope allowed me to debug the first instance. I have now shifted to the second Picoblaze and have encountered a new problem. I now have Chipscope attached to my second Picoblaze using registers to isolate the two. When I compile the design I get all the way to Bitgen and receive the following error messages:
ERROR:PhysDesignRules:2108 - Issue with pin connections and/or configuration on block:<instFlashInterface/Mram_LchipTable>:<RAMB1
ERROR:PhysDesignRules:2105 - Issue with pin connections and/or configuration on block:<instFlashInterface/Mram_LchipTable>:<RAMB1
I have found that if I still get these errors when I disconnect the registers from the Picoblaze and connect them to ground.
genChipscope : if (ChipScope) generate
begin
-- register picoblaze signals to isolate from chipscope
-- this eliminates a PACK:2811 bug in the design tools
process (SysClk)
begin
if rising_edge(SysClk) then -- if rising edge of clock
address_c <= (others => '0');
instruction_c <= (others => '0');
in_port_c <= (others => '0');
out_port_c <= (others => '0');
port_id_c <= (others => '0');
misc_c <= (others => '0');
-- address_c <= address;
-- instruction_c <= instruction;
-- in_port_c <= in_port;
-- out_port_c <= out_port;
-- port_id_c <= port_id;
-- misc_c <= "00000" & k_write_strobe & write_strobe & read_strobe;
end if;
end process;
-- instantiate chipscope ILA unit
instila : ila_picoblaze port map (
control => ila_control,
clk => SysClk,
trig0 => address_c,
trig1 => instruction_c,
trig2 => in_port_c,
trig3 => out_port_c,
trig4 => port_id_c,
trig5 => misc_c
);
end generate;
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-24-2011 10:02 AM
Oops, the error message said nothing about Picoblaze. I saw the reference to block ram and thought it referred to the Picoblaze block rams. I had so much trouble getting PB and CS to play nice with each other and thought this was more of the same.
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-24-2011 03:14 PM
For what it's worth, the workaround for this latest bug is to manually edit the XCO file for each ILA generated by coregen and change the line
"CSET disable_save_keep=false"
to
"CSET disable_save_keep=true"
Regenerate the ILA core and away you go...
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
06-30-2011 11:19 PM
Just as another data point - I was also getting Pack:2811 errors using a single Picoblaze and no Chipscope in an XC6VLX130. I'm successfully using the newer V6 version of Picoblaze in a previous XC6VLX130 design, so I'm not sure what the difference was in this design. I didn't have the time to dig, so I just reverted to the older Picoblaze implementation. Not optimal, but time is valuable.
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-01-2011 05:53 AM
Do you have multiple instances of Picoblaze in your design? I saw the PACK:2811 errors with no Chipscope when I had multiple Picoblaze instances and KEEP HIERARCHY = YES in Synthesis proterties. Setting this to SOFT worked around the problem.
Re: Multiple Picoblaze and Chipscope issues
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-01-2011 05:54 AM











