7229 - Lattice Propel: Why am I unable to view my custom Memory in the Data Memory Region of Linker Script?

• Related Articles

• 7249 - Propel: Why is my Linker Script Section Name unable to map to the instantiated memory region?

  Description: In Lattice Propel v2023.1, you may encounter a scenario where the Linker Script Section Name is unable to map to the pre-defined memory region. Solution: To workaround this issue, avoid using Linker "Section Name" as the first word of ...

• 7053 - Propel: Why I unable to run debugger with Propel SDK on my RISC-V Project?

  Description: 1. RISC-V reset vector is fixed at address 0x00000000, thus instruction memory must start at address 0x0. 2. RISC-V instruction port is a read only port. To run debugger with Propel SDK, the SoC design must support writes to the ...

• 7016 - Propel 2.2 and below: Why is File I/O Operation not working with Lattice Propel's Hello World Example?

  Based on picolib documentation, the FILE I/O operation needs heap support. In the HELLO WORLD template of Lattice Propel, the heap size is set to 0x00 and needs to be changed. Increase the heap size in the linker script and rebuild the project. Just ...

• 7156 - Propel: How to perform Memory Allocation in RISC-V

  Description: Malloc (Memory Allocation) require you to allocate memory to heap. In Propel SDK, the default heap allocation is 0. You should allocate a minimum amount of memory (example: 0x100) for malloc initialization. Solution: You may find the ...

• 7012 - Propel: Is it possible to script the process of creating a project in Lattice Propel SDK?

  Propel SDK project is based on "Eclipse CDT Management Build System". Since the system has no command-line support for creating projects fundamentally, Propel SDK also has no command-line support for creating projects.