Maybe some people here knew about Boriel's zxbasic compiler - it's a very efficient cross-compiler coded in Python (converts ansi-basic code similar to zx-spectrum, with possibility of inline-assembly code and includes), and natively supporting zx-spectrum machines.

Since the start of the development of this cross-compiler, targeting other machines else merely zx-spectrum were in mind of Boriel, and for example, he thought on start the amstrad-cpc version of it as well. Following this viewpoint, the possibility of this (awesome, imho) cross-compiler is virtually unlimited, depending on how far people can help on making it targeting different machines. I started this wikipage for helping them: http://www.boriel.com/wiki/en/index.php/ZX_BASIC:Other_architectures

The amazing part of this cross-compiler is it is really efficient and easy to use - for example, i could submit 4 entries to csscgc2011, and one now to the csscgc2012 in a relatively short time, and i really wished to be able to do the same to the msxdev, for example - and as i saw this Boriel's zxbasic compiler is becoming really popular on the zx-spectrum side, no doubt that this can be the same on msx.

the terminal doesn't provide any further information when compiling as default (i didn't try any verbose option), but the .asm stage resulted from the compiling (before the binary compiling from this .asm) is at http://pastebin.com/XCvYPC3a - i got this .asm adding a '-A' option at the zxb.py line, from that .sh script - it defaultly sets the org at 0x8000 (maybe in that case i needed to set org ('-S' option) at 0x8004 because the first 4 bytes of the .rom file? (hex:41 42 04 80) - but i didn't see any jr or jp there, i tried that and didn't work as well ) - i don't know is if Boriel's zxbasic compiler is really putting zxspectrum-based "garbage" there, or if i did something stupidly wrong in the process... :| - adding also the resulting code.rom from my .sh script, and the code.bin generated from the compiler

(btw, as the previous library snippets i added at http://www.boriel.com/wiki/en/index.php/ZX_BASIC:MSX which i used only two of them there - i tried to improve them a bit, and i were about to test them after this first step were successful - any more improvements and help are very welcome! )

That's right, nitro.The default ORG is 8000h (32768) and there's no JP to that zone.However, if you're developing a ROM, perhaps you can use ORG 0 ??If so, try compiling with:--org=0

And see if it works?

hi Boriel! btw, this is probably the best and most active forum about msx retro development you may find online! be welcome here! i learned a lot here!

btw, i tried also with this --org=0 , and nothing

afaik, msx cartridge roms works in a bit different way than usual on other 8bit computers - msx .rom files works starting on 0x8000 or 0x4000 (i think most konami 16k games, like Antarctic Adventure and Road Fighter, starts at 0x4000?) - i think this is because the whole 64kb are sliced into 4 16kb switchable slots and subslots (and not talking yet about paged memory) - 0x0000 is where are all the bios address calls, like those for doing cls, changing screenmodes, poking/peeking video memory (z80 accesses it by i/o only), etc. - 0x0000 is the adress starting in the boot, and checks if there are any rom cartridges connected, and because of this, i think i don't know any msx cartridge that starts at 0x0000 (because bios) or 0xC000 (because system variables starting around 0xF000)

DEFB "AB" ; expansion ROM headerDEFW initcode ; start of the init code, 0 if no initcodeDEFW callstat; pointer to CALL statement handler, 0 if no such handlerDEFW device; pointer to expansion device handler, 0 if no such handlerDEFW basic ; pointer to the start of a tokenized basicprogram, 0 if no basicprogramDEFS 6,0 ; room reserved for future extensions

If your header is hex 41 42 04 80, setting the .org code at 0x0804 should works because BIOS transfers control to initcode and ignores other fields. (Although to complain standard de header must be 16 bytes long)

DEFB "AB" ; expansion ROM headerDEFW initcode ; start of the init code, 0 if no initcodeDEFW callstat; pointer to CALL statement handler, 0 if no such handlerDEFW device; pointer to expansion device handler, 0 if no such handlerDEFW basic ; pointer to the start of a tokenized basicprogram, 0 if no basicprogramDEFS 6,0 ; room reserved for future extensions

If your header is hex 41 42 04 80, setting the .org code at 0x0804 should works because BIOS transfers control to initcode and ignores other fields. (Although to complain standard de header must be 16 bytes long)

i confess that i couldn't find easily information about rom headers - long time i don't access them, and forgot about - what i did were opening some .rom from msxdev entries (maybe mostly compiled from asmsx from Robsy?), and i think i found no '00 00 00' after the first 4 bytes, even those 6 bytes later as '00', only text information about name game and (random?) id code - so, i assumed the code could start on 0x8004 without further problems, but your idea on following '41 42 10 80 00 00 00 00 00 00 00 00 00 00 00 00' for following compatibility norms seems to be not bad at all... (unless the game, demo, or whatever is so shrinked that each byte counts...)

btw, Boriel, i'm seeing one situation about compiling to rom files - variables and constants must be allocated in different memory areas - contants for rom, and variables for ram - but i don't know how to do it, or if is this possible on zxbasic compiler

btw, Boriel, i'm seeing one situation about compiling to rom files - variables and constants must be allocated in different memory areas - contants for rom, and variables for ram - but i don't know how to do it, or if is this possible on zxbasic compiler

You can use DIM..AT <address> to specify a variable to be allocated at a given address. Hope that is what you're looking for.

btw, everyone, Haroldo O.P., somehow active on the sega-mastersystem retro development community, started to fork successfully zxbasic-compiler to sms ( http://www.smspower.org/forums/viewtopic.php?p=72146 ) - i hope this information and initiative can be helpful on the msx version - any help on the msx version is very welcome and considerable!