E474 Posted May 3, 2022 Share Posted May 3, 2022 Hi, I'm a bit behind with my firmware efforts, I think @manterolais now in the lead! The DW START pair at the end of the sources specifies the 6502 power up/ reset vector(s) at the very top of memory for the firmware, so I don't think it should be removed. I think the problem is that the object file produced by the Macro Assembler would have gotten loaded into the 8-bits memory, then written out to an EPROM directly - maybe this is an undocumented step? The LOC and ORG directives allow assembling code with a given base address, but stored at another address (if I recall correctly). I only found one file had extra characters at the end, but it was enough to cause problems. Maybe this is an issue with the archive. Quote Link to comment Share on other sites More sharing options...
manterola Posted May 3, 2022 Author Share Posted May 3, 2022 Yep. I needed to move the last four bytes (Start address twice) to the end of the 8kb by inserting zeros right after the DTI version and copyright text stuff (stamp?). Then I compared the files and the only difference was an FF instead 00. So, we have the sources working. 2 Quote Link to comment Share on other sites More sharing options...
E474 Posted May 3, 2022 Share Posted May 3, 2022 That's great news! There's an option in ATASM that will build a pure binary (no headers), but I'm not sure this can be done with AMA. On the other hand, writing a simple program to consolidate all the segments into 1 block should be easy, but for a ROM I think you should only have 2 segments in the object file, e.g. block of code plus start address. Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted May 3, 2022 Share Posted May 3, 2022 Has anyone thought of converting the source for being used in mads or ca65... I only mention this since we have the OS sources compilable in CA65 and the 1050 SRC in mads. Making changes and burning on the TL866 is much faster that way Quote Link to comment Share on other sites More sharing options...
HiassofT Posted May 3, 2022 Share Posted May 3, 2022 37 minutes ago, kheller2 said: Has anyone thought of converting the source for being used in mads or ca65... Not for mads or ca65 but I did that for atasm a while ago. I've attached my sources, see Makefile for atasm command line flags used to build (the sources can both build 3.10 and 3.00). so long, Hias duplicator-3.00-3.10-atasm.zip Quote Link to comment Share on other sites More sharing options...
+kheller2 Posted May 3, 2022 Share Posted May 3, 2022 42 minutes ago, HiassofT said: Not for mads or ca65 but I did that for atasm a while ago. I've attached my sources, see Makefile for atasm command line flags used to build (the sources can both build 3.10 and 3.00). so long, Hias duplicator-3.00-3.10-atasm.zip 30.51 kB · 2 downloads Thank you! That works great. Quote Link to comment Share on other sites More sharing options...
E474 Posted May 3, 2022 Share Posted May 3, 2022 Well @manterola, I believe that counts as a win for @HiassofT. Quote Link to comment Share on other sites More sharing options...
E474 Posted May 3, 2022 Share Posted May 3, 2022 GitHub repo here, though I changed the file extensions from ASM to asm so it plays nice with Eclipse/WUDSN: https://github.com/e474/DD-1050-Firmware Quote Link to comment Share on other sites More sharing options...
manterola Posted May 3, 2022 Author Share Posted May 3, 2022 5 hours ago, HiassofT said: Not for mads or ca65 but I did that for atasm a while ago. I've attached my sources, see Makefile for atasm command line flags used to build (the sources can both build 3.10 and 3.00). so long, Hias duplicator-3.00-3.10-atasm.zip 30.51 kB · 6 downloads Fantastic! The sources assembled at the first try, without any problem. Much appreciated! Quote Link to comment Share on other sites More sharing options...
E474 Posted May 9, 2022 Share Posted May 9, 2022 Made a new repo for the firmware here, as it actually worked fine with .ASM extensions: https://github.com/e474/Disk-Duplicator-1050-Firmware Quote Link to comment Share on other sites More sharing options...
E474 Posted May 10, 2022 Share Posted May 10, 2022 HI, Can anyone with a Duplicator 1050 and also a US Doubler try/test the attached Duplicator 1050 firmware? Version upped to 3.20 to avoid confusion. The (fixed?) bug is described by @ijor in: @manterola has kindly tested the 3.20 firmware, and it seems to work fine, but he doesn't have a US Doubler to test with for this bug fix. This should also work for MegaSpeedy owners (though I have no idea how to update the firmware for the Duplicator 1050 slot on a MegaSpeedy). Possibly any clones of the Duplicator 1050 too, but obviously a little less certain of that. Sources are at: https://github.com/e474/Disk-Duplicator-1050-Firmware duplicator-3.20.rom 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.