When using the getIRQ and clearIRQ functions inside the IRQ interrupt handler doesn't work as expected, when reading the status register it's read as 0x00 and not the correct value (0x1E which is the MAX_RT_IRQ flag for example).
There must be a way to improve both of those functions.

The clear_irq_flag function is writing over read-only bits on the STATUS register, we need first to read the STATUS register, then OR it with the mask (1 << flag) and write the result back to the STATUS register.

The current nRF24_get_irq_flag() implementation doesn't work with 2 or 3 asserted IRQ flags on the STATUS register, @Boland1776 suggested changing the implementation of the nRF24_get_irq_flag() from:

nrf_irq nRF24_get_irq_flag(void)
{
    nrf_irq irq = NRF_NONE_IRQ;

    // Get the STATUS register
    uint8_t sts = nRF24_cmd_nop();

    // We only care if bits 4, 5 or 6 are set, so we mask the STATUS with 0x0111_0000
    switch (sts & NRF_ALL_IRQ_MASK) {
    case NRF_STATUS_RX_DR_MASK:
        irq = NRF_RX_DR_IRQ;
        break;
    case NRF_STATUS_TX_DS_MASK:
        irq = NRF_TX_DS_IRQ;
        break;
    case NRF_STATUS_MAX_RT_MASK:
        irq = NRF_MAX_RT_IRQ;
        break;
    default:
        irq = NRF_ALL_IRQ_MASK;
        break;
    }

    return irq;
}

to

uint8_t nRF24_get_irq_flag(void)
{
    return NRF_ALL_IRQ_MASK & nRF24_cmd_nop();
}

So the user will get all the IRQ flags and check which one is asserted like so:

int main(void)
{
   ....
   uint8_t irqs = nRF24_get_irq_flag();
   process_IRQs(irqs);
   ....
}

void process_IRQs(uint8_t irqs) {
    if (0u == irqs) {
        return;
    }

    if (irqs & NRF_TX_DS_IRQ) {
        // do something
        nRF24_clear_irq_flag(NRF_TX_DS_IRQ);
    }
    if (irqs & NRF_MAX_RT_IRQ) {
        // do something else
       nRF24_clear_irq_flag(NRF_MAX_RT_IRQ);
    }
    if (irqs & NRF_RX_DR_IRQ) {
        // do something else
       nRF24_clear_irq_flag(NRF_RX_DR_IRQ);
    }
    .....
}

Current data transfer implementation triggers an RX OVERRUN interrupt (when enabled) due the data in the RX FIFO isn't being read and it does overflow when using the nRF24_write_long_register function.

I tried running 00_Basic_Tx example on CY8C4245AXI-48344. The function nRF24_get_irq_flag(), always returns NRF_MAX_RT_IRQ.
Status from nRF24_get_status() is 0x0F or 0x0E.

Any debugging steps or error description regarding this will be very helpful.

My setup:
-1 board for TX
-1 board for RX
-Channel 63
-TX and RX address both 0x0123456789
-Arduino for debugging purposes.

According to the arduino_scanner output, the PSOC_TX is transmitting strongly at channel 63.
However, the PSOC_RX is not receiving anything.

Any tips?

Update:
I just got it to run, apparently, I need to enable the auto-ack for it to work.

The component based on SCB blocks send "garbage" data when calling the nRF_Start funtion, it may be caused by a TX-FIFO problem because the bytes to send arrive late and the /SS line goes high between data transfers.
Below is a capture with data beign sent with the component based on SCB.

Below is the same data beign sent using the component based on UDB.

When fixed they must be the same.

If someone uses this component and had not changed "nRF24 Power" to "Power Up" (in the configurator) it must be done in main.c. Users should be careful NOT to call;
nRF24_set_bit(NRF_REG_CONFIG, NRF_CONFIG_PWR_UP), but use
nRF24_set_bit(NRF_REG_CONFIG, NRF_CONFIG_BIT_PWR_UP) instead.
If the user takes the latter, they must also include a delay of approx 5ms to allow the radio to stabilize.

I have three suggestions;

1. Have the default setting in the configurator be "Power On". One could assume if they are including this device they will want it powered on.
2. Add a function in FUNCS.c, such as...
   void nRF24_set_power_up_mode(void) {
   nRF24_set_bit(NRF_REG_CONFIG, NRF_CONFIG_BIT_PWR_UP);
   CyDelay(5u);
   }
3. nRF24_wakeup() is very close to being a "power up" function but needs a delay.

There are a few other function calls in FUNC.c that need to use the NRF_CONFIG_BIT_PWR_UP (instead of NRF_CONFIG_PWR_UP).

Other than those nits, great job!!