From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gatekeeper.tait.co.nz (unknown [202.37.96.21]) by ozlabs.org (Postfix) with ESMTP id 4A21867A78 for ; Mon, 31 Jan 2005 09:15:49 +1100 (EST) Received: from gatekeeper.tait.co.nz (merlin.tait.co.nz [127.0.0.1]) by localhost.tait.co.nz (Postfix) with ESMTP id 261B410BA74 for ; Mon, 31 Jan 2005 11:15:46 +1300 (NZDT) Received: from sunstrike.tait.co.nz (unknown [172.25.40.92]) by gatekeeper.tait.co.nz (Postfix) with ESMTP id 1E86210BA37 for ; Mon, 31 Jan 2005 11:15:45 +1300 (NZDT) Received: from conversion-daemon.sunstrike.tait.co.nz by sunstrike.tait.co.nz (Sun Java System Messaging Server 6.1 (built Apr 28 2004)) id <0IB500901F1XBU00@sunstrike.tait.co.nz> (original mail from robin.gilks@tait.co.nz) for linuxppc-embedded@ozlabs.org; Mon, 31 Jan 2005 11:15:45 +1300 (NZDT) Date: Mon, 31 Jan 2005 11:15:45 +1300 From: Robin Gilks In-reply-to: <41F74169.9050006@intracom.gr> To: ppc embedded list Message-id: <41FD5C91.404@tait.co.nz> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 References: <41F70114.5040200@tait.co.nz> <41F74169.9050006@intracom.gr> Subject: Re: 8xx bus monitoring Reply-To: robin.gilks@tait.co.nz List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Pantelis Antoniou wrote: > Robin Gilks wrote: > >> Greetings >> >> System is a MPC859 based controller. >> >> I'm trying to determine whether a peripheral is not responding to >> memory fetches by using the bus monitor feature on the Transfer >> Acknowledge (TA) signal. This is set to the maximum count in the Bus >> Monitor Timeout (BMT) in the System Protect Control Register (SYPCR). >> The monitoring is enabled by setting the Bus Monitor Enable (BME) bit >> in SYPCR as well. >> >> I understand that I can use the Transfer Error Status Register (TESR) >> to read the fact that I have had a timeout by checking the Data >> Transfer Monitor Timeout (DTMT) bit in this register. >> >> The problem is, how do I know any error has occured so I know to look >> at the TESR. I can't see a way of generating an exception from this >> condition. >> >> Any help appreciated. >> > > You get a machine check exception. > > It's pretty obvious then :) > Using a 2.4.22 based kernel, as far as I can see a machine check should be trapped (its only allowed to cause a reset in the reboot code I think). Assuming I got it right and it really is trapped, how come I always get a reset:-(( Any pointers to the code that does setup for causing an exception (rather than reset) would be appreciated. -- Robin Gilks Senior Design Engineer Phone: (+64)(3) 357 1569 Tait Electronics Fax : (+64)(3) 359 4632 PO Box 1645 Christchurch Email : robin.gilks@tait.co.nz New Zealand ======================================================================= This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. =======================================================================