Re: Re: RPTUN usage
So, please check the remote core call uart_rpmsg_init with isconsole=true, and no other uart driver register as console. On Wed, Feb 7, 2024 at 9:15 PM yfliu2008 wrote: > Xiang. > > > > Thanks for that. Yes I can see hello echo from master to remote and vice > versa as you suggested. > > > > > Regards, > yf > > > > Original > > > > From:"Xiang Xiao"< xiaoxiang781...@gmail.com >; > > Date:2024/2/7 20:09 > > To:"dev"< dev@nuttx.apache.org >; > > Subject:Re: RPTUN usage > > > You can try: > >1. echo hello > /dev/ttyRpmsg on one core >2. and cat /dev/ttyRpmsg on another core > > to confirm rpmsg uart work as expected before testing with cu. > > On Wed, Feb 7, 2024 at 8:00 PM yfliu2008 wrote: > > > Xiang and Bowen, > > > > > > > > I noticed that I didn't initialize the call the "uart_rpmsg_init()" > > properly thus last time "rpmsg-ttyRpmsg" end point didn't shown in the > > "rpmsg dump" result. After fixing the call parameters, they shows out > now: > > > > > > master> rpmsg dump /dev/rptun/remote > > > > > Dump rpmsg info > between cpu > > (master: yes)master <==> remote: > > > > rpmsg vq RX: > > > > > > > > rpmsg vq TX: > > > > > > > > rpmsg ept list: > > > > > > > > > ept NS > > > > > > > > ept rpmsg-ttyRpmsg > > > > > > > > > ept rpmsg-ping > > > > > > > > rpmsg buffer list: > > > > > > > > > RX buffer, total 8, pending 0 > > > > > > > TX buffer, total 8, pending 0 > > > > The "echo hello > /dev/ttyRpmsg" command doesn't block any > more, > > however the "cu" command doesn't work yet. I am not sure what is > > still missing. I think it is better to make uart-rpmsg work first > before > > try any other RPMsg device types. Please let me know if you have any > > suggestions. > > > > > > > > Regards, > > yf > > > > > > > > > > Original > > > > > > > > From:"yfliu2008"< yfliu2...@qq.com >; > > > > Date:2024/2/7 19:20 > > > > To:"dev"< dev@nuttx.apache.org >; > > > > Subject:RPTUN usage > > > > > > > > Xiang & Bowen, > > > > > > > > > > Here I seemed have RPTUN running on the two cores of K230 device and > I can > > use "rpmsg dump" to show some basic information on both cores: > > > > > > > > master> rpmsg dump /dev/rptun/remote > > > > > Dump rpmsg info > between cpu > > (master: yes)master <==> remote: > > > > rpmsg vq RX: > > > > > > > > rpmsg vq TX: > > > > > > > > rpmsg ept list: > > > > > > > > > ept NS > > > > > > > > ept rpmsg-ping > > > > > > > > rpmsg buffer list: > > > > > > > > > RX buffer, total 8, pending 0 > > > > > > > > > TX buffer, total 8, pending 0 > > > > > > remote> rpmsg /dev/rptun/master > > > > nsh: > rpmsg: > > missing required argument(s) > > > > > > remote> rpmsg dump /dev/rptun/master > > >
Re: RPTUN usage
You can try: 1. echo hello > /dev/ttyRpmsg on one core 2. and cat /dev/ttyRpmsg on another core to confirm rpmsg uart work as expected before testing with cu. On Wed, Feb 7, 2024 at 8:00 PM yfliu2008 wrote: > Xiang and Bowen, > > > > I noticed that I didn't initialize the call the "uart_rpmsg_init()" > properly thus last time "rpmsg-ttyRpmsg" end point didn't shown in the > "rpmsg dump" result. After fixing the call parameters, they shows out now: > > > master> rpmsg dump /dev/rptun/remote > > Dump rpmsg info between cpu > (master: yes)master <==> remote: > > rpmsg vq RX: > > > > rpmsg vq TX: > > > > rpmsg ept list: > > > > ept NS > > > > ept rpmsg-ttyRpmsg > > > > ept rpmsg-ping > > > > rpmsg buffer list: > > > > RX buffer, total 8, pending 0 > > > TX buffer, total 8, pending 0 > > The "echo hello > /dev/ttyRpmsg" command doesn't block any more, > however the "cu" command doesn't work yet. I am not sure what is > still missing. I think it is better to make uart-rpmsg work first before > try any other RPMsg device types. Please let me know if you have any > suggestions. > > > > Regards, > yf > > > > > Original > > > > From:"yfliu2008"< yfliu2...@qq.com >; > > Date:2024/2/7 19:20 > > To:"dev"< dev@nuttx.apache.org >; > > Subject:RPTUN usage > > > > Xiang & Bowen, > > > > > Here I seemed have RPTUN running on the two cores of K230 device and I can > use "rpmsg dump" to show some basic information on both cores: > > > > master> rpmsg dump /dev/rptun/remote > > Dump rpmsg info between cpu > (master: yes)master <==> remote: > > rpmsg vq RX: > > > > rpmsg vq TX: > > > > rpmsg ept list: > > > > ept NS > > > > ept rpmsg-ping > > > > rpmsg buffer list: > > > > RX buffer, total 8, pending 0 > > > > TX buffer, total 8, pending 0 > > > remote> rpmsg /dev/rptun/master > > nsh: rpmsg: > missing required argument(s) > > > remote> rpmsg dump /dev/rptun/master > > > Dump rpmsg info between cpu (master: no)remote <==> master: > > rpmsg vq RX: > > > > rpmsg vq TX: > > > > rpmsg ept list: > > > > ept NS > > > > rpmsg buffer list: > > > > RX buffer, total 8, pending 0 > > > TX buffer, total 8, pending 0 > > > > However, I don't know how to further check the RPTUN link yet. It seems > that "rpmsg ping /dev/rptun/remote 1 64 0 10" doesn't show anything. Also > "echo hello > /dev/ttyRpmsg" gets blocked. > > > > > > I tried "rpmsg ping" with "sim/rpserver" and "sim/rpproxy", it also > doesn't show any thing. However, the "echo hello > /dev/ttyproxy" > command can show the message on console. > > > > > Can you please suggest where should I start looking for RPTUN trouble > shooting information? > > > > > Regards, > > yf
