在TrueSTUDIO中内置的BLE_SensorDEMO无法在idb007v1上运行

你好杰伊，
谢谢截图。我想你有一个BLUENRG项目，或者？你能为BLUENRG-1制作工作软件吗？
这是我的链接器选项：
-mthumb -T'..  BlueNRG1.ld'-specs = nosys.specs -nostartfiles -nodefaultlibs -static -L ..  ..  ..  ..  ..  ..  Library  Bluetooth_LE  library - L'..'- WI，-cref，-u，-Xlinker， - defsym = ST_LINKER_OPTION = 1'-Wl，-Map = $ {BuildArtifactFileBaseName} .map'-WI， - gc-sections -Wl， - -defsym = malloc_getpagesize_P = 0x80 -Wl， - start-group -lc -lm -Wl， - end-group
-mcpu不包括在内。
这是SW在BLUENRG-1上无法启动/崩溃的原因吗？
问候，
罗伯特



以下为原文




Hi Jay,
Thanks for screenshot. I think you have a BLUENRG-project, or? Can you build working SW for BLUENRG-1?
Here my linker options:
-mthumb -T'..BlueNRG1.ld' -specs=nosys.specs -nostartfiles -nodefaultlibs -static -L............LibraryBluetooth_LElibrary -L'..' -Wl,-cref,-u,-Xlinker,--defsym=ST_LINKER_OPTION=1 '-Wl,-Map=${BuildArtifactFileBaseName}.map' -Wl,--gc-sections -Wl,--defsym=malloc_getpagesize_P=0x80 -Wl,--start-group -lc -lm -Wl,--end-group
-mcpu is not included.
Is this the reason why the SW does not start/crash on BLUENRG-1?
Regards,
Robert

罗伯特，杰伊，
仅供参考，下面您可以找到我的链接器设置。
 
我成功构建并运行了BlueNRG-1的BLE_SensorDemo。它适用于idb007v1板。请注意，没有那个cortex-m0设置链接器使用不正确的libc库。
-mthumb -T'..  BlueNRG1.ld'-specs = nosys.specs -nostartfiles -nodefaultlibs -static -L ..  ..  ..  ..  ..  ..  Library  Bluetooth_LE  library - L'..'- WI，-cref，-u，-Xlinker， - defsym = ST_LINKER_OPTION = 1'-Wl，-Map = $ {BuildArtifactFileBaseName} .map'-WI， - gc-sections -Wl， - -defsym = malloc_getpagesize_P = 0x80 -Wl， - start-group -lc -lm -Wl， - end-group
顺便问一下，你使用的是什么版本的Atollic？
问候，
 
彼得·



以下为原文




Robert, Jay,
Just for reference, below you may find my setting for linker.

I successfully built and run BLE_SensorDemo for BlueNRG-1. It worked on idb007v1 board.Please note, that without that cortex-m0 settings linker uses incorrect libc library.

-mthumb -T'..BlueNRG1.ld' -specs=nosys.specs -nostartfiles -nodefaultlibs -static -L............LibraryBluetooth_LElibrary -L'..' -Wl,-cref,-u,-Xlinker,--defsym=ST_LINKER_OPTION=1  '-Wl,-Map=${BuildArtifactFileBaseName}.map' -Wl,--gc-sections -Wl,--defsym=malloc_getpagesize_P=0x80 -Wl,--start-group -lc -lm -Wl,--end-group
By the way, what version of Atollic do you use?
Regards,

Piotr

再说一遍。我们应该在构建期间比较控制台窗口中的设置，因为这是传递给GCC的。其他设置（来自灰色设置窗口）可能与此不同，因为Atollic可以更改或扩展。
所以，我从控制台的链接器行是：
arm-atollic-eabi-gcc -o Release.elf Hal  clock.o Hal  context_switch.o Hal  osal.o Hal  sleep.o Library  BlueNRG1_adc.o Library  BlueNRG1_dma.o Library  BlueNRG1_flash.o Library  BlueNRG1_gpio .o Library  BlueNRG1_i2c.o Library  BlueNRG1_mft.o Library  BlueNRG1_pka.o Library  BlueNRG1_rng.o Library  BlueNRG1_rtc.o Library  BlueNRG1_spi.o Library  BlueNRG1_sysCtrl.o Library  BlueNRG1_uart.o Library  BlueNRG1_wdg.o Library  misc的.o SDK_Eval_BlueNRG1  LPS25HB.o SDK_Eval_BlueNRG1  LSM6DS3.o SDK_Eval_BlueNRG1  SDK_EVAL_Button.o SDK_Eval_BlueNRG1  SDK_EVAL_Com.o SDK_Eval_BlueNRG1  SDK_EVAL_Config.o SDK_Eval_BlueNRG1  SDK_EVAL_I2C.o SDK_Eval_BlueNRG1  SDK_EVAL_Led.o SDK_Eval_BlueNRG1  SDK_EVAL_SPI.o启动 system_bluenrg1.o用户 BlueNRG1_it .o User  SensorDemo_main.o User  gatt_db.o User  sensor.o
问候，
 
