Code Migration 10.0 to 10.1 messes up linker settings. RES fails.

[gseq]

Hello,

We have our code running under 10.0 - builds and runs in flash fine. However, when the project is imported to 10.1, there is an option for smart migration - which fails.

Specifically the following:

• 'Building target: example_flash'

'Invoking: ColdFire Linker'

"C:/Program Files/Freescale/CW MCU v10.1/MCU/ColdFire_Tools/Command_Line_Tools/mwldmcf" @@"example_flash.args" -o "example_flash" 

C:/Program Files/Freescale/CW MCU v10.1/MCU/ColdFire_Tools/Command_Line_Tools/mwldmcf|Linker|Error

>Linker command file error at line 48

>File not found: exceptions_cfv2.c

C:/Program Files/Freescale/CW MCU v10.1/MCU/ColdFire_Tools/Command_Line_Tools/mwldmcf|Linker|Error

>Link failed.

It seems it cannot find exceptions_cfv2.c which is already present and worked fine under 10.0 We are unsure how to proceed. Any help is appreciated. 

Thanks!

[RayD]

Find your Linker Configuration File. It has a .lcf suffix.
Look for the line that says "exceptions_cfv2.c".
Change it to say "exceptions_cfv2_c.c".
The CW10.1 Linker massages the filename in that line and makes it work. I don't know how or why. Someone else in these forums discovered this Linker behavior and posted a note about it, I forget what his note was called. Maybe someone else can post the link?

[J2MEJediMaster]

This appears to be the posting that you are talking about:

https://community.freescale.com/thread/80592

---Tom

[RayD]

That's the one!  Thanks for posting the link.

Regards

Ray

[J2MEJediMaster]

Why don't you submit a service request on this? If this is a new behavior, it needs to be better documented if it is tripping developers up. Click here to submit a service request.

---Tom

[dataScout]

- when specifing source filenames in the LCF, the linker tries to match them with their corresponding objects (since the linker will actually use the object files, not the source files)

- since the build system modified the object names (<FILE>_<EXT>.obj, instead of <FILE>.obj as it was before, but this is a different discussion), the LCF should be modified according to this change (i.e. use <FILE>_<EXT>.obj instead of <FILE>.<EXT> in the LCF - <FILE>_<EXT>.<EXT> also works because the linker know how to find the object starting from this)

- this issue should be fixed in next releases