GPIO port 1 unable to read with MCUBoot added

[Neil_CPD]

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

[sshenoy105]

v1.6.1\zephyr\boards\arm\nrf5340dk_nrf5340\nrf5340dk_nrf5340_cpunet.dts -> uart0 uses pin 0x21 (P1.01).. i changed the dts file as follows since I don't care about netcore using uart

&uart0 {
status = "disabled";
current-speed = <115200>;
tx-pin = <33>;
rx-pin = <32>;
rts-pin = <11>;
cts-pin = <10>;
};

that didn't seem to help (i did clean and rebuild, clean run cmake and rebuild as well) 

the final dts file created after build build_nrf5340dk_nrf5340_cpuapp\zephyr.dts (for the main application image created after build)  shows pwm0 using the same pin as well..

pwm0: pwm@21000 {
compatible = "nordic,nrf-pwm";
reg = < 0x21000 0x1000 >;
interrupts = < 0x21 0x1 >;
status = "okay";
label = "PWM_0";
#pwm-cells = < 0x1 >;
ch0-pin = < 0x1c >;
};

but v1.6.1\zephyr\boards\arm\nrf5340dk_nrf5340\nrf5340dk_nrf5340_cpuapp.dts only has the following 

&pwm0 {
status = "okay";
ch0-pin = <28>;
};

where do rest of entries come from and how do i ensure "interrupts" use another pin instead of 0x21 ? (I do need pwm0 and hence can not disable it)

This pin on my device is used for my touch interrupt and this is becoming a blocker for my project.. How can we use pin 0x21 (P1.01) please help