Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nordic - Gpio IRQ handler conflict in the mbed lib and nordic-sdk #1045

Closed
0xc0170 opened this issue Apr 16, 2015 · 4 comments
Closed

Nordic - Gpio IRQ handler conflict in the mbed lib and nordic-sdk #1045

0xc0170 opened this issue Apr 16, 2015 · 4 comments

Comments

@0xc0170
Copy link
Contributor

0xc0170 commented Apr 16, 2015

It looks like there was an update in nordic-sdk, which conflicts with the mbed library for nrf51.

Here are some details:
Ble Thermometer - update all libraries, so BLE_API is 341, mbed lib is 97, nrf lib is 111 (which actually cases this as the gpio app sources were added there). Selected platform - nordic nrf51822 - compiles (haven't checked which gpio irq handler was chosen by linker). Then I remove mbed lib, add mbed-src revs 514 - GPiO IRQ multiple definitions error.

@rgrover

@rgrover
Copy link
Contributor

rgrover commented Apr 22, 2015

we need GPIOTE_IRQHandler to be able to process interrupts arising from GPIO transitions. This handler can't be removed from mbed-src.

GPIOTE is Nordic's meta concept which encompasses GPIO-toogles together with 'tasks and events'. Tasks and events allow applications to capture very short-lived toggles on GPIOs. We don't need this feature.
The solution is to drop the app_gpiote support from nRF51822. mbed-src doesn't need to change.

Updates to the nRF51822 library are currently held up on the next release of the mbed-sdk. As a workaround, it should be safe to drop the files app_gpiote.[ch] from nRF51822.

@ciarmcom
Copy link
Member

ciarmcom commented Aug 1, 2016

ARM Internal Ref: IOTMORF-275

@sg-
Copy link
Contributor

sg- commented Jan 10, 2017

@0xc0170 is this still valid?

@0xc0170
Copy link
Contributor Author

0xc0170 commented Jan 12, 2017

I havent seen this issue since then, closing

@0xc0170 0xc0170 closed this as completed Jan 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants