9 years, 5 months ago.

Copyright for GCC ARM Linker script for TARGET_NUCLEO_L152RE

Hi, thanks for fixing CoIDE and emBlocks export for TARGET_NUCLEO_L152RE projects. It now compiles without error. I have however noticed a copyright notice in the STM32L152XE_FLASH.ld file:

http://developer.mbed.org/users/mbed_official/code/mbed-src/file/fc5dba704912/targets/cmsis/TARGET_STM/TARGET_STM32L1/TARGET_NUCLEO_L152RE/TOOLCHAIN_GCC_ARM/STM32L152XE_FLASH.ld

It mentions: (c)Copyright Atollic AB. You may use this file as-is or modify it according to the needs of your project. This file may only be built (assembled or compiled and linked) using the Atollic TrueSTUDIO(R) product. The use of this file together with other tools than Atollic TrueSTUDIO(R) is not permitted.

This is the file I get when exporting it for CoIDE and emBlocs. The copyright states: The use of this file together with other tools than Atollic TrueSTUDIO(R) is not permitted.

I replaced the startup and linker script with a modified version of the files for the NUCLEO_F103RB (STM32F10X.ld and startup_stm32f10x.S), which doesn't seem to have these copyright limitations. These files also seem more consistent with the startup and linker scrips used with the other Nucleo projects. Maybe someone should replace existing files with the attached ones?

/media/uploads/modtronix/stm32l152re_flash.ld /media/uploads/modtronix/startup_stm32l152xe.s

The seem to be other files with the same copyright, like STM32F302X8_FLASH.ld. This file is also exported for GNU ARM and related tools, meaning it will not be built using Atollic TrueSTUDIO. Does not comply with copyright notice.

2 Answers

9 years, 5 months ago.

It seems that pull requests should really be checked for an Apache license before they are merged in by ARM. These varying licenses make it tricky for people to actually base code off of the SDK.

Sometimes I even wonder whether the person issuing a pull request has the necessary copyright to even issue the request under the contributor agreement. Most times I would think that you could only issue a pull request containing new files which either have yourself or an organization that has given you legal privileges to represent their rights listed as the Copyright holder.

9 years, 5 months ago.

Thanks for pointing this out. We missed this, I am going to create a new issue on github, assign it to the creator of the file, to fix it as soon as possible.

Regards,
0xc0170

Hi Martin, I see someone updated all linker files. They are however wrong. See this issue:

http://developer.mbed.org/users/mbed_official/code/mbed-src/issues/11

I haven't checked other files. I see heaps of *.ls and *.s files were changed with revision 419. Maybe someone should do a good check of all these changes?

I am not sure where to post issues for mbed-src. I put it in the "issues" section of "mbed-src", but seems to be virtually no activity there. Maybe better place would be in "Bugs & Suggestions" section of forum? Please advise?

posted by modtronix H 27 Nov 2014