LayerscapeのトピックRe: Problems and lots ouf outputs in dmesg while using sec on lx2160A

Problems and lots ouf outputs in dmesg while using sec on lx2160A

td71522 — Fri, 03 Feb 2023 07:29:38 GMT

Hi togehter, i am using the lx2160A and work with the built in sec.

The encryption and decryption seems to work correct. But in dmesg a lot of messages are shown including such as "FQ xxx returned no valid Frame" but right afterwords it shows "encrypt/decrypt done err: 0x0". Many other messages are shown as well including (i think) debug messages with the key in plain.

I am accessing the sec from userspace through the kernel with the libkcapi as mentioned at the linux kernel documentation.

can someone explain what the messages/errors mean and how to fix them ?

this code:

simpleCode.PNG

produced this messages at a single run:

dmesgOutput.PNG

Thanks in advance

Regards

Re: Problems and lots ouf outputs in dmesg while using sec on lx2160A

June_Lu — Thu, 09 Feb 2023 06:40:32 GMT

If you used LSDK2108, you could try to use LSDK21.08 page855, How to test the driver to test the function.

Re: Problems and lots ouf outputs in dmesg while using sec on lx2160A

td71522 — Thu, 09 Feb 2023 14:45:58 GMT

I used LSDK 20.04 but as understand the user guide for the LSDK20.04 it should be the same, but everytime i try "insmod tcrypt.ko .... " i get the error: could not load module, no such file or directory

Re: Problems and lots ouf outputs in dmesg while using sec on lx2160A

June_Lu — Sun, 12 Feb 2023 03:02:06 GMT

Please try the steps below:

downloaded LSDK 20.04 pre-built image with the following command.

$ wget https://www.nxp.com/lgfiles/sdk/lsdk2004/lsdk2004_yocto_tiny_LS_arm64.itb

On lx2160ardb, boot the target board with the following commands.

=> sf read 0x80d00000 0xd00000 0x100000

=> fsl_mc lazyapply dpl 0x80d00000

=> tftp 0xa0000000 nxa22585/ls1046ardb/20.04/lsdk2004_yocto_tiny_LS_arm64.itb

=> bootm 0xa0000000#lx2160ardb

root@TinyLinux:~# restool dpseci create --num-queues=8 --priorities=1,2,3,4,5,6,7,8

dpseci.1 is created under dprc.1

root@TinyLinux:~# restool dprc assign dprc.1 --object=dpseci.0 --plugged=1

dpseci.0 cannot be changed plugged state because it is bound to driver:

/sys/bus/fsl-mc/devices/dpseci.0/driver -> ../../../../../../bus/fsl-mc/drivers/dpaa2_caam

unbind it first

Please use all images from LSDK 20.04, please compare your Linux Kernel configuration file with the prebuild image. You could try lsdk2004_yocto_tiny_LS_arm64.itb on your target board.