移植stm32f405vg时遇到程序进入hardfault的问题

发布于 2018-03-07 11:38:56 浏览：1701 订阅该版

* 本帖最后由 moebius.ever 于 2018-3-7 12:37 编辑 *

采用[https://github.com/RT-Thread/rt- ... sp/stm32f429-apollo](https://github.com/RT-Thread/rt-thread/tree/master/bsp/stm32f429-apollo)复制了一份文件出来，并采用stm32f4xx最新的hal库，使用sw4stm32最新版本作为开发环境，现象：程序不能正常获得USART1的地址，serial1的地址为NULL，程序执行到如下位置rt_hw_serial_register```int stm32_hw_usart_init(void)
{
    struct stm32_uart *uart;
    struct serial_configure config = RT_SERIAL_CONFIG_DEFAULT;

#ifdef RT_USING_UART1
    uart = &uart1;
    uart->UartHandle.Instance = USART1;

serial1.ops    = &stm32_uart_ops;
    serial1.config = config;

/* register UART1 device */
    rt_hw_serial_register(&serial1,
                          "uart1",
                          RT_DEVICE_FLAG_RDWR | RT_DEVICE_FLAG_INT_RX,
                          uart);
#endif /* RT_USING_UART1 */

#ifdef RT_USING_UART2
    uart = &uart2;
    uart->UartHandle.Instance = USART2;

serial2.ops    = &stm32_uart_ops;
    serial2.config = config;

/* register UART1 device */
    rt_hw_serial_register(&serial2,
                          "uart2",
                          RT_DEVICE_FLAG_RDWR | RT_DEVICE_FLAG_INT_RX,
                          uart);
#endif /* RT_USING_UART2 */

#ifdef RT_USING_UART3
    uart = &uart3;
    uart->UartHandle.Instance = USART3;

serial3.ops    = &stm32_uart_ops;
    serial3.config = config;

/* register UART3 device */
    rt_hw_serial_register(&serial3,
                          "uart3",
                          RT_DEVICE_FLAG_RDWR | RT_DEVICE_FLAG_INT_RX,
                          uart);
#endif /* RT_USING_UART3 */

#ifdef RT_USING_UART4
    uart = &uart4;
    uart->UartHandle.Instance = USART4;

serial4.ops    = &stm32_uart_ops;
    serial4.config = config;

/* register UART4 device */
    rt_hw_serial_register(&serial4,
                          "uart4",
                          RT_DEVICE_FLAG_RDWR | RT_DEVICE_FLAG_INT_RX,
                          uart);
#endif /* RT_USING_UART4 */

#ifdef RT_USING_UART5
    uart = &uart5;
    uart->UartHandle.Instance = USART5;

serial5.ops    = &stm32_uart_ops;
    serial5.config = config;

/* register UART5 device */
    rt_hw_serial_register(&serial5,
                          "uart5",
                          RT_DEVICE_FLAG_RDWR | RT_DEVICE_FLAG_INT_RX,
                          uart);
#endif /* RT_USING_UART5 */
    return 0;
}```
进入hardfault
折腾了3天，发现使用scons编译后，参照《[AN0006 RT-Thread QEMU BSP应用指南.pdf](https://pan.baidu.com/s/1pM4kr6F?errno=0&errmsg=Auth%20Login%20Sucess&&bduss=&ssnerror=0&traceid=#list/path=%2F%E5%85%AC%E5%BC%80%E5%88%86%E4%BA%AB%E7%9B%AE%E5%BD%95%2FRT-Thread%20%E7%9B%B8%E5%85%B3%E6%96%87%E6%A1%A3%2FRT-Thread%E5%BA%94%E7%94%A8%E7%AC%94%E8%AE%B0AN%2FAN0006%20QEMU&parentPath=%2F%E5%85%AC%E5%BC%80%E5%88%86%E4%BA%AB%E7%9B%AE%E5%BD%95%2FRT-Thread%20%E7%9B%B8%E5%85%B3%E6%96%87%E6%A1%A3)》能正常运行和调试，使用eclipse能编译，但是不能运行和调试。
eclipse的编译参数是根据rtconfig.py中配置的。
打印详细的编译信息，对比scons的和eclipse的，发现scons的-fPIC选项实际编译的时候没有用，最后把-fPIC这个选项去掉eclipse可以运行和调试了。不知道rtconfig.py中的fPIC选项是起什么作用的。