Failed to load static DPL with 8x DPDMUX

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

Failed to load static DPL with 8x DPDMUX

Jump to solution
3,150 Views
dunk
Contributor III

Hi Community,

Using dynamic creation of DPDMUXs and DPNIs successfully, and generate the DPL by following commands:

  • 8x ls-addni --fs-entries=8 --num-queues=8 -n
  • source /usr/local/dpdk/dpaa2/dynamic_dpl.sh <dpmac.n> <dpmac.n+1> ... <dpmac.n+7>
  • 8x restool dpdmux create <dpdmux opts>
  • 8x restool dprc connect dprc.1 --endpoint1=<dpdmux>.n.0/1/2 --endpoint2=<dpmac.n>/<dpni.j>/dpni.k>
  • restool dprc generate-dpl dprc.1 > dpl-8-dpdmux.dts

 

Update the static DPL with dpl-8-dpdmux.dtb (generate by dtc tool) for uboot to initiate MC layout.

The error shows as blow:

[E, mem_mng_get_phys_mem:655] MAJOR mem. manager memory allocation failed
[E, mem_mng_get_phys_mem:658] Required size 0x000040000 alignment 0x000000100 exceeds available memory for partition ID 7
[E, init_bman_bp:399, DPDMUX] ID[6] - dpbp_allocate_buffers(), failed to allocate dpbp buffers
[E, init_infrastructure:3750, DPDMUX] swlib_init_bman_bp : -12
[E, dpdmux_init:4487, DPDMUX] init_infrastructure : -12
[E, mem_mng_get_phys_mem:655] MAJOR mem. manager memory allocation failed
[E, mem_mng_get_phys_mem:658] Required size 0x000040000 alignment 0x000000100 exceeds available memory for partition ID 7
[E, init_bman_bp:399, DPDMUX] ID[7] - dpbp_allocate_buffers(), failed to allocate dpbp buffers
[E, init_infrastructure:3750, DPDMUX] swlib_init_bman_bp : -12
[E, dpdmux_init:4487, DPDMUX] init_infrastructure : -12
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@6 and dpmac@9
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@6 and dpni@15
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@6 and dpni@7
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@7 and dpmac@10
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@7 and dpni@16
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, resman_is_link_permitted:6375, RESMAN] Object wasn't found
[E, linkman_probe_cb:205] No common ancestor - Failed to connect dpdmux@7 and dpni@8
[E, subnode_process:155] Probing module 'connection' return error code -1. Continue dpl processing...
[E, dpl_process:527] Error while parsing 'connections'. Skip processing the rest of DPL.
[E, main:198] DPL processing failed; continuing...

 Is there any limitation on the static DPL to support same layout as dynamic way?

Labels (1)
Tags (4)
0 Kudos
Reply
1 Solution
2,635 Views
dunk
Contributor III

Hi,

I've managed to fix this issue by correcting the DPL parameter names.

 

View solution in original post

0 Kudos
Reply
3 Replies
3,067 Views
yipingwang
NXP TechSupport
NXP TechSupport

Please try whether the following method is possible.

When you create DPDMUX, please specify "--max-dmat-entries=8" to reduce the resource allocation.

--max-dmat-entries=<number>

max entries in DPDMUX address table. Default is 64.

If your problem persists, please share your whole console log to create DPDMUX and generate DPL file.

In addition, which processor are you using?

0 Kudos
Reply
3,055 Views
dunk
Contributor III

Hi yipingwang,

Using '--max-dmat-entries' in dynamic creating layout don't change the final dts by 'restool dprc generate-dpl dprc.1'.

So, I just give it a try by adding following elements 'mem-size' and 'max-dmat-entries' in .dts. manually:

dpdmux@0 {
    compatible = "fsl,dpdmux";
    options = "DPDMUX_OPT_CLS_MASK_SUPPORT", "DPDMUX_OPT_AUTO_MAX_FRAME_LEN";
    method = "DPDMUX_METHOD_CUSTOM";
    manip = "DPDMUX_MANIP_NONE";
    num_ifs = <0x2>;
    mem-size = <0x100>;  // this is manually added by me
    max-dmat-entries = <0x8>; // this is manually added by me
};

Unfornately this doesn't fix it, the same error message showing from MC debug.

Please also check my dpl as enclosed.

Tags (4)
0 Kudos
Reply
2,636 Views
dunk
Contributor III

Hi,

