This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GPIO port 1 unable to read with MCUBoot added

I've recently upgraded my SDK to 1.6.0 and I am now unable to read the state of P1.00 but I am able to read the state of P0.28.

I've stripped the project down to just a gpio setup and pin read loop.

If I remove the MCUBOOT define I can read the pin on GPIO 1 but when I add it in I can't.

I am now testing with a nRF5340-DK with a basic button example.

Any ideas will be gratefully received.

Thank you,

Neil

Parents
  • sdk1.4.99peripheral_hr.zipsdk1_7_0peripheral_hr.zip

    I've been doing some more testing,  I've used a basic bt example to test,  it shows that in sdk 1.4.99 i'm able to read the state of gpio1.0 and gpio1.1 but in 1.7.0 I am not.  In the project settings if I remove CONFIG_BT=y and hence remove the net core it starts working again.

    Thank you,

    Neil

  • Hey,

    Neil_CPD said:
    In the project settings if I remove CONFIG_BT=y and hence remove the net core it starts working again.

    This is most likely because the net core uses P1.00 and P1.01 for UART0. I'm not sure why this wouldn't be the case for earlier versions of NCS though. It seems a bit strange. Maybe the net core isn't enabled by default. That could be worth checking out.

Reply
  • Hey,

    Neil_CPD said:
    In the project settings if I remove CONFIG_BT=y and hence remove the net core it starts working again.

    This is most likely because the net core uses P1.00 and P1.01 for UART0. I'm not sure why this wouldn't be the case for earlier versions of NCS though. It seems a bit strange. Maybe the net core isn't enabled by default. That could be worth checking out.

Children
Related