EDK 8.2 Block RAM error
in [FPGA]
|
Prev: ise 7.1
Next: spartan-3e starter kit and ethernet
From: MM on 21 Nov 2006 17:02 > 1 same size rquirement is BS, the tool should tolerate also different > sized blocks It should... however it doesn't.... > 2 and.. same size blocks dont work either, only first one gets PLACED, > second stays unprocessed > > so its just another Xilinx bug, Well, I do have a V4 design, which uses 4 consecutive 32KB BRAM blocks each attached through an individual PLB_BRAM controller and it works (last tried in 8.1)... Perhaps you are trying to do something more advanced... /Mikhail
From: Antti Lukats on 21 Nov 2006 17:19 "MM" <mbmsv(a)yahoo.com> schrieb im Newsbeitrag news:4shb3eFvrarsU1(a)mid.individual.net... >> 1 same size rquirement is BS, the tool should tolerate also different >> sized blocks > > It should... however it doesn't.... > >> 2 and.. same size blocks dont work either, only first one gets PLACED, >> second stays unprocessed >> >> so its just another Xilinx bug, > > Well, I do have a V4 design, which uses 4 consecutive 32KB BRAM blocks > each > attached through an individual PLB_BRAM controller and it works (last > tried > in 8.1)... Perhaps you are trying to do something more advanced... > > > /Mikhail > > hm, i have two 64K blocks on LMB bus, and only first one is updated in the BMM file :( I dont think this is advanced use ? Antti
From: MM on 21 Nov 2006 23:46 > hm, i have two 64K blocks on LMB bus, and only first one is updated in the > BMM file :( > I dont think this is advanced use ? One obvious difference is that I am working with PPC and using PLB_BRAM controllers while you are dealing with MicroBlaze... I can't say why it should matter though... /Mikhail
From: Antti on 22 Nov 2006 07:56 MM schrieb: > > hm, i have two 64K blocks on LMB bus, and only first one is updated in the > > BMM file :( > > I dont think this is advanced use ? > > One obvious difference is that I am working with PPC and using PLB_BRAM > controllers while you are dealing with MicroBlaze... I can't say why it > should matter though... > > /Mikhail BUG::: EDK 8.2 generates BMMs incompatible with ISE 8.2 when BRAM blocks are consecutive. if there is gap in address space then it all works. there is a workaround to manually fix the generated BMM files Antti
From: MM on 22 Nov 2006 17:04
"Antti" <Antti.Lukats(a)xilant.com> wrote in message news:1164200166.358021.84400(a)m73g2000cwd.googlegroups.com... > > BUG::: EDK 8.2 generates BMMs incompatible with ISE 8.2 > when BRAM blocks are consecutive. > if there is gap in address space then it all works. > > there is a workaround to manually fix the generated BMM files So they broke it in 8.2!!!! Are you talking about the AR 24296 for the fix? This is as ugly as it can only get :( I can't beleive this.... /Mikhail |