Re: me too: watchdog timer reboot does not cause NetBoot processing to run

Hi,

I've experienced the same problem.
If the watchdog wakes up and reboots, my apps don't restart until I powercycle the units.
It is quite annoying, since the idea of the watchdog is to enhance the reliability of the device,
so that if something hangs it restarts, as it is now, if there is a temporary network outage or something,
it restarts and just runs w/o any apps loaded (i.e becomes unfunctional) making the problem worse than it was!

I've tested it using:
TINI1.02d jdk1.3.1
On the C390's


Sincerely Thomas

From: Aaron Buchanan <[email protected]>
To: "'tini-6tN4nzCoH/[email protected]'" <[email protected]>
Date: Thu, 15 Apr 2004 16:34:31 -0400
Subject: [TINI]watchdog timer reboot does not cause NetBoot processing to run

Hi,

In my testing I have observed that the NetBoot process does not execute
after a watchdog timeout reboot.  I have been testing using the
TINIs400/TINIm400 reference platform using TINI1.12 and a java application.
I enable the watchdog timer when my application starts.  I've purposefully
created test versions that do not feed the watchdog to verify its
functionality.  I have netboot enabled, and verified it is working
correctly.  If my application reboots due to the watchdog timeout, netboot
is not invoked (the file requests are not display in my tftp log).  If
generate a reboot using the TINIOS.reboot() call the Netboot process is
executed on startup.

-Aaron

______________________________
Aaron Buchanan
Firmware/Software Engineer

--__--__--

Message: 10
From: Aaron Buchanan <[email protected]>
To: "'tini-6tN4nzCoH/[email protected]'" <[email protected]>
Date: Thu, 15 Apr 2004 16:34:49 -0400
Subject: [TINI]netboot bug

Hi,

During testing of different netboot scenarios I found the following oddity.
I consider it to be a bug in the netboot process based on both the
documentation and how I'd expect it to work.

According to the documentation (DS80C400 Network Microcontroller pg. 74): 
"If either DHCP or the TFTP transfer fail, the NetBoot code checks whether
the TFTP transfer has been successful in a previous attempt.  If so, the
TINI400 ROM exits NetBoot and transfers execution to the find-user-code
routine."

I'm using the TINIs400/TINIm400 reference platform and have a succesfully
netbooted and running application.  I have the Netboot tftp option
configured in my DHCP server, and my tftp server running.  I've removed all
3 of the file variations that the netboot process looks for on the tftp
server and power-cycle the TINI.  On restart my application never boots, and
in the tftp server log I see a continuous cycle of the TINI requesting and
not finding any of the 3 netboot files.  I expect, and according to the
documentation, after failing the tftp transfer the netboot process should
exit and transfer to the find-user-code routine.  I found that by creating
an empty (0 byte) TINI400 file on my tftp server the TINI netboot process
would exit and continue with my user code.  

I was interested in having netboot enabled by default in my product, but
this operation is a concern for me.

Thanks,
-Aaron

______________________________
Aaron Buchanan
Firmware/Software Engineer

--__--__--




_______________________________________________
TINI mailing list
TINI-6tN4nzCoH/[email protected]
To UNSUBSCRIBE, edit your profile, or see list archives:
http://lists.dalsemi.com/mailman/listinfo/tini