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: The built output from SDK and Yocto are different

Part Number: TDA4VM


Hi TI Support team,

I'd like to have a question.

My team observe that the output build from SDK and the Yocto are different.

For examble:

The Linux kernel:

- Build from SDK: We have the error relate to "cryptodev" and it lead to the issue that IPC is not working:

- Built from Yocto: The built output is normall, there are no issue about cryptodev and IPC working normally.

Uboot:

We just found that the Uboot from Yocto and SDK also have different boot arguments.

We are using the SDK from here: https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-J721E/08.05.00.08

May I ask why there are different between them even the source code are the same? May I missed some steps during the environment setup?

Best regards,

Loc.Ta.

  • Hi,

    - Build from SDK: We have the error relate to "cryptodev" and it lead to the issue that IPC is not working:

    I'm not sure about the exact build steps that you have followed, but it is possible that you did not build cryptodev because it is an out of tree module.

    If your kernel is modified then you will need to rebuild the cryptodev module also and transfer to the filesystem. Please see $SDK_DIR/board-support/extra-drivers

    We just found that the Uboot from Yocto and SDK also have different boot arguments.

    Can you please share more details about this? What do you mean by different boot arguments?

    Regards
    Karthik