GPIO can't be controlled

[LanceTaiwan]

Hi,

     I encountered a very strange issue.  I need to control a device using GPIO.  What I use is p0.22/p0.02/p0.03/p1.11/p0.31/p0.30.  I modify the app.overlay file and check the final zephyr.dts which is correct.  But when I use the gpio_pin_set_dt to control those GPIO, the results are not as I expected.

p0.22 , can't control, always 1
p0.02 ,can't control, always 0
p0.03 ,can't control, always 0
p1.11 , OK
p0.31 , OK
p0.30 ,can't control, always 0

   In my project, I also control the other GPIO p0.5/p1.15/p1.14/p1.1/p1.0 using the same method and those GPIO work well.  I check the issue again and again and I can't find anything wrong.  

My questions are

1. Is it possible the pins are overlapping assignments? ( I checked zephyr.dts already, another way to check it? )
2. Is it possible those pins can't be used as GPIO? p0.22/p0.02/p0.03/p0.30

Thanks

[Sigurd Hellesvik]

From what I know about the nRF7002DK, it only supports 1.8V.

There may be methods for changing it on the DK itself, but I think they will be a bit hacky.

Can I suggest that you use a logic level converter instead for testing the DK with higher voltage peripherals?

[LanceTaiwan]

Hi

    Yes please

[Sigurd Hellesvik]

I mean:

Use a Logic Level Converter module

[LanceTaiwan]

Hi,

    Let me discuss with my hardware engineers, thanks

[Sigurd Hellesvik]

The nRF7002DK uses 1.8V as a design choice.

For custom hardware using the nRF7002, you can use whatever is within its Recommended operating conditions

EDIT: The reason that 1.8V is used for the DK seems to be this errata