TDA4VM: watchdog interrupt is not worked in custom board

Sung-IL

Part Number: TDA4VM

Dear Champs,

My customer found the watchdog interrupt(SOC_SAFETY_ERRORn) was not worked and there was no wdt interrupt generated during long time when they test watchdog using ltp command.

When they checked watchdog driver, it seems there is no issue in SW and watchdog driver was processed.

But, there was no signal change observed in SOC_SAFETY_ERRORn pin of TDA4.

As there is no specific design between TDA4 and TPS65941213 and SOC_SAFETY_ERRORn was just connected to GPIO3 of TPS65941213 in their HW, they want to get our helpful comments to debug this issue.

one other strange thing is that reset was not occurred even when they forced low signal in the GPIO3 of TPS65941213 PMIC.

When they tried all these things in TI EVM, they found the WDT reset was occurred well. And also, when they tried to force low signal in the GPIO3 of PMIC, the reset was occurred in TI EVM.

Please check below log and let me know you guide to debug this issue in their custom board.

Fullscreen watchdog_ltp.txt Download

root@j7-evm:~# cd /opt/ltp/
root@j7-evm:/opt/ltp# ./runltp -P j721e-idk-gw -f ddt/wdt_test -s "WDT_M_FUNC_WRI"
INFO: creating /opt/ltp/output directory
INFO: creating /opt/ltp/results directory
INFO: Filtering testscenarios based on j721e-idk-gw capabilities
awk: cmd. line:1: warning: regexp escape sequence `\&' is not a known regexp operator
Checking for required user/group ids

'nobody' user id and group found.
'bin' user id and group found.
'daemon' user id and group found.
Users group found.
Sys group found.
Required users/groups exist.
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.

/etc/os-release
ID=arago
NAME="Arago"
VERSION="2020.09"
VERSION_ID=2020.09
PRETTY_NAME="Arago 2020.09"

uname:
Linux j7-evm 5.10.41-g4c2eade9f7 #1 SMP PREEMPT Wed Aug 4 22:47:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux

/proc/cmdline
console=ttyS2,115200n8 earlycon=ns16550a,mmio32,0x02800000 mtdparts=47040000.spi.0:512k(ospi.tiboot3),2m(ospi.tispl),4m(ospi.u-boot),256k(ospi.env),1m(ospi.sysfw),256k(ospi.env.backup),57344k@8m(ospi.rootfs),256k(ospi.phypattern);47034000.hyperbus:512k(hbmc.tiboot3),2m(hbmc.tispl),4m(hbmc.u-boot),256k(hbmc.env),1m(hbmc.sysfw),-@8m(hbmc.rootfs) root=PARTUUID=096d2ca1-02 rw rootfstype=ext4 rootwait

Gnu C                  gcc (GCC) 9.2.1 20191025
Clang                 
Gnu make               4.3
util-linux             2.35.1
mount                  linux 2.35.1 (libmount 2.35.1: btrfs, namespaces, assert, debug)
modutils               26
e2fsprogs              1.45.4
Linux C Library        > libc.2.30
Dynamic linker (ldd)   2.30
Linux C++ Library      6..
Procps                 3.3.16
Net-tools              1.60
iproute2               iproute2-5.10.0
iputils                'V'
ethtool                5.10
Kbd                    2.2.0
Sh-utils               8.31
Modules Loaded         xhci_plat_hcd xhci_hcd rpmsg_char ti_am335x_adc kfifo_buf cdns3 udc_core roles omap_rng rng_core irq_pruss_intc pru_rproc icss_iep usbcore usb_common crct10dif_ce snd_soc_j721e_evm ti_j721e_cpsw_virt_mac phy_can_transceiver ti_k3_r5_remoteproc m_can_platform m_can can_dev ti_am335x_tscadc pruss cdns_dphy sa2ul ti_k3_dsp_remoteproc sha512_generic virtio_rpmsg_[   35.595371] LTP: starting WDT_M_FUNC_WRITE (source 'common.sh'; do_cmd install_modules.sh 'wdt' ; DEV_NODE=`get_devnode.sh "wdt"` || die "error getting devnode for wdt"; do_cmd wdt_tests -device $DEV_NODE -ioctl -write)
bus authenc vxd_dec videobuf2_dma_sg v4l2_mem2mem videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common cdns3_ti snd_soc_pcm3168a_i2c snd_soc_pcm3168a bluetooth pvrsrvkm ecdh_generic ecc rfkill ina2xx pci_endpoint_test rti_wdt sch_fq_codel rpmsg_kdrv_switch cryptodev ipv6

free reports:
              total        used        free      shared  buff/cache   available
Mem:        2321216      195776     1822592       36416      302848     1774912
Swap:             0           0           0

cpuinfo:
Architecture:                    aarch64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
CPU(s):                          2
On-line CPU(s) list:             0,1
Thread(s) per core:              1
Core(s) per socket:              2
Socket(s):                       1
Vendor ID:                       ARM
Model:                           0
Model name:                      Cortex-A72
Stepping:                        r1p0
BogoMIPS:                        400.00
L1d cache:                       64 KiB
L1i cache:                       96 KiB
L2 cache:                        1 MiB
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Not affected
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid

AppArmor disabled

SELinux mode: unknown
no big block device was specified on commandline.
Tests which require a big block device are disabled.
You can specify it with option -z
COMMAND:    /opt/ltp/bin/ltp-pan   -e -S   -a 1205     -n 1205 -p -f /tmp/ltp-s1f0Cqh1p4/alltests -l /tmp/tmp.FfBaQhQhuQ  -C /opt/ltp/output/LTP_RUN_ON-tmp.FfBaQhQhuQ.failed -T /opt/ltp/output/LTP_RUN_ON-tmp.FfBaQhQhuQ.tconf
INFO: Restricted to WDT_M_FUNC_WRI
LOG File: /tmp/tmp.FfBaQhQhuQ
FAILED COMMAND File: /opt/ltp/output/LTP_RUN_ON-tmp.FfBaQhQhuQ.failed
TCONF COMMAND File: /opt/ltp/output/LTP_RUN_ON-tmp.FfBaQhQhuQ.tconf
Running tests.......
<<<test_start>>>
tag=WDT_M_FUNC_WRITE stime=1642039187
cmdline="source 'common.sh'; do_cmd install_modules.sh 'wdt' ; DEV_NODE=`get_devnode.sh "wdt"` || die "error getting devnode for wdt"; do_cmd wdt_tests -device $DEV_NODE -ioctl -write"
contacts=""
analysis=exit
<<<test_output>>>
|TRACE LOG|Inside do_cmd:CMD=install_modules.sh wdt|
|TRACE LOG|Inside do_cmd:CMD=wdt_tests -device /dev/watchdog -ioctl -write|
|TEST START|wdt_tests|
|TRACE LOG|******** WDT Testcase  parameters  ******** |
|TRACE LOG|Device         : /dev/watchdog|
|TRACE LOG|Loop Count     : 1|
|TRACE LOG|I/O Operation  : Write|
|TRACE LOG|Operation      : Ioctl|
|TRACE LOG|Ioctl Name     : WDIOC_KEEPALIVE|
|TRACE LOG|Ioctl Arg      : 0 |
|TRACE LOG| ************* End of Test params ************* |
[ 1393.463295] rti_wdt_ping:109 start
|TRACE LOG|Keeping WDT alive, sleep counter -0(sec)|
|TEST RESULT|PASS|wdt_tests|
|TEST END|wdt_tests|
|TRACE LOG|EVM will be rebooted after 60 seconds|
|TRACE LOG|59 seconds remaining before reboot|
|TRACE LOG|58 seconds remaining before reboot|
|TRACE LOG|57 seconds remaining before reboot|
|TRACE LOG|56 seconds remaining before reboot|
|TRACE LOG|55 seconds remaining before reboot|
|TRACE LOG|54 seconds remaining before reboot|
|TRACE LOG|53 seconds remaining before reboot|
|TRACE LOG|52 seconds remaining before reboot|
|TRACE LOG|51 seconds remaining before reboot|
|TRACE LOG|50 seconds remaining before reboot|
|TRACE LOG|49 seconds remaining before reboot|
|TRACE LOG|48 seconds remaining before reboot|
|TRACE LOG|47 seconds remaining before reboot|
|TRACE LOG|46 seconds remaining before reboot|
|TRACE LOG|45 seconds remaining before reboot|
|TRACE LOG|44 seconds remaining before reboot|
|TRACE LOG|43 seconds remaining before reboot|
|TRACE LOG|42 seconds remaining before reboot|
|TRACE LOG|41 seconds remaining before reboot|
|TRACE LOG|40 seconds remaining before reboot|
|TRACE LOG|39 seconds remaining before reboot|
|TRACE LOG|38 seconds remaining before reboot|
|TRACE LOG|37 seconds remaining before reboot|
|TRACE LOG|36 seconds remaining before reboot|
|TRACE LOG|35 seconds remaining before reboot|
|TRACE LOG|34 seconds remaining before reboot|
[ 1423.466311] rti_wdt_ping:109 start
|TRACE LOG|33 seconds remaining before reboot|
|TRACE LOG|32 seconds remaining before reboot|
|TRACE LOG|31 seconds remaining before reboot|
|TRACE LOG|30 seconds remaining before reboot|
|TRACE LOG|29 seconds remaining before reboot|
|TRACE LOG|28 seconds remaining before reboot|
|TRACE LOG|27 seconds remaining before reboot|
|TRACE LOG|26 seconds remaining before reboot|
|TRACE LOG|25 seconds remaining before reboot|
|TRACE LOG|24 seconds remaining before reboot|
|TRACE LOG|23 seconds remaining before reboot|
|TRACE LOG|22 seconds remaining before reboot|
|TRACE LOG|21 seconds remaining before reboot|
|TRACE LOG|20 seconds remaining before reboot|
|TRACE LOG|19 seconds remaining before reboot|
|TRACE LOG|18 seconds remaining before reboot|
|TRACE LOG|17 seconds remaining before reboot|
|TRACE LOG|16 seconds remaining before reboot|
|TRACE LOG|15 seconds remaining before reboot|
|TRACE LOG|14 seconds remaining before reboot|
|TRACE LOG|13 seconds remaining before reboot|
|TRACE LOG|12 seconds remaining before reboot|
|TRACE LOG|11 seconds remaining before reboot|
|TRACE LOG|10 seconds remaining before reboot|
|TRACE LOG|9 seconds remaining before reboot|
|TRACE LOG|8 seconds remaining before reboot|
|TRACE LOG|7 seconds remaining before reboot|
|TRACE LOG|6 seconds remaining before reboot|
|TRACE LOG|5 seconds remaining before reboot|
|TRACE LOG|4 seconds remaining before reboot|
|TRACE LOG|3 seconds remaining before reboot|
|TRACE LOG|2 seconds remaining before reboot|
|TRACE LOG|1 seconds remaining before reboot|
|TRACE LOG|0 seconds remaining before reboot|
|TRACE LOG|-1 seconds remaining before reboot|
|TRACE LOG|-2 seconds remaining before reboot|
|TRACE LOG|-3 seconds remaining before reboot|
|TRACE LOG|-4 seconds remaining before reboot|
|TRACE LOG|-5 seconds remaining before reboot|
|TRACE LOG|-6 seconds remaining before reboot|
|TRACE LOG|-7 seconds remaining before reboot|
|TRACE LOG|-8 seconds remaining before reboot|
|TRACE LOG|-9 seconds remaining before reboot|
|TRACE LOG|-10 seconds remaining before reboot|
|TRACE LOG|-11 seconds remaining before reboot|
|TRACE LOG|-12 seconds remaining before reboot|
|TRACE LOG|-13 seconds remaining before reboot|
|TRACE LOG|-14 seconds remaining before reboot|
|TRACE LOG|-15 seconds remaining before reboot|
|TRACE LOG|-16 seconds remaining before reboot|
|TRACE LOG|-17 seconds remaining before reboot|
|TRACE LOG|-18 seconds remaining before reboot|
|TRACE LOG|-19 seconds remaining before reboot|
|TRACE LOG|-20 seconds remaining before reboot|
|TRACE LOG|-21 seconds remaining before reboot|
|TRACE LOG|-22 seconds remaining before reboot|
|TRACE LOG|-23 seconds remaining before reboot|
|TRACE LOG|-24 seconds remaining before reboot|
|TRACE LOG|-25 seconds remaining before reboot|
|TRACE LOG|-26 seconds remaining before reboot|
|TRACE LOG|-27 seconds remaining before reboot|
|TRACE LOG|-28 seconds remaining before reboot|
|TRACE LOG|-29 seconds remaining before reboot|
|TRACE LOG|-30 seconds remaining before reboot|
|TRACE LOG|-31 seconds remaining before reboot|
|TRACE LOG|-32 seconds remaining before reboot|
|TRACE LOG|-33 seconds remaining before reboot|
|TRACE LOG|-34 seconds remaining before reboot|
|TRACE LOG|-35 seconds remaining before reboot|
|TRACE LOG|-36 seconds remaining before reboot|
|TRACE LOG|-37 seconds remaining before reboot|
|TRACE LOG|-38 seconds remaining before reboot|
|TRACE LOG|-39 seconds remaining before reboot|
|TRACE LOG|-40 seconds remaining before reboot|
|TRACE LOG|-41 seconds remaining before reboot|
|TRACE LOG|-42 seconds remaining before reboot|
|TRACE LOG|-43 seconds remaining before reboot|
|TRACE LOG|-44 seconds remaining before reboot|
|TRACE LOG|-45 seconds remaining before reboot|
|TRACE LOG|-46 seconds remaining before reboot|
|TRACE LOG|-47 seconds remaining before reboot|
|TRACE LOG|-48 seconds remaining before reboot|
|TRACE LOG|-49 seconds remaining before reboot|
|TRACE LOG|-50 seconds remaining before reboot|
|TRACE LOG|-51 seconds remaining before reboot|
|TRACE LOG|-52 seconds remaining before reboot|
|TRACE LOG|-53 seconds remaining before reboot|
|TRACE LOG|-54 seconds remaining before reboot|
|TRACE LOG|-55 seconds remaining before reboot|
|TRACE LOG|-56 seconds remaining before reboot|
|TRACE LOG|-57 seconds remaining before reboot|
|TRACE LOG|-58 seconds remaining before reboot|
|TRACE LOG|-59 seconds remaining before reboot|
|TRACE LOG|-60 seconds remaining before reboot|

Their SW SDK is Processor Linux SDK v8.0.

Thanks and Best Regards,

SI.

over 3 years ago

0 Keerthy J over 3 years ago

TI__Guru**** 162950 points

Hi SI,

This works well on the TDA4VM board. This can be an issue with board connections. Is the design different when compared to TI EVM?

- Keerthy

0 Sung-IL over 3 years ago in reply to Keerthy J

TI__Mastermind 30850 points

Hi Keerthy,

No. I could not find any difference between customer's board and TI EVM. I attached their HW schematic for SOC_SAFETY_ERR pin.

Thanks and Best Regards,

SI.

0 Sung-IL over 3 years ago in reply to Sung-IL

TI__Mastermind 30850 points

Hi Keerthy,

Could you please let me know your opinion why WDT interrupt was not worked in SOC_SAFETY_ERRORn pin?

My customer found they have not set PMIC registers properly and now they can observed PMIC works well properly when they forced LOW signal on LEOA_GPIO3 and LEOA_GPIO7.

But, they are still not make SOC_SAFETY_ERRORn pin of TDA4 to be low by WDT timer, and they could not find any debug things for it.

Please let me know your idea on this.

Thanks and Best Regards,

SI.

0 Keerthy J over 3 years ago in reply to Sung-IL

TI__Guru**** 162950 points

Hi SI,

Can you let me know the exact SDK version on which you are facing this? I will try to reproduce this on that SDK on TI EVM & get back to you
with my findings.

- Keerthy

0 Sung-IL over 3 years ago in reply to Keerthy J

TI__Mastermind 30850 points

Hi Keerthy,

They are using Linux SDK v8.0 now. But, as I mentioned, this issue is not produced in the EVM even in the customer side.

So, what they want is to get some guidance what should be checked and how they can debug it.

They traced linux driver, but could not find any strange thing in the SW.

Please let me know your idea on this.

Thanks and Best Regards,

SI.

0 Keerthy J over 3 years ago in reply to Sung-IL

TI__Guru**** 162950 points

Hi SI,

I am checking internally on this. I will get back in couple of days.

- Keerthy

0 Keerthy J over 3 years ago in reply to Keerthy J

TI__Guru**** 162950 points

Hi SI,

ESM is being configured only in the U-Boot. This configures a bunch of PMIC registers. Just another data point that could be different
on your custom board.

- Keerthy

0 Sung-IL over 3 years ago in reply to Keerthy J

TI__Mastermind 30850 points

Hi Keerthy,

Thanks for your response.

As I mentioned, there were 2 issues as below.

1. no interrupt from SOC_SAFETY_ERRORn pin of TDA4.

2. no reset from PMIC

Your solution was helped to resolve '2. no reset from PMIC' issue, but '1. no interrupt from SOC_SAFETY_ERRORn pin of TDA4' issue is still there.

Do you have any idea on '1. no interrupt from SOC_SAFETY_ERRORn pin of TDA4' ?

Thanks and Best Regards,

SI.

0 Keerthy J over 3 years ago in reply to Sung-IL

TI__Guru**** 162950 points

Hi SI,

This is still being tracked internally. The watchdog reset is failing on internal boards as well:

https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/08_02_00_03/exports/docs/devices/J7/linux/Release_Specific_Release_Notes.html

Are you still facing this on custom board? let me know.

- Keerthy

0 Sung-IL over 3 years ago in reply to Keerthy J

TI__Mastermind 30850 points

Hi Keerthy,

Sorry for late. My customer developed workaround using PMIC.

Thanks and Best Regards,

SI.

Processors

Processors forum

TDA4VM: watchdog interrupt is not worked in custom board