- Last edited 10 months ago ago
How to use coprocessor service for Android
This article explains how to use the CoproService which is a SystemService embedded in the Android framework, allowing to use a serial connection to communicate with the Arm® Cortex®-M processor embedded in a compatible hardware board.
See STM32MPU Embedded Software for Android architecture overview to get more information on compatible hardware boards.
The environment must be installed using the Developer Package adapted to your selected microprocessor device. See the list of Android Developer Package.
CoproService is composed of two parts: Firmware management and TTY management.
2.1 Firmware management
The Arm® Cortex®-M processor can be used to offload real time algorithms (such as MotorControl), support connectivity mediums (like LORA), etc.
The users develop their firmwares thanks to the STM32CubeMX and SW4STM32 tools.
The firmware is embedded in the Android vendor partition in the
The CoproService looks at the contents of
/vendor/firmware/copro/ to get the list of available firmwares. It then loads the requested firmware at the user's/application's request.
2.2 TTY management
When the firmware is loaded and running, a
/dev/ttyRPMSG0 driver is available to communicate with the Arm® Cortex®-M processor.
It is up to the users to define and write their own protocol on top of
Application is then able to:
- write to
- read from
3.1 CoproManager API
The CoproManager API gives access to the Firmware management.
CoproManager getInstance(): Gets the instance of the available
CoproManagerto start using it.
FirmwareInfo getFirmwareList(): Returns the list of available firmwares present in
FirmwareInfo getFirmwareByName(String name): Looks up a firmware by its name in the
/vendor/firmware/copro/folder and returns all useful information about it, otherwise returns
boolean isFirmwareRunning(int id): Returns
trueif the firmware of identifier
idis running, otherwise returns
void startFirmware(int id): Starts the firmware defined by its identifier
void stopFirmware(): Stops any running firmware
CoproSerialPort getSerialPort(): Gets access to
CoproSerialPortto interact with the firmware. See below for more info.
3.2 FirmwareInfo API
The FirmwareInfo API gives information about firmwares.
int getId(): get the ID given by the CoproService to this firmware
String getName(): get the file name of this firmware
boolean getState(): returns the state of the firmware at the moment of the call: running (
true) or stopped (
3.3 CoproSerialPort API
The CoproSerialPort API gives access to the
/dev/ttyRPMSG0 driver available when a firmware is running. It allows the application to open and close the interface and also to send and receive data.
void open(int mode): opens a file descriptor to
/dev/ttyRPMSG0with the given mode : 0 for normal mode, 1 for raw mode
void close(): closes the file descriptor to
String read(): reads available string if the file descriptor is open, otherwise an empty string is returned.
byte readB(): reads available bytes if the file descriptor is open, otherwise "-1" is returned.
void write(String command): writes the given string to the file descriptor.
void writeB(byte command): writes the given bytes to the file descriptor.
4 Develop an application using the coprocessor service
In order to build the application, make sure you are using the appropriate Android SDK including CoproService (refer to How to build and install an SDK for Android).
In Android Studio create a new application.
Then, do not forget to select the right API level in the application Manifest, in order to be sure that CoproService is available.
To use the CoproService you need to get the instance to the CoproManager, then you will be able to use the CoproManager API defined above:
CoproManager mCoproManager = CoproManager.getInstance();
To be able to communicate with the running firmware you need to get a CoproSerialPort from CoproManager, then you will be available to use the CoproSerialPort API defined above :
ICoproSerialPort mCoproSerialPort = mCoproManager.getSerialPort();
The serial communication is possible only if a firmware is running. Make sure to close the serial communication when you stop a firmware and open it when you start one.