Ok, I found what was wrong with DAMSx. The problem was between the chair and the computer.... I just declared vectors in place of RST entries at beginning of the symbol file. So DAMSx interprets the data at address 0x0000 as a jump to address 0x06B9... In fact, RST are not vectors for the 8085, they are entry-points, and the symbol must be different in the table for DASMx. I just updated my symbol table and now, the EPROM file is disassembled correctly. Benoit --- In korgpolyex@yahoogroups.com, "benoitdmx" <benoit@...> wrote: > > Ok thanks Mike > > It means that my 8085 disassembler is... humm... (it reports this sequence as unknown instruction... like most of the RST vectors entries). I did not check in the datasheet to be honnest, just trusted the software > > I will try another disassembler then (for those being interested : the problem I saw comes from DASMx. It worked perfectly to disassemble the 6303 code from my DSS1... but clearly not the case for the 8085) > > Is there a 8085 disassembler you would recommend Mike ? > > Benoit > > > --- In korgpolyex@yahoogroups.com, Michael Hawkins <korgpolyex800@> wrote: > > > > It is not corrupt. > > > > 06 B9 is mvi b, 0B9h > > > > > > Mike > > > > > > > > ________________________________ > > From: benoitdmx <benoit@> > > To: korgpolyex@yahoogroups.com > > Sent: Wednesday, June 26, 2013 8:35 AM > > Subject: [korgpolyex] EX800 EPROM file corrupted in Files section ? > > > > > > > > Â > > Hello guys, > > > > I started some investigations on the EX800 firmware, and I tried to disassemble the binary file located in the Files section (EX800 firmware) > > > > As far as I can see, the file is corrupted : the first bytes are 06 B9 for address 0x0000 (the reset vector). And there are no instructions with 0x06 prefix in the 8085. > > > > I will try to compare the file with the EPROM content in my EX800, but if somebody already made another dump and can compare it too... > > > > Benoit > > >
Message
Re: EX800 EPROM file corrupted in Files section ?
2013-06-27 by benoitdmx
Attachments
- No local attachments were found for this message.