Question with RSTOUT_WD_OUT on DM8148

Hi Marcus,

Are you using DM814x EVM or custom board?

BR
Pavel

Hi Pavel :

I appreciate your reply!

I have tried EVM board and our board.

And the result is the same.

I use TI 8148 EVM board to test RSTOUT_WD_OUT.

I switch BTMODE[11] to low and run watchdog test program refer link below.

http://www.deyisupport.com/question_answer/dsp_arm/davinci_digital_media_processors/f/39/t/23557.aspx

When system reboot, the RSTOUT_WD_OUT is always high and it do not pull low.

Best regards,

Marcus

Marcus,

Regarding BTMODE[11], it does not have any impact to the Watchdog reset. See DM814x datasheet:

BTMODE[11]   RSTOUT_WD_OUTn Configuration.

0x0: RSTOUTn is asserted when a Watchdog Timer reset, POR, RESET, or Emulation/Software-Global Cold/Warm reset occurs

0x1: RSTOUT_WD_OUTn is asserted only when a Watchdog Timer reset occurs

In both cases (BTMODE[11] is 0x0 or 0x1), the RSTOUTn pin is asserted when a Watchdog Timer reset occurs.

I made the test with DM814x/AM387x EVM and RSTOUTn pin is asserted for 600ns when Watchdog Timer reset is generated, the RSTOUTn pin is not always high.

The difference is that I have no access to RDK, thus I am using EZSDK. Please find in attachment the Watchdog Timer reset test available in EZSDK: 8231.watchdog.tar.gz

For how to use this Watchdog test, refer to the below link:

http://processors.wiki.ti.com/index.php/TI81XX_PSP_WDT_Support#Sample_Applications

To sum up, I can propose you to try to implement this Watchdog test in your RDK.

Best regards,
Pavel

Hi Pavel :

I appreciate your reply!

I am a little confused about your description.

0x0: RSTOUTn is asserted when a Watchdog Timer reset, POR, RESET, or Emulation/Software-Global Cold/Warm reset occurs

0x1: RSTOUT_WD_OUTn is asserted only when a Watchdog Timer reset occurs

RSTOUTn and RSTOUT_WD_OUTn are the same pin,right?

Because I can not find RSTOUTn in hardware schematic of TI8148 EVM board.

If my understanding is correct, no matter what the BTMODE[11]   RSTOUT_WD_OUTn Configuration is, it should be asserted when watchdog overflow.

Below is part of  hardware schematic of TI8148 EVM board which is related with RSTOUTn_WD_OUT.

I do not know if there is something wrong with the circuit.

I have test sawatchdog in TI8148EVM board, but I do not see RSTOUT_WD_OUTn is pulled low when watchdog overflow.

I also use SD card that comes from with TI8148 EVM board and execute sawatchdog to test  RSTOUT_WD_OUTn, but the result is the same.

RSTOUT_WD_OUTn is always high even though the watchdog overflow and system reboot.

The message "OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec" shows when kernel is loaded.

But I can not see "<*> OMAP Watchdog" option when I execute make menuconfig.

I do not know if it is a hardware or software issue.

Please kindly give me your suggestion, because we need  RSTOUT_WD_OUTn pin to reset whole system.

Best regards,

Marcus

Marcus,

lu yuenjune said:

RSTOUTn and RSTOUT_WD_OUTn are the same pin,right?

Right

lu yuenjune said:

If my understanding is correct, no matter what the BTMODE[11]   RSTOUT_WD_OUTn Configuration is, it should be asserted when watchdog overflow.

Correct

lu yuenjune said:

I do not know if there is something wrong with the circuit.

I compared with my working circuit, everything is the same. Please make sure you are attaching the oscilloscope to TP59 (RST OUT) and TP67 (GND). Also double check your oscilloscope settings. The expected/default RSTOUT_WD_OUTn signal is 600ns.

lu yuenjune said:

I do not know if it is a hardware or software issue.

As the test is performed on EVM, I suspect it is software issue.

Please provide me full log (u-boot, kernel. user space) and I will make a deeper look.

Regards,
Pavel

Hi Pavel :

I really appreciate your help!

Below is the log and I have confirmed that the scope is OK and test point is TP59.

U-Boot 2010.06 (Nov 10 2011 - 23:50:16)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

DRAM: 2 GiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
MMC: OMAP SD/MMC: 0
Hit any key to stop autoboot: 0
reading u-boot.bin

185044 bytes read
## Starting application at 0x80800000 ...

U-Boot 2010.06 (Nov 10 2011 - 23:45:47)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

I2C: ready
DRAM: 2 GiB
NAND: HW ECC Hamming Code selected
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
NAND bus width 8 instead 16 bit
No NAND device found!!!
0 MiB
*** Warning - bad CRC or NAND, using default environment

.:;rrr;;.
,5#@@@@#####@@@@@@#2,
,A@@@hi;;;r5;;;;r;rrSG@@@A,
r@@#i;:;s222hG;rrsrrrrrr;ri#@@r
:@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:
B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B | VT102 離線 @@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@
@@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@
@@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@
G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G
@9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@
X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
@#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
@A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
@&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
@#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
:@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
@@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@
@A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@
;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;
r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r
,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,
B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H
.@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.
.A@@#5r;;;r;;;rrr;r:r#AsM@@H.
;&@@@@MhXS5i5SX9B@@@@G;
:ihM#@@@@@##hs,

MMC: OMAP SD/MMC: 0
Net: <ethaddr> not set. Reading from E-fuse
Detected MACID:40:5f:c2:1f:f6:d2
cpsw
Hit any key to stop autoboot: 0
reading boot.scr

301 bytes read
Running bootscript from MMC/SD to set the ENV...
## Executing script at 80900000
reading uImage

2570080 bytes read
## Booting kernel from Legacy Image at 80009000 ...
Image Name: Arago/2.6.37-psp04.01.00.06/dm81
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2570016 Bytes = 2.5 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (x0029463@swubn01) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 Thu Nov 10 23:48:02 IST 2011
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
bootconsole [earlycon0] enabled
vram size = 52428800 at 0x0
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.0
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 52224
Kernel command line: console=ttyO0,115200n8 rootwait root=/dev/mmcblk0p2 rw mem=256M earlyprintk notifyk.vpssm3_sva=0xBF900000 vram=50M ti814xfb.vram=0:16M,d
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 206MB = 206MB total
Memory: 203148k/203148k available, 58996k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)
lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003a000 ( 200 kB)
.text : 0xc003a000 - 0xc04de000 (4752 kB)
.data : 0xc04de000 - 0xc0526300 ( 289 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
registered ti814x_vpss device
registered TI814x on-chip HDMI device
NOR: Can't request GPMC CS
registered ti81xx_vidout device
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
Registered ti81xx_fb device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xd0820000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
pcf857x 1-0021: gpios 128..143 on a pcf8575
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d081e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d0826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) �© 2001-2006 Red Hat, Inc.
msgmni has been set to 396
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xca (Micron NAND 256MiB 3,3V 16-bit)
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000260000 : "U-Boot"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x00000cee0000 : "File System"
0x00000cee0000-0x000010000000 : "Reserved"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffc
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
asoc: tlv320aic3x-hifi <-> davinci-mcasp.2 mapping ok
ALSA device list:
#0: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=40:5f:c2:1f:f6:d2
omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:01 UTC (946684801)
ata1: SATA link down (SStatus 0 SControl 300)
Waiting for root device /dev/mmcblk0p2...
mmc0: new high speed SDHC card at address e624
mmcblk0: mmc0:e624 SD08G 7.40 GiB
mmcblk0: p1 p2 p3
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (mmcblk0p2): using internal journal
EXT3-fs (mmcblk0p2): recovery complete
EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
VFS: Mounted root (ext3 filesystem) on device 179:2.
devtmpfs: mounted
Freeing init memory: 200K
INIT: version 2.86 booting
Error opening /dev/fb0: No such file or directory
Please wait: booting...
Starting udev
udevd (76): /proc/76/oom_adj is deprecated, please use /proc/76/oom_score_adj instead.
EXT3-fs: barriers not enabled
kjournald starting. Commit interval 5 seconds
EXT3-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
EXT3-fs (mmcblk0p3): using internal journal
EXT3-fs (mmcblk0p3): recovery complete
EXT3-fs (mmcblk0p3): mounted filesystem with writeback data mode
Remounting root file system...
Caching udev devnodes
NET: Registered protocol family 10
ALSA: Restoring mixer settings...
Configuring network interfaces... ifconfig: SIOCGIFFLAGS: No such device
done.
Setting up IP spoofing protection: rp_filter.
Fri Nov 11 01:33:00 UTC 2011
INIT: Entering runlevel: 5
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
PRCM for IVHD0 is in Progress, Please wait.....
BW Phy Addr : 0x48180600 Data : 0x00000001
AW Phy Addr : 0x48180600 Data : 0x00000002
Phy Addr : 0x48180c04 Data : 0x00000037
BW Phy Addr : 0x48180620 Data : 0x00070000
AW Phy Addr : 0x48180620 Data : 0x00070002
BW Phy Addr : 0x48180624 Data : 0x00030000
AW Phy Addr : 0x48180624 Data : 0x00010002
Phy Addr : 0x48180600 Data : 0x00000102
BW Phy Addr : 0x48180c10 Data : 0x00000007
AW Phy Addr : 0x48180c10 Data : 0x00000003
Phy Addr : 0x48180c14 Data : 0x00000004
BW Phy Addr : 0x58088000 Data : 0x4ecd3d66
AW Phy Addr : 0x58088000 Data : 0xeafffffe
BW Phy Addr : 0x58098000 Data : 0x647d80f2
AW Phy Addr : 0x58098000 Data : 0xeafffffe
BW Phy Addr : 0x48180c10 Data : 0x00000003
AW Phy Addr : 0x48180c10 Data : 0x00000000
Phy Addr : 0x48180c14 Data : 0x00000007
PRCM for IVHD0 is Done Successfully
PRCM Initialization completed
SysLink version : 2.00.04.83
SysLink module created on Date:Nov 11 2011 Time:00:02:38
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [Location of Mem map bin file]
FIRMWARE: Default memory configuration is used
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.1.1
FIRMWARE: Memory Configuration status : In Progress
FIRMWARE: 2 start Successful
Configuring fb0 to LCD
HDMI W1 rev 4.0
Starting system message bus: dbus.
Starting telnet daemon.
CMEMK module: built on Nov 10 2011 at 23:54:30
Reference Linux version 2.6.37
File /swcoe/sdk/cm/netra/arago-tmp/work/dm814x-evm-none-linux-gnueabi/ti-linuxutils-1_3_21_00_04-r1d/linuxutils_3_21_00_04/packages/ti/sdo/linuxutils/cmemc
allocated heap buffer 0xd7000000 of size 0x4ac000
cmemk initialized
Starting syslogd/klogd: done
Starting thttpd.
Starting PVR
/dev/mem opened.
Memory mapped at address 0x40228000.
Read at address 0x48180F04 (0x40228f04): 0x00000001
Write at address 0x48180F04 (0x40228f04): 0x00000000, readback 0x00000000
/dev/mem opened.
Memory mapped at address 0x4005e000.
Read at address 0x48180900 (0x4005e900): 0x00000102
Write at address 0x48180900 (0x4005e900): 0x00000002, readback 0x00000002
/dev/mem opened.
Memory mapped at address 0x4038a000.
Read at address 0x48180920 (0x4038a920): 0x00040002
Write at address 0x48180920 (0x4038a920): 0x00000002, readback 0x00000002
Starting Matrix GUI application.

