Forum Discussion
Dual Port Nios V BSP error
Hi Fabian
This is the response I received from the factory.
"In Quartus Prime Pro 26.1, the BSP Editor presents your true dual-port onchip RAM as two separate memory devices:
- intel_onchip_memory_0_s1 (instruction / .text / reset path)
- intel_onchip_memory_0_s2 (data path: .bss, .heap, .rodata, .rwdata, .stack)
Both are reported at base address 0 with length 32,768 bytes, so the editor flags overlapping memory devices and marks the BSP as not valid. That matches what Fabian described on the forum: Pro lists dual-port OCM as two BSP devices (s1 / s2), while Quartus Prime Standard presents the same hardware as a single memory device connected to both instruction and data.
This is how we treat this on Pro today:
For Nios V BSP generation on Quartus Prime Pro, each slave port that appears in the BSP memory list is validated as its own memory device. If two of those devices share the same (or overlapping) address range, BSP creation fails. There is no published Pro fix that collapses true dual-port OCM into one BSP device the way Standard does. Prior Embedded guidance for this class of failure is: do not leave instruction and data views of the same physical memory as two overlapping slaves in the Pro address / BSP map.
Interim options:
1. Preferred for Pro BSP: use separate onchip memories for instruction and data instead of one true dual-port block shared by both managers at the same base address.
2. If you must keep dual-port hardware: assign non-overlapping base/size for the two ports in Platform Designer, then map linker sections across the two non-overlapping BSP memory regions. This can allow BSP create to succeed, but it splits the contiguous map and reduces usable shared memory efficiency (same tradeoff noted on the forum).
3. Avoid any instruction/data bridge topology that creates an additional overlapping slave view of the same physical RAM in the system address map."
Hello Steve,
thanks for the confirmation. Is a fix for this issue planned in a future Quartus release and if yes for which?
With limited FPGA RAM ressources available an efficient memory usage model for NIOS applications is inevitable.
best regards
Fabian