This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TDA4VM: When "ifconfig am up", qnx is panic.

Part Number: TDA4VM

Hi

expert.

I have qnx panic error.

I use SDK7_1 and custom key HS-SE board.

So I rebuild SBL with "make sciclient_boardcfg BOARD=j721e_evm BUILD_HS=yes -j8" command.

After that, I have qnx panic error. HS-TI dummy key board have no error.

I compared SBL code and I find difference in "sciclient_defaultBoardcfg_rm.c" because of es1_1 patch.

In Custom key board if I change "io-pkt-v6-hc" command option, other outputs appear.

"on -C 0 io-pkt-v6-hc -d cpsw2g ptp=1,mac-to-mac=1,speed=1000,p0mac=020000002010,typed_mem=cpsw2g,udma_chnum=53,smmu=1,virt_id=5 -ptcpip pkt_typed_mem=cpsw2g"

1. smmu = 1 -> 0

no panic

2. smmu = 1 and virt_id=5 -> 2

no panic, but virt_id=1 and virt_id=4 have panic status.

Q. I want to know role of smmu and virt_id and how to set those value?

Thank you.

  • Hi,

    Is the QNX sMMUMan framework running in the setup under test?  This will dictate whether virt_id parameter should be being used when launching the CPSW2G driver.

    6.2. How To Enable SMMU For The DEVNP CPSW2G Driver — Processor SDK QNX (ti.com)

    For information on sMMUMan configuration please contact QNX or reference QNX documentation.

    If the sMMUMan framework is in use the channel Id and virt_id, must align with the available resources that have been assigned to the A72.   In the two screenshots above:

    • Left side shows valid A72 virt_ids as: 2,3,4,5,6
    • Right side shows valid A72 virt_ids as: 2

    Regards,

    kb

  • Hi,

    Q1. How do you know valid A72 virt_ids on the two pictures? I can't distinguish.

    Q2. Does difference of x509CertificateGen.sh affect setting to virt_ids?

    -> No effect

    I rollbacked ES1_1 patches and I applied only "ti-fs-firmware-j721e_sr1_1-hs-cert.bin", ti-fs-firmware-j721e_sr1_1-hs-enc.bin and "firmwareHeaderGen.sh" in ES1_1 patch. I resolved this issue.

    Thank you.