Watchdog has expired.

I guess that you must have one timer which will reset system when timeout occurs. When debugging, for example, application code stop by breakpoint, but the timer still works, when timeout, it will reset system ,then IDE will report that watchdog timeout...

FYI.

David

--- Quote Start ---

originally posted by david_cai@Aug 1 2006, 09:37 AM

i guess that you must have one timer which will reset system when timeout occurs. when debugging, for example, application code stop by breakpoint, but the timer still works, when timeout, it will reset system ,then ide will report that watchdog timeout...

fyi.

david

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=17315)

--- quote end ---

--- Quote End ---

I completely agree with you, David. However this is essencially my problem. I can&#39;t find what timer or component could be causing the problem. As far as I know, a timer configured with &#39;Writeable Period&#39; and &#39;Start/Stop control bits&#39; registers (Full-featured preset configuration) resets the counter when period timeouts but never the system.

Another info that could help you and others nios users to help me: Always I try to use ssram to store data and instructions (.rodata, .rwdata, etc..), I have problems with debug too, and the watchdog error is reported just in the terminals of the cpus that are coneccted to ssram. How could ssram be affecting watchdog?

Thanks again!

Hi,

Today I encountered the same problem under the following operation:

I reset Nios system by hardware when debugging, then NiosII IDE report the same problem...

Maybe when your system broken when debugging then IDE will report this issue.

FYI.

David

--- Quote Start ---

originally posted by david_cai@Aug 2 2006, 08:28 AM

today i encountered the same problem under the following operation:

i reset nios system by hardware when debugging, then niosii ide report the same problem...

maybe when your system broken when debugging then ide will report this issue.

<div align='right'><{post_snapback}> (index.php?act=findpost&pid=17350)

--- quote end ---

--- Quote End ---

Yes, your info made me remeber another spot. I discussed this error once with a mastership student and he told me that a possible reason to this is when the communication between some Nios CPU and the Nios IDE falls. It was exactly what happen with you, wasn&#39;t it? However may exist other reasons to this communication falls, such as when a Nios CPU, or the Avalon switch fabric, is so busy so that stops sending messages to jtag_debug_module. However I&#39;m not being able to identify what component in the SOPC builder could be answerable for this.

Mendonça.

The message you&#39;re seeing is a standard GDB message which indicates a failure (or, at the very least, a timeout) in communications between the host and the remote side. You can look through any GDB source code and you&#39;ll find this message in the remote.c file.

The point being, here, that you shouldn&#39;t waste your time debugging SOPC Builder components, as they aren&#39;t generating this message.

Regards,

- slacker