Map to RAM OUT&HFE,3 for to memorize 18 LEVELS SCENE GAME in 2 files BINARY from BASIC for MSX2.

Hello Manuel and to all you gentilments users MSX,

I ask sorry to all of you if you do not do that in any way
I'm well explained.

So, the point of the situation is as follows:

I would like to allocate my two routines in assembler, once compiled
in binary files, which contain all 18 levels of play via ASCII code,
in SCREEN1, but in my case of my project in question we used
the SCREEN4 IN SCREEN 1 mode, doing a trick with the VDP registers.

Therefore, I would like to allocate these two binary files on the memory mapper for MSX2,
and from BASIC using with OUT&HFE,3

Because already on OUT&HFE,2 music is already stored in binary with the PSG.

I hope I have explained myself well this time, I understand that at the level of programming is a very
difficult thing to solve, that's why I'm here with you to kindly ask your help forever.

See you to soon as always......

Friend respect!

Friend gasparrini.
I also use a translator. It's a problem.
Look at the pdf "Top Secret", from the Brazilian colleagues, you can understand well the being in portuges, a Latin language. Check it out on Google. Animos, that with illusion can achieve many things in programming.

Sorry to say you haven't, and it is NOT a language problem imho. More in the area of documentation / problem analysis as done by yourself. As in: it isn't clear to yourself what the problem is (or what you want to do exactly), and that makes it difficult to explain to others. Posting a chunk of code doesn't help much if it isn't clear what it's supposed to do, context, data structure, or which parts work / which parts don't.

Actually this is a fairly simple one. I went over the code yesterday evening, and several things became obvious. Problem is those things only became obvious from looking at the code, NOT because you told us. That also makes it harder for us to understand the issue, and thus less likely someone will help. Again: not a language issue (although the language issue doesn't help either). Some observations:

• Data for each level is a fixed size block of 32*22 = 704 bytes that's copied from RAM -> VRAM. For 18 levels that's 18*704 = 12672 bytes, which easily fits in a single mapper block -> no need to split up level data in 2 separate .bin files. Because level data is fixed size, start of each block can be calculated, that is: no need for a list of dw's with address of each level.
• Afaict there's no need to do any slot switching. BASIC part does some calculation of a slot ID, which on a disk-BASIC MSX can simply be taken from a system variable. Then several interslot-call routines are installed, which aren't needed because with the data/code in 8000-BFFFh, code can be CALLed directly. If memory switching in 8000-BFFFh is needed because a BASIC program is running there, machine code can simply switch mapper blocks & leave slot settings alone.
• When doing a USR(X) function call, parameters can be passed from, and back to BASIC in the BASIC statement itself. Seen from the assembler code, 2 system variables are used for that: VALTYP (F663h) and DAC (F7F6h). Assuming BASIC takes care an integer (level #) is passed, VALTYP can be ignored, and integer passed is found at DAC+2.

A simple setup would be to put the level data in a single mapper block, starting with the data first, followed by the code, so that everything starts at fixed addresses. The single .bin file might look something like this:

LDIRVM  .equ $005C ; copy data from RAM -> VRAM
CHRPUT  .equ $1800 ; destination address in VRAM
DAC     .equ $F7F6 ; buffer for argument passed from / to BASIC


    .db $fe
    .dw startProgram,endProgram-1,runAddress

    .org $8000

startProgram:

level_data:
  (level 1 data)   ; 32*22 = 704 bytes
  (level 2 data)
    .
    .
  (level 18 data)  ; total 18 * 704 = 12672 bytes

main:
    ld a,(DAC+2)   ; level (1-18) passed from BASIC
    ld hl,level_data-704
    ld bc,32*22
add704:
    add hl,bc
    dec a
    jr nz,add704

    ld de,CHRPUT+64
    call LDIRVM

runAddress:        ; just in case this .bin is BLOAD,R-ed by accident
    ret

endProgram:
    .end

If as gdx suggested, main BASIC program starts at C000h, "main" can be called directly with a USR(X) statement.

If BASIC needs more space and starts at 8000h, you could use a small helper routine that does the equivalent of:

    ld a,3
    out (FEh),a
    call main
    ld a,1
    out (FEh),a
    ret

Similar thing for calling the music code from a '32K sized' BASIC program.