Welcome in the forum!
I would suggest you to create a "MyCase" to have Cypressed informed. At top of this page Support & Community -> Technical Support -> Create a MyCase
Best is to attach a project that reproduces the error.
I cannot find an interrupt source called 'TRIGGER'. Do you maybe mean 'RX FIFO Level'? That one should not be enabled by default, so it should never trigger an interrupt - did you maybe enable it manually?
What you can do: register a custom interrupt handler, and clear the interrupt source there. It gets called from the internal ISR.
Maybe I should have asked: are you using the SCB-based UART opr the UDB-based one?
For the SCB-based, there is UART_PutString that takes an uint8 array, and SpiUartPutArray that can take either uint8 or uint16, depending on the UART configuration. Yes, the naming is weird since this is a multi-functional component.
This is a UDB UART.
Page 1790 of the TRM for PSoC4 BLE, in section 25.1.78 SCB0_INTR_RX_MASK ... describes TRIGGER.
The register you are looking at is only for SCB_based UARTs, which you don't use. How do you determine which interrupts are currently requested for that particular ISR?
(Btw: from the description of TRIGGER in the SCB0_INTR_RX register it the RX_level interrupt)
The UDB-based UARTs don't use any of the standard registers. Their component implementation uses an internal interrupt component (at least I think so), which gets triggered by an UDB output.
Are you using another SCB-Based component that might request an interrupt you are looking at?
Sorry, no, this is an SCB Uart. Not UDB.
I arrived at that register name by drilling into the generated code.
If its a SCB UART - check whether the "RX level" interrupt is enabled in the UART config. When testing, I see that setting this flag changes the UART_DEB_UART_INTR_RX_MASK values from 0x04 to 0x05 - so maybe thats your problem?
(I cannot see any other place where this interrupt source is enabled)