Feb 13, 2019
03:32 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 13, 2019
03:32 AM
Hi,
I modified the "AscLinAscDemoSwp" example of TC29x for my TC27X/TC27C/TC27D processor. I changed the processor and added the same peripherals. However, when building the application, the following error appears:
Linking to AscLinAscDemoSwp.elf
ltc E112: cannot locate 3 section(s):
ltc I455: requirement: 0x1e bytes of ROM area in space mpe:tc0:linear
ltc I456: section type: group restriction - ordered
ltc I457: .text.inttab0.intvec.000 (180) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (183) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (185) (0xa bytes)
amk E452: ["makefile" 106/0] target 'AscLinAscDemoSwp.elf' returned exit code 1
amk E451: make stopped
I restored the project for TC29x and using that processor the application can be built.
Have someone fixed this error? Or Do you know how to solve that?
Thanks in advance,
I modified the "AscLinAscDemoSwp" example of TC29x for my TC27X/TC27C/TC27D processor. I changed the processor and added the same peripherals. However, when building the application, the following error appears:
Linking to AscLinAscDemoSwp.elf
ltc E112: cannot locate 3 section(s):
ltc I455: requirement: 0x1e bytes of ROM area in space mpe:tc0:linear
ltc I456: section type: group restriction - ordered
ltc I457: .text.inttab0.intvec.000 (180) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (183) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (185) (0xa bytes)
amk E452: ["makefile" 106/0] target 'AscLinAscDemoSwp.elf' returned exit code 1
amk E451: make stopped
I restored the project for TC29x and using that processor the application can be built.
Have someone fixed this error? Or Do you know how to solve that?
Thanks in advance,
1 Reply
Feb 13, 2019
08:44 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Feb 13, 2019
08:44 AM
Hi Asier,
The error message can be an indication that your application footprint has grown to a certain size that it is pushing itself into the area reserved for the interrupt vector table. Presuming you're using Infineons BIFACES framework, you'll need to take a peek into Lcf_Tasking.lsl and see how it locates the interrupt vector table and trap vector table. I think it's by means of define LCF_INTVEC0_START. Sometimes, by simply adjusting the start address to a different location the problem can be resolved. You may also want to instruct the linker to include the locate rules into the mapfile (see linker command line option --map-file-format). These will tell you which sections were selected by what rules and can offer clues what's causing the conflict.
Best regards,
Henk-Piet Glas
Principal Technical Specialist
Embedded Software
alarrucea wrote:
Hi,
I modified the "AscLinAscDemoSwp" example of TC29x for my TC27X/TC27C/TC27D processor. I changed the processor and added the same peripherals. However, when building the application, the following error appears:
Linking to AscLinAscDemoSwp.elf
ltc E112: cannot locate 3 section(s):
ltc I455: requirement: 0x1e bytes of ROM area in space mpe:tc0:linear
ltc I456: section type: group restriction - ordered
ltc I457: .text.inttab0.intvec.000 (180) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (183) (0xa bytes)
ltc I457: .text.inttab0.intvec.000 (185) (0xa bytes)
amk E452: ["makefile" 106/0] target 'AscLinAscDemoSwp.elf' returned exit code 1
amk E451: make stopped
I restored the project for TC29x and using that processor the application can be built.
Have someone fixed this error? Or Do you know how to solve that?
Thanks in advance,
The error message can be an indication that your application footprint has grown to a certain size that it is pushing itself into the area reserved for the interrupt vector table. Presuming you're using Infineons BIFACES framework, you'll need to take a peek into Lcf_Tasking.lsl and see how it locates the interrupt vector table and trap vector table. I think it's by means of define LCF_INTVEC0_START. Sometimes, by simply adjusting the start address to a different location the problem can be resolved. You may also want to instruct the linker to include the locate rules into the mapfile (see linker command line option --map-file-format). These will tell you which sections were selected by what rules and can offer clues what's causing the conflict.
Best regards,
Henk-Piet Glas
Principal Technical Specialist
Embedded Software