developer@... wrote:

> 1-What is .cnop? (pad to an even number of blocks? What is it?)

Yep - the .cnop instruction pads out to an even number of blocks. The
first argument is the byte to pad it with, and the second argument is
the multiple of bytes to pad to (i.e. $200= pad to $200, $400, $600,
etc.)

> 2-How do I use the LDF e STF instructions? (I read john maushammer's
> page but I did not understand)

Sorry for the poor documentation - I didn't have a good source.

>
> 3-I can use the writeflash_OS, but how can I "readflash_OS"?
> 4-How can I get the VMU Bios?
> 5-What is an object file and how does it work? (marcus comstedt's
> assembler doesnt support, i know)

Object files usually contain more information than regular binary files
(which usually contain just code and data and nothing else). They
usually contain information on variable and function names, and also the
information needed to make the file relocatable. Sometimes they have
debug information (such as source line numbers).

The point of object files is usually to break a program into smaller
portions (modules), each of which can be compiled separately. A linker
will then take a bunch of object files, combine them, and produce an
executable. This way, when you change one module, you don't have to
recompile every thing -- instead, just recompile the changed module and
re-link it with the unchanged modules. The linking process is usually
pretty quick, especially compared to compiling.

Object files would be good to produce information for a source-level
debugger, but since the memory of the VMU is so small, it's not that
much of a hassle to just recompile everything.

>
> I have the vmu official development, with the assembler, simulator
> (this one doesnt work) and other tools... If you want me to attach
> the assembler, just ask me and I'll do it...
>
> Thanks for any advice,
>
> I, Me, Mine
> (sorry if i made any mistake:)
>