PAD SNVS_TAMPER8 and GPIO5_IO08

[app025]

Hi,

I have a board using a iMX6UL G2.

In dts section

   iomuxc => imx6ul-evk => pinctrl_hog

I added

   MX6UL_PAD_SNVS_TAMPER8__GPIO5_IO08      0x1f0b0      // 22K pullup

After the kernel load completely, the board provides a 3.3 V at GPIO5_IO8 (as expected).

The same board can use a iMX6ULL Y2.

In the dts section

   iomuxc_svns => imx6ul-evk => pinctrl_hog

I added

   MX6ULL_PAD_SNVS_TAMPER8__GPIO5_IO08     0x1f0b0      // 22K pullup

After the kernel load completely, the board provides a 0 V at GPIO5_IO8 (unexpected).

On the target, if I check the file

   /sys/kernel/debug/pinctrl/pinctrl-maps

it reports the pad MX6ULL_PAD_SNVS_TAMPER8 programmed correctly with config 0x1f0b0.

Nothing is connected to the pin but my scope.

Why I'm seeing this different behavior?

Is this a know behavior?

Thanks

BR

Pier

[mleblanc]

Hi Igor, 

Hi Pier,

We  are working with the following date codes:

CTAP1806
CTBD1838

And both will not provide the pull up using 0x1b0b0 in config.

Michel

[igorpadykov]

Hi Pier, Michel

I escalated internally this issue and answer when receive any updates.

Best regards
igor

[igorpadykov]

Hello

I received answer indicating that there are no known pull issues with that part.

Could you try to reproduce issue on i.MX6ULL EVK (has iMX6ULL Y2) schematic SPF-29364

Schematics (1)
Design files, including hardware schematics, Gerbers, and OrCAD files.
MCIMX6ULL-EVK_DESIGNFILES

MCIMX6ULL-EVK|i.MX6ULL Evaluation Kit | NXP 

using NXP official Demo Images on

i.MX Software | NXP 

Best regards
igor

[app025]

Hi Igor,

we are working with the following date codes:

- CTAB1643

- CTAL1720

When you write that there's no known issue, do you mean that anyone successfully tested the above PAD configuration with an iMX6ULL ?

Thanks

BR

Pier

[app025]

Hi Igor,

I can confirm the problem with different boards, as long as the use iMX6ULL.

Any suggestion?

BR

Pier

[igorpadykov]

Hi Pier

I checked internally there are no known issues with it.

Are you able to check with different batches/date codes samples.

Best regards
igor

[mleblanc]

Hi Igor,

I have experienced this issue on my side as well with several boards.

We are using this GPIO to wake up from suspend mode.

Now we are considering to do a reworks on our production boards by adding an external 10K pull up to 3.3V, unless this can be fix through device tree files.

Is this an issue you can replicate or not?

Regards,

Michel

[app025]

Hi Igor,

correct settings but no internal pullup.

The problem is reproducible on the whole GPIO5 bank and only when using iMX6ULL (Y2) flavour.

I would appreciate if any clarification would be provided (included no pullup support available on Y2).

Thanks

BR

Pier

[igorpadykov]

Hi Pier

is this just one part, is it possible to check it on

other parts preferably from other batch.

 

Best regards
igor

[app025]

Hi Igor,

thanks for your reply.

Actually the pin works great as GPIO, I can set it as input (and read the correct input) or output (and observe the correct output).

The problem is that, with Y2 only, it does not allow to setup any internal pullup.

Is this is a known problem?

Thanks

BR

Pier

[igorpadykov]

Hi Pier

I am not aware of problems with it, so had you confirmed with jtag correct settings :

IOMUXC_SNVS_SW_MUX_CTL_PAD_SNVS_TAMPER8 ALT5

IOMUXC_SNVS_SW_PAD_CTL_PAD_SNVS_TAMPER8  0x1f0b0.

Best regards
igor

[igorpadykov]

Hi Pier

in general it could be used as gpio, one can try to test gpio with jtag,

may be useful AN5229 ARM DS-5 Development Studio Debug i.MX6UL-EVK

https://www.nxp.com/docs/en/application-note/AN5229.pdf 

Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------