This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC1125 GPIO in eWOR

Other Parts Discussed in Thread: CC1125

GPIO3 on the CC1125 is experiencing a weird toggle when switching from SLEEP mode to RX mode when running Wake-On-Radio (WOR).  I am configure GPIO3_CFG as 0x14 for MARC state wake up.  The problem is that when in SLEEP mode, GPIO3 is hardwired to 1 and then when the radio switches to RX mode and the GPIO3 pin goes to 0 which fires an interrupt on my MCU.  I thought that setting the GPIO3_INV bit to 1 would fix this because the pin would be hardwired to 0 in SLEEP mode, but this inverts the entire signal so that the pin now goes to 1 when the radio enters RX mode, which still triggers an interrupt.  I need some way to use the GPIO3 pin for MARC state wake up in WOR mode, any suggestions would be appreciated. 

  • Hi,

    I suggest that you use WOR_EVENT0 or WOR_EVENT1 for your interrupt instead. It is described in detail when these interrupts happen and how to program them at page 61 in the user guide. 

    And as these signals are located at 0x37(event0) and 0x38(event1), GPIO3 won't be inverted with these settings.

    Hope this helps.

    -Fredrik

  • Fredrik,

    Thanks for the response.  I don't think your suggestion addresses my issue, though.  I don't want an interrupt to fire at event0 or event1.  I want an interrupt such as the MARC state, so that when the radio is in RX mode I have an interrupt that triggers when a packet is received (or if RX overflow happens, etc).  The problem is that even when configured at 0x14 (or 0x54, with the INV bit set to 1), the interrupt is firing when the radio enters RX mode. 

    I believe there should be a way to configure GPIO3 so that it is useful during the RX window and does not trigger during radio transitions.

    Cheers,

    Max

  • Sorry for the delay on this one. If you haven't found a solution to your question, could you please describe why you want an interrupt on MARC wake-up?