TDA4VH-Q1: TDA4VH : J784S4 EVM ethernet interface error : Unknown symbol : gEnetPhyDrvVsc8514 referenced from devnp-cpsw2g.so with latest PSDK QNX and RTOS

VAISALI B

Part Number: TDA4VH-Q1
Other Parts Discussed in Thread: TDA4VH

Hi Team,

We have TDA4VH - J784S4 EVM board, tried to do make the ethernet interface up (am0) in QNX, followed the below documents

https://software-dl.ti.com/jacinto7/esd/processor-sdk-qnx-j784s4/08_06_00_07/exports/docs/qnx_sdk_components_j784s4.html#

QNX - SDK used SDP - 7.1

BSP packages installed,

QNX Software Development Platform 7.1

QNX SDP 7.1 ScreenBoard support j784s4 (with debug symbols)

QNX SDP 7.1 BSP for Texas Instruments jacinto 7 j784s4 Evaluation modules

QNX SDP 7.1 Multimedia - OpenMAX IL API (with Debug Symbols)

With the latest PSDK QNX and RTOS,

QNX - dr-download.ti.com/.../ti-processor-sdk-qnx_j784s4_09_00_00_03.tar.gz

RTOS - https://dr-download.ti.com/software-development/software-development-kit-sdk/MD-zv2DZbDzFz/09.00.00.02/ti-processor-sdk-rtos-j784s4-evm-09_00_00_02.tar.gz

Build steps followed - https://software-dl.ti.com/jacinto7/esd/processor-sdk-qnx-j784s4/09_00_00_03/exports/docs/build_steps_j784s4.html

The compilation is successfull, but when we tried to make the ethernet interface up using steps mentioned as,

https://software-dl.ti.com/jacinto7/esd/processor-sdk-qnx-j784s4/08_06_00_07/exports/docs/qnx_sdk_components_j784s4.html#

We are getting symbol link errors as below screenshot,

Unknown symbol: gEnetPhyDrvVsc8514 referenced from devnp-cpsw2g.so

Kindly provide us the clarification on this error, why is this happening with the latest versions of PSDK QNX and RTOS.

Please note - The same issue observed with j721e_evm board as well, procedure followed is same as above with respective BSP

over 2 years ago

0 Michael Nichols over 2 years ago

TI__Intellectual 1990 points

Hi,

Are you building for SPL+Uboot or for SBL?

Additionally, before you run the io-pkt command, can you run "slog2info -w &" and share the logs that get generated trying to start the network driver?

-MN

0 VAISALI B over 1 year ago in reply to Michael Nichols

Prodigy 30 points

Hi,

Yes, we are building SPL+Uboot

PFB log messages after slog2info started,

J784S4-EVM@QNX:/# slog2info -c
J784S4-EVM@QNX:/# slog2info -w &
[1] 573465
J784S4-EVM@QNX:/# random.5 low 0 -----UNSYNC-----
random.5 high 0 -----UNSYNC-----
Jan 01 00:00:00.031 console.2 0 -----ONLINE-----
console.2 out 0 -----UNSYNC-----
Jan 01 00:00:00.038 random.5 0 -----ONLINE-----
random.5 default 0 -----UNSYNC-----
Jan 01 00:00:00.039 random.5..0 0 -----ONLINE-----
random.5..0 slog 0 -----UNSYNC-----
Jan 01 00:00:00.001 devb_sdmmc_am65x.4105 0 -----ONLINE-----
devb_sdmmc_am65x.4105 slog 0 -----UNSYNC-----
Jan 01 00:00:00.003 devb_sdmmc_am65x.4106 0 -----ONLINE-----
devb_sdmmc_am65x.4106 slog 0 -----UNSYNC-----
Jan 01 00:00:00.130 iopkt.434187 0 -----ONLINE-----
iopkt.434187 main_buffer 0 -----UNSYNC-----
Jan 01 00:00:00.133 io_usb_otg.434188 0 -----ONLINE-----
io_usb_otg.434188 slog 0 -----UNSYNC-----
Jan 01 00:00:00.537 tisci_mgr.479246 0 -----ONLINE-----
tisci_mgr.479246 slog 0 -----UNSYNC-----
Jan 01 00:00:00.544 shmemallocator.491537 0 -----ONLINE-----
shmemallocator.491537 slog 0 -----UNSYNC-----
Jan 01 00:00:00.558 tiipc_mgr.495634 0 -----ONLINE-----
tiipc_mgr.495634 slog 0 -----UNSYNC-----
Jan 01 00:00:00.737 tiudma_mgr.499731 0 -----ONLINE-----
tiudma_mgr.499731 slog 0 -----UNSYNC-----
Jan 01 00:00:00.776 ti_vpu_codec_mgr.503828 0 -----ONLINE-----
ti_vpu_codec_mgr.503828 slog 0 -----UNSYNC-----
Jan 01 00:00:00.972 screen.507925 0 -----ONLINE-----
screen.507925 slog 0 -----UNSYNC-----
Jan 01 00:00:00.981 screen.507925..0 0 -----ONLINE-----
screen.507925..0 default 0 -----UNSYNC-----
Jan 01 00:00:01.015 devf_j7_ospi.520214 0 -----ONLINE-----
devf_j7_ospi.520214 slog 0 -----UNSYNC-----

J784S4-EVM@QNX:/# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33136
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
J784S4-EVM@QNX:/# io
io io-blk.so io-pkt-v6-hc io-usb-otg
J784S4-EVM@QNX:/# io-pkt-v6-hc -d cpsw2g
J784S4-EVM@QNX:/# unknown symbol: gEnetPhyDrvVsc8514 referenced from devnp-cpsw2g.so
unknown symbol: gEnetPhyDrvVsc8514 referenced from devnp-cpsw2g.so
unknown symbol: EnetOsalDflt_initCfg referenced from devnp-cpsw2g.so
Jan 01 00:01:28.006 iopkt.598042 0 -----ONLINE-----
Jan 01 00:01:28.007 iopkt.598042 main_buffer* 0 tcpip starting
Jan 01 00:01:28.007 iopkt.598042 main_buffer 0 smmu support is disabled
Jan 01 00:01:28.008 iopkt.598042 main_buffer 0 initializing IPsec...
Jan 01 00:01:28.008 iopkt.598042 main_buffer 0 done

Jan 01 00:01:28.008 iopkt.598042 main_buffer 0 IPsec: Initialized Security Association Processing.

Jan 01 00:01:28.033 iopkt.598042 main_buffer 0 Unable to load devnp-cpsw2g.so: (null)

J784S4-EVM@QNX:/# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33136
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1

0 Michael Nichols over 1 year ago in reply to VAISALI B

TI__Intellectual 1990 points

Hi Vaisali,

I believe I have found a root cause and need to talk to one of the developers. I will get back to you tomorrow.

-MN

0 Michael Nichols over 1 year ago in reply to Michael Nichols

TI__Intellectual 1990 points

Hi,

It seems to been an issue with a few files being left out of the 9.0 release. My suggestion is to use the 8.6 release until the 9.0 release is updated.

-MN