彼得·



以下为原文




Just one more note. We should compare setting that are in console window during the build, beacause this is what is passed to GCC. Other settings (from grey setting window) may differ from that because Atollic can alter it or extend.
So, my linker line from console is:

arm-atollic-eabi-gcc -o Release.elf Halclock.o Halcontext_switch.o Halosal.o Halsleep.o LibraryBlueNRG1_adc.o LibraryBlueNRG1_dma.o LibraryBlueNRG1_flash.o LibraryBlueNRG1_gpio.o LibraryBlueNRG1_i2c.o LibraryBlueNRG1_mft.o LibraryBlueNRG1_pka.o LibraryBlueNRG1_rng.o LibraryBlueNRG1_rtc.o LibraryBlueNRG1_spi.o LibraryBlueNRG1_sysCtrl.o LibraryBlueNRG1_uart.o LibraryBlueNRG1_wdg.o Librarymisc.o SDK_Eval_BlueNRG1LPS25HB.o SDK_Eval_BlueNRG1LSM6DS3.o SDK_Eval_BlueNRG1SDK_EVAL_Button.o SDK_Eval_BlueNRG1SDK_EVAL_Com.o SDK_Eval_BlueNRG1SDK_EVAL_Config.o SDK_Eval_BlueNRG1SDK_EVAL_I2C.o SDK_Eval_BlueNRG1SDK_EVAL_Led.o SDK_Eval_BlueNRG1SDK_EVAL_SPI.o Startupsystem_bluenrg1.o UserBlueNRG1_it.o UserSensorDemo_main.o Usergatt_db.o Usersensor.o  
Regards,

Piotr

有用！非常感谢！
我的错误：我用逗号添加-mcpu选项 - ＆gt;错误
-Wl，-cref，-u，-Xlinker， - defsym = ST_LINKER_OPTION = 1-MCPU =皮质-M0
没有逗号（只有空格） - ＆gt;好
-Wl，-cref，-u，-Xlinker， - defsym = ST_LINKER_OPTION = 1-MCPU =皮质-M0
现在我可以使用TrueStudio 9.0.0构建正在运行的SW
非常感谢！
问候，
罗伯特



以下为原文




It works! Thanks a lot!
My mistake: I added -mcpu option with a comma -> Error
-Wl,-cref,-u,-Xlinker,--defsym=ST_LINKER_OPTION=1-mcpu=cortex-m0
without comma (only space) -> OK
-Wl,-cref,-u,-Xlinker,--defsym=ST_LINKER_OPTION=1-mcpu=cortex-m0
Now I can build running SW with TrueStudio 9.0.0
Thanks a lot!
Regards,
Robert

感谢您分享此解决方案@Piotr Romaniuk（社区会员），@ Robert Scholz（社区会员），为我工作。
（问题仍然存在于BlueNRG-1_2 DK 3.0.0中。）



以下为原文

Thanks for sharing this solution @Piotr Romaniuk (Community Member)​ , @Robert Scholz (Community Member)​ , works for me.
(The problem still exists in BlueNRG-1_2 DK 3.0.0.)

谢谢大家详细介绍这个问题！
 
我同意即使使用BlueNRG-1_2 DK 3.0.0。和TrueStudio 9.0.1即使它们看起来构建和加载没有错误，也不会运行开发工具包BLE示例。
 
使用上述-mcpu = cortex-m0选项可以立即解决问题。在我的例子中，我将它添加到Assembler和Linker工具选项中。 -mcpu = cortex-m0 optoion已经在BlueMS App兼容示例的编译器选项中。
 
 我不认为我会自己想出这个。再次感谢你！



以下为原文

Thank you all for presenting this issue in detail!

I agree that even with BlueNRG-1_2 DK 3.0.0. and TrueStudio 9.0.1 none of the dev kit BLE examples will run even though they appear to build and load without error.

Using the -mcpu=cortex-m0 option as described above instantly fixes the problem. In my case I added it to the Assembler and Linker tool options. the -mcpu=cortex-m0 optoion was already in the Compiler options for the BlueMS App compatible example.

I do not think I would have ever figured this out on my own. Thank you again!