---- START NEW MESSAGE --- Received: from cherry.ease.lsoft.com [209.119.0.109] by dpmail10.doteasy.com with ESMTP (SMTPD32-8.05) id A6E61D2300E0; Wed, 28 Jan 2004 14:25:42 -0800 Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <21.00CC190A@cherry.ease.lsoft.com>; Wed, 28 Jan 2004 17:25:29 -0500 Received: from MITVMA.MIT.EDU by MITVMA.MIT.EDU (LISTSERV-TCP/IP release 1.8e) with spool id 8815 for PICLIST@MITVMA.MIT.EDU; Wed, 28 Jan 2004 17:25:23 -0500 Received: from MITVMA (NJE origin SMTP@MITVMA) by MITVMA.MIT.EDU (LMail V1.2d/1.8d) with BSMTP id 6798; Wed, 28 Jan 2004 17:23:32 -0500 Received: from *unknown [210.8.51.66] by mitvma.mit.edu (IBM VM SMTP Level 430) via TCP with ESMTP ; Wed, 28 Jan 2004 17:23:31 EST X-Warning: mitvma.mit.edu: Host *unknown claimed to be whitlam.corp.gli.com.au Received: by whitlam.corp.gli.com.au with Internet Mail Service (5.5.2653.19) id <4T7L19M1>; Thu, 29 Jan 2004 09:26:15 +1100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Message-ID: <2193429B07D9914D97216EBBAA6AB8BD1A049F@whitlam.corp.gli.com.au> Date: Thu, 29 Jan 2004 09:26:14 +1100 Reply-To: pic microcontroller discussion list Sender: pic microcontroller discussion list From: Liam O'Hagan Subject: Re: [PIC:] Disassemblers To: PICLIST@MITVMA.MIT.EDU Precedence: list X-RCPT-TO: Status: U X-UIDL: 371856166 Well that message lost its subject line somewhere along the way... The reason I ask, is that we (as a 3rd party) test certain devices which handle large quantities of money, and someone has recently discovered a way to remove more money from these devices that he or she is entitled to... This has generated quite a bit of interest and investigation, and along the way we noted that the binary image on the Z86 micro installed in these devices was different to that which was meant to be there, possibly facilitating this unauthorised cash removal. As such we needed to find out what the binary did that the official binary didn't. Hence the need for a disassembler... I have a working one now, and I'm trying to deduce what the code is doing. Sorry to be so roundabout in my description, by necessity there are a lot of security concerns with an issue like this. > -----Original Message----- > From: Liam O'Hagan [SMTP:liam@GLI.COM.AU] > Sent: Wednesday, January 28, 2004 10:32 AM > To: PICLIST@MITVMA.MIT.EDU > Subject: [PIC:] > > Hi Everyone, > > This is sort of pic related sort or EE, but anyway... > > Does anyone remember the tool that would take a PIC hex file and produce > ASM > from it? > > Does anyone know if there's a similar tool for Zilog Z86 devices?? > > It's a shot in the dark I know... > > -- > http://www.piclist.com hint: PICList Posts must start with ONE topic: > [PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics .