OSD32MP153C GPIO read

[gil_he]

hello,

We implemented the STUSB1600 in our board using the OSD32MP153C-512M-BAA.

Its ALERT# pin is connected to PE8, which is defined as an interrupt for the SoC.

Implementation is the same as ST DK2 eval board (except we use PE8 and ST uses PI11).

When I measure the voltage on PE8, I read Low.

When I read the value using an I2C4 read command, from the UBOOT CLI, I get High.

How can that be?

From UBOOT CLI, I use:

i2c dev 0

gpio input GPIOE8

Attached find the UBOOT device tree files.

thanks,

Gil

• This topic was modified 2 weeks, 1 day ago by gil_he.

Attachments:

1. stm32mp157c-osd32mp1-brk_UBOOT.zip

[Neeraj Dantu]

Gil,

The device tree attached shows that GPIOE8 has the internal pull-up enabled. However, there should not be a measurement discrepancy between u-boot CLI and measurement.

Here is an interaction I just had on the CLI to show status of GPIOE8 on the RED board:

STM32MP> gpio input GPIOE8 gpio: pin GPIOE8 (gpio 72) value is 0 STM32MP> gpio status GPIOE8 Bank GPIOE: GPIOE8: input: 0 [ ]

1 2 3 4 5 6 7 8 9

STM32MP> gpio input GPIOE8   gpio: pin GPIOE8 (gpio 72) value is 0   STM32MP> gpio status GPIOE8   Bank GPIOE:   GPIOE8: input: 0 [ ]

 

 

[gil_he]

Hi Neeraj,

I agree.

There shouldn’t be any discrepancy.

But, there is.

What is wrong here?

Why do the GPIO measurement and GPIO I2C read give different results?

thanks,

Gil

[Author]

Posts