Hello Ville, * On Thu, Mar 16, 2017 at 07:24:08PM +0200 Ville Laustela wrote: > >> Can you please try if you can dump the ROM and send it to me? > >> > >> $ cbmctrl download 8 0xc000 0x4000 rom2031.dump > > One more note… if I try running cbmctrl detect several times, I get different replies: > > 8: *unknown*, footprint=<DOB@> > 8: *unknown*, footprint=<C@BL> > 8: *unknown*, footprint=<CBCC> > Then it stops replying and drive led starts blinking, and in reply to cbmctrl status 8 it gives "syntax error,00,00” (am I missing characters there?) Ok, I see, you have a very general communication problem, that's the real problem! BTW, I interpreted the footprint completely wrong. It checks $FF40, but also $FFFE if $FF40 has the contents $AA, $AA, like in the case of early 1541, the 1540 and the 2031. I missed that. And it does not output the footprint in hex, but in some weird form. > I tried dumping the ROM (under OS X) but all I got is ".,A transfer > error occurred!” and a zero-size output. Tried it a couple of times. > Best I could get was 512 bytes (attached) but it looked like trash. That's not trash, that's the exact output of first 512 byte of the 901484-03 ROM. It is just missing the remaing 7.5 KB. ;) But: The "A transfer error occurred!" tells me that you have a very big communication problem. Do you own an IEC (serial) based drive, so that we can find out if the problem is on the "CBM side" (IEEE bus), or on the "PC side" (USB, PC)? Regards, Spiro. -- Spiro R. Trikaliotis http://www.trikaliotis.net/ Message was sent through the cbm-hackers mailing listReceived on 2017-03-17 11:00:03
Archive generated by hypermail 2.2.0.