2219 - LatticeECP2/ECP3: What does the LatticeMico8 linker error message "lm8-elf/bin/ld: region data is full (C_code.elf section .irq_stack)" mean?

The data region of the .elf generated by the LatticeMico8 compiler refers to the initialized and uninitialized data in the C/C++ source code and will be stored in the scratchpad memory of the LatticeMico8 controller. When this data generated exceeds the size of scratchpad memory declared, linker throws the above error.

To eliminate this error, you must increase the size of the Mico8 scratchpad memory in the Mico System Builder(MSB) hardware platform.

To increase the scratchpad size double click LM8 component in the hardware platform and you can configure the scratchpad size under scratchpad settings. The size of the scratchpad memory can be configured from 32 bytes to 4G bytes, in power-of-two increments.

Related Articles
2220 - LatticeECP2/ECP3: What does the LatticeMico8 linker error message "lm8-elf/bin/ld: region text is full (C_code.elf section .text)" mean?
Description: The text region of the .elf generated by the LatticeMico8 compiler refers to the instruction opcodes in the C/C++ source code and will be stored in the PROM memory of the LatticeMico8 controller. When these opcodes generated exceed the ...
ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?
In Diamond version 3.14, there is a bug where it incorrectly limits the number of PLLs in the device to 0 for LFE5U-12F. Example error message: ERROR - (device oversize error). The number of PLL components needed (1) exceeds the number available. ...
1536 - All FPGAs: What is an<b> .</b>elf file in LatticeMico8 Mico System Builder (MSB)?
Description: A LatticeMico8 .elf file is a software "Executable Linked Formal" file. The .elf file contains the Mico8 instructions, debug information, and information about the pre-initialized data.The .elf file is included in the directory that the ...
1479 - Why am I getting the error message "Failed to verify ID" during Full Scan using DL3A/B/C cable?
One will get the above error when the Device ID is not read back properly. The probable workarounds are, 1) Within the ispVM go to the pull down menu Project -> Project Settings, select Advanced and increase the TCK low pulse width to try slowing the ...
2781 - Why do I get the message "ERROR - map: IO buffer em_ddr_data_c_0 drives IO buffer em_ddr_data_pad_0 directly, but this is not possible" on most DDR3 interface signals after instantiation of a Lattice DDR3 IP core?
This FAQ is applicable to all Lattice DDR memory controller IP cores (DDR1/DDR2/DDR3/DDR3-PHY/LPDDR). When a DDR memory interface signal uses a dedicated DDR I/O function, the DDR memory controller or PHY IP core netlist file (.ngo) includes an I/O ...

2219 - LatticeECP2/ECP3: What does the LatticeMico8 linker error message "lm8-elf/bin/ld: region data is full (C_code.elf section .irq_stack)" mean?

2219 - LatticeECP2/ECP3: What does the LatticeMico8 linker error message "lm8-elf/bin/ld: region data is full (C_code.elf section .irq_stack)" mean?

Related Articles

2220 - LatticeECP2/ECP3: What does the LatticeMico8 linker error message "lm8-elf/bin/ld: region text is full (C_code.elf section .text)" mean?

ECP5 / Diamond 3.14: Why does my design get a Map device oversize error related to PLL for LFE5U-12F in with Diamond 3.14, but completes map successfully in earlier releases of Diamond software?

1536 - All FPGAs: What is an<b> .</b>elf file in LatticeMico8 Mico System Builder (MSB)?

1479 - Why am I getting the error message "Failed to verify ID" during Full Scan using DL3A/B/C cable?

2781 - Why do I get the message "ERROR - map: IO buffer em_ddr_data_c_0 drives IO buffer em_ddr_data_pad_0 directly, but this is not possible" on most DDR3 interface signals after instantiation of a Lattice DDR3 IP core?