rpmsg not working in in latest bsp imx-5.4.24-2.1.0.xml

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

rpmsg not working in in latest bsp imx-5.4.24-2.1.0.xml

ソリューションへジャンプ
2,010件の閲覧回数
rakesh_patel
Senior Contributor I

Board

======

imx6sx

 

Logs

===============

[ 0.234310] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.24-2.1.0+gbabac00 #1
[ 0.234318] Hardware name: Freescale i.MX6 SoloX (Device Tree)
[ 0.234347] [<8010f978>] (unwind_backtrace) from [<8010b668>] (show_stack+0x10/0x14)
[ 0.234364] [<8010b668>] (show_stack) from [<807b516c>] (dump_stack+0x90/0xa4)
[ 0.234386] [<807b516c>] (dump_stack) from [<8012ad14>] (__warn+0xbc/0xd8)
[ 0.234404] [<8012ad14>] (__warn) from [<8012ad94>] (warn_slowpath_fmt+0x64/0xc4)
[ 0.234421] [<8012ad94>] (warn_slowpath_fmt) from [<80115f0c>] (__arm_ioremap_pfn_caller+0xe0/0x1bc)
[ 0.234435] [<80115f0c>] (__arm_ioremap_pfn_caller) from [<80116028>] (__arm_ioremap_caller+0x40/0x50)
[ 0.234455] [<80116028>] (__arm_ioremap_caller) from [<80640b7c>] (imx_rpmsg_find_vqs+0x98/0x18c)
[ 0.234472] [<80640b7c>] (imx_rpmsg_find_vqs) from [<80640000>] (rpmsg_probe+0xe4/0x358)
[ 0.234492] [<80640000>] (rpmsg_probe) from [<8046c528>] (virtio_dev_probe+0x1f4/0x2c0)
[ 0.234508] [<8046c528>] (virtio_dev_probe) from [<804b73d4>] (really_probe+0x1e0/0x348)
[ 0.234523] [<804b73d4>] (really_probe) from [<804b76b0>] (driver_probe_device+0x60/0x170)
[ 0.234535] [<804b76b0>] (driver_probe_device) from [<804b7960>] (device_driver_attach+0x58/0x60)
[ 0.234546] [<804b7960>] (device_driver_attach) from [<804b79c0>] (__driver_attach+0x58/0xcc)
[ 0.234564] [<804b79c0>] (__driver_attach) from [<804b5730>] (bus_for_each_dev+0x78/0xc0)
[ 0.234580] [<804b5730>] (bus_for_each_dev) from [<804b6754>] (bus_add_driver+0x15c/0x1e0)
[ 0.234594] [<804b6754>] (bus_add_driver) from [<804b8220>] (driver_register+0x74/0x108)
[ 0.234614] [<804b8220>] (driver_register) from [<80b38118>] (rpmsg_init+0x10/0x38)
[ 0.234633] [<80b38118>] (rpmsg_init) from [<801026d0>] (do_one_initcall+0x58/0x1c4)
[ 0.234649] [<801026d0>] (do_one_initcall) from [<80b00ef4>] (kernel_init_freeable+0x138/0x1d4)
[ 0.234666] [<80b00ef4>] (kernel_init_freeable) from [<807cb358>] (kernel_init+0x8/0x110)
[ 0.234682] [<807cb358>] (kernel_init) from [<801010e8>] (ret_from_fork+0x14/0x2c)
[ 0.234691] Exception stack(0x92051fb0 to 0x92051ff8)
[ 0.234704] 1fa0: 00000000 00000000 00000000 00000000
[ 0.234715] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 0.234728] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000
[ 0.234741] ---[ end trace 5faca3ea20d7e545 ]---
[ 0.234767] virtio_rpmsg_bus: probe of virtio0 failed with error -12

 

Dts 

===========

&rpmsg{
vdev-nums = <1>;
compatible = "fsl,imx6sx-rpmsg";
reg = <0x9FFF0000 0x10000>;
status = "okay";
};

 

Query

============

1) What is the reason for this?

2) NXP has released a new BSP for A9 core. Does any changes on the M4 side? (I see, there is no release for M4 code )

Note:

========

We were using NXP BSP(having kernel 4.1), where everything was working fine.

This is with only new kernel 5.4

 

ラベル(1)
0 件の賞賛
1 解決策
1,923件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie : I solved rpmsg issue. This is because of some memory corruption issue due to rpmsg_reserved memory node.

元の投稿で解決策を見る

0 件の賞賛
9 返答(返信)
1,986件の閲覧回数
joanxie
NXP TechSupport
NXP TechSupport

pls don't use 5.4.24-2.1.0, try to use 5.4.3-1.0.0 or 5.4.47_2.2.0, then tell me the result

0 件の賞賛
1,979件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie :

Thanks for your reply.

I got just worried why  imx-5.4.24-2.1.0.xml not work? It is part of NXP yocto user guide.

Can you please add more information here?

 

Rakesh

0 件の賞賛
1,956件の閲覧回数
joanxie
NXP TechSupport
NXP TechSupport

refer to the release note, we didn't test this version on imx6sx, so don't know what error or issue customer would get, so I don't suggest that you test this version, pls try the latest version 5.4.47_2.2.0, this is tested version, if you get any error, we can support and debug it

0 件の賞賛
1,951件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie :

I could not find it in the release note "Known issue/Limitations" section.

Can you please add more detail here?

 

0 件の賞賛
1,944件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie :

In release note, it is mentioned that:

"All
i.MX 6, 7 and 8M Mini and 8M Quad boards were full tested
and production quality as GA in 5.4.24_2.1.0"

 

I can not find anything not tested for imx6sx. Can you please add more detail here?

0 件の賞賛
1,936件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie :

Any update here?

0 件の賞賛
1,929件の閲覧回数
joanxie
NXP TechSupport
NXP TechSupport

pls find Table 1. Board Validation and Support Scope of release note, we suggest customer to use GA Quality. if you don't insist on using this version, I really suggest that you can use the latest 5.4.47 version

0 件の賞賛
1,926件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie :

This 5.4.24-2.1.0 also says GA quality for imx6sx as per Table-1 in the release note.

We are using a custom board having imx6sx. So porting custom changes again required a full re-cycle of everything and re-testing.

 

If there is any specific known issue in this release(5.4.24-2.1.0) then only, we can think to use the latest version. Otherwise, it is difficult for us.

 

 

0 件の賞賛
1,924件の閲覧回数
rakesh_patel
Senior Contributor I

@joanxie : I solved rpmsg issue. This is because of some memory corruption issue due to rpmsg_reserved memory node.

0 件の賞賛