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

当我下载图像时，电路板什么都不做
这几乎肯定是做某事 - 所以连接，并找出它在做什么！



以下为原文





when I download the image, the board does nothing
It's almost certainly doing something - so connect the , and find out what it's doing!

嗨安德鲁，
我做了，但从TrueStudio调试，也不起作用！
请阅读我的问题：
https://community.st.com/0D50X00009Xkht2SAB
 我希望ST的参考设计能够工作，但不能进行调试。
 
我的配置坚持：
- ST的董事会，
- TrueSTUDIO（ST建议作为IDE之一） - ST开发工具包（库和TrueStudio项目）
- 来自ST的jtag / programmer
问候，
 
彼得·
 注意：原始帖子包含大量线程对话，只能迁移到第9级



以下为原文




Hi Andrew,
I did, but debugging from TrueStudio, does not work either!
Please read my question:

https://community.st.com/0D50X00009Xkht2SAB
I expected that reference design from ST should work, but not to be debugged.

My configuration constains:
- the board from ST,
- TrueSTUDIO (ST recommended as one of the IDE)- development kit from ST (library and TrueStudio project)
- jtag/programmer from ST
Regards,

Piotr
Note: the original post contained a large number of threaded conversations and was only able to be migrated to the 9th level

OP？这是什么意思？



以下为原文




OP? What does it mean?

romaniuk.piotr写道：
我做了，但从TrueStudio调试，也不起作用！
请阅读我的问题：
https://community.st.com/0D50X00009Xkht2SAB
 那么在OP中包含它会有所帮助。
 
 注意：原始帖子包含大量线程对话，只能迁移到第9级



以下为原文




romaniuk.piotr wrote:
I did, but debugging from TrueStudio, does not work either!
Please read my question:

https://community.st.com/0D50X00009Xkht2SAB
Would have been helpful to include that in the OP, then.

Note: the original post contained a large number of threaded conversations and was only able to be migrated to the 9th level

'Original Post'，或'Opening Post'
也用作'原始海报'或'开场海报'



以下为原文




'Original Post', or 'Opening Post'
Also used as 'Original Poster', or 'Opening Poster'

仔细查看程序执行情况表明它不会从BlueNRG_Stack_Initialization（）返回main（）。
在函数内部生成HardFault异常。
这是一个堆栈跟踪：
[...]
 主要（）
 
BlueNRG_Stack_Initialization
 BlueNRG_Stack_Perform_Crystal_Check
 BlueNRG_Stack_Initialize_Layers
 PM_init
 __aeabi_fdiv（）=＆gt;中的异常HardFaultHandler
pc = 10041722 HardFault处理程序
 
msp = 0x2000.5f98
 
2000.5f98 36 R0＆lt; - msp指向此处
 
2000.5f9c 0 R1
 
2000.5fa0 0350.0000 R2
 
2000.5fa4 0000.6c00 R3
 
2000.5fa8 0000.0018 R12
 
2000.5fac 1004.705f LR - 将返回PM_init
__aeabi_fdiv中的2000.5fb0 1004.08d8＆lt; ---异常位置
 
2000.5fb4 0100.0000
 
2000.5fb8 2000.094c
 
2000.5fbc 2000.08d4
 
2000.5fc0 2000.094c
 
BlueNRG_Stack_Initialize_Layers中的2000.5fc4 1004.1dc1
 
2000.5fc8 2000.094c
 
2000.5fcc 0000.0040
 
2000.5fd0 0000.0001
 
BlueNRG_Stack_Perform_Crystal_Check中的2000.5fd4 1004.1feb
 
2000.5fd8 2000.2604
 
2000.5fdc 0
 
2000.5fe0 0
 
2000.5fe4 ffff.ffff
 
2000.5fe8 ffff.ffff
 
BlueNRG_Stack_Initialization中的2000.5fec 1004.1d51
 
2000.5ff0 1004.b580
 
2000.5ff4 1004.17bb
 
2000.5ff8 1004.b580
 
2000.5ffc 1004.14fd



以下为原文




Closer look to program execution show that it does not return to main() from BlueNRG_Stack_Initialization().
Inside the function HardFault exception is generated.
Here is a stack trace:
[...]
   main()

      
BlueNRG_Stack_Initialization

          BlueNRG_Stack_Perform_Crystal_Check

             BlueNRG_Stack_Initialize_Layers

                 PM_init

                   exception in __aeabi_fdiv()   => HardFaultHandler

pc = 10041722                HardFault Handler

msp = 0x2000.5f98


2000.5f98 36          R0 <- msp points here

2000.5f9c 0           R1

2000.5fa0 0350.0000   R2

2000.5fa4 0000.6c00   R3

2000.5fa8 0000.0018   R12

2000.5fac 1004.705f   LR - would return to PM_init

2000.5fb0 1004.08d8 in __aeabi_fdiv <--- exception location

2000.5fb4 0100.0000

2000.5fb8 2000.094c

2000.5fbc 2000.08d4

2000.5fc0 2000.094c

2000.5fc4 1004.1dc1 in BlueNRG_Stack_Initialize_Layers

2000.5fc8 2000.094c

2000.5fcc 0000.0040

2000.5fd0 0000.0001

2000.5fd4 1004.1feb in BlueNRG_Stack_Perform_Crystal_Check

2000.5fd8 2000.2604

2000.5fdc 0

2000.5fe0 0

2000.5fe4 ffff.ffff

2000.5fe8 ffff.ffff

2000.5fec 1004.1d51 in BlueNRG_Stack_Initialization

2000.5ff0 1004.b580

2000.5ff4 1004.17bb

2000.5ff8 1004.b580

2000.5ffc 1004.14fd

不幸的是没有。我仍然无法从TrueSTUDIO IDE调试。
 
以上数据来自BlueNRG-ST-Link Utility。该工具具有非常有限的功能，但足以获得ARM内核寄存器和RAM内容。我从链接器生成的列表中获取了函数名称。



以下为原文




Unfortunatelly not. I still cannot debug from TrueSTUDIO IDE.

Above data is from BlueNRG-ST-Link Utility. This tool has very limitted functionality, but enough for getting ARM core register and RAM contents. I have taken function names from a listing generated by the linker.

romaniuk.piotr写道：
 __aeabi_fdiv（）=＆gt;中的异常HardFaultHandler
听起来像是与浮点相关 - 所以请检查您的FP设置。
尝试在没有FP HW的芯片上进行硬件FP可能会产生硬故障......



以下为原文




romaniuk.piotr wrote:

                   exception in __aeabi_fdiv()   => HardFaultHandler
Sounds like something to do with Floating Point - so check your FP setup.
Trying to do hardware FP on a chip with no FP HW probably would give a Hard Fault ...

romaniuk.piotr写道：
仔细查看程序执行情况表明它不会从BlueNRG_Stack_Initialization（）返回main（）。
在函数内部生成HardFault异常。
这是否意味着你有调试器工作，那么？



以下为原文




romaniuk.piotr wrote:
Closer look to program execution show that it does not return to main() from BlueNRG_Stack_Initialization().
Inside the function HardFault exception is generated.
Does this mean you've got the debugger to work, then?

是的我在Atollic论坛上发布了这个问题，但尚未发布到ST。



以下为原文




Yes I post the issue on Atollic forum, but not yet to ST.

哦 - 那是一种痛苦。
你有没有尝试过Atollic论坛？
你试过用ST提起诉讼吗？



以下为原文




Oh - that's a pain.
Have you tried on the Atollic forum?
Have you tried raising a case with ST?

ST DevKit的TrueSTUDIO项目缺少架构选项：
 -mcpu =皮质-M0
如果没有链接的libc包含ARM模式的指令（但它应该只是Thumb - 因为它是Cortex-M0）。
 
这就是HardFault异常发生的原因。
该选项应添加到：
 项目属性| C / C ++ Build |设置，选项卡工具设置
对于每个组：
 汇编程序，C编译器，C链接器
在Miscellaneouos |其他选项领域。



以下为原文




TrueSTUDIO project from ST DevKit has missing architecture option:
   -mcpu=cortex-m0
Without that linked libc contains instructions in ARM mode (but it should be only Thumb - because it is Cortex-M0).

That is why HardFault Exception occured.
The option should be added in:
   Project Properties | C/C++ Build |Settings, tab Tool Settings
for each group:
  Assembler, C Compiler, C Linker
in Miscellaneouos |Other options field.

嗨，
请在Assembler组中选择子组，然后在字段中选择白色体系结构选项。
 
通过类比，对于C和link.Regards，
彼得·



以下为原文




Hi,
please select subgroup in Assembler group, then white architecture option in field.

The same, by analogy, for C and linker.Regards,
Piotr

我是TrueStudio的新手，我在更新选项时遇到问题......
在所有情况下，“所有选项：”字段都显示为灰色，我无法修改内容（请参见随附的屏幕截图）。关于如何解决这个问题的任何想法？
谢谢！
松鸦



以下为原文




I'm new to TrueStudio and am having trouble updating the  option...
In all cases the ''All Options:'' field is grayed out and I'm unable to modify the contents (see attached screenshot). Any ideas on how to get around this?
Thanks!
jay

谢谢Piotr，
正如对其他人仍然遇到问题的说明一样，我没有必要修改链接器选项，它已经为我正确配置，这可以通过查看'C Linker'子菜单中的'All options：'字段来验证。尝试在“其他选项”下第二次添加它会导致构建错误。
但是，省略这个仍然没有导致工作二进制文件，它将编译正常但不会正确执行。我还必须将Assembler / C编译器/ C链接器 - ＆gt; Target-＆gt;'指令集'从'Thumb2'更改为'Thumb'。
在这两个更改之后，我能够编译，刷新并运行st示例。
松鸦



以下为原文




Thanks Piotr,
Just as a note to others still experiencing issues, I didn't have to modify the linker options, it was already configured correctly for me, this can be verified by looking at the 'All options:' field in the 'C Linker' submenu. Trying to add it a second time under the 'Other options' lead to build errors.
However, omitting this still didn't result in a working binary, it would compile fine but wouldn't execute properly. I additionally had to change the Assembler/C compiler/C linker->Target->'instruction set' from 'Thumb2' to 'Thumb'.
After these two changes I was able to compile, flash, and run the st examples.
jay

你好杰伊，
我很惊讶程序没有使用Thumb2设置。根据ST文档，BlueNRG芯片是Cortex-M0，并且来自ARM Cortex-M0技术参考手册（rev.r0p0）DDI0432C第28页：
 '实施的设备提供：
 
 •低门数处理器，具有以下特点：
  - ARMv6-MThumb®指令集。
  - 技术
 [...]'我在灰色选项字段中看到仍然是-mthumb通过我在目标指令集中设置Thumb2。
 
从thumb2切换到thumb时，选项有什么变化吗？请在构建控制台窗口中验证，比较两个版本的内容。
问候，
 
彼得·



以下为原文




Hi Jay,
I am surprised that programs were not working with Thumb2 setting. According to ST documentation BlueNRG chips are Cortex-M0, and from ARM Cortex-M0 Technical Reference Manual (rev. r0p0) DDI0432C p.28:
   'The implemented device provides:

    • A low gate count processor that features:
         — The ARMv6-M Thumb® instruction set.
         —  technology
         [...]'I saw in gray options field is still -mthumb althrough I set Thumb2 in target instruction set.

Is there any change in options when you switch from thumb2 to thumb?Please verify in build console window, comparing the contents for both builds.
Regards,

Piotr

嗨彼得，
对不起，你是对的。没有拇指与拇指2的问题，我以前的配置一定存在其他一些问题。
松鸦



以下为原文




Hi Piotr,
I'm sorry, you're right. There was no thumb vs thumb2 issue, there must have been some other problem with my previous configuration.
jay

嗨彼得，
谢谢你的链接。
我仍然有问题为BLUENRG-1构建一个正在运行的图像
我为Assembler添加了选项
在C-Compiler的情况下，已经设置好了。
如果是Linker，我无法添加-mcpu。我会得到以下错误：
无法识别的仿真模式：cpu = cortex-m0 BLE_SensorDemo_BlueMSapp C / C ++问题
这是我的链接器选项：
-Wl，-cref，-u，-Xlinker， - defsym = ST_LINKER_OPTION = 1，-mcpu =皮质-M0
哪里不对？
我正在使用以下示例：
STMicroelectronics  BlueNRG-1_2 DK 2.6.0  Project  BLE_Examples  BLE_SensorDemo_BlueMSapp
TrueStudio 9.0.0
谢谢！



以下为原文




Hi Piotr,
Thanks for the link.
I still have problem to build a running image for BLUENRG-1
I added  option to Assembler
In case of C-Compiler,  was already set.
In case of Linker I can not add -mcpu. I will get following error:
unrecognised emulation mode: cpu=cortex-m0    BLE_SensorDemo_BlueMSapp             C/C++ Problem
Here my Linker Options:
-Wl,-cref,-u,-Xlinker,--defsym=ST_LINKER_OPTION=1,-mcpu=cortex-m0
What is wrong?
I'm using following example:
STMicroelectronicsBlueNRG-1_2 DK 2.6.0ProjectBLE_ExamplesBLE_SensorDemo_BlueMSapp
TrueStudio 9.0.0
Thanks!

嗨罗伯特，
这是我遇到的同样问题。我发现已经设置了
''C Linker'子菜单中的''所有选项：''字段。如果你再次使用它添加它
''C Linker'' - ＆gt;''Miscellaneous'' - ＆gt;
''其他选项：''字段，它会导致构建错误。
仔细检查''所有选项：''字段，查看附加屏幕截图，显示-mcpu = cortex-m0突出显示并已设置。如果它显示在此处，则不需要使用“其他”子菜单添加它。
松鸦



以下为原文




Hi Robert,
This is the same problem I was having. I found that  was already set in the
''All options:'' field in the ''C Linker'' submenu. If you add it a second time using the
''C Linker''->''Miscellaneous''->
''Other options:'' field, it leads to build errors.
Double check the ''All Options:'' field, see attached screenshot showing the -mcpu=cortex-m0 highlighted and already set. If it shows up here, you shouldn't need to add it using the Miscellaneous submenu.

jay