Re: BlockRAM connection error
- From: young <zhang.young@xxxxxxxxx>
- Date: Fri, 07 Sep 2007 01:47:30 -0000
Hi Paulo,
Thank you for your help.
I will try to read the report as you suggested. I have tried in some
other way and can build
the project without this map error. But now I have 2 very wired cases.
In one case, I have a failed project and then create new a new porject
with the same mhs
and mss configuration, the latter one succeed.
In another case, I change the a successful case's configuration, which
repaces an opb uart
and an opb intc with an opb_gpio, this project fail with the same map
error.
At this time, I am really not sure what's the casue of error. Do you
have any suggestion ?
Many thanks,
On Sep 5, 6:07 pm, Paulo Dutra <paulo.du...@xxxxxxxxxxxxx> wrote:
The typical source of the error is leaving the clock unconnected on the
bus (opb, lmb, or plb) which is then forward propagated to all periphals
on the bus. if this is the problem, then read no further.
However, your situation may not be typical. First, you'll need to
discover your source of the error in the trimming section of the MAP
report. This is the .MRP file. To get a verbose description of the
trimming report. You'll need to run xflow/projnav without the .BMM file.
Without the BMM file in the flow, map/par will run to completion without
the "all memory mapped blockram" error. Open the MRP and follow the
trimming report.
Good luck.
.
- References:
- Re: BlockRAM connection error
- From: Paulo Dutra
- Re: BlockRAM connection error
- Prev by Date: Rocket IO clock
- Next by Date: Re: VCCAUX too high on a Spartan 3 design
- Previous by thread: Re: BlockRAM connection error
- Next by thread: 【Nios II】How Can I Find Out These Functions ?
- Index(es):
Relevant Pages
|