FUSION-C the C library for MSX (SDCC)

Good job Eric! I'm impressed.

I bought mine from Amazon with Free Shipping.

Sound very interesting because I never really programming in C ever.

Great job Eric.

@fr3nd "Fusion C is available for free at: www.repro-factory.com in the FUSION-C section."

Did you miss that part? It was a bit hidden in a little sentence at the bottom :).

Fusion-c library is provided with all source code (C and ASM source codes are include), also include a script to compile the library with new functions, or if you make changes in functions's sources code.
You can collaborate of course. If you have idea, new functions, bugs, let me know. All your ideas and new functions can be included in further release ... Share you work

@fr3nd : Yes, GitHub is great and I'm using it also. I've chosen to publish FUSION-C via Repro-factory, to keep an eye on its distribution, i'm just curious to know how many people will download it.
Anyway in the futur the library will be available on GitHub too...

Cool! Gotta try it out on Linux!

@wimple3 : with disk2rom utility (included in tools folders). Ok this is not suitable for 32K or 64K rom size but in most cases you can make a rom version of any floppy disk, and put it in a 512K or 1024K Cartridge.

OK, so this basically means the program cannot be used to make games for the MSDEV competition.

There is a guide online how to create a rom file from SDCC, several, here is one.
But Fusion-C probably has a few libraries using things specifically for DOS 1/2, also probably some CALLSLOT resolves. These need to be altered for a ROM project of course.

I think this is great, thanks Eric! :)

Great work Eric and Fernando!
Thanks!

>>¿How do you guys convert an MSX DOS program to a ROM version?

>> with disk2rom utility (included in tools folders). Ok this is not suitable for 32K or 64K rom size but in most cases you >>can make a rom version of any floppy disk, and put it in a 512K or 1024K Cartridge.

As far as my understanding arrives, you can't.
As MSX-DOS is in a ROM any you are trying to executing another ROM.
Both occupuies the same logic space. Thus, it is not possible.

SDCC with tools can produce a .COM file
But a COM file can not be executed in a ROM.

You can, it works very well.

How it works is the first 16K of the ROM is a diskROM, one which interfaces with the ROM mapper instead of a disk controller. The remainder of the ROM then contains a disk image, a ROM disk very similar to how a RAM disk works. The program is loaded in the computer's RAM memory exactly like a DOS game.

Downside is that it requires a 64K MSX, and that data needs to be loaded rather than accessing ROM banks directly. Upside is that you have the DOS environment with the full 64K of TPA RAM space available, rather than the first 32K to 48K occupied by ROM (BIOS + ROM data).

The large TPA is useful for any program, but especially for C programs I think. And it's easy to install a custom ISR and to use self-modifying or generated code, and on turboR it will run in fast internal memory. Lastly you can program for one environment and release both a downloadable disk and cartridge ROM version with little extra effort.

I received the book today, looks great!

Thanks
I also hope the developers will use FUSION-C, and the Library will evolve with the needs of the coders. Do not forget to share your work, so that everyone can enjoy, and thus make a futur version 2.0

I always wanted a good set of libraries and extensive documentation for developing C in MSX. I already ordered the book Combining FUSION-C with ASMLIB I think many interesting things can be achieved!

Got the book yesterday and I'm a bit disappointed. This is basically a reference guide, not a programmer's manual. Perhaps I was expecting too much. Lots of English mistakes too.

@ericb59 What I expected (and what I would have liked personnaly) is a bit more guidance on how to make sprites move, how to create tiles, basically how to create software on the MSX. The book is now only a reference for the libraries (which is good) and partly an introduction in C (which is also good). However, there is not much material that glues both together. Most examples in the second part are limited to the standard SCREEN 0. Which is not bad, you have to start at the beginning. But begin the book with a library reference talking about screen modes, sprites, sound, followed by a C introduction talking about pointers, variables, functions... without a connection between both sections. How to create sprites? Tiles? Music? This means there is still a lot left to explore and learn for people not used to work with the MSX. The book is IMHO probably too easy for someone who knows the MSX, but too difficult for beginners.

I do not understand what you 're meaning

Making sprites with Fusion-c is explained in the Book.
An you're right, this is not a guide for people who never tried to code something. This was not my purpose.

Would be nice to have a digital version of the book, take long time to ship to Brazil

I'm really happy to read such answer

Hi...

I just received my book. I'm already reading and configuring the system. good job!

I have just received my book too. Great work!

Somehow I got it running on my side.
After successful compilation always a new instance of openmsx ist started.

