UserSpace rpmsg_proto not working in GLSDK 7.03.00.03

Fabio Calabro

I'm testing rpmsg user-space test application with the latest GLSDK image (VERSION: 7_03_00_03)
and I got the same kernel panic with it.

The problem seems to be in the kernel side and rpmsg_proto code because
I get the following error to dmesg:

[   37.285252] rpmsg_proto rpmsg3: unexpected inbound message (from 51)
[   37.291678] Unable to handle kernel NULL pointer dereference at
virtual address 00000008
[   37.299832] pgd = c0004000
[   37.302551] [00000008] *pgd=00000000
[   37.306151] Internal error: Oops: 17 [#1] PREEMPT SMP ARM

The system hangs after that message.

This is what I did:

1. Extract boot-dra7xx-evm.tar.gz to boot partition and
arago-glsdk-multimedia-image-dra7xx-evm.tar.gz to root partition from
GLSDK's filesystem subdirectory to SD card. You can also use GLSDK's SD
card creator mksdboot.sh.
2. Run 'make ipc_ipu' in GLSDK directory to create ping_rpmsg firmware.
3. Copy
$GLSDK/component-sources/ipc_3_40_00_06/packages/ti/ipc/tests/bin/ti_platforms_evmDRA7XX_ipu1/ping_rpmsg.xem4
to /lib/firmware/dra7-ipu1-fw.xem4 of the SD-card's root file system.
4. Make ipc test binaries for linux. Root Makefile lacks support for
them so I made them inside ipc package. Yocto compiles the same
ping_rpmsg binary so this step is not required if Yocto is built.
5. If ipc test binaries are made, copy
$GLSDK/component-sources/ipc_3_40_00_06//linux/src/tests/ping_rpmsg to
/usr/bin directory of the SD-card's root file system.
5. Or alternatively, copy
$GLSDK/yocto-layers/build/arago-tmp-external-linaro-toolchain/work/dra7xx_evm-linux-gnueabi/ti-ipc/3.40.00.06-r0/packages-split/ti-ipc-test/usr/bin/ping_rpmsg
to /usr/bin directory of the SD-card's root file system.
6. Boot to the SD-card.
7. Run ping_rpmsg

Is this known issues or i'm doing something wrong on the procedure?

Regards

over 9 years ago

0 Pavel Botev over 9 years ago

TI__Guru**** 170625 points

Hi Fabio,

Which Linaro toolchain version you are using? See the below e2e thread, similar issue has been discussed:
e2e.ti.com/.../488712

Regards,
Pavel

0 Ilkka Karvinen over 9 years ago in reply to Pavel Botev

Prodigy 30 points

Hello Pavel, I'm working on the same subject so I can answer to this question.

We are using version 4.7.

Can you repeat this issue or is it only some problem in the procedure? I have tested rpmsg with rpmsg_client_sample.ko module and it works as documented. This ping_rpmsg seems to always trigger kernel oops.

0 Pavel Botev over 9 years ago in reply to Ilkka Karvinen

TI__Guru**** 170625 points

Ilkka,

Do you read the e2e thread that I provided to you in my previous post?

For the correct usage of the Linaro toolchain (and its version) and compiling with it modules and applications, refer also to:
processors.wiki.ti.com/.../DRA7xx_GLSDK_Software_Developers_Guide

Regards,
Pavel

0 Ilkka Karvinen over 9 years ago in reply to Pavel Botev

Prodigy 30 points

Yes, I think it is a different case because this seems to oops to rpmsg_proto when using it and also different toolchain version. However, if you think using later version of toolchain helps, I can try that.

Ilkka

0 Sunita Nadampalli over 9 years ago in reply to Ilkka Karvinen

TI__Expert 5970 points

Hi llkka,

Any luck with the later version of tool chain.

As pavel suggested, please check the release user guide to not to miss any steps. copying link one more time here.

processors.wiki.ti.com/.../DRA7xx_GLSDK_Software_Developers_Guide

Thanks & Regards,

Sunita.

0 Suman Anna over 9 years ago in reply to Sunita Nadampalli

TI__Guru** 111415 points

Hi Fabio,

rpmsg-proto driver is designed to work with the MessageQ IPC stack, and after the error recovery addition, is ill-suited with the direct socket-based ping_rpmsg sample, especially if you are using a single socket for both Tx and Rx. rpmsg-proto is not a traditional networking driver that follows all the networking semantics.

Please check if your ping_rpmsg.c has the updates from the following patch, you should be able to run properly if you have the changes from this that switches the ping_rpmsg to use different sockets for Rx and Tx.
git.ti.com/.../

regards
Suman

0 Ilkka Karvinen over 9 years ago in reply to Suman Anna

Prodigy 30 points

Hello Suman,

Thanks for your reply.

I tested with Linaro version 4.9 and latest GLSDK: No change.

Then I cloned that ipcdev code and compiled it against the GLSDK kernel. It contains that patch you are referring but unfortunately that didn't help. Are there changes to rpmsg-proto driver also? I'm only using GLSDK kernel right now and its latest commits are from November 2015.

I must admit I'm a newbie in rpmsg so that is why I asked if my procedure was correct. GLSDK guide does not say much about the user space client. Kernel module usage is documented in http://processors.wiki.ti.com/index.php/RPMsg_Kernel_Client_Application

I'm only looking for some proof-of-concept test for rpmsg on user space at this time with working code. Any ideas would be helpful in this work right now.

0 Suman Anna over 9 years ago in reply to Ilkka Karvinen

TI__Guru** 111415 points

Hi Ilkka,

Did you update the sample base image as well? If you are just looking to validate userspace, then you should be able to use the MessageQApp with the messageq_single firmware image. Do note that different samples work with different firmware images, so hopefully, you have them matched.

You can cross-check your commits against the tree that I maintain which feeds into GLSDK. Not sure whether this is 3.14 or a 4.1 kernel.

3.14 kernel: http://git.ti.com/gitweb/?p=rpmsg/rpmsg.git;a=shortlog;h=refs/heads/rpmsg-ti-linux-3.14.y

4.1 kernel: git.ti.com/.../

regards

Suman

Processors

Processors forum

UserSpace rpmsg_proto not working in GLSDK 7.03.00.03