SjASM 0.4 beta 2

by wolf_ on 04-03-2008, 11:39
Topic: Software
Tags: Utilities
Languages:

Only days after we reported about SjASM 0.4 beta 1, XL2s have released SjASM 0.4 beta 2 for you to try. New in this version:

  • Fixed UPDATE command
  • Fixed jumps to numbered labels
  • Fixed INCBIN file length check
  • Added ERROR command
  • Added CODE! overlay code parts
  • Added more text to the manual

Relevant link: XL2s

Comments (8)

By ro

Guardian (4121)

ro's picture

06-03-2008, 11:32

I've always wondered. Would it not be super cool to have such PC environments working close with (any) MSX emulators?
So assembling a piece of code directly to emulator would instantly change the MSX state. Great for development! (realtime assembling)

now, THAT would make cross assembling go a step further.

By wolf_

Ambassador_ (9771)

wolf_'s picture

06-03-2008, 11:53

OpenMSX has a DirAsDisk feature which you can update outside the emulation. So, imagine you're assembling a .bin file with some xdev tool: all you do is output this file to that dir, and in the emulator you just bload"file.bin",r again. (in case you got back to basic). I tried this some months ago, it works!

By ro

Guardian (4121)

ro's picture

06-03-2008, 13:59

that's not what I was talking about, I was talking about REALTIME assembling. Poking direct in memory so to speak Wink

(And the DirAsDisk is not that flexible, IIRC. Updates of files are not realtime. but I could remember incorrectly...)

By wolf_

Ambassador_ (9771)

wolf_'s picture

06-03-2008, 14:37

huu, runtime poking into mem? That may work for tables, variables, but for actual code?

And as for the DirAsDisk thing: it works the way I wrote: startup with some DirAsDisk dir, e.g. c:\code, make a line in basic called bload"out.bin",r. then in the xdev assembler assemble your stuff as c:\code\out.bin, and next you only need to move your cursor in msx basic and press enter on that command! (or run it again in case you do 1bload"out.bin",r). At least it works like this in the OpenMSX build I have.. *perhaps* it didn't work in the latest official release, dunno.

By Manuel

Ascended (15765)

Manuel's picture

06-03-2008, 20:18

Wolf and ro: how Wolf describes it, is how it is working in our current development tree (since October 2007). This code was too late for the 0.6.3 release, so it will end up in the next stable release, together with other great stuff, like universal keyboard support.

So, keep an eye on that release and you can always ask us for a snapshot if you'd like to try things out earlier.

By sjoerd

Hero (593)

sjoerd's picture

09-03-2008, 16:31

It would be fun to be able to step through the source, instead of some disassembly. With some edit+continue option, like Ro suggested.
If it is possible with C++, it is also possible with Z80 ASM with emulator.

By Manuel

Ascended (15765)

Manuel's picture

09-03-2008, 17:16

The openMSX debugger has already symbol support which shows up in the disassembly. Same goes for blueMSX, IIRC. Not identical to what you want, but still Smile The difference with C++ is that the generated assembly from C++ code contains a lot of debugging information to help debuggers match information from source with binary.

By Pat

Expert (66)

Pat's picture

10-03-2008, 11:01

How about eclipse based plug-ins? Anyone working on this?