Jump to content

RetroCoder

New Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

20 Excellent

About RetroCoder

  • Rank
    Space Invader

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Does the Nuc+ have a cartridge port or can it be added?
  2. Would love to see the code for this
  3. There is a Visual Studio Code extension that combines ATasm with Altirra. Allows for source level debugging and breakpoints. look for Atasm-altirra-bridge in VSCode extensions. I would love for someone to compile the latest version of ATasm on a mac and send me the executable so that I can put it into the extension. Currently it ships with Linux and windows support.
  4. No his source it still on sourceforge. I updated the source code to - add labels with a terminating : - Add an .align statement - fixed some of the reported bugs Some of the changes were merged into 1.09, not the latest yet. The atasm-altirra-bridge vscode extension that I wrote includes V1.11
  5. Atasm has been updated a couple times over the past years. Sitting at V1.11 now. Here is the source to BASIC and OS versions atarirom_2000_12_12.zip
  6. Some of my ATasm fixed have already been merged in. I want to fix a couple more of the reported problems and the make a merge request. For now the fixes are going into my GitHub repo.
  7. Version 1.2.0 of the extension has been released. - Better integration of the ATasm assembler - Fixed a bug that reset the path to be always the Windows path of the atasm - Build Task now also works when 'atasm-build.json' is the currently open file - Added configuration options to allow for another emulator to be used - Set the ownEmulator setting and supply the path and arguments - The extension will not add any parameters. You will need to supply them in the correct format. With this release you can specify a different emulator. The readme had some instructions. Should now be able to run any emulator. You just have to supply the arguments I'll have to find a Mac with a dev environment on it to get atasm v1.11 compiled, then I can have the extension Windows/Linux/MacOS compatible Happy debugging
  8. Thank you for testing the extension on MacOS. I don't have a mac to try it on, but will make a plane to get the latest version of ATasm into the extension. At for it using the linux path, yes that is a bug. I'll fix it and release a new version asap.
  9. I added a Linux version of ATasm 1.11 in version 1.1.0 of the extension. Should at least be able to assemble your code under Linux now. I tried running Altirra under wine under WSL2 on Win10 (hmm a bit much there) and did not get it to work, but it should work running on a Linux machine
  10. The code is available on Github so a pull request would be great. Let get this cross-platform
  11. I started back into 6502 assembler after a good 30+ years and wanted to use the tools I'm familiar with. That is VS Code as the editor. ATasm was the assembler of choice and Altirra the emulator. Now getting back into learning some 6502 had me dumping hex codes on the screen until I found out that Altirra has a nice debugger. Still I had no easy way of finding my code in the disassembly view, so I was padding the points of interest with nops etc. There had to be a better way. I found some topics here talking about debugging options in Altirra but there was no guide or documentation (none that I could find). At least the source code for Altirra is available and after getting it to compile and running, I managed to figure out the file format to get source level debugging to work. I modified ATasm to generate the required symbol and list files so that Altirra could load them. Then I wrote a VSCode extension to bring it all together. Now I can write my asm code, set a breakpoint in VSCode and launch the debugger and have it stop where I want it. The extension is called Atasm Altirra Bridge https://marketplace.visualstudio.com/items?itemName=cerebus.atasm-altirra-bridge
  12. For those interested in debugging asm code in Altirra. I've created a Visual Studio code extension that lets you use ATasm to assemble your code and Altirra to run and debug it. The extension allows you to use source level debugging with breakpoints being set in your assembler code https://marketplace.visualstudio.com/items?itemName=cerebus.atasm-altirra-bridge
  13. I've been playing with some code and using atasm to assemble it. Loading the code and using the Altirra debugger is ready easy, especially with the -l options to dump the labels to a file. As long as the labels file has the same base filename as the executable all is ok. The only thing missing from the joy was source level debugging; Altirra's documentation mentioned you had to use mads or xasm. But atasm is my tool of choice, so I pulled the source code and made the changes. If you assemble a file with the -l and -g options you will now get a .lst file that allows source level debugging under Altirra. Also added support for the ;##TRACE and ;##ASSERT diagnostics. If you assemble the above file with atasm 1.11 (https://github.com/CycoPH/atasm) and launch Altirra like this: Altirra.exe altirra.xex /debugcmd:.loadsym /debug you will see Altirra break into the debugger and showing you where the display list is located. Clicking Debug and selecting "Source file list ..." will give you altirra.asm as an option. Load it and you will have full source level debugging
  14. I've been working on atasm source a bit a fixed a couple of small bugs. The new 1.10 version at https://github.com/CycoPH/atasm was used to compile the attached test_opcodes.asm file and produce the test_opcodes.bin.4compare output. I ran that through a disassembler and checked each line and it looks correct. I would love to see others assemble the test_opcodes.asm file and check their results. We should be able to produce a general test case file. Even if the formats an capabilities of some assemblers are very different test_opcodes.asm test_opcodes.bin.4compare
×
×
  • Create New...