_____ _____ _ _
| _ |___ ___ ___ ___ | _ |___ ___ |_|___ ___| |_
| | _| .'| . | . | | __| _| . | | | -_| _| _|
|__|__|_| |__,|_ |___| |__| |_| |___|_| |___|___|_|
|___| |___|

Arago Project http://arago-project.org dm814x-evm ttyO0

Arago 2011.09 dm814x-evm ttyO0

dm814x-evm login: root
root@dm814x-evm:~# cd /opt/
root@dm814x-evm:/opt# ./saWatchdog 12

Current timeout value is : 60 seconds

New timeout value is : 10 seconds
Current timeout value is : 10 seconds
Write succeeded

Best regards,

Marcus

Marcus,

From this log, it is not clear that you actually managed to reset the board. Here is lot a I have:

root@dm814x-evm:~# ./saWatchdog 12

Current timeout value is : 60 seconds

New timeout value is : 10 seconds
Current timeout value is : 10 seconds
Write succeeded


U-Boot 2010.06 (Dec 26 2012 - 18:17:23)

TI8148-GP rev 2.1

ARM clk: 600MHz
DDR clk: 400MHz

DRAM:  2 GiB
MMC:   OMAP SD/MMC: 0
Using default environment

Do you have the same as me, after the "Write succeeded" line?

Also, I see you are using very old software, is it EZSDK or RDK? For example your U-boot is "U-Boot 2010.06 (Nov 10 2011 - 23:45:47)" while mine is "U-Boot 2010.06 (Dec 26 2012 - 18:17:23)". Your PSP is psp04.01.00.06 while mine is psp04.04.00.01. Could you try with the latest version of the EZSDK 5.05.02.00, just for the test?

Best regards,
Pavel

Hi Pavel :

Thanks for your reply!

When watchdog is overflow, I did see reboot message.

I use SD card that comes from with TI8148 EVM board, so firmware is very old.

Since I use DVSDK, I do not have latest version of EZSDK.

Could you give me your uImage, and I can try on our EVM board?

I think if it is a software issue, it should be related with kernel not uboot, right?

I have latest DVSDK and I will try again on EVM board and let you know the result.

Best regards,

Marcus

Hi Pavel :

This issue has been solve.

I think I made a mistake with our scope.

Now, I can see RSTOUT_WD_OUT which is polled low over 600ns when watchdog is overflow.

I am very sorry about bothering you so many times.

Anyway, thanks for your help!

Best regards,

Marcus

Marcus,

I am glad to know the issue is solved.

Best regards,
Pavel