Closed GoogleCodeExporter closed 9 years ago
Original comment by jeffrey....@gmail.com
on 20 Jan 2012 at 6:17
Thank you for reporting this issue and helping improve ODIN II!
The memories are undergoing a major overhaul now. I have fixed the overflow
problem in the printout in my local version and it will be released to SVN as
soon as we've published our results.
The depth ODIN II can handle depends on what optimizations you are doing, the
amount of RAM in your machine and which architecture you are mapping to. In
your case, ODIN II was splitting all memories down to a data width of 1, which
resulted in poor mapping performance on such a large memory block. If you
remove the class="memory" from the memory specifications in the architecture
file you supplied, it will prevent ODIN II from splitting all the memories down
to 1 bit data. Then the compilation will succeed.
Original comment by andy16...@gmail.com
on 5 Apr 2012 at 2:01
Original comment by andy16...@gmail.com
on 5 Apr 2012 at 2:09
Added a configurable bound to memories.h.
Original comment by andy16...@gmail.com
on 5 Apr 2012 at 2:40
Original issue reported on code.google.com by
eddie.h...@gmail.com
on 20 Jan 2012 at 1:08Attachments: