Multi Source Translation Content

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Multi Source Translation Content

Discussions

Sort by:
VFIO_FLS_MC: reset device has failed LX2160 : I am getting below error while running my application. After reboot works fine . Next time same error again. This problem seen if i configure as below  #export DPIO_COUNT=20 set -x #export DPIO_COUNT=10 # ls-listni #to check if 40G is enabled or not #Remove 40G port if it is enabled (40G=dpmac.2) echo dpni.1 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind restool dpni destroy dpni.1 echo 0 > /proc/sys/kernel/randomize_va_space #export DPIO_COUNT=20 export DPMCP_COUNT=3 export FS_ENTRIES=12 #/usr/local/dpdk/dpaa2/dynamic_dpl.sh dpmac.3 /usr/local/dpdk/dpaa2/dynamic_dpl.sh dpni dpni -b 00:00:00:00:05:00 # dpni.1 00:00:00:00:05:01 # dpni.2 00:00:00:00:05:02 ls-addni --no-link #eth0 dpni.3 ls-addni --no-link #eth2 dpni.4 #/////OUTPUT///////// # Unbinding dprc.2 from VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/unbind #dpn.2 is the output of dynamicdpl.sh #dpni.1 dpmac.4 -Dynamic- # #restool dprc disconnect dprc.2 --endpoint=dpni.1 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.3 --endpoint2=dpdmux.0.0 restool dprc connect dprc.1 --endpoint1=dpni.1 --endpoint2=dpdmux.0.1 restool dprc connect dprc.1 --endpoint1=dpni.3 --endpoint2=dpdmux.0.2 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.4 --endpoint2=dpdmux.1.0 restool dprc connect dprc.1 --endpoint1=dpni.2 --endpoint2=dpdmux.1.1 restool dprc connect dprc.1 --endpoint1=dpni.4 --endpoint2=dpdmux.1.2 #echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind # Bind the DPRC back to VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind # Export the DPRC export DPRC=dprc.2 [ 3103.545665] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.545690] ------------[ cut here ]------------ [ 3103.545701] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.545703] Modules linked in: libdes mali_dp [ 3103.545715] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Not tainted 5.10.35 #5 [ 3103.545717] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.545721] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.545724] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.545727] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.545729] sp : ffff800012ef3c90 [ 3103.545731] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.545735] x27: 0000000000000000 x26: 0000000000000000 [ 3103.545740] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.545745] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.545749] x21: ffff0e7d1edc7800 x20: ffff0e7d3d39f040 [ 3103.545754] x19: ffff0e7d1d71db80 x18: 0000000000000001 [ 3103.545758] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.545763] x15: ffff0e7d3d39f040 x14: 00000000000007dd [ 3103.545767] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.545771] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.545776] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.545781] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.545785] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.545789] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.545793] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.545798] Call trace: [ 3103.545802] vfio_fsl_mc_release+0xdc/0x190 [ 3103.545806] vfio_device_fops_release+0x24/0x48 [ 3103.545811] __fput+0x78/0x230 [ 3103.545814] ____fput+0x10/0x20 [ 3103.545818] task_work_run+0x80/0x140 [ 3103.545821] do_exit+0x324/0xa08 [ 3103.545824] do_group_exit+0x44/0xa0 [ 3103.545826] __wake_up_parent+0x0/0x30 [ 3103.545831] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.545834] do_el0_svc+0x24/0x90 [ 3103.545839] el0_svc+0x14/0x20 [ 3103.545841] el0_sync_handler+0xb0/0xb8 [ 3103.545845] el0_sync+0x178/0x180 [ 3103.545847] ---[ end trace d15991a0fbaef713 ]--- [ 3103.546381] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.546399] ------------[ cut here ]------------ [ 3103.546406] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.546411] Modules linked in: libdes mali_dp [ 3103.546430] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.546435] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.546441] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.546447] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.546453] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.546458] sp : ffff800012ef3c90 [ 3103.546462] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.546466] x27: 0000000000000000 x26: 0000000000000000 [ 3103.546471] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.546475] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.546479] x21: ffff0e7d02d77000 x20: ffff0e7d3d39f040 [ 3103.546484] x19: ffff0e7d1dc13480 x18: ffffb28536ab3470 [ 3103.546488] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.546492] x15: ffff0e7d3d39f040 x14: 0000000000000805 [ 3103.546497] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.546501] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.546506] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.546510] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.546514] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.546518] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.546522] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.546527] Call trace: [ 3103.546529] vfio_fsl_mc_release+0xdc/0x190 [ 3103.546532] vfio_device_fops_release+0x24/0x48 [ 3103.546536] __fput+0x78/0x230 [ 3103.546539] ____fput+0x10/0x20 [ 3103.546541] task_work_run+0x80/0x140 [ 3103.546544] do_exit+0x324/0xa08 [ 3103.546546] do_group_exit+0x44/0xa0 [ 3103.546548] __wake_up_parent+0x0/0x30 [ 3103.546552] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.546555] do_el0_svc+0x24/0x90 [ 3103.546557] el0_svc+0x14/0x20 [ 3103.546559] el0_sync_handler+0xb0/0xb8 [ 3103.546562] el0_sync+0x178/0x180 [ 3103.546564] ---[ end trace d15991a0fbaef714 ]--- [ 3103.547072] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.547086] ------------[ cut here ]------------ [ 3103.547090] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.547091] Modules linked in: libdes mali_dp [ 3103.547098] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.547100] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.547103] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.547105] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547107] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547109] sp : ffff800012ef3c90 [ 3103.547111] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.547116] x27: 0000000000000000 x26: 0000000000000000 [ 3103.547120] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.547125] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.547129] x21: ffff0e7d02d32000 x20: ffff0e7d3d39f040 [ 3103.547133] x19: ffff0e7d1dc13d80 x18: ffffb28536ab3470 [ 3103.547138] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.547142] x15: ffff0e7d3d39f040 x14: 000000000000082d [ 3103.547146] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.547151] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.547155] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.547159] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.547164] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.547168] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.547172] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.547176] Call trace: [ 3103.547179] vfio_fsl_mc_release+0xdc/0x190 [ 3103.547182] vfio_device_fops_release+0x24/0x48 [ 3103.547185] __fput+0x78/0x230 [ 3103.547188] ____fput+0x10/0x20 [ 3103.547190] task_work_run+0x80/0x140 [ 3103.547193] do_exit+0x324/0xa08 [ 3103.547195] do_group_exit+0x44/0xa0 [ 3103.547198] __wake_up_parent+0x0/0x30 [ 3103.547201] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.547204] do_el0_svc+0x24/0x90 [ 3103.547207] el0_svc+0x14/0x20 [ 3103.547209] el0_sync_handler+0xb0/0xb8 [ 3103.547211] el0_sync+0x178/0x180 [ 3103.547213] ---[ end trace d15991a0fbaef715 ]--- [ 3103.547721] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.547735] ------------[ cut here ]------------ [ 3103.547739] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.547740] Modules linked in: libdes mali_dp [ 3103.547748] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.547750] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.547752] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.547755] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547757] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547759] sp : ffff800012ef3c90 [ 3103.547761] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.547765] x27: 0000000000000000 x26: 0000000000000000 [ 3103.547770] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.547777] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.547781] x21: ffff0e7d1e989000 x20: ffff0e7d3d39f040 [ 3103.547785] x19: ffff0e7d1dcc6680 x18: ffffb28536ab3470 [ 3103.547790] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.547794] x15: ffff0e7d3d39f040 x14: 0000000000000855 [ 3103.547798] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.547802] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.547807] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.547812] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.547819] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.547823] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.547827] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.547831] Call trace: [ 3103.547834] vfio_fsl_mc_release+0xdc/0x190 [ 3103.547837] vfio_device_fops_release+0x24/0x48 [ 3103.547840] __fput+0x78/0x230 [ 3103.547843] ____fput+0x10/0x20 [ 3103.547845] task_work_run+0x80/0x140 [ 3103.547848] do_exit+0x324/0xa08 [ 3103.547850] do_group_exit+0x44/0xa0 [ 3103.547853] __wake_up_parent+0x0/0x30 [ 3103.547858] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.547861] do_el0_svc+0x24/0x90 [ 3103.547864] el0_svc+0x14/0x20 [ 3103.547866] el0_sync_handler+0xb0/0xb8 [ 3103.547868] el0_sync+0x178/0x180 [ 3103.547870] ---[ end trace d15991a0fbaef716 ]--- [ 3103.548378] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.548392] ------------[ cut here ]------------ [ 3103.548395] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.548397] Modules linked in: libdes mali_dp [ 3103.548404] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.548406] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.548408] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.548411] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.548413] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.548415] sp : ffff800012ef3c90 [ 3103.548417] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.548421] x27: 0000000000000000 x26: 0000000000000000 [ 3103.548426] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.548430] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.548437] x21: ffff0e7d1ea4e000 x20: ffff0e7d3d39f040 [ 3103.548442] x19: ffff0e7d1dcc6f80 x18: ffffb28536ab3470 [ 3103.548446] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.548450] x15: ffff0e7d3d39f040 x14: 000000000000087d [ 3103.548455] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.548459] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.548464] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.548468] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.548472] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.548479] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.548483] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.548488] Call trace: [ 3103.548490] vfio_fsl_mc_release+0xdc/0x190 [ 3103.548493] vfio_device_fops_release+0x24/0x48 [ 3103.548497] __fput+0x78/0x230 [ 3103.548500] ____fput+0x10/0x20 [ 3103.548502] task_work_run+0x80/0x140 [ 3103.548505] do_exit+0x324/0xa08 [ 3103.548507] do_group_exit+0x44/0xa0 [ 3103.548509] __wake_up_parent+0x0/0x30 [ 3103.548513] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.548516] do_el0_svc+0x24/0x90 [ 3103.548519] el0_svc+0x14/0x20 [ 3103.548523] el0_sync_handler+0xb0/0xb8 [ 3103.548526] el0_sync+0x178/0x180 [ 3103.548528] ---[ end trace d15991a0fbaef717 ]--- [ 3103.549035] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.549049] ------------[ cut here ]------------ [ 3103.549052] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.549054] Modules linked in: libdes mali_dp [ 3103.549060] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.549062] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.549065] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.549067] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549069] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549071] sp : ffff800012ef3c90 [ 3103.549073] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.549077] x27: 0000000000000000 x26: 0000000000000000 [ 3103.549082] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.549086] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.549090] x21: ffff0e7d1dd80000 x20: ffff0e7d3d39f040 [ 3103.549094] x19: ffff0e7d1dc09880 x18: ffffb28536ab3470 [ 3103.549098] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.549103] x15: ffff0e7d3d39f040 x14: 00000000000008a5 [ 3103.549107] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.549111] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.549116] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.549120] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.549124] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.549129] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.549133] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.549137] Call trace: [ 3103.549139] vfio_fsl_mc_release+0xdc/0x190 [ 3103.549142] vfio_device_fops_release+0x24/0x48 [ 3103.549145] __fput+0x78/0x230 [ 3103.549148] ____fput+0x10/0x20 [ 3103.549151] task_work_run+0x80/0x140 [ 3103.549153] do_exit+0x324/0xa08 [ 3103.549155] do_group_exit+0x44/0xa0 [ 3103.549158] __wake_up_parent+0x0/0x30 [ 3103.549161] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.549164] do_el0_svc+0x24/0x90 [ 3103.549166] el0_svc+0x14/0x20 [ 3103.549168] el0_sync_handler+0xb0/0xb8 [ 3103.549171] el0_sync+0x178/0x180 [ 3103.549172] ---[ end trace d15991a0fbaef718 ]--- [ 3103.549679] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.549693] ------------[ cut here ]------------ [ 3103.549699] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.549701] Modules linked in: libdes mali_dp [ 3103.549708] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.549710] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.549712] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.549715] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549717] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549718] sp : ffff800012ef3c90 [ 3103.549720] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.549725] x27: 0000000000000000 x26: 0000000000000000 [ 3103.549729] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.549733] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.549738] x21: ffff0e7d1dd9dc00 x20: ffff0e7d3d39f040 [ 3103.549744] x19: ffff0e7d1d6adc80 x18: ffffb28536ab3470 [ 3103.549749] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.549753] x15: ffff0e7d3d39f040 x14: 00000000000008cd [ 3103.549757] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.549762] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.549766] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.549771] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.549775] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.549782] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.549786] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.549790] Call trace: [ 3103.549792] vfio_fsl_mc_release+0xdc/0x190 [ 3103.549795] vfio_device_fops_release+0x24/0x48 [ 3103.549798] __fput+0x78/0x230 [ 3103.549801] ____fput+0x10/0x20 [ 3103.549804] task_work_run+0x80/0x140 [ 3103.549806] do_exit+0x324/0xa08 [ 3103.549809] do_group_exit+0x44/0xa0 [ 3103.549811] __wake_up_parent+0x0/0x30 [ 3103.549814] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.549818] do_el0_svc+0x24/0x90 [ 3103.549822] el0_svc+0x14/0x20 [ 3103.549824] el0_sync_handler+0xb0/0xb8 [ 3103.549827] el0_sync+0x178/0x180 [ 3103.549829] ---[ end trace d15991a0fbaef719 ]--- [ 3103.550346] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) [ 3103.550360] ------------[ cut here ]------------ [ 3103.550368] WARNING: CPU: 2 PID: 3644 at drivers/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.550373] Modules linked in: libdes mali_dp [ 3103.550393] CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: G W 5.10.35 #5 [ 3103.550398] Hardware name: NXP Layerscape LX2160ARDB (DT) [ 3103.550404] pstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.550410] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.550416] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.550420] sp : ffff800012ef3c90 [ 3103.550426] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.550432] x27: 0000000000000000 x26: 0000000000000000 [ 3103.550437] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.550441] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.550456] x21: ffff0e7d1ee17800 x20: ffff0e7d3d39f040 [ 3103.550469] x19: ffff0e7d1dc81580 x18: ffffb28536ab3470 [ 3103.550483] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.550496] x15: ffff0e7d3d39f040 x14: 00000000000008f5 [ 3103.550510] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.550523] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.550536] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.550549] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.550564] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.550577] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.550587] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.550591] Call trace: [ 3103.550594] vfio_fsl_mc_release+0xdc/0x190 [ 3103.550597] vfio_device_fops_release+0x24/0x48 [ 3103.550600] __fput+0x78/0x230 [ 3103.550603] ____fput+0x10/0x20 [ 3103.550605] task_work_run+0x80/0x140 [ 3103.550608] do_exit+0x324/0xa08 [ 3103.550610] do_group_exit+0x44/0xa0 [ 3103.550612] __wake_up_parent+0x0/0x30 [ 3103.550616] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.550618] do_el0_svc+0x24/0x90 [ 3103.550621] el0_svc+0x14/0x20 [ 3103.550623] el0_sync_handler+0xb0/0xb8 [ 3103.550626] el0_sync+0x178/0x180 [ 3103.550628] ---[ end trace d15991a0fbaef71a ]--- [ 3103.551136] vfio-fsl-mc dprc.2: VFIO_FLS_MC: reset device has failed (-13) Re: VFIO_FLS_MC: reset device has failed Thanks @Bio_TICFSL  I will execute and confirm  Re: VFIO_FLS_MC: reset device has failed Hello, The core problem is a missing restool dprc assign step in your setup script. Your script: Creates dpdmux.0 and dpdmux.1 under dprc.1 (the root container). Connects dpni.1 / dpni.2 (which reside inside dprc.2 , the VFIO container) to those DPDMUX interfaces. Binds dprc.2 to the VFIO driver. When the application exits, the VFIO driver attempts to reset all objects inside dprc.2 . However, dpni.1 / dpni.2 are still externally connected to dpdmux.0 / dpdmux.1 objects that live in dprc.1 . The MC firmware cannot cleanly reset the container because of these cross-container connections it doesn't have authority over → returns -13 (permission denied). Why it works after reboot: After a cold boot, the DPAA2 objects are in a clean initial state. The first run succeeds. But on exit, the DPDMUX connections are not properly torn down, leaving the MC in a partial state. On the next run (without reboot), the container reset fails again. Fix: Add restool dprc assign for DPDMUX Objects The DPDMUX objects must be assigned into dprc.2 before binding to VFIO. This tells the MC that these objects are owned by the VFIO container and can be reset when the container is released. Insert the following lines after creating/connecting the DPDMUX objects and before rebinding dprc.2 to VFIO: # Assign dpdmux objects into dprc.2 so VFIO can reset them cleanly restool dprc assign dprc.1 --object=dpdmux.0 --child=dprc.2 --plugged=1 restool dprc assign dprc.1 --object=dpdmux.1 --child=dprc.2 --plugged=1 # Now bind dprc.2 back to VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind export DPRC=dprc.2   Your corrected script section should look like: # Unbind dprc.2 from VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/unbind # Create and connect DPDMUX for port dpmac.3 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.3 --endpoint2=dpdmux.0.0 restool dprc connect dprc.1 --endpoint1=dpni.1 --endpoint2=dpdmux.0.1 restool dprc connect dprc.1 --endpoint1=dpni.3 --endpoint2=dpdmux.0.2 # Create and connect DPDMUX for port dpmac.4 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.4 --endpoint2=dpdmux.1.0 restool dprc connect dprc.1 --endpoint1=dpni.2 --endpoint2=dpdmux.1.1 restool dprc connect dprc.1 --endpoint1=dpni.4 --endpoint2=dpdmux.1.2 # *** KEY FIX: Assign dpdmux objects to dprc.2 so VFIO can reset them *** restool dprc assign dprc.1 --object=dpdmux.0 --child=dprc.2 --plugged=1 restool dprc assign dprc.1 --object=dpdmux.1 --child=dprc.2 --plugged=1 # Bind dprc.2 back to VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind export DPRC=dprc.2   Additional Recommendations Update MC firmware to the latest version for your BSP  Proper teardown between runs (without reboot): Before re-running your setup script, destroy the previously created DPDMUX objects to ensure a clean state: restool dpdmux destroy dpdmux.0 restool dpdmux destroy dpdmux.1     Check MC console log at /dev/dpaa2_mc_console for additional firmware-level error details that may accompany the -13 error. Regards
View full article
デフォルトのWinbond FlashをEverspin Memory Custom Flash Driverに置き換えるための助けが必要です こんにちは、NXPコミュニティの皆さん、 私は i.MX RT1170 EVKB / MIMXRT1176 ボード を扱っており 、デフォルトのWinbond外部メモリを Everspin EM032LXQADG13IS2T メモリデバイス に交換する方法についてアドバイスが必要です 。 現在のハードウェア この基板は元々 Winbond W25Q512というデバイスを使用していましたが、私はそれを以下のデバイスに交換しました。 Everspin EM032LXQADG13IS2T 主な問題は、Everspinメモリが SFDPをサポートしていないのに対し、デフォルトのWinbondメモリはSFDPに対応していることです。 現在の状況 すでに i.MX RT1170 FlexSPIインターフェースを使ってEverspinメモリと通信できています。 アプリケーションがRAMから動作している間は、メモリは機能的に動作しています。特に: Everspin製メモリとのFlexSPI通信は正常に動作しています。 メモリの読み書き操作も可能です。 アプリケーションイメージ(XIPイメージ)はメモリ書き込みコードを使ってEverspinメモリにロード・プログラムできます。 Everspinメモリに保存されたイメージは、正常にアクセス・実行可能です。 しかし、 通常のRT1170フラッシュプログラミングでは、アプリケーションを直接Everspinメモリにフラッシュ・プログラムすることはできません i.MX。 EverspinメモリはSFDPをサポートしていないため、Winbondメモリに使われているデフォルトのFlexSPIフラッシュドライバー/設定ではEverspinデバイスを自動的に識別・設定できないのではないかと疑っています。 SFDP以外のメモリデバイスをサポートするためのNXPの推奨アプローチについて理解を深めたい。 アドバイスをいただければ幸いです。 1. RT1170のEverspin EM032LXQADG13IS2T用のカスタムフラッシュドライバー i.MX どうやって作成できますか? 2. i.MX RT1170 FlexSPIコントローラで非SFDPのSPI/QSPIメモリをサポートする既存の例はありますか? ブートROM|ブート|フラッシュ 開発ボード Re: Help Required Replacing Default Winbond Flash with Everspin Memory Custom Flash Driver @jyothzz様、 ご質問ありがとうございます。 はい、MIMXRT1170_SFDP_QSPI.cfxフラッシュドライバーはRT1170 EVKおよびMCUXpresso SDKで使われているデフォルトのフラッシュドライバーです: ShellyZhang_0-1790052100477.png 現在、i.MX RT1170 FlexSPIコントローラで非SFDP SPI/QSPIメモリをサポートする例は存在しません。顧客の修正なしで直接サポートされているフラッシュドライバーは以下の通りです: ShellyZhang_1-1790052161488.png カスタムフラッシュドライバーを作成するには、以下の情報を参照してください: 1. https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/How-to-create-a-new-Flash-driver-of-the-MCUXPresso-IDE/ta-p/1274718 2. https://community.nxp.com/t5/i-MX-RT-Crossover-MCUs-Knowledge/RT1170-flexSPI1-secondary-QSPI-flash-debug-flashdriver/tac-p/1938828 カスタムフラッシュドライバーの開発中にご質問があれば、どうぞお気軽にお問い合わせください。 よろしくお願いいたします。 シェリー Re: Help Required Replacing Default Winbond Flash with Everspin Memory Custom Flash Driver こんにちは、 @ShellyZhang さん。 ご回答ありがとうございました。大変参考になりました。 新しいメモリでSFDPをサポートしていないフラッシュドライバーの問題は解決しました。 同じi.MXRT117x_SFDP_QSPIドライバを使っていました。SFDPの部分はi.MXRT1050_QSPIの非SFDPドライバーを指しています。 その後、新しいドライバーファイル(.cfx)を生成し、問題なく動作しました。 改めて、ご指導いただきありがとうございました。 よろしくお願いいたします。 ジョーティッシュ
View full article
jailhouse DTS for 9x9 imx.93 Hi - Do you provide DTS files for jailhouse on the 9x9 imx.93?  I can only find ones for the 11x11. Thanks David Re: jailhouse DTS for 9x9 imx.93 Hello, This device tree will be included in the next BSP release. // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright 2023 NXP */ /dts-v1/; #include / { model = "NXP i.MX93 9x9 QSB"; compatible = "fsl,imx93-9x9-qsb", "fsl,imx93"; interrupt-parent = <&gic>; #address-cells = <2>; #size-cells = <2>; aliases { mmc0 = &usdhc1; serial1 = &lpuart2; }; cpus { #address-cells = <1>; #size-cells = <0>; A55_0: cpu@0 { device_type = "cpu"; compatible = "arm,cortex-a55"; reg = <0x0>; enable-method = "psci"; #cooling-cells = <2>; }; }; psci { compatible = "arm,psci-1.0"; method = "smc"; }; gic: interrupt-controller@48000000 { compatible = "arm,gic-v3"; reg = <0 0x48000000 0 0x10000>, <0 0x48040000 0 0xc0000>; #interrupt-cells = <3>; interrupt-controller; interrupts = ; interrupt-parent = <&gic>; }; timer { compatible = "arm,armv8-timer"; interrupts = , , , ; clock-frequency = <24000000>; }; clk_dummy: clock-dummy { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <0>; clock-output-names = "clk_dummy"; }; clk_400m: clock-400m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <200000000>; clock-output-names = "200m"; }; osc_24m: clock-osc-24m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <24000000>; clock-output-names = "osc_24m"; }; pci@fd700000 { compatible = "pci-host-ecam-generic"; device_type = "pci"; bus-range = <0 0>; #address-cells = <3>; #size-cells = <2>; #interrupt-cells = <1>; interrupt-map-mask = <0 0 0 7>; interrupt-map = <0 0 0 1 &gic GIC_SPI 227 IRQ_TYPE_EDGE_RISING>, <0 0 0 2 &gic GIC_SPI 228 IRQ_TYPE_EDGE_RISING>, <0 0 0 3 &gic GIC_SPI 229 IRQ_TYPE_EDGE_RISING>, <0 0 0 4 &gic GIC_SPI 230 IRQ_TYPE_EDGE_RISING>; reg = <0x0 0xfd700000 0x0 0x100000>; ranges = <0x02000000 0x00 0x10000000 0x0 0x10000000 0x00 0x10000>; }; soc@0 { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; ranges = <0x0 0x0 0x0 0x80000000>, <0x28000000 0x0 0x28000000 0x10000000>; aips1: bus@44000000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x44000000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; lpuart2: serial@44390000 { compatible = "fsl,imx93-lpuart", "fsl,imx8ulp-lpuart", "fsl,imx7ulp-lpuart"; reg = <0x44390000 0x1000>; interrupts = ; status = "disabled"; }; }; aips3: bus@42800000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x42800000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; usdhc1: mmc@42850000 { compatible = "fsl,imx93-usdhc", "fsl,imx8mm-usdhc"; reg = <0x42850000 0x10000>; interrupts = ; fsl,tuning-start-tap = <20>; fsl,tuning-step= <2>; status = "disabled"; }; }; }; }; &lpuart2 { clocks = <&osc_24m>; clock-names = "ipg"; status = "okay"; }; &usdhc1 { clocks = <&clk_dummy>, <&clk_dummy>, <&clk_400m>; clock-names = "ipg", "ahb", "per"; bus-width = <8>; non-removable; status = "okay"; }; Best regards. Re: jailhouse DTS for 9x9 imx.93 do you also have the matching root cell config file for qsb jailhouse on the 9x9? thanks
View full article
MIMXRT1176 ADP – SEGGER J-Link debugging issue Hi everyone, I am currently working with the MIMXRT1176 / i.MX RT1170 platform. I initially used the MIMXRT1170-EVKB for development, but have now shifted to the MIMXRT1176-ADP for interfacing a parallel RGB panel. I am facing an issue with SEGGER J-Link debugging on the ADP board. Environment: Board: MIMXRT1176-ADP Board revision: 700-51950 REV A1 Schematic revision: SCH-51950 REV B1 MCUXpresso IDE: v25.6.136 MCUXpresso SDK: v25.09.00 SEGGER J-Link: latest version On the EVKB, both J-Link and LinkServer worked without any issues. However, on the ADP: Firmware flashes successfully. Debugger reaches the first line of main(). If I Step Over once, it stops at: Break at address "0xdeadbeee" with no debug information available, or outside of program code. Breakpoints at other locations work and are hit correctly. However, Resume/Continue from a breakpoint again results in 0xDEADBEEE. Could someone please confirm whether J-Link is fully supported with MCUXpresso IDE on the MIMXRT1176-ADP, and whether there is any specific J-Link script, reset/debug configuration, or ADP-specific initialization required? Could this be related to the memory configuration, external flash/SDRAM, or startup code on the ADP? Any guidance or working J-Link configuration for the ADP would be greatly appreciated. Thanks! Re: MIMXRT1176 ADP – SEGGER J-Link debugging issue Hi @HasanIqbalKhan , Thanks for your questions! As far as I know, when using JLink with the RT1170-ADP in MCUXpresso IDE, only "attach" is supported while direct debugging is not supported. This is likely a support issue with the JLink flashloader. In IAR, this issue has been resolved. We apologize for any inconvenience this may cause. Best regards, Gavin Re: MIMXRT1176 ADP – SEGGER J-Link debugging issue One more thing I tried, I connected an external MCU-Link and then tried debugging via the LinkServer in MCUXpresso IDE. The Execution reached main, I am able to step through from there, but when I try to resume execution it gives "Break at address "0x0" with no debug information available, or outside of program code.", and sometimes when I try to restart execution, it gives "Break at address "0x2230c8" with no debug information available, or outside of program code." For reference I am trying to run the "MIMXRT1176_dashboard_bt_ble_multiprofile" project, SW1 on the board is set to 01 and SW5 on the board is set to 000000000000. I tried to test with MCU-Link because the EVKB board uses the same and works fine. Also I do not think we can use Jlink, as it is clearly mentioned on their website that there is no support for octal flash, which the ADP board uses. Thanks. Re: MIMXRT1176 ADP – SEGGER J-Link debugging issue Is it possible to use debug via USB (J33) ? Re: MIMXRT1176 ADP – SEGGER J-Link debugging issue Hi @HasanIqbalKhan , 1. J33 is USB-OTG1 and cannot be used for debugging.  2. It’s not that JLink doesn’t support Octal Flash; it’s just that by default, it only recognizes the flash found on the EVK/EVKB. As for IAR, this is because a corresponding download algorithm is provided. If you’re interested in this topic, you can refer to the RT-UFL project. 3. For information on current debugger/IDE support, please refer to: AN14387: https://docs.nxp.com/bundle/AN14378/page/topics/download_images_to_ADP_board.html Best regards, Gavin
View full article
TJA1103 的勘误表 TJA1103 是否有勘误表? Re: Errata document for TJA1103 你好 naumova 再会! 是的,我们确实有一份勘误表,但它被列为安全文件;因此,您需要与我们签署保密协议才能访问。 请访问我们的官方网站,进入“支持”部分,然后选择“支持工单”。您可以在那里提交申请以请求访问权限,然后您将被转接到相应的团队。 对于可能由此导致的不便,我们深感抱歉。 希望这些信息对您有所帮助,如果您还需要其他帮助,请告诉我。 祝你今天过得愉快,一切顺利。
View full article
VFIO_FLS_MC: デバイスのリセットに失敗しました LX2160 : アプリケーションを実行しているときにエラーを下回っています。 再起動後は正常に動作します。次回も同じエラーが発生します。以下のように設定すると、この問題が発生します。 #export DPIO_COUNT=20 set -x #export DPIO_COUNT=10 # ls-listni #40Gが有効になっているかどうかを確認する #40Gポートが有効になっている場合は削除します(40G=dpmac.2) Echo DPNI.1 > /sys/bus/fsl-mc/drivers/fsl_dpaa2_eth/unbind Restool DPNI destroy DPNI.1 echo 0 > /proc/sys/kernel/randomize_va_space #export DPIO_COUNT=20 export DPMCP_COUNT=3 export FS_ENTRIES=12 #/usr/local/dpdk/dpaa2/dynamic_dpl.sh dpmac.3 /usr/local/dpdk/dpaa2/dynamic_dpl.sh dpni dpni -b 00:00:00:00:05:00 # dpni.1 00:00:00:00:05:01 # dpni.2 00:00:00:00:05:02 ls-addni --no-link #eth0 dpni.3 ls-addni --no-link #eth2 dpni.4 #/////出力///////// # VFIOからdprc.2の拘束を解除 Echo DPRC.2 > /sys/bus/FSL-MC/drivers/vfio-fsl-mc/unbind #dpn.2 は dynamicdpl.sh の出力です #dpni.1 dpmac.4-動的- # #restool dprc disconnect dprc.2 --endpoint=dpni.1 restool dpdmux create --num-ifs=3 --方法 DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.3 --endpoint2=dpdmux.0.0 restool dprc connect dprc.1 --endpoint1=dpni.1 --endpoint2=dpdmux.0.1 restool dprc connect dprc.1 --endpoint1=dpni.3--endpoint2=dpdmux.0.2 restool dpdmux create --num-ifs=3 --方法 DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.4 --endpoint2=dpdmux.1.0 restool dprc connect dprc.1 --endpoint1=dpni.2--endpoint2=dpdmux.1.1 restool dprc connect dprc.1 --endpoint1=dpni.4--endpoint2=dpdmux.1.2 #echo DPRC.2 > /sys/bus/FSL-MC/drivers/vfio-fsl-mc/bind # DPRCをVFIOに縛り付けろ Echo DPRC.2 > /sys/bus/FSL-MC/drivers/vfio-FSL-MC/Bind # DPRCを輸出する エクスポートDPRC=dprc.2 [ 3103.545665] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) [ 3103.545690] ------------[ ここから切り取り ]------------ [3103.545701]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.545703]リンクされているモジュール: libdes mali_dp [3103.545715]CPU: 2 PID: 3644 Comm: gnb_du_layer2 汚染なし 5.10.35 #5 [ 3103.545717]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.545721] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.545724] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.545727] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.545729] sp : ffff800012ef3c90 [ 3103.545731] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.545735] x27: 0000000000000000 x26: 0000000000000000 [ 3103.545740] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.545745] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.545749] x21: ffff0e7d1edc7800 x20: ffff0e7d3d39f040 [ 3103.545754] x19: ffff0e7d1d71db80 x18: 0000000000000001 [ 3103.545758] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.545763] x15: ffff0e7d3d39f040 x14: 00000000000007dd [ 3103.545767] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.545771] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.545776] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.545781] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.545785] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.545789] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.545793] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.545798]通話追跡: [ 3103.545802] vfio_fsl_mc_release+0xdc/0x190 [ 3103.545806] vfio_device_fops_release+0x24/0x48 [ 3103.545811] __fput+0x78/0x230 [ 3103.545814] __ __fput+0x10/0x20 [ 3103.545818] task_work_run+0x80/0x140 [ 3103.545821] do_exit+0x324/0xa08 [ 3103.545824] do_group_exit+0x44/0xa0 [ 3103.545826] __wake_up_parent+0x0/0x30 [ 3103.545831] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.545834] do_el0_svc+0x24/0x90 [ 3103.545839] el0_svc+0x14/0x20 [ 3103.545841] el0_sync_handler+0xb0/0xb8 [ 3103.545845] el0_sync+0x178/0x180 [ 3103.545847] ---[ トレース終了 d15991a0fbaef713 ]--- [ 3103.546381] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) [ 3103.546399] ------------[ ここから切り取り ]------------ [3103.546406]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.546411]リンクされているモジュール: libdes mali_dp [ 3103.546430]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [ 3103.546435]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.546441] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.546447] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.546453] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.546458] sp : ffff800012ef3c90 [ 3103.546462] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.546466] x27: 0000000000000000 x26: 0000000000000000 [ 3103.546471] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.546475] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.546479] x21: ffff0e7d02d77000 x20: ffff0e7d3d39f040 [ 3103.546484] x19: ffff0e7d1dc13480 x18: ffffb28536ab3470 [ 3103.546488] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.546492] x15: ffff0e7d3d39f040 x14: 0000000000000805 [ 3103.546497] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.546501] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.546506] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.546510] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.546514] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.546518] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.546522] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.546527]通話追跡: [ 3103.546529] vfio_fsl_mc_release+0xdc/0x190 [ 3103.546532] vfio_device_fops_release+0x24/0x48 [ 3103.546536] __fput+0x78/0x230 [ 3103.546539] __ __fput+0x10/0x20 [ 3103.546541] task_work_run+0x80/0x140 [ 3103.546544] do_exit+0x324/0xa08 [ 3103.546546] do_group_exit+0x44/0xa0 [ 3103.546548] __wake_up_parent+0x0/0x30 [ 3103.546552] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.546555] do_el0_svc+0x24/0x90 [ 3103.546557] el0_svc+0x14/0x20 [ 3103.546559] el0_sync_handler+0xb0/0xb8 [ 3103.546562] el0_sync+0x178/0x180 [ 3103.546564] ---[ トレース終了 d15991a0fbaef714 ]--- [ 3103.547072] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) [ 3103.547086] ------------[ ここから切り取り ]------------ [ 3103.547090]警告:CPU: 2 PID: 3644 ドライバー/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.547091]リンクされているモジュール: libdes mali_dp [3103.547098]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [ 3103.547100]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.547103] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.547105] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547107] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547109] sp : ffff800012ef3c90 [ 3103.547111] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.547116] x27: 0000000000000000 x26: 0000000000000000 [ 3103.547120] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.547125] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.547129] x21: ffff0e7d02d32000 x20: ffff0e7d3d39f040 [ 3103.547133] x19: ffff0e7d1dc13d80 x18: ffffb28536ab3470 [ 3103.547138] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.547142] x15: ffff0e7d3d39f040 x14: 000000000000082d [ 3103.547146] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.547151] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.547155] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.547159] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.547164] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.547168] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.547172] x1 : 0000000000000000 x0 : 0000000000000000 [3103.547176]通話追跡: [ 3103.547179] vfio_fsl_mc_release+0xdc/0x190 [ 3103.547182] vfio_device_fops_release+0x24/0x48 [ 3103.547185] __fput+0x78/0x230 [ 3103.547188] __ __fput+0x10/0x20 [ 3103.547190] task_work_run+0x80/0x140 [ 3103.547193] do_exit+0x324/0xa08 [ 3103.547195] do_group_exit+0x44/0xa0 [ 3103.547198] __wake_up_parent+0x0/0x30 [ 3103.547201] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.547204] do_el0_svc+0x24/0x90 [ 3103.547207] el0_svc+0x14/0x20 [ 3103.547209] el0_sync_handler+0xb0/0xb8 [ 3103.547211] el0_sync+0x178/0x180 [ 3103.547213] ---[ トレース終了 d15991a0fbaef715 ]--- [ 3103.547721] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) [ 3103.547735] ------------[ ここから切り取り ]------------ [ 3103.547739]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.547740]リンクされているモジュール: libdes mali_dp [ 3103.547748]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [ 3103.547750]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.547752] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.547755] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547757] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.547759] sp : ffff800012ef3c90 [ 3103.547761] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.547765] x27: 0000000000000000 x26: 0000000000000000 [ 3103.547770] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.547777] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.547781] x21: ffff0e7d1e989000 x20: ffff0e7d3d39f040 [ 3103.547785] x19: ffff0e7d1dcc6680 x18: ffffb28536ab3470 [ 3103.547790] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.547794] x15: ffff0e7d3d39f040 x14: 0000000000000855 [ 3103.547798] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.547802] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.547807] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.547812] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.547819] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.547823] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.547827] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.547831]通話追跡: [ 3103.547834] vfio_fsl_mc_release+0xdc/0x190 [ 3103.547837] vfio_device_fops_release+0x24/0x48 [ 3103.547840] __fput+0x78/0x230 [ 3103.547843] __ __fput+0x10/0x20 [ 3103.547845] task_work_run+0x80/0x140 [ 3103.547848] do_exit+0x324/0xa08 [ 3103.547850] do_group_exit+0x44/0xa0 [ 3103.547853] __wake_up_parent+0x0/0x30 [ 3103.547858] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.547861] do_el0_svc+0x24/0x90 [ 3103.547864] el0_svc+0x14/0x20 [ 3103.547866] el0_sync_handler+0xb0/0xb8 [ 3103.547868] el0_sync+0x178/0x180 [ 3103.547870] ---[ トレース終了 d15991a0fbaef716 ]--- [ 3103.548378] vfio-fsl-mc dprc.2:VFIO_FLS_MC: リセットデバイスが失敗しました (-13) [ 3103.548392] ------------[ ここから切り取り ]------------ [3103.548395]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.548397]リンクされているモジュール: libdes mali_dp [3103.548404]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [3103.548406]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.548408] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.548411] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.548413] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.548415] sp : ffff800012ef3c90 [ 3103.548417] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.548421] x27: 0000000000000000 x26: 0000000000000000 [ 3103.548426] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.548430] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.548437] x21: ffff0e7d1ea4e000 x20: ffff0e7d3d39f040 [ 3103.548442] x19: ffff0e7d1dcc6f80 x18: ffffb28536ab3470 [ 3103.548446] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.548450] x15: ffff0e7d3d39f040 x14: 000000000000087d [ 3103.548455] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.548459] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.548464] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.548468] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.548472] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.548479] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.548483] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.548488]通話追跡: [ 3103.548490] vfio_fsl_mc_release+0xdc/0x190 [ 3103.548493] vfio_device_fops_release+0x24/0x48 [ 3103.548497] __fput+0x78/0x230 [ 3103.548500] __ __fput+0x10/0x20 [ 3103.548502] task_work_run+0x80/0x140 [ 3103.548505] do_exit+0x324/0xa08 [ 3103.548507] do_group_exit+0x44/0xa0 [ 3103.548509] __wake_up_parent+0x0/0x30 [ 3103.548513] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.548516] do_el0_svc+0x24/0x90 [ 3103.548519] el0_svc+0x14/0x20 [ 3103.548523] el0_sync_handler+0xb0/0xb8 [ 3103.548526] el0_sync+0x178/0x180 [ 3103.548528] ---[ トレース終了 d15991a0fbaef717 ]--- [ 3103.549035] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) [ 3103.549049] ------------[ ここから切り取り ]------------ [3103.549052]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.549054]リンクされているモジュール: libdes mali_dp [3103.549060]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [3103.549062]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.549065] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.549067] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549069] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549071] sp : ffff800012ef3c90 [ 3103.549073] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.549077] x27: 0000000000000000 x26: 0000000000000000 [ 3103.549082] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.549086] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.549090] x21: ffff0e7d1dd80000 x20: ffff0e7d3d39f040 [ 3103.549094] x19: ffff0e7d1dc09880 x18: ffffb28536ab3470 [ 3103.549098] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.549103] x15: ffff0e7d3d39f040 x14: 00000000000008a5 [ 3103.549107] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.549111] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.549116] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.549120] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.549124] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.549129] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.549133] x1 : 0000000000000000 x0 : 0000000000000000 [3103.549137]通話追跡: [ 3103.549139] vfio_fsl_mc_release+0xdc/0x190 [ 3103.549142] vfio_device_fops_release+0x24/0x48 [ 3103.549145] __fput+0x78/0x230 [ 3103.549148] __ __fput+0x10/0x20 [ 3103.549151] task_work_run+0x80/0x140 [ 3103.549153] do_exit+0x324/0xa08 [ 3103.549155] do_group_exit+0x44/0xa0 [ 3103.549158] __wake_up_parent+0x0/0x30 [ 3103.549161] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.549164] do_el0_svc+0x24/0x90 [ 3103.549166] el0_svc+0x14/0x20 [ 3103.549168] el0_sync_handler+0xb0/0xb8 [ 3103.549171] el0_sync+0x178/0x180 [ 3103.549172] ---[ トレース終了 d15991a0fbaef718 ]--- [ 3103.549679] vfio-fsl-mc dprc.2:VFIO_FLS_MC: リセットデバイスが失敗しました (-13) [ 3103.549693] ------------[ ここから切り取り ]------------ [ 3103.549699]警告:CPU: 2 PID: 3644 ドライバ/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.549701]リンクされているモジュール: libdes mali_dp [3103.549708]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [3103.549710]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.549712] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.549715] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549717] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.549718] sp : ffff800012ef3c90 [ 3103.549720] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.549725] x27: 0000000000000000 x26: 0000000000000000 [ 3103.549729] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.549733] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.549738] x21: ffff0e7d1dd9dc00 x20: ffff0e7d3d39f040 [ 3103.549744] x19: ffff0e7d1d6adc80 x18: ffffb28536ab3470 [ 3103.549749] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.549753] x15: ffff0e7d3d39f040 x14: 00000000000008cd [ 3103.549757] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.549762] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.549766] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.549771] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.549775] x5 : ffff0e83fc27d860 x4 : 0000000000000000 [ 3103.549782] x3 : 0000000000000027 x2 : 0000000000000000 [ 3103.549786] x1 : 0000000000000000 x0 : 0000000000000000 [ 3103.549790]通話追跡: [ 3103.549792] vfio_fsl_mc_release+0xdc/0x190 [ 3103.549795] vfio_device_fops_release+0x24/0x48 [ 3103.549798] __fput+0x78/0x230 [ 3103.549801] __ __fput+0x10/0x20 [ 3103.549804] task_work_run+0x80/0x140 [ 3103.549806] do_exit+0x324/0xa08 [ 3103.549809] do_group_exit+0x44/0xa0 [ 3103.549811] __wake_up_parent+0x0/0x30 [ 3103.549814] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.549818] do_el0_svc+0x24/0x90 [ 3103.549822] el0_svc+0x14/0x20 [ 3103.549824] el0_sync_handler+0xb0/0xb8 [ 3103.549827] el0_sync+0x178/0x180 [ 3103.549829] ---[ トレース終了 d15991a0fbaef719 ]--- [ 3103.550346] vfio-fsl-mc dprc.2:VFIO_FLS_MC: リセットデバイスが失敗しました (-13) [ 3103.550360] ------------[ ここから切り取り ]------------ [3103.550368]警告:CPU: 2 PID: 3644 ドライバー/vfio/fsl-mc/vfio_fsl_mc.c:212 vfio_fsl_mc_release+0xdc/0x190 [ 3103.550373]リンクされているモジュール: libdes mali_dp [3103.550393]CPU: 2 PID: 3644 Comm: gnb_du_layer2 Tainted: GW 5.10.35 #5 [3103.550398]ハードウェア名:NXP Layerscape LX2160ARDB (DT) [ 3103.550404] psstate: 60000005 (nZCv daif -PAN -UAO -TCO BTYPE=--) [ 3103.550410] pc : vfio_fsl_mc_release+0xdc/0x190 [ 3103.550416] lr : vfio_fsl_mc_release+0xdc/0x190 [ 3103.550420] sp : ffff800012ef3c90 [ 3103.550426] x29: ffff800012ef3c90 x28: ffff0e7d3d39f040 [ 3103.550432] x27: 0000000000000000 x26: 0000000000000000 [ 3103.550437] x25: 0000000000000000 x24: ffff0e7d3d39f440 [ 3103.550441] x23: ffff0e7d030cc800 x22: 00000000fffffff3 [ 3103.550456] x21: ffff0e7d1ee17800 x20: ffff0e7d3d39f040 [ 3103.550469] x19: ffff0e7d1dc81580 x18: ffffb28536ab3470 [ 3103.550483] x17: ffff0e7d00001088 x16: ffff0e7d000010a8 [ 3103.550496] x15: ffff0e7d3d39f040 x14: 00000000000008f5 [ 3103.550510] x13: ffff0e7d3d39f4a0 x12: 00000000ffffffea [ 3103.550523] x11: ffffb28536b23468 x10: ffffb28536b0b428 [ 3103.550536] x9 : ffffb28536b0b480 x8 : 0000000000017fe8 [ 3103.550549] x7 : c0000000ffffefff x6 : 0000000000000001 [ 3103.550564] x5 : 0000000000000000 x4 : ffff0e83fc27d860 [ 3103.550577] x3 : ffff0e83fc284770 x2 : 0000000000000000 [ 3103.550587] x1 : 0000000000000000 x0 : 0000000000000000 [3103.550591]通話追跡: [ 3103.550594] vfio_fsl_mc_release+0xdc/0x190 [ 3103.550597] vfio_device_fops_release+0x24/0x48 [ 3103.550600] __fput+0x78/0x230 [ 3103.550603] __ __fput+0x10/0x20 [ 3103.550605] task_work_run+0x80/0x140 [ 3103.550608] do_exit+0x324/0xa08 [ 3103.550610] do_group_exit+0x44/0xa0 [ 3103.550612] __wake_up_parent+0x0/0x30 [ 3103.550616] el0_svc_common.constprop.0+0x78/0x1a0 [ 3103.550618] do_el0_svc+0x24/0x90 [ 3103.550621] el0_svc+0x14/0x20 [ 3103.550623] el0_sync_handler+0xb0/0xb8 [ 3103.550626] el0_sync+0x178/0x180 [ 3103.550628] ---[ トレース終了 d15991a0fbaef71a ]--- [ 3103.551136] vfio-fsl-mc dprc.2:VFIO_FLS_MC: デバイスのリセットに失敗しました (-13) Re: VFIO_FLS_MC: reset device has failed @Bio_TICFSL さん、ありがとうございます。実行して確認します。 Re: VFIO_FLS_MC: reset device has failed こんにちは、 根本的な問題は、セットアップスクリプトに restool dprc assign 手順が欠落していることです。あなたのスクリプト: dprc.1 (ルートコンテナ)の下に dpdmux.0 と dpdmux.1 を作成します。 dpni.1 / dpni.2 を接続します(これらは dprc.2 、VFIOコンテナ内に存在します)これらのDPDMUXインターフェースに繋がります。 dprc.2 をVFIOドライバーに割り当てます。 アプリケーションが終了すると、VFIOドライバーは dprc.2 内のすべてのオブジェクトをリセットしようとします。しかし、 dpni.1 / dpni.2 は依然として dprc.1 に存在する dpdmux.0 / dpdmux.1 オブジェクトと外部接続されています。 MCファームウェアはこれらのクロスコンテナ接続のため、コンテナをきれいにリセットできず、→返品 -13 権限を持っていません(許可拒否)。 再起動後に機能する理由:コールドブート後、DPAA2オブジェクトはクリーンな初期状態になります。最初の試みは成功した。しかし、終了時にDPDMUX接続が適切に切断されないため、MCは部分的な状態のままになる。次回の実行時(再起動なし)にも、コンテナのリセットが再び失敗します。 修正:DPDMUXオブジェクトに restool dprc assign を追加 DPDMUXオブジェクトは dprc.2 に割り当てる必要があります。VFIOに結合する前に。これにより、これらのオブジェクトはVFIOコンテナの所有物であり、コンテナが解放されるとリセット可能であることがMCに伝えられます。 DPDMUXオブジェクトを作成/接続した 後 、 dprc.2 VFIOに再バインドする 前に 、以下の行を挿入してください。 # Assign dpdmux objects into dprc.2 so VFIO can reset them cleanly restool dprc assign dprc.1 --object=dpdmux.0 --child=dprc.2 --plugged=1 restool dprc assign dprc.1 --object=dpdmux.1 --child=dprc.2 --plugged=1 # Now bind dprc.2 back to VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind export DPRC=dprc.2   修正後のスクリプトセクションは次のようになります。 # Unbind dprc.2 from VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/unbind # Create and connect DPDMUX for port dpmac.3 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.3 --endpoint2=dpdmux.0.0 restool dprc connect dprc.1 --endpoint1=dpni.1 --endpoint2=dpdmux.0.1 restool dprc connect dprc.1 --endpoint1=dpni.3 --endpoint2=dpdmux.0.2 # Create and connect DPDMUX for port dpmac.4 restool dpdmux create --num-ifs=3 --method DPDMUX_METHOD_MAC --max-dmat-entries=3 --manip=DPDMUX_MANIP_NONE restool dprc connect dprc.1 --endpoint1=dpmac.4 --endpoint2=dpdmux.1.0 restool dprc connect dprc.1 --endpoint1=dpni.2 --endpoint2=dpdmux.1.1 restool dprc connect dprc.1 --endpoint1=dpni.4 --endpoint2=dpdmux.1.2 # *** KEY FIX: Assign dpdmux objects to dprc.2 so VFIO can reset them *** restool dprc assign dprc.1 --object=dpdmux.0 --child=dprc.2 --plugged=1 restool dprc assign dprc.1 --object=dpdmux.1 --child=dprc.2 --plugged=1 # Bind dprc.2 back to VFIO echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind export DPRC=dprc.2   追加の推奨事項 MCファームウェアをBSPの最新バージョンにアップデートしてください。 実行間の適切なクリーンアップ(再起動なし):セットアップスクリプトを再実行する前に、以前に作成されたDPDMUXオブジェクトを破棄して、クリーンな状態を確保します。 restool dpdmux destroy dpdmux.0 restool dpdmux destroy dpdmux.1     -13 エラーに伴うファームウェアレベルのエラーの詳細については、 /dev/dpaa2_mc_console にある MC コンソールログを確認してください 。 よろしくお願いします。
View full article
[i.MX8MQ] Is MIPI-DSI SSC (Spread Spectrum Clocking) enabled or disabled by default? Hi there,  On i.MX8MQ platform, we want to confirm what MIPI-DSI SSC default setting is? ON or OFF? Re: [i.MX8MQ] Is MIPI-DSI SSC (Spread Spectrum Clocking) enabled or disabled by default? Hi, SSC is disabled (OFF) in our testing. We are not sure whether the enabled (ON) case has been tested. You may find the discussion below helpful: https://community.nxp.com/t5/i-MX-Processors/iMX8M-Mini-Spread-Spectrum/m-p/1024187. Thanks
View full article
[i.MX8MQ] MIPI-DSI SSC(扩频时钟)默认是启用还是禁用? 您好, 在 i.MX8MQ 平台上,我们想确认 MIPI-DSI SSC 的默认设置是什么?是开启还是关闭? Re: [i.MX8MQ] Is MIPI-DSI SSC (Spread Spectrum Clocking) enabled or disabled by default? 您好, 在我们的测试中,SSC 已禁用(关闭)。 我们不确定启用(ON)的情况是否已经过测试。 您或许会发现以下讨论很有帮助: https://community.nxp.com/t5/i-MX-Processors/iMX8M-Mini-Spread-Spectrum/mp/1024187 . 谢谢!
View full article
求助关于RT1052显示旋转问题 因为购买的屏幕是竖屏,而我需要横屏显示。我使用的是guiguider生成RT1052的基础显示代码 并且添加软件旋转 disp_drv.sw_rotate = 1; disp_drv.rotated = 1;   设置成单缓冲 SDK_ALIGN( __attribute__((section("lvglDisplayBuffer"))) static uint8_t s_frameBuffer[1][DEMO_FB_SIZE], DEMO_FB_ALIGN); SDK_ALIGN( __attribute__((section("lvglDisplayBuffer"))) static uint8_t s_lvglBuffer[DEMO_DB_SIZE], DEMO_FB_ALIGN); 屏幕能够正常显示,但是刷新速度太慢,不符合我的需求。   设置成双缓冲 SDK_ALIGN( __attribute__((section("lvglDisplayBuffer"))) static uint8_t s_frameBuffer[2][DEMO_FB_SIZE], DEMO_FB_ALIGN); 只有背光亮,屏幕黑屏。 这是为什么?   #if FB_USE_SRAM static void DEMO_WaitVsync(lv_disp_drv_t *disp_drv) { s_framePending = true; #if defined(SDK_OS_FREE_RTOS) if (xSemaphoreTake(s_frameSema, portMAX_DELAY) != pdTRUE) { PRINTF("Display flush failed\r\n"); assert(0); } #else while (s_framePending) { } #endif } static void copy_area(const lv_area_t *area, lv_color_t *color_p, uint8_t *fb, uint32_t fbStrideBytes) { uint32_t y; uint32_t areaWidth = lv_area_get_width(area); fb += (area->y1 * fbStrideBytes + area->x1 * sizeof(lv_color_t)); for (y = area->y1; y <= area->y2; y++) { lv_memcpy(fb, color_p, areaWidth * sizeof(lv_color_t)); fb += fbStrideBytes; color_p += areaWidth; } } static void DEMO_FlushDisplay(lv_disp_drv_t *disp_drv, const lv_area_t *area, lv_color_t *color_p) { /* Wait VSYNC for each small update. */ DEMO_WaitVsync(disp_drv); /* Copy data from draw buffer to frame buffer. */ copy_area(area, color_p, (uint8_t*) s_frameBuffer, LCD_WIDTH * LCD_FB_BYTE_PER_PIXEL); SCB_CleanInvalidateDCache(); lv_disp_flush_ready(disp_drv); } #else static void DEMO_FlushDisplay(lv_disp_drv_t *disp_drv, const lv_area_t *area, lv_color_t *color_p) { // DCACHE_CleanByRange((uint32_t)color_p, DEMO_FB_SIZE); DCACHE_CleanInvalidateByRange((uint32_t)color_p, DEMO_FB_SIZE); ELCDIF_SetNextBufferAddr(LCDIF, (uint32_t)color_p); s_framePending = true; #if defined(SDK_OS_FREE_RTOS) if (xSemaphoreTake(s_frameSema, portMAX_DELAY) == pdTRUE) { /* IMPORTANT!!! * Inform the graphics library that you are ready with the flushing*/ lv_disp_flush_ready(disp_drv); } else { PRINTF("Display flush failed\r\n"); assert(0); } #else while (s_framePending) { } /* IMPORTANT!!! * Inform the graphics library that you are ready with the flushing*/ lv_disp_flush_ready(disp_drv); #endif } #endif i.MXRT 105x Re: 求助关于RT1052显示旋转问题 Hi @dsd , 感谢您的问题! 首先,请检查以下LVGL的限制,启用了full_refresh=1时,不支持屏幕旋转。请参考: 1. https://github.com/lvgl/lvgl/issues/4060 2. https://forum.lvgl.io/t/why-cannot-rotate-a-full-refreshed-display/10490/3   另外,RT1050有硬件pxp支持旋转,这是更推荐的方案,请参考:https://docs.nxp.com/bundle/GUIGUIDERUG-1.6.1/page/topics/rotate_screen_and_widgets.html 以及SDK中的PXP旋转相关demo。   Best regards, Gavin Re: 求助关于RT1052显示旋转问题 Helllo, 在使用 NXP i.MX RT1052 结合 Guiguider (LVGL) 进行屏幕旋转开发时,你遇到的“单缓冲刷新慢、双缓冲黑屏”问题,核心原因在于软件旋转(Software Rotate)与硬件 ELCDIF 控制器、双缓冲切换机制以及内存地址索引没有适配好。 Best Regards Re: 求助关于RT1052显示旋转问题 非常感谢,pxp旋转确实可行,完美解决问题
View full article
ヒューズを焼損させずにHABをテストする 私はIMXRT1024コアの開発に取り組んでおり、ヒューズを焼損させることなくHABをテストしたいと考えています。データシートによると、すべてのヒューズにはシャドウレジスタがあり、CPU/ROMはそのシャドウレジスタから読み取られます。 シャドウレジスタを書き込み、ブートROMがボードがHAB対応であると認識するようなシナリオを作成することを考えています。しかし、ブートROMの実行はまだ初期段階なので、シャドウレジスタを活用してテスト環境を作る方法を教えてもらえますか? Q.2 -> もし閉鎖されたボードでHAB認証が失敗した場合、監査報告書はどうやって入手できますか? Re: Testing HAB without burning fuses こんにちは、 @Abhay2080。 この スレッドでのカン・リーの回答を参照してください。ヒューズをプログラムせずにHABをテストするためのいくつかの方法について説明しています。 2つ目のご質問についてですが、セキュアプロビジョニングツールのご利用を強くお勧めします。HAB対応イメージの作成プロセスが大幅に簡素化されます。このツールは自動的にCSFを生成し、画像を準備してHABが起動シーケンス中に正しく認証できるようにするため、このようなアプリケーションを扱う標準的なツールとなっています。認証済み (HAB)イメージの起動 手順に従うことができます。 ヒューズの焼きは一度しかできず、その後プロセッサは認証済み画像しか実行できないことを覚えておいてください。 BR ハビブ Re: Testing HAB without burning fuses ええ、カン・リーの回答は既に読みましたが、シャドウレジスターについては何も記載されていませんでした。そこで、私の質問は単純にシャドウレジスタを使ってテストすることが可能かどうかです。 監査ログについては、記録目的でのみ必要です。SPTを適切に使用すれば、HABをうまく生成できると理解しています。 Re: Testing HAB without burning fuses こんにちは、 @Abhay2080 さん。 Kan Li氏が推奨する方法に従ってください。HAB認証は、デバイスがOpenセキュリティ構成中であっても実施されます。これはRMの第9.3.6章「ブートセキュリティ設定」に記載されています。したがって、ROMブート時に生成されたHABイベントログを確認し、HAB認証プロセスが正しく実行されているかを確認することも可能です。 シャドウレジスタの主な目的は、RMの図23-1「OCOTPシステムレベルブロック図」に示されているように、デバイスがロードするOTPヒューズ値をソフトウェアでアクセス可能な表現を提供することです。 監査ログについてですが、あなたが言っているのは起動認証プロセス中にROMが生成するHABイベントログのことです。私の理解は正しいでしょうか?もしそうなら、この コミュニティ投稿 でGavin Jiaはこのログを観察する2つの方法を説明しています。特に、質問2への回答は顧客の問い合わせに直接答えています。 BR ハビブ
View full article
jailhouse DTS for 9x9 imx.93 こんにちは。9x9 imx.93版の「Jailhouse」のDTSファイルは提供していますか?11x11用のものしか見つかりません。 よろしくお願いします。 デビッド Re: jailhouse DTS for 9x9 imx.93 こんにちは、 このデバイスツリーは、次回のBSPリリースに含まれる予定です。 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright 2023 NXP */ /dts-v1/; #include / { model = "NXP i.MX93 9x9 QSB"; compatible = "fsl,imx93-9x9-qsb", "fsl,imx93"; interrupt-parent = <&gic>; #address-cells = <2>; #size-cells = <2>; aliases { mmc0 = &usdhc1; serial1 = &lpuart2; }; cpus { #address-cells = <1>; #size-cells = <0>; A55_0: cpu@0 { device_type = "cpu"; compatible = "arm,cortex-a55"; reg = <0x0>; enable-method = "psci"; #cooling-cells = <2>; }; }; psci { compatible = "arm,psci-1.0"; method = "smc"; }; gic: interrupt-controller@48000000 { compatible = "arm,gic-v3"; reg = <0 0x48000000 0 0x10000>, <0 0x48040000 0 0xc0000>; #interrupt-cells = <3>; interrupt-controller; interrupts = ; interrupt-parent = <&gic>; }; timer { compatible = "arm,armv8-timer"; interrupts = , , , ; clock-frequency = <24000000>; }; clk_dummy: clock-dummy { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <0>; clock-output-names = "clk_dummy"; }; clk_400m: clock-400m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <200000000>; clock-output-names = "200m"; }; osc_24m: clock-osc-24m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <24000000>; clock-output-names = "osc_24m"; }; pci@fd700000 { compatible = "pci-host-ecam-generic"; device_type = "pci"; bus-range = <0 0>; #address-cells = <3>; #size-cells = <2>; #interrupt-cells = <1>; interrupt-map-mask = <0 0 0 7>; interrupt-map = <0 0 0 1 &gic GIC_SPI 227 IRQ_TYPE_EDGE_RISING>, <0 0 0 2 &gic GIC_SPI 228 IRQ_TYPE_EDGE_RISING>, <0 0 0 3 &gic GIC_SPI 229 IRQ_TYPE_EDGE_RISING>, <0 0 0 4 &gic GIC_SPI 230 IRQ_TYPE_EDGE_RISING>; reg = <0x0 0xfd700000 0x0 0x100000>; ranges = <0x02000000 0x00 0x10000000 0x0 0x10000000 0x00 0x10000>; }; soc@0 { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; ranges = <0x0 0x0 0x0 0x80000000>, <0x28000000 0x0 0x28000000 0x10000000>; aips1: bus@44000000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x44000000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; lpuart2: serial@44390000 { compatible = "fsl,imx93-lpuart", "fsl,imx8ulp-lpuart", "fsl,imx7ulp-lpuart"; reg = <0x44390000 0x1000>; interrupts = ; status = "disabled"; }; }; aips3: bus@42800000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x42800000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; usdhc1: mmc@42850000 { compatible = "fsl,imx93-usdhc", "fsl,imx8mm-usdhc"; reg = <0x42850000 0x10000>; interrupts = ; fsl,tuning-start-tap = <20>; fsl,tuning-step= <2>; status = "disabled"; }; }; }; }; &lpuart2 { clocks = <&osc_24m>; clock-names = "ipg"; status = "okay"; }; &usdhc1 { clocks = <&clk_dummy>, <&clk_dummy>, <&clk_400m>; clock-names = "ipg", "ahb", "per"; bus-width = <8>; non-removable; status = "okay"; }; よろしくお願いいたします。 Re: jailhouse DTS for 9x9 imx.93 9x9 用の qsb jailhouse に対応するルートセル設定ファイルもお持ちですか? ありがとう
View full article
TJA1103の正誤表 TJA1103の正誤表はありますか? Re: Errata document for TJA1103 こんにちは、ナウモワさん 良い一日! はい、訂正書はありますが、それはセキュアファイルとして分類されています。したがって、アクセスするには当事務所とNDAに署名する必要があります。 公式ウェブサイトを訪問し、「サポート」セクションから「サポートチケット」を選択してください。そこでCASEを開いてアクセスを申請でき、適切なチームに案内されます。 ご迷惑をおかけして申し訳ありません。 この情報がお役に立てば幸いです。他に何かご不明な点がありましたら、お気軽にお問い合わせください。 良い一日をお過ごしください。幸運を祈ります。
View full article
NXP Config Tools 26.06 for i.MX 无法加载已保存的配置 你好, 在评估 i.MX95 的新版 DDR 配置时,我发现配置工具中似乎存在一个错误。 以下是我具体的操作步骤,以便可以重现该问题: 1. 安装了该工具的Linux版本。 2. 创建了一个新配置。 3. 选定处理器 MIMX9596xxxxN。 4. 将预设更改为“LPDDR4X EVK / FRDM 15x15 4000MTs 配置”。 5. 保存配置,然后关闭工具。 6. 重新打开工具并加载已保存的配置。 此时根本不显示DDR配置信息。 至少 26.03 版本启动时 MCU 未被选中(手动选择即可解决问题),现在这个问题无法解决。 非常感谢您的帮助。 此致, 埃马努埃莱 Re: NXP Config Tools 26.06 for i.MX not loading saved configuration 该工具的 Windows 版本也存在同样的问题。 附图。 Re: NXP Config Tools 26.06 for i.MX not loading saved configuration 你好, 感谢您报告该工具的这个漏洞。 我能看出我这边的问题所在。 我会将此事上报给内部团队,以便尽快解决。 顺祝商祺! Re: NXP Config Tools 26.06 for i.MX not loading saved configuration 是否有更新或变通方法?它根本无法使用。 Re: NXP Config Tools 26.06 for i.MX not loading saved configuration 我刚刚安装并测试了 26.09 版本。按照 Emanuele 列出的步骤进行操作,但针对的是 MIMX9529xxxxx。 错误行为相同,无法加载先前创建的配置文件。 已在 Ubuntu 24.04 上测试。 顺祝商祺!
View full article
[i.MX8MQ] MIPI-DSI SSC(スペクトラム拡散クロッキング)はデフォルトで有効になっていますか、それとも無効になっていますか? こんにちは、 i.MX8MQプラットフォーム上で、MIPI-DSI SSCのデフォルト設定が何なのか確認したいのですが、オンかオフか? Re: [i.MX8MQ] Is MIPI-DSI SSC (Spread Spectrum Clocking) enabled or disabled by default? こんにちは、 当社のテスト環境では、SSCは無効(OFF)になっています。 有効(ON) CASEがテストされたかどうかは不明です。 以下の議論が参考になるかもしれません。 https://community.nxp.com/t5/i-MX-Processors/iMX8M-Mini-Spread-Spectrum/mp/1024187 . よろしくお願いします。
View full article
NXP Config Tools 26.06 for i.MX not loading saved configuration Hello, While evaluating the new version of the DDR configuration for the i.MX95, I came across what looks like a bug in the configuration tool. Here is exactly what I did, so the behavior can be reproduced: 1. Installed the Linux version of the tool. 2. Created a new configuration. 3. Selected processor MIMX9596xxxxN. 4. Changed the preset to "LPDDR4X EVK / FRDM 15x15 4000MTs Configuration". 5. Saved the configuration, then closed the tool. 6. Reopened the tool and loaded the saved configuration. At that point the DDR configuration is not displayed at all. At least the 26.03 version was starting with MCU unselected (selecting it manually solves the problem), now there is no way to solve the problem. Thank you very much for your help. Best regards, Emanuele Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Also the windows version of the tool shows the same problem. Attached screenshots. Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Hello, Thank you for report this bug in the tool. I was able to see the issue on my side. I will report it with internal team to solve it as soon as possible. Best regards. Re: NXP Config Tools 26.06 for i.MX not loading saved configuration Is there an update or a workaround? It is impossible to use it Re: NXP Config Tools 26.06 for i.MX not loading saved configuration I've just installed and tested version 26.09. Followed the same steps that Emanuele listed but for MIMX9529xxxxx. The incorrect behavior is the same, impossible to load previously created config files. Tested on Ubuntu 24.04. Best regards,
View full article
监狱 DTS 适用于 9x9 imx.93 您好 - 请问你们提供适用于 9x9 imx.93 的 jailhouse 的 DTS 文件吗?我只能找到11x11尺寸的。 谢谢! 大卫 Re: jailhouse DTS for 9x9 imx.93 你好, 该设备树将包含在下一个 电路板支持包。 版本中。 // SPDX-License-Identifier: (GPL-2.0+ OR MIT) /* * Copyright 2023 NXP */ /dts-v1/; #include / { model = "NXP i.MX93 9x9 QSB"; compatible = "fsl,imx93-9x9-qsb", "fsl,imx93"; interrupt-parent = <&gic>; #address-cells = <2>; #size-cells = <2>; aliases { mmc0 = &usdhc1; serial1 = &lpuart2; }; cpus { #address-cells = <1>; #size-cells = <0>; A55_0: cpu@0 { device_type = "cpu"; compatible = "arm,cortex-a55"; reg = <0x0>; enable-method = "psci"; #cooling-cells = <2>; }; }; psci { compatible = "arm,psci-1.0"; method = "smc"; }; gic: interrupt-controller@48000000 { compatible = "arm,gic-v3"; reg = <0 0x48000000 0 0x10000>, <0 0x48040000 0 0xc0000>; #interrupt-cells = <3>; interrupt-controller; interrupts = ; interrupt-parent = <&gic>; }; timer { compatible = "arm,armv8-timer"; interrupts = , , , ; clock-frequency = <24000000>; }; clk_dummy: clock-dummy { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <0>; clock-output-names = "clk_dummy"; }; clk_400m: clock-400m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <200000000>; clock-output-names = "200m"; }; osc_24m: clock-osc-24m { compatible = "fixed-clock"; #clock-cells = <0>; clock-frequency = <24000000>; clock-output-names = "osc_24m"; }; pci@fd700000 { compatible = "pci-host-ecam-generic"; device_type = "pci"; bus-range = <0 0>; #address-cells = <3>; #size-cells = <2>; #interrupt-cells = <1>; interrupt-map-mask = <0 0 0 7>; interrupt-map = <0 0 0 1 &gic GIC_SPI 227 IRQ_TYPE_EDGE_RISING>, <0 0 0 2 &gic GIC_SPI 228 IRQ_TYPE_EDGE_RISING>, <0 0 0 3 &gic GIC_SPI 229 IRQ_TYPE_EDGE_RISING>, <0 0 0 4 &gic GIC_SPI 230 IRQ_TYPE_EDGE_RISING>; reg = <0x0 0xfd700000 0x0 0x100000>; ranges = <0x02000000 0x00 0x10000000 0x0 0x10000000 0x00 0x10000>; }; soc@0 { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <1>; ranges = <0x0 0x0 0x0 0x80000000>, <0x28000000 0x0 0x28000000 0x10000000>; aips1: bus@44000000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x44000000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; lpuart2: serial@44390000 { compatible = "fsl,imx93-lpuart", "fsl,imx8ulp-lpuart", "fsl,imx7ulp-lpuart"; reg = <0x44390000 0x1000>; interrupts = ; status = "disabled"; }; }; aips3: bus@42800000 { compatible = "fsl,aips-bus", "simple-bus"; reg = <0x42800000 0x800000>; #address-cells = <1>; #size-cells = <1>; ranges; usdhc1: mmc@42850000 { compatible = "fsl,imx93-usdhc", "fsl,imx8mm-usdhc"; reg = <0x42850000 0x10000>; interrupts = ; fsl,tuning-start-tap = <20>; fsl,tuning-step= <2>; status = "disabled"; }; }; }; }; &lpuart2 { clocks = <&osc_24m>; clock-names = "ipg"; status = "okay"; }; &usdhc1 { clocks = <&clk_dummy>, <&clk_dummy>, <&clk_400m>; clock-names = "ipg", "ahb", "per"; bus-width = <8>; non-removable; status = "okay"; }; 顺祝商祺! Re: jailhouse DTS for 9x9 imx.93 您是否也有适用于 9x9 上 qsb jailhouse 的匹配根单元配置文件? 谢谢
View full article
PEmicro GDB Launch Failure in S32 Design Studio for Power Architecture v2.1 Hi, The board I am testing is MTRCKTSPS5744P (3-Phase PMSM Motor Control Development Kit with MPC5744P MCU). For some reason, the download process doesn't go well. This window pops up after failure in downloading when I click debug button. eunwoo_lee_0-1789496057004.png An window pops up showing this error message. Error in services launch sequence PEmicro GDB Launch Failure : The GDB Server was not able to establish a connection to the target processor. Please check your connections and power. Verify that the launch settings in the Debug Configuration are accurate. Console panel displays this message. Connection from "127.0.0.1" via 127.0.0.1. Connection from port "53438" to 7224 PE-ERROR: Warning. Can't read registers while part is running. PE-ERROR: Warning. Can't read memory while part is running. @0 (4 bytes) PE-ERROR: Warning. Can't read memory while part is running. @0 (4 bytes) PE-ERROR: Warning. Can't read registers while part is running. PE-ERROR: Warning. Can't read memory while part is running. @0 (4 bytes) PE-ERROR: Warning. Can't read memory while part is running. @0 (4 bytes) PE-ERROR: Warning. Can't Write Binary while part is running. 40001000 - Length of: 0 - Value of: Binary Data PE-ERROR: Warning. Can't Write Binary while part is running. 40001000 - Length of: 460 - Value of: Binary Data PE-ERROR: Warning. Can't Write Binary while part is running. 40001460 - Length of: 460 - Value of: Binary Data PE-ERROR: Warning. Can't Write Binary while part is running. 400018c0 - Length of: 460 - Value of: Binary Data PE-ERROR: Warning. Can't Write Binary while part is running. 40001d20 - Length of: 2e0 - Value of: Binary Data PE-ERROR: GDB Client Processing : Exception Occured : PROGRAM EXCEPTION! EXCEPTION CLASS: EIDCONNCLOSEDGRACEFULLY MESSAGE: CONNECTION CLOSED GRACEFULLY. ADDRESS 0X0046EA89 Disconnected from "127.0.0.1" via 127.0.0.1. Disconnection by port "53438" from 7224 Target Disconnected. Is there any solution you know for this problem? Thanks. Re: PEmicro GDB Launch Failure in S32 Design Studio for Power Architecture v2.1 Hello, Is there any solution you know for this problem? As the message explains you cannot write/read registers on the fly. First stop the execution of the code in debugger and then you can modify the registers, memory, etc... The MPC5744P is running user code and the P&E probe is unable to halt the device, therefore all memory/register accesses fail and the download operation aborts. This looks less like a flash programming problem and more like a debugger failing to halt the MPC5744P before download. Is there for example SW with SWT0 enabled in the microcontroller? Or is it a fresh sample with no SW running? Best regards, Peter Re: PEmicro GDB Launch Failure in S32 Design Studio for Power Architecture v2.1 I solved this problem by replacing the flat ribbon cable. Although the cable seems good in terms of connection, it fails to connect the debugger. I guess the cable is susceptible to crosstalk or line-to-line noise. I ended up making it work by creating shorter cable.
View full article
在ubuntu上,如何使用mcuxpresso-secure-provisioning软件来固件加密加密并烧写到芯片 首先,我使用的芯片是 MCXN947。 我已经在我的Ubuntu系统中下载并安装了mcuxpresso-secure-provisioning-26.09-1_amd64-ubuntu26.deb软件包。 那么如何使用该软件生成已签名和加密的sb格式文件呢? 我已经观看了视频,对 bin 文件进行了签名和加密,并在 Windows 系统中成功地将 sb 文件写入了芯片。 Ubuntu系统上有视频操作软件吗?是否有关于签名和加密bin文件的命令行的相关文档? 谢谢! Re: 在ubuntu上,怎样使用 mcuxpresso-secure-provisioning 软件给固件签名加密并烧写到芯片 嗨@justdomyself 文档: https://docs.mcuxpresso.nxp.com/secure/latest/ 描述 MCXN 设备工作流程的章节: https://docs.mcuxpresso.nxp.com/secure/latest/06_processor_specific_workflow.html#n23x-n24x-n52x-n53x-n54x-n94x-device-workflow 命令行支持: https://docs.mcuxpresso.nxp.com/secure/latest/08_command_line_operations.html 另请参阅 securep.exe 打印 - cli - 示例 Ubuntu 和 Windows 上的用户体验非常相似。如果遇到任何问题,请参阅故障排除部分: https://docs.mcuxpresso.nxp.com/secure/latest/09_troubleshooting.html
View full article
MIMXRT700 EVK Battery Connection and External Power Up Clarification Hi Team, We are currently working on the MIMXRT700 EVK and need clarification regarding battery connection and external board power-up. We observed that the PMIC IC has a VBAT input, but we are unable to identify the exact connector/header on the EVK where a battery can be connected directly. Could you please help us with the following: Please point us to the official battery connector/header available on the RT700 EVK. Exact connector/header location on the board Supported battery type/specification Recommended connector/part number We would also like to understand the correct procedure to power up the RT700 EVK using an external power adapter while still supporting flashing and debugging. Currently, we are powering and debugging the board through the USB debug port. We want to know: What changes/setup are required when powering the board externally for battery and adapter Whether flashing and debugging through USB/J-Link will continue to work in this setup. Thanks & Regards, Suhas Evaluation Board Re: MIMXRT700 EVK Battery Connection and External Power Up Clarification Hi @suhas1503 , Thanks for your interest in NXP MIMXRT series! The PMIC supports battery power, but on the EVK, it is set to DNP by default. You can locate J37 on the schematic. A detailed description can be found in the “MIMXRT700-EVK Board User Manual[UM12188]”. Please take a look. Gavin_Jia_0-1779932324256.pngGavin_Jia_0-1779932324256.pngGavin_Jia_0-1779932324256.png Gavin_Jia_1-1779932333707.pngGavin_Jia_1-1779932333707.pngGavin_Jia_1-1779932333707.png For the RT700, there is no specific requirement regarding the choice of battery for the PMIC; you can select one based on the PCA9422 datasheet. In addition, the RT700-EVK supports powered by an external power adapter and supports a 5V power supply. It is connected via J45, and the power source is selected by shorting pins 1 and 2 on J2. The details is in “MIMXRT700-EVK Board User Manual[UM12188]” Section 2.2 . The on-board debugger continues to function normally when powered by an external power source. Best regards, Gavin Re: MIMXRT700 EVK Battery Connection and External Power Up Clarification Hi, I am using the MIMXRT700-EVK with a Murata 2EL M.2 module connected to the M.2 socket on the RT700-EVK. I am testing different examples from the MCUXpresso SDK. Hardware setup: - Board: MIMXRT700-EVK - M.2 module: Murata 2EL M.2 module - Murata 2EL module is connected to the M.2 socket - Power is supplied through JP37 using a battery - MCUXpresso SDK: SDK_26_03_00_MIMXRT700-EVK Observed behavior: When the RT700-EVK is powered through JP37 using a battery: 1. The hello_world example works correctly. 2. The xaf_record example works correctly. 3. The edgefast_bluetooth_examples/peripheral_ht example builds and flashes successfully, but the application fails during runtime initialization. The UART log is: BLE Peripheral HT demo start... [sdio] Error: Card initialization failed [wifi_io] Error: SDIO driver init failed. ASSERT ERROR " API_SUCCESS == result ": file "middleware/wireless/ethermind/port/pal/mcux/bluetooth/controller/controller_wifi_nxp.c" Line "120" However, when I use the same edgefast_bluetooth_examples/peripheral_ht example with the J54 USB debug port and J45 port with the adapter, the example works correctly. Therefore, the EdgeFast Bluetooth example works correctly with the J54/J45 configuration but fails when the board is powered through JP37 using a battery. The hello_world and xaf_record examples work correctly with the JP37 battery configuration. Expected behavior: I expect the edgefast_bluetooth_examples/peripheral_ht example to initialize the Bluetooth controller successfully when the RT700-EVK is powered through JP37 using a battery and the Murata 2EL M.2 module is connected. Questions: 1. Is the JP37 power configuration supported for running the EdgeFast Bluetooth examples with the Murata 2EL M.2 module? 2. Does the Murata 2EL M.2 module require any additional jumper, switch, or power configuration when JP37 is used with a battery? 3. Why does the application report the following errors when using the JP37 battery configuration? [sdio] Error: Card initialization failed [wifi_io] Error: SDIO driver init failed. 4. Is there any required power sequencing or M.2 power-enable configuration for the wireless module when using battery power through JP37? 5. Is there a recommended RT700-EVK jumper and power configuration for using the Murata 2EL M.2 module with the EdgeFast Bluetooth examples and battery power? Please let me know if you need any additional information, such as the complete UART log, jumper configuration, SDK configuration, schematic details, or power measurements. Thank you. Bluetooth Example Fails with SDIO/Wi-Fi Initialization Error When Powered by Battery Through JP37 Hi, I am using the MIMXRT700-EVK with a Murata 2EL M.2 module connected to the M.2 socket on the RT700-EVK. I am testing different examples from the MCUXpresso SDK. Hardware setup: - Board: MIMXRT700-EVK - M.2 module: Murata 2EL M.2 module - Murata 2EL module is connected to the M.2 socket - Power is supplied through JP37 using a battery - MCUXpresso SDK: SDK_26_03_00_MIMXRT700-EVK Observed behavior: When the RT700-EVK is powered through JP37 using a battery: 1. The hello_world example works correctly. 2. The xaf_record example works correctly. 3. The edgefast_bluetooth_examples/peripheral_ht example builds and flashes successfully, but the application fails during runtime initialization. The UART log is: BLE Peripheral HT demo start... [sdio] Error: Card initialization failed [wifi_io] Error: SDIO driver init failed. ASSERT ERROR " API_SUCCESS == result ": file "middleware/wireless/ethermind/port/pal/mcux/bluetooth/controller/controller_wifi_nxp.c" Line "120" However, when I use the same edgefast_bluetooth_examples/peripheral_ht example with the J54 USB debug port and J45 port with the adapter, the example works correctly. Therefore, the EdgeFast Bluetooth example works correctly with the J54/J45 configuration but fails when the board is powered through JP37 using a battery. The hello_world and xaf_record examples work correctly with the JP37 battery configuration. Expected behavior: I expect the edgefast_bluetooth_examples/peripheral_ht example to initialize the Bluetooth controller successfully when the RT700-EVK is powered through JP37 using a battery and the Murata 2EL M.2 module is connected. Questions: 1. Is the JP37 power configuration supported for running the EdgeFast Bluetooth examples with the Murata 2EL M.2 module? 2. Does the Murata 2EL M.2 module require any additional jumper, switch, or power configuration when JP37 is used with a battery? 3. Why does the application report the following errors when using the JP37 battery configuration? [sdio] Error: Card initialization failed [wifi_io] Error: SDIO driver init failed. 4. Is there any required power sequencing or M.2 power-enable configuration for the wireless module when using battery power through JP37? 5. Is there a recommended RT700-EVK jumper and power configuration for using the Murata 2EL M.2 module with the EdgeFast Bluetooth examples and battery power? Please let me know if you need any additional information, such as the complete UART log, jumper configuration, SDK configuration, schematic details, or power measurements. Thank you. Re: Bluetooth Example Fails with SDIO/Wi-Fi Initialization Error When Powered by Battery Through JP3 Hi @suhas1503 , I think the most likely reason is that the power required for the M.2 on the EVK comes from other components rather than VBAT. I suggest you take a look at the schematic. In particular, Sheet 5 and Sheet 6. In Sheet 5, identify all jumper caps similar to JP33 and switch them from SYS_5V0 to VBAT. In Sheet 6, identify all jumper caps similar to JP11 and switch them from PMIC to DCDC_3V3. The ultimate goal is to enable VBAT to power the corresponding modules. From what I’ve quickly glanced at, the key is to ensure that the power sources for MCU_3V3 and WL_3V3 are correctly configured. (If you have a new question, please feel free to submit a new ticket or post. Updates in closed threads are easily overlooked. Thank you for your understanding and cooperation!) Best regards, Gavin Re: Bluetooth Example Fails with SDIO/Wi-Fi Initialization Error When Powered by Battery Through JP3 Hi, I followed the jumper changes you suggested and tested the RT700-EVK with the battery supply. I changed the jumper settings as follows: JP33 → 2–3 JP34 → 2–3 JP36 → 2–3 JP11 → 2–3 JP7 → 2–3 I connected the 3.7 V, 500 mAh Li-Po battery to JP37. With these changes, the BLE Peripheral HT demo initialises successfully, and BLE starts advertising as expected. However, after running for some time, the RT700-EVK starts resetting continuously. After each reset, the application starts again, BLE initialises, and advertising starts again. So, the jumper changes have enabled the BLE functionality on battery power, but the continuous reset issue is still present. Could you please suggest what could be causing this repeated reset during battery-powered operation and what I should check next?
View full article
I.MX6ULLのENET1は物理からデータを受信できません I.M6ULL + 4.19.35 + KSZ 8081rnb  この機器は現場に300台配備されています。ほとんどの場合、それらは正常に稼働し、事業やサービスは期待どおりに機能します。しかしながら、時折、サービスにアクセスできなくなることがあります。調査の結果、eth1(ENET1)のLINK LEDは点灯したままで、ACT LEDが時々点滅しているにもかかわらず、eth1がパケットを受信しなくなることが確認されました。 さらに、ENET1のイーサネットケーブルを一度抜き差しすると、ネットワークが正常に戻ることも確認しました。デバイスを再起動することでも復元されます。根本原因の分析を手伝ってもらえますか?それはPHYにあるのかMACなのか? そこから読み取られるレジスタ値は以下のとおりです。 読み取るレジスタのリストには、MACレジスタとPHYレジスタの両方が含まれます。かなり長いため、次のページに掲載しています。 コマンド: phy eth1 0x1は PHY レジスタ 1 を読み取ります。 memtool i.MX6UL Linux Re: I.MX6ULL ENET1 can't recv data from phy こんにちは、@240697273 読み取るレジスタのリストには、MACレジスタとPHYレジスタの両方が含まれます。かなり長いため、次のページに掲載しています。 >>>これらのレジスターが見つからなかった。もう一度送ってください。 B、R
View full article