When using vasm (vasmm68k_mot) to assemble a source with "data section" using the a.out output module, the <mem_type> attributes are ignored. According to the vasm manual this is by design, quote "The memory attributes are currently only used in the hunk-format output module.". Here is the link to the quote: http://sun.hasenbraten.de/vasm/relea...-Syntax-Module

However when using gcc (m68k-amigaos-as) to assemble a source with ".datachip" it is possible to place data in chip memory.

I've verified the above using "m68k-amigaos-objdump -x", vasm places the data in .data while as places it in .data_chip. I also managed to move .data sections from the vasm generated a.out files into .data_chip section, and verified that the data is correctly placed in chip memory when running an exe linked with gcc from modified vasm a.out-files.