Driver runtime error: [pfeng-drv.c:545] Failed to set clock 'pfe_sys'. Error: -22).

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

Driver runtime error: [pfeng-drv.c:545] Failed to set clock 'pfe_sys'. Error: -22).

Jump to solution
710 Views
irfank
Contributor III

Hello;

We are using fipimage(uboot) which was generate via bsp35 and linuximage which was generated via bsp37 for some internal issues.

The error is : ([    2.386446] pfeng 46000000.pfe: ERR: (DRIVER) event 1 - Driver runtime error: [pfeng-drv.c:545] Failed to set clock 'pfe_sys'. Error: -22).

Should we use uboot and kernel image which is generated via same bsp?

 

2.385943] pfeng 46000000.pfe: PFEng ethernet driver loading ...
[    2.385964] pfeng 46000000.pfe: Version: 1.4.0
[    2.385969] pfeng 46000000.pfe: Driver commit hash: M4_DRIVER_COMMIT_HASH
[    2.385974] pfeng 46000000.pfe: Multi instance support: disabled (standalone)
[    2.385979] pfeng 46000000.pfe: Compiled by: 11.3.0
[    2.386021] pfeng 46000000.pfe: Cbus addr 0x46000000 size 0x1000000
[    2.386032] pfeng 46000000.pfe: nxp,fw-class-name: s32g_pfe_class.fw
[    2.386039] pfeng 46000000.pfe: nxp,fw-util-name: s32g_pfe_util.fw
[    2.386099] pfeng 46000000.pfe: netif name: pfe0
[    2.386108] pfeng 46000000.pfe: DT mac addr: 00:01:be:be:ef:11
[    2.386118] pfeng 46000000.pfe: netif(pfe0) linked phyif: 0
[    2.386125] pfeng 46000000.pfe: netif(pfe0) mode: std
[    2.386141] pfeng 46000000.pfe: netif(pfe0) HIFs: count 1 map 01
[    2.386156] pfeng 46000000.pfe: EMAC0 interface mode: 4
[    2.386340] pfeng 46000000.pfe: HIF channels mask: 0x0001
[    2.386374] pfeng 46000000.pfe: PFE port coherency enabled, mask 0x1e
[    2.386446] pfeng 46000000.pfe: ERR: (DRIVER) event 1 - Driver runtime error: [pfeng-drv.c:545] Failed to set clock 'pfe_sys'. Error: -22
[    2.386459] pfeng 46000000.pfe: PM runtime resume returned: -13
[    2.386467] pfeng 46000000.pfe: HIF3 not enabled, skipped
[    2.386472] pfeng 46000000.pfe: HIF2 not enabled, skipped
[    2.386477] pfeng 46000000.pfe: HIF1 not enabled, skipped
[    2.386482] pfeng 46000000.pfe: HIF0 not enabled, skipped
[    2.386555] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    2.386751]  pfeng_dt_release_config+0x34/0x80 [pfeng]
[    2.386912]  pfeng_drv_remove+0xc0/0x290 [pfeng]
[    2.387018]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    2.387214]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    2.787773] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    2.787965]  pfeng_dt_release_config+0x3c/0x80 [pfeng]
[    2.788104]  pfeng_drv_remove+0xc0/0x290 [pfeng]
[    2.788212]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    2.788406]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    3.088924] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    3.089106]  pfeng_dt_release_config+0x50/0x80 [pfeng]
[    3.089218]  pfeng_drv_remove+0xc0/0x290 [pfeng]
[    3.089324]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    3.089513]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    3.390099] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    3.390292]  pfeng_dt_release_config+0x58/0x80 [pfeng]
[    3.390452]  pfeng_drv_remove+0xc0/0x290 [pfeng]
[    3.390560]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    3.390755]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    3.691242] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    3.691432]  pfeng_drv_remove+0x118/0x290 [pfeng]
[    3.691552]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    3.691759]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    4.692555] Modules linked in: pfeng(O+) ipc_shm_dev(O)
[    4.692746]  pfeng_drv_remove+0x120/0x290 [pfeng]
[    4.692901]  pfeng_drv_probe+0x1a4/0xd20 [pfeng]
[    4.693106]  pfeng_platform_driver_init+0x24/0x1000 [pfeng]
[    5.193571] pfeng: probe of 46000000.pfe failed with error -22

0 Kudos
Reply
1 Solution
688 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

For the question:

"Should we use uboot and kernel image which is generated via same bsp?"

The answer is that this is correct, you should always use the same BSP version for uboot/ATF/image. Can you confirm if this situation is happening under using the same uboot/ATF/image version?

Please, let us know.

View solution in original post

0 Kudos
Reply
1 Reply
689 Views
Daniel-Aguirre
NXP TechSupport
NXP TechSupport

Hi,

For the question:

"Should we use uboot and kernel image which is generated via same bsp?"

The answer is that this is correct, you should always use the same BSP version for uboot/ATF/image. Can you confirm if this situation is happening under using the same uboot/ATF/image version?

Please, let us know.

0 Kudos
Reply