PicoBlaze

[richkeefe]

Hello,

Has anyone experienced a problem in Virtex 6 when a set of Chipscope elements (ILAs and ICON) are included in the build with the KCPSM6? When I try this, I get a bunch of MAP errors during mapping of elements in the pBlaze data path. Here's an example:

ERROR:Pack:2811 - Directed packing was unable to obey the user design
   constraints (BLKNM=LCD/processor/KCPSM6_SANDR) which requires the combination
   of the symbols listed below to be packed into a single SLICE component.

   The directed pack was not possible because: There are not enough resources in
   the SLICE to meet the demand of the registers within the SLICE.

   The symbols involved are:
    FLOP symbol "LCD/processor/data_path_loop[0].low_hwbuild.shift_rotate_flop"
   (Output Signal = LCD/processor/shift_rotate_result<0>)

The pBlaze component is logically isolated from the components that are being monitored by the ILAs. If I exclude the Chipscope components, all is well and the FPGA build is successful.

[chapman]

Yes! Please see this previous thread...

http://forums.xilinx.com/t5/PicoBlaze/Spartan-6-and-Chipscope-on-ISE-12-3/td-p/108717

Ok, that one was reported by a Spartan-6 user but that isn't relevant. I hope the workaround is adequate for now.

[richkeefe]

Hi Ken,

Thanks for the quick reply.

I've reviewed the thread you provided.

I am using the KCPSM6 to operate the LCD of the ML605. The CS is monitoring elements unrelated to the LCD or KCPSM6. Thus, it seems that the workaround (adding a register between CS & KCPSM) is not applicable to me, since I am not using CS to monitor any portion of the KCPSM6.

Any other ideas?

Regards,

Rich

[chapman]

Rich,

Sorry, I should have read your first post a bit better before I relied!

Anyway, it looks like your case is somewhat different but since it clearly indicates that there is no issue unless you add Chipscope then I feel it needs to be treated as a Chipscope issue rather that PicoBlaze. As such, can I request that you take this to Xilinx technical support for them to reveiw?

http://www.xilinx.com/support/clearexpress/websupport.htm

[nicetyproject]

Rich, if it still matters you may wish to try forcing your ILA instance to 1.03.a version directly in the xco file - at least this was a solution for me. Note that I am on 13.1 and Spartan-6 here.

I tried to use the latest (1.04.a) version of ILA for my existing project with kcpsm6 (it was initially on ila 1.03.a) and those mapping errors happened to me. Then I moved back to ILA 1.03.a and everything went fine. I hope this may help you as well.

Regards,

Vladislav

[maquicoser]

Many thanks for this link kcmman, Work well for me.