This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Help me to use ARM_DRIVER_UART API in Keil ARM MDK5

Hi,
I am new bie in STM32F4 microcontroller. I am studying STM32 with STM32F4 Discovery Board. I want to program communication via 2 UART on chip. I have read Help documents of Keil IDE but I don't understand and how to use API functions of ARM_DRIVER_UART and RTX Keil.
Anyone has a template example or help me some good idea?
Thank you in advance,

PS. sorry for my bad English.

Parents
  • Hi,

    Reasons for hitting FaultHandler can be different. In MDK5 UART depends on RTOS. Check for settings in RTX_Conf_CM.c file. You can edit it manually or via GUI. My current working settings are as follows:

    Thread Configuration
     - Number of concurent running threads 6
     - Default thread stack size 200
     - Main thread stack 200
     - Number of of threads with user.... 0
     - Total stack size [bytes]...... 0
     - Check for stack overflow   ... checked
     - Processor mode.... Privileged mode
    
    RTX Kernel timer Tick configuration
     - Use cortex-m systick.... checked
     - clock (depends on device)
     - timer tick value [us] 1000
    

    Quite common reason can be too small stack size for threads. But this is just one small point for a possible fault. There can be other reasons as well.

    Hope it helps.

Reply
  • Hi,

    Reasons for hitting FaultHandler can be different. In MDK5 UART depends on RTOS. Check for settings in RTX_Conf_CM.c file. You can edit it manually or via GUI. My current working settings are as follows:

    Thread Configuration
     - Number of concurent running threads 6
     - Default thread stack size 200
     - Main thread stack 200
     - Number of of threads with user.... 0
     - Total stack size [bytes]...... 0
     - Check for stack overflow   ... checked
     - Processor mode.... Privileged mode
    
    RTX Kernel timer Tick configuration
     - Use cortex-m systick.... checked
     - clock (depends on device)
     - timer tick value [us] 1000
    

    Quite common reason can be too small stack size for threads. But this is just one small point for a possible fault. There can be other reasons as well.

    Hope it helps.

Children