Hi,
I'm trying to set the SNVS_TAMPER2 pin as follows:
&iomuxc_snvs {
pinctrl-names = "default_snvs";
pinctrl-0 = <&pinctrl_hog_2>;
imx6ull-evk {
pinctrl_hog_2: hoggrp-2 {
fsl,pins = <
MX6ULL_PAD_SNVS_TAMPER2__GPIO5_IO02 0x17059
>;
};
};
};
but when I try to read the register of the pin I find the following value:
~# devmem2 0x2290054
/dev/mem opened.
Memory mapped at address 0x76f8c000.
Read at address 0x02290054 (0x76f8c054): 0x000110A0
what's the problem?
Thanks so much
Domenico Acri
Hi Igor
I don't understand what the i.MX6ULL EVK board has to do with it.
We are talking about a processor pin that if it is configured as gpio output I can move it correctly, but if it is configured as input I cannot customize the SW_PAD_CTL_PAD via dts.
I see you don't have a precise answer to my question, thank you anyway.
Best Regards
Domenico Acri
Hi Domenico
if this is issue with silicon or nxp software bsp, it should be reproduced
on i.MX6ULL EVK board with nxp official linux releases.
If it can be reproduced, then I can escalate it for further investigation.
So if you think that this is silicon or bsp bug please provide detailed steps
how it could be reproduced on nxp side.
Best regards
igor
Hi Igor,
it seems strange.
I am using this NXP BSP with kernel version 4_14_98.
root@microgea:~# uname -a
Linux microgea 4.14.98-gffb034d225d4 #1 SMP Fri Feb 14 09:00:56 CET 2020 armv7l GNU/Linux
root@microgea:~# devmem2 0x229005C
/dev/mem opened.
Memory mapped at address 0xb6f43000.
Read at address 0x0229005C (0xb6f4305c): 0x000110A0
As you can see it doesn't work with the official NXP kernel.
Do you have other ideas?
Best Regards
Domenico Acri
Hi Domenico
had you tried on i.MX6ULL EVK board.
Please try it with Demo Images from link:
i.MX Software and Development Tools | NXP
Best regards
igor
Hi Igor,
Thanks a lot for the answer.
Unfortunately with the changes you suggest it doesn't work, this is what the memtool command gives me:
MX6ULL_PAD_SNVS_TAMPER0__GPIO5_IO00 0x80000000
memtool 229004C 1
E
Reading 0x1 count starting at address 0x0229004C
0x0229004C: 000110A0
MX6ULL_PAD_SNVS_TAMPER3__GPIO5_IO03 0x79
memtool 2290058 1
E
Reading 0x1 count starting at address 0x02290058
0x02290058: 000110A0
MX6ULL_PAD_SNVS_TAMPER9__GPIO5_IO09 0x79
memtool 2290070 1
E
Reading 0x1 count starting at address 0x02290070
0x02290070: 000110A0
it seems that if the tamper pins are configured as inputs, it is not possible to write to the SW_PAD_CTL_PAD from the device tree; but from devmem everything works.
Do you have other ideas?
Best Regards
Domenico Acri
Hi Domenico
probably you are using non-nxp linux as devmem is not supported by nxp.
Please try official nxp linux from source.codeaurora.org/external/imx/linux-imx repository
with nxp i.MX6ULL EVK reference board.
Also one can try Demo Images from link:
i.MX Software and Development Tools | NXP
Best regards
igor
Hi Domenico
just for test one can check other MX6ULL_PAD_SNVS_TAMPER pads defined in
imx6ull-14x14-evk.dts\dts\boot\arm\arch - linux-imx - i.MX Linux kernel
using memtool
memtool\test - imx-test - i.MX Driver Test Application Software
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------