如何在Harmony框架中管理USART ISR？

我是一个新的和声框架，我想把我的一个项目从一个普通的MPLAB环境转移到ValueV1.10框架。为此，我想首先实现一个测试UART通信，比如Hello World：当接收到“A”字符时，一个LED亮起。我想通过RX上的中断来实现这种通信。我阅读了很多教程和指南，对驱动程序的系统接口、驱动程序的客户端接口、动态驱动程序或静态驱动程序的概念有点困惑。但是，如果我理解正确，我必须使用一个静态驱动程序（“只使用驱动程序的一个实例”）和一个字节传输模型。因此，当我在StulyBuff.c中生成代码时，DrviUsARTHOTASKSSEVELVER（）在DRVIUS UARTARXIMAN C中定义：并且DRVIUSAART00TASKSSEVELVER（）定义在DRVIUS UARTARSHIDECT.C中：我认为这个最后一个任务，DRVIUSART00TASKSSEVER（），是我必须插入代码的地方。读取字节并检查它最终打开LED。这里是我的疑问：如果我在DRVIUSART00TASKSSEVELVER（）中写下这一点，是正确的吗？因为在MPLAB®和声帮助-驱动库中，我读到（PG 6），一个客户端接口（例如，由DrviUsARTHARADEQUEL字节（AppDATA，MySART）函数进行RAPDIVE）被称为API和（PG 1013），API（除非另有规定）不应该从中断上下文调用。也就是说，它们不应该从ISR或在ISR上下文中执行的事件处理程序调用。“所以我的问题是：我的代码是正确的吗？如果不是，在ISR内部获得字节的正确方法是什么？



      以下为原文

    I'm new to HARMony framework and I want to transfer one of my projects from a common MPLAB environment to the Harmony v1.10 framework.
For this reason I want first implement a test UART communication like an Hello World: when receives the "A" character a LED turns on. And I want implement this communication via Interrupt on RX.
I read many tutorials and guides and I'm a bit confused on the concepts of a Driver's System Interface, Driver's Client Interface, dynamic driver or static driver. However, if I understood correctly, I have to use a static driver ('cause use only one instance of driver) with the interrupt on and a Byte Transfer Model.

So, when I generate the code I have in the system_interrupt.c
void __ISR(_UART1_TX_VECTOR, ipl0AUTO) _IntHandlerDrvUsartTransmitInstance0(void)
{
    DRV_USART_TasksTransmit(sysObj.drvUsart0);
}
void __ISR(_UART1_RX_VECTOR, ipl1AUTO) _IntHandlerDrvUsartReceiveInstance0(void)
{
    DRV_USART_TasksReceive(sysObj.drvUsart0);
}
void __ISR(_UART1_FAULT_VECTOR, ipl0AUTO) _IntHandlerDrvUsartErrorInstance0(void)
{
    DRV_USART_TasksError(sysObj.drvUsart0);
}

Now the DRV_USART_TasksReceive() is defined in the drv_usart_mapping.c:
void DRV_USART_TasksReceive ( SYS_MODULE_OBJ object )
{
    switch(object)
    {
        case DRV_USART_INDEX_0:
        {
            DRV_USART0_TasksReceive();
            break;
        }
         default:
         {
             break;
         }
     }
}


and the DRV_USART0_TasksReceive() is defined in the drv_usart_static.c:
void DRV_USART0_TasksReceive(void)
{
     /* This is the USART Driver Receive tasks routine. If the receive
     interrupt flag is set, the tasks routines are executed.
     */

     /* Reading the receive interrupt flag */
     if(SYS_INT_SourceStatusGet(INT_SOURCE_USART_1_RECEIVE))
     {

         /* Clear up the interrupt flag */
         SYS_INT_SourceStatusClear(INT_SOURCE_USART_1_RECEIVE);
     }
}

I think that this last task, DRV_USART0_TasksReceive(), is where I have to insert my code to read the byte and check it to turn on the LED eventually.
And here come my doubt: is correct if I write the following in the DRV_USART0_TasksReceive()?
void DRV_USART0_TasksReceive(void)
{
     /* This is the USART Driver Receive tasks routine. If the receive
     interrupt flag is set, the tasks routines are executed.
     */

     /* Reading the receive interrupt flag */
     if(SYS_INT_SourceStatusGet(INT_SOURCE_USART_1_RECEIVE))
     {
         if(!DRV_USART_ReceiverBufferIsEmpty())
         {
             __uint8_t byte = DRV_USART_ReadByte(appData.myusart);

             if(byte=='A')
             {
                 LED_ON();
             }
         }

         /* Clear up the interrupt flag */
         SYS_INT_SourceStatusClear(INT_SOURCE_USART_1_RECEIVE);
     }
}

Because in the MPLAB® Harmony Help - Driver Libraries I read (pg. 6) that a Client Interface (rappresented by the DRV_USART_ReadByte(appData.myusart) function, for example) is called an API and (pg. 1013) that an API

"unless otherwise specified, should not be called from an interrupt
context. That is, they should not be called from an ISR or from event
handlers that are executing within an ISR context."

So my question is: Is my code correct? If not, what is the correct metod to obtain a byte inside the ISR?