• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 508 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: rum CDDIPC demo at autosar meet problem. linux not found rpmsg chrdev device

wang liu
Prodigy 241 points
Part Number: TDA4VM

     I has integrate SciServer at vector autosar by the scieserver guide (https://www.ti.com/lit/an/spracy6/spracy6.pdf).

but rum CDDIPC demo  meet problem，linux not found rpmsg chrdev device.

Could you please provided some suggest about integrate CDDIPC demo to autoSAR?

  • +1
    TI__Guru** 112775 points

    Hi Wang,

    Which example are you using within the MCUSW. Your firmware has to publish a "rpmsg_chrdev" device supported on an end-point to Linux.

    The current CDD IPC examples/demos only create and announce "ti.ipc4.ping-pong" device.

    regards

    Suman

  • 0 in reply to Suman Anna
    Prodigy 241 points

    hi

     The cdd_ipc_profile_app_rc_linux demo has been successfully run on the EVM board，then I porting the cdd_ipc_profile_app_rc_linux demo to autosar platform，linux not found rpmsg chrdev device. Could you please provided some suggest about integrate CDDIPC demo to autoSAR?

  • 0
    TI__Mastermind 36307 points

    Hi,

    The biggest change needed to port the MCUSW demos to AUTOSAR stacks is OSAL layer, which could conflict with the configuration done by the AUTOSAR stack for interrupts and other things. How did you port the OSAL layer. Did you include the OSAL calls for registering interrupts? Or did you replace these?

    Regards,

    Erick