Machine Code Monitor?
Florian Bantner (8397) 3 posts |
Hi all, I recently came to like machine code monitors on the c64. Something like “Final Cartridge III” or “Action Replay V”. There you can use commands like But since what I really want to do is play around with arm assembly and not 6510 I managed to compile and run rpcemu with riscos 5 for my linux box. But now: Is there some kind of machine code monitor for riscos? Thanks |
Rick Murray (539) 13425 posts |
If you want to just play around with ARM assembly yourself, then you can do this from a command line and/or from BASIC and there’s a module called Debugger that will help. When you’re in the command line, enter |
Rick Murray (539) 13425 posts |
To assemble literal mnemonics (like “MOV R0, #0”), you’ll need to use the BASIC assembler. Debugger doesn’t do that. |
Florian Bantner (8397) 3 posts |
Thank you for the quick answer. Can you recommend some manual for those commands? Oh and … are there some extensions (?) to get a command history? |
Fred Graute (114) 629 posts |
Now there’s a blast from the past. I should still have a copy of the Final Cartridge floating around here somewhere (not sure if it’s a v3 though). However I used its built-in machine code monitor only in case of emergency. I preferred to use my own machine code monitor, based on a type-in listing (called RatMon IIRC) in a German magazine but extended in numerous ways. On RISC OS, as Rick has pointed out, you can use the Debugger module to inspect memory contents and BASIC to assemble instructions. In addition you can use the Zap or StrongED editor to look at assembly code. Both programs allow you to load executable code for inspection, you can also extract application and module code from memory.
I don’t think there is one. Use Note though that the information provided by *Help and the StarCmds manual is rather terse so taking it in will require a bit of effort.
Yes, you’ll need to install the “LineEditor module” (http://old-www.moreofthesa.me.uk/progs.utils.html#lineeditor) as RISC OS itself doesn’t provide a command history. The command history will work on the command line as well as in a TaskWindow. |
Stuart Painting (5389) 684 posts |
The URL leads you to a download on another site (zap.tartarus.org) which gives 404. Apparently it’s supplied with Zap, which appears to be the only way of getting it now. A quick glance at the old Zap repository on GitHub didn’t show any sign of it, but perhaps Rick Murray knows more… |
Rick Murray (539) 13425 posts |
http://zap.tartarus.org/ftp/pub/ds/ There’s a bug – see https://www.riscosopen.org/forum/forums/11/topics/3454 |
Steve Pampling (1551) 7957 posts |
Given the information Jon Abbott gave I’m surprised you’ve not done a version with patched/fixed source and included it in your “Ultimate” release. |
Rick Murray (539) 13425 posts |
Me too, but I’m not at the computer to check what version is there. Hmm, do I even have the LineEditor source here? I don’t have any recollection of it 1 which might be why… 1 Or what I had for dinner yesterday. |
Steve Pampling (1551) 7957 posts |
Hmmm? Let’s see, what exactly is the link directly below the link for 2.76d on the page you linked to? Ah, yes = http://zap.tartarus.org/ftp/pub/ds/LineEditor_2.76d_src.zip That might just be what you were looking for.
Now that’s a worry. I have a blank period from when Dad died. People say that although I was there, I wasn’t, if you follow me. I think you need to talk to someone. You could take that as a cue to do long items on Aldershot, but I think a human might be better. |
Rick Murray (539) 13425 posts |
I meant here, not there. ;-) The rest – taken you know where… https://www.riscosopen.org/forum/forums/12/topics/15077 |
John WILLIAMS (8368) 485 posts |
Steve – I sent you an e-mail, but perhaps DSL.pipex doesn’t exist any more? petit.four at free fr if you will. |
Steve Pampling (1551) 7957 posts |
Pipex were taken over (service standard went down, that was taken over the service quality went down, that was taken over… Mail from current active address in the pipes |
Steve Pampling (1551) 7957 posts |
You do realise that if you released a fixed version in a Zap archive I’d have to download Zap :) |
Rick Murray (539) 13425 posts |
This is UNTESTED (LineEditor reports that it is ‘in use’ and I don’t want to reboot). It’s a binary hack to push R4 into the list of preserved registers around the ReadLine gubbins, soi it shouldn’t mess up with ReadLine32. http://heyrick.ddns.net/files/led276e.zip If it works okay, I can put it into the next Zap distro (yeah, you’re the guinea pig, until I next reboot). |
Michael Grunditz (467) 531 posts |
Saved my day! AND some OT: I also use your SerialUSB module that you posted in the forums some years(?) ago. I use it with a ttl<→usb adapter that I have connected to the RockPro board. It does it work well , apart from not behaving when unplugged and replugged. |
Steve Pampling (1551) 7957 posts |
I was curious so I read more of the bug thread and linked items, which brought up this post in which the bug is identified as being in RO4.36 (possibly carried into the release as 6) however, even if the bug is not in RO5 but rather in 4.39 and that isn’t open source there isn’t much anyone here can do to fix it. Not to say there aren’t similar bugs that do affect RO5 users of course. |