SK-AM62: I want to use ti-rpmsg-char in my own project

Hi, to understand better are you developing on Linux Processor SDK or in MCU+RTOS SDK?

thank you,

Paula

Hi,
I'm sorry I Forgot to mention it. I'm developing on Linux Processor SDK. I did some digging and found a way to do it. Can you confirm if this is the best way to do it

#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <fcntl.h>
#include <unistd.h>
#include <errno.h>

#define RPMSG_DEVICE "/dev/rpmsg0"
#define GET_COMMAND "GET_DATA\n"
#define BUFFER_SIZE 128
#define POLL_INTERVAL_SEC 4000  // Delay between requests in microseconds

void rpmsg_poll_loop(void) {
    int fd;
    char buffer[BUFFER_SIZE];
    ssize_t bytes_written, bytes_read;

    // Open RPMsg device
    fd = open(RPMSG_DEVICE, O_RDWR);
    if (fd < 0) {
        perror("Error opening RPMsg device");
        return;
    }

    printf("Starting continuous RPMsg polling...\n");

    while (1) {
        // Send "GET DATA\n" to MCU
        bytes_written = write(fd, GET_COMMAND, strlen(GET_COMMAND));
        if (bytes_written < 0) {
            perror("Error writing to RPMsg device");
            break;
        }

        printf("Sent: %s", GET_COMMAND);

        // Read response from MCU
        bytes_read = read(fd, buffer, BUFFER_SIZE - 1);
        if (bytes_read < 0) {
            perror("Error reading from RPMsg device");
            break;
        }

        buffer[bytes_read] = '\0';  // Null-terminate the string
        printf("Received: %s\n", buffer);

        usleep(POLL_INTERVAL_SEC);  // Wait before next request
    }

    close(fd);
}

Thanks,
Bawantha

Let me loop our expert for Linux IPC. Please give him a day or two to reply

thank you,

Paula

Hello Bawantha,

This thread might be helpful:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1248401/processor-sdk-am62x-question-of-ti-rpmsg-char-scripts-specifically-the-recv_msg-method/4731803#4731803

If you want any other comments, you'll want to give me more information about your usecase.

e.g.:
what data are you sending? What direction is the data flowing?

How much data is getting sent at once?

Are there throughput requirements?

Are there latency requirements?

etc.

Regards,

Nick