So I modified "compil.bat" that openmsx is only started once. (it is faster if rapidly change source code and compile again for testing

I found here:https://stackoverflow.com/questions/162291/how-to-check-if-a-process-is-running-via-a-batch-script a dos snippet

and modified "compil.bat" at the lower section to this:

:Emulator
SETLOCAL EnableExtensions
set EXE=openmsx.exe
FOR /F %%x IN ('tasklist /NH /FI "IMAGENAME eq %EXE%"') DO IF %%x == %EXE% goto FOUND
echo Not running
goto FIN
:FOUND
echo Running
goto end
:FIN
openMSX\openmsx.exe -machine Philips_NMS_8255 -ext msxdos2 -diska dsk\
:end

It is only allowed to do variable declarations at the beginning of scope block or function, so use something like:

void main(void) 
{
        int dk_V;

	PrintNumber(5); 
  	dk_v = 5;

And even better, as a good practice always initialize your variables with a value (be it f.e. either 0 or in your case 5);

After more than 220 downloaded Package since 5 months, the world wide's MSX community proved its interest in a complete easy language package usable on recent computers to program our good old MSX !

The new version 1.1 of FUSION-C is available.[/b]

Now more stability, less memory used in compiled programs, a lot BUGS fixed, and new features available.
Some functions have been fully reprogrammed to consume less memory and be faster.
The new functions now allow:
- Manage an MSX mouse
- Have a real time timer variable
- Decompress RLEWB data (Compressor include)
- Read and write data directly on disk's sectors
- Play Samples via a Covox module
- Manage an automatic interruption
- the new crt0 now initialize global variables.
and more...

FUSION-C 1.1 is always free, downloadable from www.repro-factory.com
The book FUSION-C Complete Journey has been updated and corrected, is still available on Amazon:
https://www.amazon.com/FUSION-C-MSX-Library-complete-journey/dp/1730828612/ref=sr_1_3

Code, play, publish!

Eric.

Ok, I've just got the new updated 1.1 book, downloaded and installed everything as per the book instructions.
Everything compiles (test.c) without issue in Sublime and the emulator kicks up.
I then get to the a:\ prompt and I type test and hit enter only to be presented with "ooooooooooooooo" instead of "Hello MSX World".
Have I not done something right, I've also tried compiling the console.c example and it just prints junk to the screen but works perfectly.

Any help would be appreciated.

This is the code

//
// Fusion-C
// My First Program in C
//
//#include
#include "fusion-c/header/msx_fusion.h"

void main(void)
{
//printf("Hello world!\n");
Print("Hello world!");
}

And this is the result

Screenshot

There is a separate thread for issues related to FUSION-C, so it's better to post your question over there

The new version of FUSION_C 1.2 is available.

What's up...
Fixes, optimizations, and new features, including MSX2 VDP features, Support of the V9990 and GR8NET TCPIP

- CheckBreak: Check Break sequence in MSX-DOS console

- PutCharHex: Pint Hex conversion of a char on console

- PrintHex: Print Hex conversion of an integer on console

- HMMM: Vram to Vram

- LMMC: Ram to Vram Fast Copy Function

- YMMM: Vram to Vram Fast Copy to Y Position

- HMMV: High speed draw filled rectangle

- LMMV: High speed filled rectangle with operator

- MouseReadTo: Fast Read mouse state and buttons to variable structure

- Itoa: Integer to Char conversion

- StrReverse: Reverse a string

- BoxFill: Fast Draw of a box on screen (easy version of HMMV / LMMV)

- BoxLine: Fast Draw of an empty box on screen

Added support for the V9990 by porting the TeamBomba's GFX9K graphics library to SDCC (Thanks to Sylvain). (beta, no manual, but a .h file to read!)

Added TCP TCP Support for GR8NET Cartridge (Thanks to Eugeny) (beta. No manual but a .h to read!)

The library is still free.
To download this version, 2 possibilities:
on the Repro-Factory Site: http://www.ebsoft.fr/shop/es/19-fusion-c
or on GitHub: https://github.com/ericb59

Be happy and code for MSX !
See you

I think i missed the last link in your last post ;-)

hi Gregory,
you can also find everything on github, for the toolchain:
https://github.com/ericb59/Fusion-C-v1.2/tree/master/Working...

https://github.com/ericb59/Fusion-C-v1.2/blob/master/FUSION-...

took me 20 seconds too find ;-)

Have fun! ;)

Hi,
Please, Could someone explain how I can put assembly inline routine in fusion C ?
I know there some code with it, but I don`t understand when I use #, (), or things like ld a, 0 (iy)

For example, at this code, I am getting the error message:
testasm.asm:52: Error: machine specific addressing or addressing mode error

#include "fusion-c/header/msx_fusion.h"

void write(void)
{
__asm

ld hl,#0
add de,#8192
ld c,#0

rotina: push hl
ld a,#255
call 0x004d
add hl,de
ld a,c
call 0x004d
add a,#16
ld c,a
pop hl
inc hl
ld a,h
cp #24
jr nz,rotina

ret

__endasm;
}

void main(){
Screen(2);
write();
Screen(0);
}

I mistyped it.

The correct is ld de, #8192 . However, Is it really the decimal value 8192 ?

If I put ,
ld a,(1000)
Then will register "a" contain the byte value from address 1000 ?

And what's mean " ld e,4(ix) ; lenght value Byte high" ?

thanks all in advance.

It's a shame that fusion C has this exotic notation.

Hi Eric,

Thank you for such a good piece of software!

I'm testing Fusion-C 1.2 and I was wondering if there is a way to use the "Sprite Priority Control" bit to use the "OR color" technique to add an additional 3rd color when overlapping just 2 sprites...

Thank you in advance!

Sorry for adding to this thread, but it's not a bug and not a real issue: will we see a new updated 64 bit version of the build chain?