Forum Discussion
Altera_Forum
Honored Contributor
11 years agoLooking into the code, my guess is that it is the index to RAM3 in the fourth case that might trick the mapper into believing that it could possibly go out of range. What happens if you try to compile with that line looking like this instead:
TRAM(cnt0) <= TRAM(cnt2)(14 downto 0) & RAM3(cnt2)(cnt1); I understand that it will render a functional bug, I would just compile with this to see if that is what causing Quartus to error out.