CC1310: Setting up interrupt at DIO1

Lasse Lundholm

Part Number: CC1310
Other Parts Discussed in Thread: , EVM430-FR6047

Hi CC1310 experts

I have a project where I need to receive an interrupt (Comm_IRQ) from an EVM430FR6047 on my CC1310. In the beginning the interrupt line was connected to DIO14, aka BTN2 and it worked perfectly. One of my fellow students have made a PCB with the IRQ line connected to DIO1 and I'm now struggling to get the same respons.

The GPIO is set up like this. There is an pull-up resistor of 10 k.

I have added DIO1 to board.h

In the CC1310_LAUNCHXL.c I have added

And:

And the gpio_interrupt_handler just post a semaphore. The idea is that a sem_timedwait is called when I wait for a package from the EVM430. The EVM430 makes an interrupt on the CommIRQ just before the message is ready to be send to the CC1310. The interrupt calls sem_post and immediately after I2C_Transfer.

Generally the program compiles and runs but I never hit the breakpoint. Zooming way out and measuring at the Comm_IRQ line gives this

With interrupts occuring with approximatly 1 sec. intervals - I suspect it to be an error message from the EVM430. No matter the reason the interrupts are not registered on the CC1310 so I suspect my configuration of DIO1 is wrong. I just can't figure out why since its just an GPIO pin the same way Pin 14 is!!

Kind regards

Lasse

over 5 years ago

0 Ryan Brown1 over 5 years ago

TI__Guru**** 218837 points

Hi Lasse,

Your setup looks fine (if you look in GPIO.h you will see that GPIO_CFG_INPUT and GPIO_CFG_IN_NOPULL are the same therefore you only need to set one or the other) and the default LAUNCHXL-CC1310 hardware and software configurations do not use DIO1 which is interrupt-capable like the other GPIO pins. I suggest you start with the gpiointerrupt example and only change Board_GPIO_BUTTON0 code for Board_DIO1 to determine whether the issue could lie within other parts of your application. I also recommend that you manually toggle the DIO1 pin on your custom board to ensure that there is no connection issue with the EVM430-FR6047. Double-check the CC1310 datasheet to ensure that you are handling the correct pin.

Regards,
Ryan

0 TER over 5 years ago in reply to Ryan Brown1

TI__Guru**** 317180 points

Please also take a look at this post: https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz/f/156/t/711372?CC1312R-Unable-to-modify-value-of-GPIOs-in-CC1312R which cover a typical usage issue with the GPIO driver.

0 Lasse Lundholm over 5 years ago in reply to Ryan Brown1

Intellectual 280 points

Thanks. I will give it a go in the morning or friday maybe. I actually began my project with the i2ctmp project and used the gpiointerrupt example when I should implement the interrupt. I will let you know how it went either tomorrow or friday.

Regards Lasse

0 Lasse Lundholm over 5 years ago in reply to Ryan Brown1

Intellectual 280 points

Thank you for your help.

My issue is solved with the link you posted in an answer. The CC1310_LAUNCHXL.h file table needed to have the pin added to the table.

I just had to come up with a another name than CC1310_LAUNCHCL_DIO1 and then assign the BOARD_DIO1 to that instead

#define BOARD_DIO1 CC1310_LAUNCHCL_DIO1_IRQ

It now breaks in my interrupt_handler and post the semaphore

Sub-1 GHz

Sub-1 GHz forum

CC1310: Setting up interrupt at DIO1