PROCESSOR-SDK-J784S4: Unknown symbol from devnp-cpsw9g.so

Hi,

Can you please confirm, have you tried using the default images/binaries or building the SDK and using it?

Santosh Malagar said:

2. enet_osal_dflt.c source file is missing/removed from psdkqa/pdk/packages/ti/drv/enet/src/common/. Function definition of EnetOsalDflt_initCfg() is not available in this case. Hence call to EnetOsalDflt_initCfg from enet.c will fail. 

If you are building the SDK, you may observe the failure as you are pointing some files are missing in SDK offering.

Will check with QNX expert and get back to you soon.

Best Regards,
Sudheer

Hello Santosh,

With 9.0 the QNX make files to build pdk have been updated so that only files that are used by the PSDKQA sources are included in the release package.  From your symptom, it looks like the pdk lib builds need to be migrated from 8.6 to 9.0 way of building at your end.

BR

Subbu

Hi Subbu, 

The make files adaptation is taken as it is from the 9.0 package.

The above mentioned issue is observed when cpsw9g driver is initialized in the ifs. 

This leads to the failure of loading the driver.

please find the slog2info

Jan 01 00:00:00.830                    iopkt.12305          main_buffer*     0  5  tcpip starting
Jan 01 00:00:00.831                    iopkt.12305          main_buffer      0  5  smmu support is disabled
Jan 01 00:00:00.832                    iopkt.12305          main_buffer      0  5  initializing IPsec...
Jan 01 00:00:00.832                    iopkt.12305          main_buffer      0  5   done

 

Jan 01 00:00:00.832                    iopkt.12305          main_buffer      0  5  IPsec: Initialized Security Association Processing.

 

Jan 01 00:00:00.842                    iopkt.12305          main_buffer      0  2  Unable to load devnp-cpsw9g.so: (null)

 

Hi Santhosh,

For any driver launched from the IFS, the build file / IFS would need include the required libraries, up until the filesystem is mounted.   

Please check the following:

• Is the io-pkt driver being launched prior to the filesystem being mounted.
• If yes, 
  • Is devnp-cpsw9g.so part of the IFS image?
  • Check build file and/or build file build logs, or do a 'find' on the target to ascertain this
• If no, and/or the devnp-cpsw9g.so is part of the IFS
  • Check the library search paths to ensure that the shared library can be found.

Regards,

kb

Hi KB,

- Is the io-pkt driver being launched prior to the filesystem being mounted.  -->  Yes. filesystem is mounted after the initialization of drivers 

- Is devnp-cpsw9g.so part of the IFS image? --> Yes. attached the find result 

- Check build file and/or build file build logs, or do a 'find' on the target to ascertain this

(tda4vh_tol) / # find . -iname devnp-cpsw9g.so
./proc/boot/devnp-cpsw9g.so

- Check the library search paths to ensure that the shared library can be found.

please find the use command result  and the library path details 

(tda4vh_tol) / # use -i /proc/boot/devnp-cpsw9g.so
QNX_BUILDID=(GNU)a735b0e29b90ec2b8b1b2803008c9987
NAME=devnp-cpsw9g.so
DESCRIPTION=j784s4 cpsw9g driver
DATE=2023/10/03-19:01:51-IST
STATE=Experimental
HOST=KOR-C-003XC
USER=feo1kor
TAGID=QNX710_j784s4_evm
VERSION_REL=PSDKQNX_09_00_00


(tda4vh_tol) / #
(tda4vh_tol) / # ldd /proc/boot/devnp-cpsw9g.so
/proc/boot/devnp-cpsw9g.so:
        devnp-cpsw9g.so => /proc/boot/devnp-cpsw9g.so (0x3d28cbe000)



(tda4vh_tol) / # echo $LD_LIBRARY_PATH
/proc/boot:/lib:/usr/lib:/lib/dll:/lib/dll/pci        
        

Thanks in advance.

Thanks Santosh

What is the behavior if the driver is launched manually from the command line?  Does it work?

If it does not work please try running the below command prior to launching the driver, and parse through the output for possible reasons why library cannot be located:

• export DL_DEBUG=libs

If it does work from command line, then please ensure the library search path in the build file, is referencing /proc/boot.

Regards,

kb

Hi Santosh,

Please be aware of below e2e thread, that is tracking the same issue.  

(99+) TDA4VH-Q1: TDA4VH : J784S4 EVM ethernet interface error : Unknown symbol : gEnetPhyDrvVsc8514 referenced from devnp-cpsw2g.so with latest PSDK QNX and RTOS - Processors forum - Processors - TI E2E support forums

Regards,

kb

Hi KB,

When is the patch with fix planned?

Thank you