Forum Discussion
Altera_Forum
Honored Contributor
19 years agoOkay, I just went and deleted the second processor, and removed all the dual-port stuff from my RAM blocks. I left the two extra RAM blocks at the same non-contiguous addresses mentioned above. I get the exact same behavior as above http://forum.niosforum.com/work2/style_emoticons/<#EMO_DIR#>/mad.gif - the extra blocks are never populated by the debugger even though these blocks show up in all of the generated.* script files, and are clearly properly embedded in the ELF objects.
generated.x: /* Define symbols for each memory base-address */
__alt_mem_onchip_memory_main = 0x00010000;
__alt_mem_onchip_memory_int_code = 0x00020000;
__alt_mem_onchip_memory_int_data = 0x00040000; generated.gdb: # onchip_memory_main
mem 0x00010000 0x00010000+20480 cache
# onchip_memory_int_code
mem 0x00020000 0x00020000+4096 cache
# onchip_memory_int_data
mem 0x00040000 0x00040000+1024 cache Even the .hex files for these last two sections are empty, which means that elf2hex is busted as well since I can tell from the elfobj dump that the data should be there $(QUARTUS_PROJECT_DIR)/onchip_memory_main.hex: $(ELF)
@echo Post-processing to create $(notdir $@)
elf2hex $(ELF) 0x00010000 0x14FFF --width=32 $(QUARTUS_PROJECT_DIR)/onchip_memory_main.hex --create-lanes=0
$(QUARTUS_PROJECT_DIR)/onchip_memory_int_code.hex: $(ELF)
@echo Post-processing to create $(notdir $@)
elf2hex $(ELF) 0x00020000 0x20FFF --width=32 $(QUARTUS_PROJECT_DIR)/onchip_memory_int_code.hex --create-lanes=0
$(QUARTUS_PROJECT_DIR)/onchip_memory_int_data.hex: $(ELF)
@echo Post-processing to create $(notdir $@)
elf2hex $(ELF) 0x00040000 0x403FF --width=32 $(QUARTUS_PROJECT_DIR)/onchip_memory_int_data.hex --create-lanes=0