STM32

为什么__libc_init_array会导致异常？

2019-07-14 17:30发布

站内问答 / STM32/STM8
8220 6 1009
经过很长一段时间试图调试为什么我的STM32F446RE微控制器的简单闪烁代码无法正常工作后，我在启动组件文件中发现了一条我正在链接到它的行，导致异常将微控制器推入无限循环异常处理程序。
这是主要代码：
  1. <font size="4">.syntax unified
  2.   .cpu cortex-m4
  3.   .fpu softvfp
  4.   .thumb

  6. .global  g_pfnVectors
  7. .global  Default_Handler

  9. /* start address for the initialization values of the .data section.
  10. defined in linker script */
  11. .word  _sidata
  12. /* start address for the .data section. defined in linker script */  
  13. .word  _sdata
  14. /* end address for the .data section. defined in linker script */
  15. .word  _edata
  16. /* start address for the .bss section. defined in linker script */
  17. .word  _sbss
  18. /* end address for the .bss section. defined in linker script */
  19. .word  _ebss
  20. /* stack used for SystemInit_ExtMemCtl; always internal RAM used */

  22. /**
  23. * [url=home.php?mod=space&uid=2666770]@Brief[/url]  This is the code that gets called when the processor first
  24. *          starts execution following a reset event. Only the absolutely
  25. *          necessary set is performed, after which the application
  26. *          supplied main() routine is called.
  27. * @param  None
  28. * @retval : None
  29. */

  31.     .section  .text.Reset_Handler
  32.   .weak  Reset_Handler
  33.   .type  Reset_Handler, %function
  34. Reset_Handler:  
  35.   ldr   sp, =_estack      /* set stack pointer */

  37. /* Copy the data segment initializers from flash to SRAM */  
  38.   movs  r1, #0
  39.   b  LoopCopyDataInit

  41. CopyDataInit:
  42.   ldr  r3, =_sidata
  43.   ldr  r3, [r3, r1]
  44.   str  r3, [r0, r1]
  45.   adds  r1, r1, #4

  47. LoopCopyDataInit:
  48.   ldr  r0, =_sdata
  49.   ldr  r3, =_edata
  50.   adds  r2, r0, r1
  51.   cmp  r2, r3
  52.   bcc  CopyDataInit
  53.   ldr  r2, =_sbss
  54.   b  LoopFillZerobss
  55. /* Zero fill the bss segment. */  
  56. FillZerobss:
  57.   movs  r3, #0
  58.   str  r3, [r2], #4

  60. LoopFillZerobss:
  61.   ldr  r3, = _ebss
  62.   cmp  r2, r3
  63.   bcc  FillZerobss

  65. /* Call the clock system intitialization function.*/
  66.   bl  SystemInit   
  67. /* Call static constructors */
  68.       bl __libc_init_array
  69. /* Call the application's entry point.*/
  70.   bl  main
  71.   bx  lr   
  72. .size  Reset_Handler, .-Reset_Handler

  74. /**
  75. * @brief  This is the code that gets called when the processor receives an
  76. *         unexpected interrupt.  This simply enters an infinite loop, preserving
  77. *         the system state for examination by a debugger.
  78. * @param  None     
  79. * @retval None      
  80. */
  81.     .section  .text.Default_Handler,"ax",%progbits
  82. Default_Handler:
  83. Infinite_Loop:
  84.   b  Infinite_Loop
  85.   .size  Default_Handler, .-Default_Handler
  86. </font>
复制代码导致异常的行是：/* Call static constructors */      bl __libc_init_array这导致微控制器跳转到最终导致异常的函数，从而跳转到Default_Handler无限循环。您可能会注意到，此次通话后直接__libc_init_array进入我的入口点main。如果我bl __libc_init_array完全评论我的程序实际上工作正常; 它跳进main并继续运行代码以使我的LED闪烁。
我做了一ARM-none-eabi-objdump -D blink.elf > blink.list' to see what __libc_init_array件事。这是功能：
  1. <font size="4">08000608 <__libc_init_array>:
  2. 8000608:   e92d4070    push    {r4, r5, r6, lr}
  3. 800060c:   e59f6064    ldr r6, [pc, #100]  ; 8000678 <__libc_init_array+0x70>
  4. 8000610:   e59f5064    ldr r5, [pc, #100]  ; 800067c <__libc_init_array+0x74>
  5. 8000614:   e0656006    rsb r6, r5, r6
  6. 8000618:   e1b06146    asrs    r6, r6, #2
  7. 800061c:   13a04000    movne   r4, #0
  8. 8000620:   0a000005    beq 800063c <__libc_init_array+0x34>
  9. 8000624:   e2844001    add r4, r4, #1
  10. 8000628:   e4953004    ldr r3, [r5], #4
  11. 800062c:   e1a0e00f    mov lr, pc
  12. 8000630:   e12fff13    bx  r3
  13. 8000634:   e1560004    cmp r6, r4
  14. 8000638:   1afffff9    bne 8000624 <__libc_init_array+0x1c>
  15. 800063c:   e59f603c    ldr r6, [pc, #60]   ; 8000680 <__libc_init_array+0x78>
  16. 8000640:   e59f503c    ldr r5, [pc, #60]   ; 8000684 <__libc_init_array+0x7c>
  17. 8000644:   e0656006    rsb r6, r5, r6
  18. 8000648:   eb000104    bl  8000a60 <_init>
  19. 800064c:   e1b06146    asrs    r6, r6, #2
  20. 8000650:   13a04000    movne   r4, #0
  21. 8000654:   0a000005    beq 8000670 <__libc_init_array+0x68>
  22. 8000658:   e2844001    add r4, r4, #1
  23. 800065c:   e4953004    ldr r3, [r5], #4
  24. 8000660:   e1a0e00f    mov lr, pc
  25. 8000664:   e12fff13    bx  r3
  26. 8000668:   e1560004    cmp r6, r4
  27. 800066c:   1afffff9    bne 8000658 <__libc_init_array+0x50>
  28. 8000670:   e8bd4070    pop {r4, r5, r6, lr}
  29. 8000674:   e12fff1e    bx  lr
  30. 8000678:   08000aac    stmdaeq r0, {r2, r3, r5, r7, r9, fp}
  31. 800067c:   08000aac    stmdaeq r0, {r2, r3, r5, r7, r9, fp}
  32. 8000680:   08000ab4    stmdaeq r0, {r2, r4, r5, r7, r9, fp}
  33. 8000684:   08000aac    stmdaeq r0, {r2, r3, r5, r7, r9, fp}</font>
复制代码但我并不流利的装配，所以我真的不知道它想要完成什么或产生什么。除了我的main.c之外，我唯一包含的其他源文件和启动程序集是system_stm32f4xx.c由cubeMX生成的（SystemInit调用的地方），但它没有调用函数__libc_init_array。那么这个__libc_init_array功能来自哪里？为什么它会导致异常（将我的micro踢到异常处理程序）？以及如何防止这种情况（除了明显编写我自己的启动程序集而不包括无关的自动生成的文件）？这是我用来构建代码的makefile：
  1. #-{ Project Relative Paths }----------------------------------------------------

  3. # executables, intermediate objects, and libraries.
  4. BIN= ./binary
  5. # program source files
  6. SRC= ./source
  7. # on-architecture specific header files
  8. BHD= ./header
  9. # architecture/device specific files
  10. ARC= ./architecture
  11. # pre-compiled libraries that the project will link against
  12. LIB= ./library

  14. #-{ Compiler Definitions }------------------------------------------------------

  16. #include directories
  17. INC= $(ARC)/CMSIS/inc
  18.      $(ARC)/HAL/inc
  19.      $(ARC)/inc
  20.      $(header)

  22. INC_PARAMS= $(INC:%=-I%)

  24. # Compiler
  25. CC = arm-none-eabi-gcc

  27. # Device specific flags [1]
  28. # -mcpu=cortex-m4 sets target CPU
  29. # -mthumb tells gcc to compile to thumb2 instructions
  30. DFLAGS = -mcpu=cortex-m4 -mthumb

  32. # Compiler flags
  33. CFLAGS = $(DFLAGS) -g -c -Wall -Wextra

  35. #-{ Linker Definitions }------------------------------------------------------

  37. # Linker
  38. LD = arm-none-eabi-gcc #same as compilter but uses different flags

  40. # Path to linker script #linking script
  41. LSCRIPT = $(ARC)/STM32F446RETx_FLASH.ld

  43. # Linker flags
  44. LFLAGS = -T $(LSCRIPT) --specs=nosys.specs

  46. # Object copy (for converting formats)
  47. OBJCOPY = arm-none-eabi-objcopy
  48. OFLAGS = -O ihex
  49. OFLAGSbin = -O binary

  51. #-{ Programming/Debugging Definitions }-----------------------------------------

  53. # Debugger
  54. DBG = arm-none-eabi-gdb

  56. # OpenOCD
  57. OCD = openocd

  59. # Debug/programming interface configuration file
  60. INTRF = /usr/local/share/openocd/scripts/interface/stlink-v2-1.cfg
  61. # Target device configurations file
  62. OCDTARGET = /usr/local/share/openocd/scripts/target/stm32f4x.cfg
  63. OCDBOARD = /usr/local/share/openocd/scripts/board/st_nucleo_f4.cfg

  65. #-{ Build Rules }---------------------------------------------------------------

  67. # Final binaries
  68. HEX = $(BIN)/blink.hex
  69. ELF =  $(BIN)/blink.elf
  70. binfile = $(BIN)/blink.bin

  72. # All intermediate object files
  73. OBJ = $(BIN)/blink.o $(BIN)/boot.o $(BIN)/init.o

  75. #-- These rules for the final binaries will usually not require modification

  77. # Convert the ELF into intel hex format
  78. $(HEX): $(ELF)
  79.     $(OBJCOPY) $(OFLAGS) $(ELF) $(HEX)

  81. #convert the ELF into binary format
  82. $(binfile): $(ELF)
  83.     $(OBJCOPY) $(OFLAGSbin) $(ELF) $(binfile)

  85. # Link all intermediate objects into a single executable
  86. $(ELF): $(OBJ)
  87.     $(LD) $(LFLAGS) $(OBJ) -o $(ELF)

  89. #-- These rules will vary depending on the program being built

  91. # Compile the main file
  92. $(BIN)/blink.o: $(SRC)/blink.c $(ARC)/CMSIS/inc/stm32f4xx.h
  93.     $(CC) $(CFLAGS) $(INC_PARAMS) $(SRC)/blink.c -o $(BIN)/blink.o

  95. # Compile the reset handler
  96. $(BIN)/boot.o: $(ARC)/CMSIS/src/startup_stm32f446xx.S
  97.     $(CC) $(CFLAGS) $(INC_PARAMS) $(ARC)/CMSIS/src/startup_stm32f446xx.S -o $(BIN)/boot.o

  99. #compile the post-reset, pre-main, system handler
  100. $(BIN)/init.o: $(ARC)/CMSIS/src/system_stm32f4xx.c
  101.     $(CC) $(CFLAGS) $(INC_PARAMS) $(ARC)/CMSIS/src/system_stm32f4xx.c -o $(BIN)/init.o


  104. #-{ Utility Rules }-------------------------------------------------------------

  106. # OpenOCD command to program a board
  107. program: $(HEX)
  108.     [url=home.php?mod=space&uid=1361969]@sudo[/url] -E $(OCD) -f $(INTRF) -f $(OCDTARGET) -c "program $(ELF) verify reset exit"

  110. # OpenOCD command to load a program and launch GDB
  111. debug: $(ELF)
  112.     @(sudo -E $(OCD) -f $(INTRF) -f $(OCDTARGET) &);
  113.     $(DBG) $(ELF) -ex "target remote localhost:3333; load";
  114.     sudo kill $(OCD)

  116. # Build the entire program
  117. all: $(HEX) $(binfile)

  119. # Delete all of the generated files
  120. clean:
  121.     rm $(OBJ) $(HEX) $(ELF) $(binfile)

  123. # Delete all intermediate object files
  124. tidy:
  125.     rm $(OBJ)
复制代码
除了blink.c我使用system_stm32f4xx.c哪个有system_init函数。
友情提示: 此问题已得到解决，问题已经关闭,关闭后问题禁止继续编辑，回答。
该问题目前已经被作者或者管理员关闭, 无法添加新回复
6条回答
riverdj
1楼-- · 2019-07-14 18:42
这是初始化功能的一部分，是在主程序启动之前初始化和C / C ++对象的。崩溃的可能是您的代码或库中的某些内容或编译方式导致问题。
阿兵888824
2楼-- · 2019-07-14 21:33
如果删除其余的源代码，执行是否会使其超过此阶段？你编写了多少示例代码？
比吥匕卟
3楼-- · 2019-07-14 22:34
很可能问题不在于您的源代码本身，而是在生成期间的链接步骤中。您可能正在使用为32位经典ARM（非CortexM）编译的库，它不使用拇指指令集。您用于编译的命令行和/或工具是什么？
dsgdadsad
4楼-- · 2019-07-15 03:44
尝试将-mthumb和-mcpu = cortex-m4添加到您的LFLAGS变量中。
冰箱洗衣机
5楼-- · 2019-07-15 07:28
 精彩回答 2  元偷偷看……
随行者011011
6楼-- · 2019-07-15 09:06
感谢各位的解答！

一周热门 更多>