mikroBasic PRO for ARM allows embedding assembly in the source code by means of the asm statement. Note that you cannot use numerals as absolute addresses for register variables in assembly instructions. You may use symbolic names instead (listing will display these names as well as addresses).

You can group assembly instructions with the asm keyword:

asm
   block of assembly instructions
end asm

The only types whose name remains the same in asm as it is in the mikroBasic PRO for ARM are registers, e.g. GPIO_PORTB, etc.

Basic comments are allowed in embedded assembly code, along with one-line assembly comments starting with semicolon.

Accessing variables

Depending on the place of declaration, accessing a variable can be done in several ways :

• Accessing global variable :
  1. If declared under implementation section (visible only in the file where it was declared) : <source_file_name>_<variable_name>.
  2. If declared in the interface section (visible throughout the whole project) : _<variable_name>.
  3. If accessing registers (declared through register, rx or sfr specifiers, visible throughout the whole project) : <variable_name>.
• Accessing local variable : <routine_name>_<variable_name>.
• Accessing routine parameter : FARG_<routine_name>_<variable_name>.

Asm code and SSA optimization

If asm code is mixed with the Basic code, keep in mind that the generated code can substantially differ when SSA optimization option is enabled or disabled.
This is due to the fact that SSA optimization uses certain working registers to store routine parameters (W10-W13), rather than storing them onto the function frame.

Because of this, user must be very careful when writing asm code as existing values in the working registers used by SSA optimization can be overwritten.
To avoid this, it is recommended that user includes desired asm code in a separate routine.

Want more examples and libraries? 
Find them on