I've managed to fix this issue by correcting the DPL parameter names.

 

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2268202%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3EFailed%20to%20load%20static%20DPL%20with%208x%20DPDMUX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2268202%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%20Community%2C%3C%2FP%3E%3CP%3EUsing%20dynamic%20creation%20of%20DPDMUXs%20and%20DPNIs%20successfully%2C%20and%20generate%20the%20DPL%20by%20following%20commands%3A%3C%2FP%3E%3CUL%3E%3CLI%3E8x%20ls-addni%20--fs-entries%3D8%20--num-queues%3D8%20-n%3C%2FLI%3E%3CLI%3Esource%20%2Fusr%2Flocal%2Fdpdk%2Fdpaa2%2Fdynamic_dpl.sh%20%3CDPMAC.N%3E%20%3CDPMAC.N%3E%20...%20%3CDPMAC.N%3E%3C%2FDPMAC.N%3E%3C%2FDPMAC.N%3E%3C%2FDPMAC.N%3E%3C%2FLI%3E%3CLI%3E8x%20restool%20dpdmux%20create%20%3CDPDMUX%20opts%3D%22%22%3E%3C%2FDPDMUX%3E%3C%2FLI%3E%3CLI%3E8x%26nbsp%3Brestool%20dprc%20connect%20dprc.1%20--endpoint1%3D%3CDPDMUX%3E.n.0%2F1%2F2%20--endpoint2%3D%3CDPMAC.N%3E%2F%3CDPNI.J%3E%2Fdpni.k%26gt%3B%3C%2FDPNI.J%3E%3C%2FDPMAC.N%3E%3C%2FDPDMUX%3E%3C%2FLI%3E%3CLI%3Erestool%20dprc%20generate-dpl%20dprc.1%20%26gt%3B%20dpl-8-dpdmux.dts%3C%2FLI%3E%3C%2FUL%3E%3CBR%20%2F%3E%3CP%3EUpdate%20the%20static%20DPL%20with%20dpl-8-dpdmux.dtb%20(generate%20by%20dtc%20tool)%20for%20uboot%20to%20initiate%20MC%20layout.%3C%2FP%3E%3CP%3EThe%20error%20shows%20as%20blow%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%5BE%2C%20mem_mng_get_phys_mem%3A655%5D%20MAJOR%20mem.%20manager%20memory%20allocation%20failed%3CBR%20%2F%3E%5BE%2C%20mem_mng_get_phys_mem%3A658%5D%20Required%20size%200x000040000%20alignment%200x000000100%20exceeds%20available%20memory%20for%20partition%20ID%207%3CBR%20%2F%3E%5BE%2C%20init_bman_bp%3A399%2C%20DPDMUX%5D%20ID%5B6%5D%20-%20dpbp_allocate_buffers()%2C%20failed%20to%20allocate%20dpbp%20buffers%3CBR%20%2F%3E%5BE%2C%20init_infrastructure%3A3750%2C%20DPDMUX%5D%20swlib_init_bman_bp%20%3A%20-12%3CBR%20%2F%3E%5BE%2C%20dpdmux_init%3A4487%2C%20DPDMUX%5D%20init_infrastructure%20%3A%20-12%3CBR%20%2F%3E%5BE%2C%20mem_mng_get_phys_mem%3A655%5D%20MAJOR%20mem.%20manager%20memory%20allocation%20failed%3CBR%20%2F%3E%5BE%2C%20mem_mng_get_phys_mem%3A658%5D%20Required%20size%200x000040000%20alignment%200x000000100%20exceeds%20available%20memory%20for%20partition%20ID%207%3CBR%20%2F%3E%5BE%2C%20init_bman_bp%3A399%2C%20DPDMUX%5D%20ID%5B7%5D%20-%20dpbp_allocate_buffers()%2C%20failed%20to%20allocate%20dpbp%20buffers%3CBR%20%2F%3E%5BE%2C%20init_infrastructure%3A3750%2C%20DPDMUX%5D%20swlib_init_bman_bp%20%3A%20-12%3CBR%20%2F%3E%5BE%2C%20dpdmux_init%3A4487%2C%20DPDMUX%5D%20init_infrastructure%20%3A%20-12%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%406%20and%20dpmac%409%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%406%20and%20dpni%4015%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%406%20and%20dpni%407%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%407%20and%20dpmac%4010%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%407%20and%20dpni%4016%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20resman_is_link_permitted%3A6375%2C%20RESMAN%5D%20Object%20wasn't%20found%3CBR%20%2F%3E%5BE%2C%20linkman_probe_cb%3A205%5D%20No%20common%20ancestor%20-%20Failed%20to%20connect%20dpdmux%407%20and%20dpni%408%3CBR%20%2F%3E%5BE%2C%20subnode_process%3A155%5D%20Probing%20module%20'connection'%20return%20error%20code%20-1.%20Continue%20dpl%20processing...%3CBR%20%2F%3E%5BE%2C%20dpl_process%3A527%5D%20Error%20while%20parsing%20'connections'.%20Skip%20processing%20the%20rest%20of%20DPL.%3CBR%20%2F%3E%5BE%2C%20main%3A198%5D%20DPL%20processing%20failed%3B%20continuing...%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3BIs%20there%20any%20limitation%20on%20the%20static%20DPL%20to%20support%20same%20layout%20as%20dynamic%20way%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2268202%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CLINGO-LABEL%3EQorIQ%20LS2%20Device%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2269081%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Failed%20to%20load%20static%20DPL%20with%208x%20DPDMUX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2269081%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F52411%22%20target%3D%22_self%22%3E%3CSPAN%20class%3D%22%22%3Eyipingwang%3C%2FSPAN%3E%3C%2FA%3E%2C%3C%2FP%3E%3CP%3EUsing%20'--max-dmat-entries'%20in%20dynamic%20creating%20layout%20don't%20change%20the%20final%20dts%20by%20'restool%20dprc%20generate-dpl%20dprc.1'.%3C%2FP%3E%3CP%3ESo%2C%20I%20just%20give%20it%20a%20try%20by%20adding%20following%20elements%20'mem-size'%20and%20'%3CSPAN%3Emax-dmat-entries'%26nbsp%3B%3C%2FSPAN%3Ein%20.dts.%20manually%3A%3C%2FP%3E%3CBLOCKQUOTE%3E%3CDIV%3E%3CSPAN%3Edpdmux%400%20%7B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20compatible%20%3D%20%22fsl%2Cdpdmux%22%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20options%20%3D%20%22DPDMUX_OPT_CLS_MASK_SUPPORT%22%2C%20%22DPDMUX_OPT_AUTO_MAX_FRAME_LEN%22%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20method%20%3D%20%22DPDMUX_METHOD_CUSTOM%22%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20manip%20%3D%20%22DPDMUX_MANIP_NONE%22%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20num_ifs%20%3D%20%26lt%3B0x2%26gt%3B%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20mem-size%20%3D%20%26lt%3B0x100%26gt%3B%3B%26nbsp%3B%20%2F%2F%20this%20is%20manually%20added%20by%20me%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3B%20max-dmat-entries%20%3D%20%26lt%3B0x8%26gt%3B%3B%26nbsp%3B%2F%2F%20this%20is%20manually%20added%20by%20me%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%3E%3CSPAN%3E%7D%3B%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FBLOCKQUOTE%3E%3CP%3EUnfornately%20this%20doesn't%20fix%20it%2C%20the%20same%20error%20message%20showing%20from%20MC%20debug.%3C%2FP%3E%3CP%3EPlease%20also%20check%20my%20dpl%20as%20enclosed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2269065%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Failed%20to%20load%20static%20DPL%20with%208x%20DPDMUX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2269065%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EPlease%20try%20whether%20the%20following%20method%20is%20possible.%3C%2FP%3E%0A%3CP%3EWhen%20you%20create%26nbsp%3BDPDMUX%2C%20please%20specify%20%22--max-dmat-entries%3D8%22%20to%20reduce%20the%20resource%20allocation.%3C%2FP%3E%0A%3CP%3E--max-dmat-entries%3D%3CNUMBER%3E%3C%2FNUMBER%3E%3C%2FP%3E%0A%3CP%3Emax%20entries%20in%20DPDMUX%20address%20table.%20Default%20is%2064.%3C%2FP%3E%0A%3CP%3EIf%20your%20problem%20persists%2C%20please%20share%20your%20whole%20console%20log%20to%20create%26nbsp%3BDPDMUX%20and%20generate%20DPL%20file.%3C%2FP%3E%0A%3CP%3EIn%20addition%2C%20which%20processor%20are%20you%20using%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2269939%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20Failed%20to%20load%20static%20DPL%20with%208x%20DPDMUX%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2269939%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3EI've%20managed%20to%20fix%20this%20issue%20by%20correcting%20the%20DPL%20parameter%20names.%3C%2FP%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E