ContributionsMost RecentMost LikesSolutionsRe: LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro Hello Liang Yu, The QSYS workaround is simpler, and resolved the issue. Thank you! D. Re: LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro Never mind. It actually works, even though it shows two devices with the same name. Thank you, D. Re: LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro Hello Liang Yu, So I tried to manually add linker memory device, following the steps in the link you provided. Unfortunately, it does not work. What happens is, a second, duplicate device is created, and still not accessible for creating linker regions, section mappings etc. Here is how the memory map looks originally. The EMIF IP is shown as lpddr4_s0_axi4: I add a new Memory Device, with name lpddr4_s0_axi4, Base Address 0 and Size 0x80000000. This results in the following Memory Map: Notice how now there are two lpddr4_s0_axi4 devices, and neither one of them is usable in the BSP Linker Script. Please advise. Thank you, D. Re: LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro Hello Liang Yu, Thank you for your reply. Will try Quartus Prime 26.1.1 Pro once it is available. Best regards, D. LPDDR4 not available in NIOSV/g linker script - Agilex-5, Quartus 26.1 Pro Hello, I have a simple design for Agilex 5, using NIOS V/g and EMIF IP with LPDDR4 memory. I have the NIOS V instruction and data manager ports connected to the EMIF IP. Design compiles Ok. But when I create a BSP, in the linker section, there is not a memory device for the LPDDR4. In this thread, a similar problem seems to be mentioned - issue-with-bsp-creation-for-nios-vm-using-lpddr4-on-agilex-5-quartus-24-1--24-3 Does it mean that Address Span Extender IP must be used in order to have the LPDDR4 show in the linker script section, as an available memory device? SolvedRe: NIOS V/g - peripherals under 2GB Peripheral Region Hello Liang Yu, Thank you for your detailed response. This answers my question. Best regards, D. NIOS V/g - peripherals under 2GB Peripheral Region Hello, I am trying to clarify the information provided in the following KB: Why are the peripherals under 2gb peripheral region still cached by the NIOS V/g Does the above KB recommends to have non-cacheable peripheral regions above the 2GB address - that is, non-cacheable space starts from address 0x80000000, or any address above that? Thank you, D. SolvedRe: NIOSV firmware stuck when juart-terminal is not open for the print messasges. When you generate BSP, go to the JUART Driver settings - there is an option to allow the driver to ignore when the output FIFO is full. Enable that option and it will not wait for somebody to read the output. Re: NIOS V with FreeRTOS Hi @BoonBengT_Altera , No further doubts. Thank you, d. Re: NIOS V with FreeRTOS Thank you for this information. I was wondering if copying the source code, manually, from the IP-s, would work. Now you confirmed it.