1˵

    òʾUARTyUARTzͨжʵֵĻͨš
    UARTyTxBuffer1UARTzUARTzݴRxBuffer2ͬʱUARTzTxBuffer2UARTyUARTyݴRxBuffer1
    󣬷ֱȽ뷢ݣȽϽTransferStatus1TransferStatus2
    UARTyUARTzUART1UART2


2ʹû

    KEIL MDK-ARM Professional Version 5.34

    ӲСϵͳN32G003F5S7-STB_V1.0


3ʹ˵
	
    ϵͳʱ£
    - ϵͳʱ = 48MHz
    
    UART£
    -  = 115200 baud
    - ֳ = 8λ
    - 1ֹͣλ
    - Уƽ
    - ͷʹ
    
    UART£    
    - UART1_Tx.PA14    <------->    UART2_Rx.PA1
    - UART1_Rx.PA12   <------->   UART2_Tx.PA2

    
    Բ
    - DemoKEIL±MCU
    - λУβ鿴TransferStatus1TransferStatus2У
      PASSEDΪͨFAILEDΪ쳣


4ע

    ȽNS-LINKMCU_TXMCU_RXñϿ

1. Function description

    This test case demonstrates the basic communication between UARTy and UARTz through interrupts.
    UARTy sends TxBuffer1 data to UARTz, and UARTz receives data to RxBuffer2. At the same time, UARTz sends TxBuffer2 data to UARTy, and UARTy receives data to RxBuffer1.
    Subsequently, the two groups of received data and sent data are compared respectively, and the comparison results are stored in the TransferStatus1 variable and the TransferStatus2 variable.
    UARTy and UARTz can be UART1 and UART2.


2. Use environment

    Software development environment: KEIL MDK-ARM Professional Version 5.34

    Hardware environment: minimum system board N32G003F5S7-STB_V1.0


3. Instructions for use

    The system clock configuration is as follows:
    -System clock = 48MHz
    
    The UART configuration is as follows:
    -Baud rate = 115200 baud
    -Word length = 8 data bits
    -1 stop bit
    -Verification control disabled
    -Receiver and transmitter enable
    
    The UART pin connections are as follows:
    - UART1_Tx.PA14    <------->    UART2_Rx.PA1
    - UART1_Rx.PA12   <------->   UART2_Tx.PA2

    
    Test steps and phenomena:
    -After the Demo is compiled in the KEIL environment, download it to the MCU
    -Reset operation, check the variables TransferStatus1 and TransferStatus2 in turn, among them,
      PASSED means the test passed, FAILED means the test is abnormal


4. Matters needing attention

    the MCU_TX and MCU_RX jumper cap of the development board NS-LINK needs to be disconnected first