dogdark Posted November 25, 2020 Share Posted November 25, 2020 Hello, I'm with versión 3.6 donwloaded from DIS6502 download | SourceForge.net it does not work to retrieve the modified listing in wrk again. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted December 11, 2020 Share Posted December 11, 2020 @JAC! what is the output format for dis6502? What can I use to re-assemble? I want to use this to modify and extend a game for #FujiNet. -Thom Quote Link to comment Share on other sites More sharing options...
+JAC! Posted December 11, 2020 Author Share Posted December 11, 2020 5 hours ago, tschak909 said: @JAC! what is the output format for dis6502? What can I use to re-assemble? I want to use this to modify and extend a game for #FujiNet. -Thom Hi Thom. The output format is configurable and there are several presets named "profiles" included for MADS and other assemblers. You can change and tweak the output format at any time and export the listing again. 2 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted December 12, 2020 Share Posted December 12, 2020 I've tried the mads and ca65 profiles. In both cases, the output contains a "D:" devicespec (WTF?!) and neither produce workable binaries. ctf.zip Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 2, 2021 Share Posted January 2, 2021 I've managed to make it assemble in mads, but the output is both different and crashes on load. ARGH. I need something stable to start from! -Thom Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 2, 2021 Share Posted January 2, 2021 @JAC! what toolchain are you using with this? Each of the profiles have weird inconsistencies in them, e.g. the MADS profile lacks dots for the BYTE/WORD/etc directives, which I will correct and push up for a pull request. But I am really confused as to why, even if I am assembling exactly the same code, why am I not getting the same binary back (much less one that actually runs) -Thom Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 2, 2021 Share Posted January 2, 2021 With the latest (3.6) I've been able to get something that assembles in MADS with the default profile. The binaries are very different (and the new binary is two bytes shorter)... ctf-20210102.zip Quote Link to comment Share on other sites More sharing options...
baktra Posted January 2, 2021 Share Posted January 2, 2021 1 hour ago, tschak909 said: @JAC! what toolchain are you using with this? Each of the profiles have weird inconsistencies in them, e.g. the MADS profile lacks dots for the BYTE/WORD/etc directives, which I will correct and push up for a pull request. But I am really confused as to why, even if I am assembling exactly the same code, why am I not getting the same binary back (much less one that actually runs) Best to do binary diff and find a mismatch. I am thinking of creating a cross platform diff utility for xex files, but perhaps it already exists. Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 2, 2021 Share Posted January 2, 2021 cmp output. https://gist.github.com/tschak909/26fe26a032a903d4c2f20f130c47db46 -Thom Quote Link to comment Share on other sites More sharing options...
+DjayBee Posted January 3, 2021 Share Posted January 3, 2021 (edited) Two zero page addresses are accessed with 16-bit addresses by CTF which is optimized away by MADS. 1st one: L55AC dec L0000 .byte $00 cpy.a L00CE ; add .a to mnemonic .byte $00 L55B3 cpy L0085 2nd one: sta LB6A2,Y cpy.a L00F3 ; again add .a .byte $F3 L5B4F jsr L0820 Btw.: Your cmp output did not help because you cannot really "see" anything usefol from it. For binary diffs I use "Beyond Compare" which unfortunately is not free. It costs US$ 30 at least. Then you immediately see that all different bytes differ by a value of 2 - because your binary is two bytes shorter. And by scrolling down, you can also spot the two gaps with the missing data. A free utility is WinMerge, but it only works well with text files. Therefore you need to convert the binary into a hexdump; and to receive useful results it may only contain data bytes (and no address info which usually is at the beginning of every hexdump line). Edited January 3, 2021 by DjayBee added tool info 2 Quote Link to comment Share on other sites More sharing options...
tschak909 Posted January 3, 2021 Share Posted January 3, 2021 That did it! wow. Would never have caught that! I wonder if the non-zp compares were to intentionally add an additional cycle? -Thom Quote Link to comment Share on other sites More sharing options...
tsom Posted January 4, 2021 Share Posted January 4, 2021 I've been going through the disassembly, using DIS6502, and marking up the data sections as best as I can. I believe that "odd" section referenced above is just some data table. it's referenced in other parts of the code. Assigning the "byte" type to that section, seems to straighten it out: There's definitely all kinds of weirdness going on in this code. Setting up the display list uses several subroutines, just to put the right values into memory, instead of just defining it inline, for example. 1 Quote Link to comment Share on other sites More sharing options...
+DjayBee Posted January 4, 2021 Share Posted January 4, 2021 (edited) 16 minutes ago, tsom said: I believe that "odd" section referenced above is just some data table. I think, you are right. The only reference to this label is an LDA L55AC,Y 16 minutes ago, tsom said: Setting up the display list uses several subroutines Could this be because it is mirrored from top to bottom to save RAM and CPU? Means the top and bottom point to identical memory, and also the center part. I believe to have read somewhere about this. Edited January 4, 2021 by DjayBee Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted December 3, 2021 Share Posted December 3, 2021 Hello Peter and Eric, Is there any updates comming to dis6502? Gr. Marco Quote Link to comment Share on other sites More sharing options...
+JAC! Posted December 12, 2021 Author Share Posted December 12, 2021 On 12/3/2021 at 5:56 AM, marcokitt2000 said: Hello Peter and Eric, Is there any updates comming to dis6502? Gr. Marco Hello Marco. Sorry nothing new here. Visiting Fujiama and SillyVenture parties was the only Atari related thing my job allowed me to do this year. Hard to believe one year has already passed... Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted December 12, 2021 Share Posted December 12, 2021 36 minutes ago, JAC! said: Hello Marco. Sorry nothing new here. Visiting Fujiama and SillyVenture parties was the only Atari related thing my job allowed me to do this year. Hard to believe one year has already passed... Hello Peter, Thanks for the info i saw that has for 2 months make some opdates on sourceforge. Thats why i ask if there some updates. But take the time you needed iam now in 3d printing. All other atari things is now low level. Gr. Marco Quote Link to comment Share on other sites More sharing options...
+JAC! Posted February 15, 2022 Author Share Posted February 15, 2022 Finally a sign of life from project. Over 60 commits took place meanwhile. Still most of the work is under the hood, yet I feel this is worth sharing. The following may seen simple, but it was a long hard way from DOS plain C with pointers and fixed array sizes everywhere and logic interwoven with WIN32 API calls and UI parts .. to the code without fixed limits (number of segments, size of labels, ..) , without char pointers and instead with standard libararies and the lasted C++ 20 features (type inference, bounds checking). But what does that mean?? This means I can now finally write tests for all the essential parts and run them automatically, instead of clicking though the UI. This will bring back the confidence in that all the changes have the correct results, simplify tracing and fixing bugs and it will help make the project more and more stable over time. 6 Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted February 15, 2022 Share Posted February 15, 2022 Hello Peter, Thanks for all the good atari programming and thanks for do this project. Dis6502 can be a very easy tool to handel all atari 6502 machine languages to dissassembler it to a source asm code. To learn from it how it is build up or update the code make it smaller faster etc or debugging. Is there a windows test version yet? Gr. Marco Quote Link to comment Share on other sites More sharing options...
+JAC! Posted February 15, 2022 Author Share Posted February 15, 2022 18 hours ago, marcokitt2000 said: Hello Peter, Is there a windows test version yet? Gr. Marco Hello Marco. Today I've managed to fix the bug when reading old workspaces, I was able to load a large example and click around. The new daily is uploaded to https:/www.wudsn.com/productions/windows/dis6502/dis6502.zip . If you find something, please send a PM. 1 Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted February 16, 2022 Share Posted February 16, 2022 15 hours ago, JAC! said: Hello Marco. Today I've managed to fix the bug when reading old workspaces, I was able to load a large example and click around. The new daily is uploaded to https:/www.wudsn.com/productions/windows/dis6502/dis6502.zip . If you find something, please send a PM. Thnxxx Peter, I will test it soon i am busy with a 3d printer and learning playing on digi piano. Gr. Marco Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted February 17, 2022 Share Posted February 17, 2022 On 2/15/2022 at 11:52 PM, JAC! said: Hello Marco. Today I've managed to fix the bug when reading old workspaces, I was able to load a large example and click around. The new daily is uploaded to https:/www.wudsn.com/productions/windows/dis6502/dis6502.zip . If you find something, please send a PM. Hello Peter, I download the latest 16 feb round 1.11am from your web site. When i use file open or add image file ex ... from atr image and select dos 2.5 file it doesn work. doesnt load file and dissassembed not. Greatings Marco Quote Link to comment Share on other sites More sharing options...
+JAC! Posted February 20, 2022 Author Share Posted February 20, 2022 On 2/17/2022 at 10:04 PM, marcokitt2000 said: I download the latest 16 feb round 1.11am from your web site. When i use file open or add image file ex ... from atr image and select dos 2.5 file it doesn work. doesnt load file and dissassembed not. Haha, thanks for pointing me to the "box of pandora"... the code for handling ATR files and DOS 2.5 file systems. I had never really used that (only tested .XEX/.BIN) and ended up reworking it completely now. It is now complemented with a set of unit tests that will test 8.3 filename conversion, read 3 reference ATRs, compare the directories, compile the file sizes and contents with the reference content. So in case there anything still does not work, it can now be found quickly. Also all file related dialogs require much less code now. https://sourceforge.net/p/dis6502/git/ci/master/tree/src/systems/atari800/AtariDiskImageTest.cpp Daily is updated. Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted February 20, 2022 Share Posted February 20, 2022 4 hours ago, JAC! said: Haha, thanks for pointing me to the "box of pandora"... the code for handling ATR files and DOS 2.5 file systems. I had never really used that (only tested .XEX/.BIN) and ended up reworking it completely now. It is now complemented with a set of unit tests that will test 8.3 filename conversion, read 3 reference ATRs, compare the directories, compile the file sizes and contents with the reference content. So in case there anything still does not work, it can now be found quickly. Also all file related dialogs require much less code now. https://sourceforge.net/p/dis6502/git/ci/master/tree/src/systems/atari800/AtariDiskImageTest.cpp Daily is updated. Thnxxx i will test it later. Gr. Marco Quote Link to comment Share on other sites More sharing options...
marcokitt2000 Posted February 20, 2022 Share Posted February 20, 2022 (edited) 7 hours ago, JAC! said: Haha, thanks for pointing me to the "box of pandora"... the code for handling ATR files and DOS 2.5 file systems. I had never really used that (only tested .XEX/.BIN) and ended up reworking it completely now. It is now complemented with a set of unit tests that will test 8.3 filename conversion, read 3 reference ATRs, compare the directories, compile the file sizes and contents with the reference content. So in case there anything still does not work, it can now be found quickly. Also all file related dialogs require much less code now. https://sourceforge.net/p/dis6502/git/ci/master/tree/src/systems/atari800/AtariDiskImageTest.cpp Daily is updated. Ok i test it with a atr from me not working. see foto error. Gr. Marco atari utilities A.ATR Edited February 20, 2022 by marcokitt2000 atr file insert first file dos 2.5 works dos 2.0 not etc Quote Link to comment Share on other sites More sharing options...
+JAC! Posted February 22, 2022 Author Share Posted February 22, 2022 File handling of the input stream and the pasers for reading XEX and other file types has been revised. Now, instead of simply returning "false" and a generic error message like "is corrupted or contains more then 4096 segments", you now get a specific error message for every error situation. The texts are not yet great, but there is a different text not for every error which should already be helpful. With this instrumentation you can see that in the sample file given above there is a file with broken DOS file links (corrupted file) and one which is valid file, but not a valid XEX file with and $FFFF header. The last file loaded was OK, so no error message. Daily is updated. UPDATE: Name of the inner EXE and number sectors are now also output in the status message and the message texts have been revised already. Note that adding freely selected sectors does not yet work. That's next. 1 Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
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.