05-24-2010 01:58 PM
05-26-2010 02:45 AM
This message was moved from Timing Analysis.
You should work to resolve the timing issue in the design as this may result in the incorrect behaviour of hardware. Turning off the option "Treat timing closure failure as error" will allow the tools to complete but this only workarounds the timing issue.
Can someone with EDK knowledge please comment on issue 2.
05-26-2010 03:41 AM
On the 2nd issue, did you increase the size in the linker script or in the actual hardware.
They must both match each other and you can't just increase the size of memory in the linker script without increasing the same amount of memory in hardware.
I would also just increase the memory in step of 2x since large LMB memory has a negative impact on the frequency.
05-26-2010 11:42 AM
I increased both ( dlmb_ctrl and ilmb_ctrl ) to 256 K.....
...In linkerScript properties I see :
-ilmb_ctrl_dlmb_ctrl ... 256K Leght
When I implement bitstreamno error appear related with mb_crl, so, I assumed it passed....
...I know I have to get into Timing Analyzer and timing constraint stuffs, the point is that "system.ucf" constraint was generated along with BSB process....and MMU configuration is carried out after it...and I posted it hoping somebody had faced before with same "system.ucf" MMU adjunting trouble.
Attached is my system.ucf...maybe it will gives a clue for somebody