1˵

    òʾUARTyUARTzͨDMA(ж)ʵֵĻͨš
    ȣDMATxBuffer1UARTyݼĴɲ
DMAжϣݷUARTzUARTzڽжнݣݴ洢
RxBuffer2ɺرжϡ
    ͬʱDMATxBuffer2UARTzݼĴɲ
DMAжϣݷUARTyUARTyͨѯ־λʽݴ洢
RxBuffer1
    󣬷ֱȽաݣȽϽTransferStatus1
TransferStatus2


2ʹû

    KEIL MDK-ARM V5.34.0.0
    Ӳ 
        N32G05xϵУ
            N32G05xRBQ7_STB V1.0
        N32G05xϵУ
            N32G05xRBL7_STB V1.0


3ʹ˵
	
    ϵͳʱ£
    - ϵͳʱ = 64MHz
    
    UART£
    -  = 115200 baud
    - ֳ = 8λ
    - 1ֹͣλ
    - Уƽ
    - ͷʹ
    
    UART£    
    - UART1_Tx.PA2   <------->   UART2_Rx.PA7
    - UART1_Rx.PA3   <------->   UART2_Tx.PA6

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


4ע

    ȽNS-LINKMCU_TXMCU_RXñϿ

1. Function description

    This test example demonstrates basic communication between UARTy and UARTz via DMA. 

   First, the DMA transfers the TxBuffer1 data to the UARTy transmit data register, and then the 
   data is sent to the UARTz. UARTz uses the interrupt to receive data and store it in RxBuffer2. 

   At the same time, the DMA transfers the TxBuffer2 data to the UARTz transmit data register,
   and then the data is sent to the UARTy. UARTy receives data by querying the check flag and 
   stores it in RxBuffer1. 

2. Use environment

	Software development environment: KEIL MDK-ARM V5.34.0.0
    Hardware development environment:
         N32G05x series:
            Developed based on the evaluation board N32G05xRBQ7_STB V1.0
         N32G05x series:
            Developed based on the evaluation board N32G05xRBL7_STB V1.0

3. Instructions for use

    The system clock configuration is as follows:
    -System clock = 64MHz
    
    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.PA2   <------->   UART2_Rx.PA7
    - UART1_Rx.PA3   <------->   UART2_Tx.PA6

    
    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