Announcements

Robots are revolutionizing our lives in many ways. Join our webinar to learn about Infineon’s broad portfolio of robot building blocks.
Click here to register.

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

AURIX™ Forum Discussions

SagarZF
Level 1
Level 1
First question asked Welcome!

Error:

"C:\\app\\TASKING\\TriCore v6.3r1\\ctc\\bin\\amk" -j12 all
Linking to RN050524-S1-Bootloader-Mainline.elf
ltc F014: core mpe:tc0 specified on commandline not found in LSL file
amk E452: ["makefile" 68/0] target 'RN050524-S1-Bootloader-Mainline.elf' returned exit code 1
amk E451: make stopped

please suggest me how to resolve this error. 

0 Likes
1 Solution
User13836
Level 5
Level 5
10 likes received 50 sign-ins 10 solutions authored

The information provided indicates that you are using the TASKING TriCore toolset v6.3r1. The linker error message:

ltc F014: core mpe:tc0 specified on commandline not found in LSL file

is generated when the linker LSL file you are using is for the virtual core definition (vtc) and not for a core 0 only core definition. Please verify the linker invocation options used. I suppose the option 

--core=mpe:tc0 

is used. If so please replace this by option:

--core=mpe:vtc 

to verify if the linker error persists or disappears.

Best regards,

Ulrich Kloidt
TASKING tools support

View solution in original post

0 Likes
2 Replies
dw
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

@User13836 Could you please have a look?

Hi Sagar,

Suggest to start from an original project to build, then check what is changed in your project.

0 Likes
User13836
Level 5
Level 5
10 likes received 50 sign-ins 10 solutions authored

The information provided indicates that you are using the TASKING TriCore toolset v6.3r1. The linker error message:

ltc F014: core mpe:tc0 specified on commandline not found in LSL file

is generated when the linker LSL file you are using is for the virtual core definition (vtc) and not for a core 0 only core definition. Please verify the linker invocation options used. I suppose the option 

--core=mpe:tc0 

is used. If so please replace this by option:

--core=mpe:vtc 

to verify if the linker error persists or disappears.

Best regards,

Ulrich Kloidt
TASKING tools support

0 Likes
This widget could not be displayed.