Fdma.ko insmod failed

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

Fdma.ko insmod failed

Jump to solution
2,816 Views
435761040
Contributor II

My environment is:
BSP19.0
Kernel v4.14.34_bsp19.0
Vsdk RTM 1.3

After loading fdma.ko is the following error popping up?

root@s32v234sbc:~/bp_lib# insmod apex.ko
[ 147.867278] apex: loading out-of-tree module taints kernel.
root@s32v234sbc:~/bp_lib# insmod oal_cma.ko
root@s32v234sbc:~/bp_lib# insmod csi.ko
[ 168.033143] CSI: driver ready -> CSI0 = enabled | CSI1 = enabled.
root@s32v234sbc:~/bp_lib# insmod cam.ko
[ 171.634874] Load sbc board configuration
[ 171.638658] CGD: ready.
root@s32v234sbc:~/bp_lib# insmod seq.ko
[ 176.507937] SEQ: driver ready.
root@s32v234sbc:~/bp_lib# insmod viulite.ko
root@s32v234sbc:~/bp_lib# insmod fdma.ko
[ 184.678998] /home/calmcar-maker/disk2/NXP/vsdk1.3/s32v234_sdk/libs/isp/fdma/kernel/build-v234ce-gnu-linux-d/../src/fdma_func.c: 831/FDMA_TdtInit : [Error]: Failed to allocate TDTs in SRAM.
[ 184.695428] /home/calmcar-maker/disk2/NXP/vsdk1.3/s32v234_sdk/libs/isp/fdma/kernel/build-v234ce-gnu-linux-d/../src/fdma_func.c: 284/FDMA_Setup : [Error]: TDT init failed
[ 184.710501] /home/calmcar-maker/disk2/NXP/vsdk1.3/s32v234_sdk/libs/isp/fdma/kernel/build-v234ce-gnu-linux-d/../src/fdma_func.c: 332/FDMA_Setup : [Error]: Canceling FDMA insmod.
[ 184.726186] FDMA: driver setup failed.
[ 184.730015] FDMA: Error during insmod. Terminating ...
insmod: ERROR: could not insert module fdma.ko: Operation not permitted


How to fix? Is there a patch?

0 Kudos
Reply
1 Solution
2,496 Views
jiri_kral
NXP Employee
NXP Employee

Hi,

The prebuild SD card image uses kernel: 

Linux s32v234sbc 4.14.34-rt27+g3b93d42 #1 SMP Tue Dec 4 16:37:13 EET 2018 aarch64 aarch64 aarch64 GNU/Linux

Anyway, it is hard to say what else may be wrong. For me are all VSDK examples working without any issue. 

Jiri

View solution in original post

6 Replies
2,496 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

what is your EVB? Are you using Debian or Yocto?  I just tried remove/insert again fdma on S32V234_SBC with Yocto - and there is no issue. 

Jiri 

0 Kudos
Reply
2,494 Views
435761040
Contributor II

I am Manually building Linux BSP components

0 Kudos
Reply
2,494 Views
435761040
Contributor II

This is my current kernel

Linux s32v234sbc 4.14.34-rt27-dirty #2 SMP Thu Feb 14 12:22:27 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

What is your environment? I used bsp17.0S before to use Insmod fdma
But bsp19.0 has this problem
I saw on other posts that I can support VSDK through the patch kernel?

0001-s32v234-dts-Add-VSDK-specific-configuration.patch


Where is this patch obtained? Finally, I would like to ask which branch of linux bsp19.0 corresponds to git?

Thank you

0 Kudos
Reply
2,496 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

the patch is part of VSDK installation - located in [YOUR_VSDK_INSTALL_PATH]/s32v234_sdk/os/linux/

I'm using pre-build SD card image with Yocto linux. This image contains all configurations. You can get this image here:

https://nxp.flexnetoperations.com/control/frse/download?element=10595057 

Jiri

0 Kudos
Reply
2,496 Views
435761040
Contributor II

Yes, the problem is solved after the patch is finished.
But reported when applying vsdk demo
Bus error .
I can determine if it is a kernel or a device tree.

My kernel is

Linux s32v234sbc 4.14.34-rt27-00002-g12135f4-dirty #4 SMP Fri Feb 15 10:07:37 CST 2019 aarch64 aarch64 aarch64 GNU/Linux

What I want to ask is, which is the bsp19.0 kernel branch corresponding to vsdk1.3?
According to the manual I git clone https://source.co deaurora.org/external/autobsps32/linux
Get the kernel of bsp19.0
But which branch of the branch corresponds to vsdk1.3?

微信截图_20190216155041.png

Thank 

0 Kudos
Reply
2,497 Views
jiri_kral
NXP Employee
NXP Employee

Hi,

The prebuild SD card image uses kernel: 

Linux s32v234sbc 4.14.34-rt27+g3b93d42 #1 SMP Tue Dec 4 16:37:13 EET 2018 aarch64 aarch64 aarch64 GNU/Linux

Anyway, it is hard to say what else may be wrong. For me are all VSDK examples working without any issue. 

Jiri