fdma.ko can not be insmod

cancel
Showing results for 
Search instead for 
Did you mean: 

fdma.ko can not be insmod

387 Views
yager0203
Contributor I
NFS daemon support not enabled in kernel
Starting syslogd/klogd: done
Starting internet superserver: xinetd.
[ 4.190084] apex: loading out-of-tree module taints kernel.
[ 4.302751] CSI: driver ready -> CSI0 = enabled | CSI1 = enabled.
[ 4.374527] CGD: ready.
[ 4.438849] SEQ: driver ready.
[ 4.483947] /home/myg/VisionSDK_S32V2_RTM_1_2_0_HF1/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.
[ 4.504025] /home/myg/VisionSDK_S32V2_RTM_1_2_0_HF1/s32v234_sdk/libs/isp/fdma/kernel/build-v234ce-gnu-linux-d/../src/fdma_func.c: 284/FDMA_Setup : [Error]: TDT init failed
[ 4.522490] /home/myg/VisionSDK_S32V2_RTM_1_2_0_HF1/s32v234_sdk/libs/isp/fdma/kernel/build-v234ce-gnu-linux-d/../src/fdma_func.c: 332/FDMA_Setup : [Error]: Canceling FDMA insmod.
[ 4.541684] FDMA: driver setup failed.
[ 4.546277] FDMA: Error during insmod. Terminating ...
insmod: ERROR: could not insert module /vsdk/demos/fdma.ko: Operation not permitted
[ 4.747789] H264Enc driver ready.
0 Kudos
3 Replies

89 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

what is your EVB? 

Jiri 

0 Kudos

89 Views
lemficb
Contributor II

Hi  Jiri

       The problem has already been solved, when I use the 0001-s32v234-dts-Add-VSDK-specific-configuration.patch patch in kernel.  But now ,I have another problem on my board. I have no ov01640 ,so I use max9286+max96705+ISX016+4N321(or max96705+AP0101+AR0140) instead. When I run isp_ov10640_quad.elf on my board, there are sereral errors .I am not sure whether there are some other things what should I do . And the sensor on the top  are  shows normal on imx6q&imx8qxp.I have no other source about s32v234,In addition to the official website. I think there is something wrong with my isp module , but I don't know how to modify. Could you give me some advices ?thanks a lot . The log just as below.

 

root@s32v234evb:/camera_test# ./isp_ov10640_quad.elf

**************************************************************
** Omnivision Ov10640 quad demo using Maxim Ser/Des HW setup
** Description:
** o Maxim 9286 deserializer board with 4xOmnivision Ov10640
** cameras each with 9271 serializer (on MipiCsi_0) expected as
** image input.
** o ISP does debayering and HDR processing.
** o Resulting image is displayed live using DCU.
**
** Usage:
** o no cmd line parameters available.
** o runtime control using nonblocking keyboard input.
** press 'h' for available commands listing.
**
**************************************************************

Press Ctrl+C to terminate the demo.
[ 156.153411] Probing I2c client @ 0x6a on I2C bus #0.
[ 156.158266] Generic camera I2c driver added successfully.
[ 156.163515] Probing I2c client @ 0x40 on I2C bus #0.
[ 156.168580] Probing I2c client @ 0x30 on I2C bus #0.
[ 156.206647] /home/link/s32v_sdk/s32v234_1_3_0/VisionSDK_S32V2_RTM_1_3_0/s32v234_sdk/libs/isp/cam_generic/kernel/build-v234ce-gnu-linux-d/..6
../../../../../libs/isp/cam_generic/user/src/cam_user.cpp: 569/CAM_WriteSingle : [Error]: I2c write single failed
[ 156.258645] /home/link/s32v_sdk/s32v234_1_3_0/VisionSDK_S32V2_RTM_1_3_0/s32v234_sdk/libs/isp/cam_generic/kernel/build-v234ce-gnu-linux-d/..6
../../../../../libs/isp/cam_generic/user/src/cam_user.cpp: 569/CAM_WriteSingle : [Error]: I2c write single failed
[ 156.394501] Probing I2c client @ 0x41 on I2C bus #0.
[ 156.399687] Probing I2c client @ 0x31 on I2C bus #0.
[ 156.408616] Probing I2c client @ 0x42 on I2C bus #0.
[ 156.413789] Probing I2c client @ 0x32 on I2C bus #0.
[ 156.422666] Probing I2c client @ 0x43 on I2C bus #0.
[ 156.427820] Probing I2c client @ 0x33 on I2C bus #0.
[ 156.436723] Probing I2c client @ 0x44 on I2C bus #0.
[ 156.441902] Probing I2c client @ 0x34 on I2C bus #0.
[ 156.473671] /home/link/s32v_sdk/s32v234_1_3_0/VisionSDK_S32V2_RTM_1_3_0/s32v234_sdk/libs/isp/cam_generic/kernel/build-v234ce-gnu-linux-d/..0
../../../../../libs/isp/cam_generic/user/src/cam_user.cpp: 379/CAM_ReadSingle : [Error]: I2c read single failed
../src/sdi.cpp: 1517/IOsReserve : [Error]: Failed to reserve IO object 4.
../src/sdi.cpp: 979/PreStart : [Error]: Failed to reserve IO objects.
Failed to prestart the grabber.
Demo failed in preparation phase.
root@s32v234evb:/camera_test# i2cdetect -y -r 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: 40 41 42 43 44 -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- 6a -- -- -- -- --
70: -- -- -- -- -- -- -- --

0 Kudos

89 Views
lemficb
Contributor II

Hi  Jiri,

    I have the same error with yager0203. My evk borad is s32v234-EVK 29288.Could you give some advices?

Thanks a lot.

    Link

0 Kudos