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.

TMDS64GPEVM: Sbl, crypto and ethernet example working together error

Part Number: TMDS64GPEVM

Hi TI Experts

I'm working on a bootloader project on the TMDS64GPEVM development board.

The versions of CCS, SysConfig and mcu_plus_sdk I use are as follows:

CCS: 12.1.0

SDK: mcu_plus_sdk_am64x_08_05_00_24

SysConfig: 1.14.0

I first started by integrating the crypto_aes_ecb_256 project into the sbl_ospi_linux project. As a result, I can use both bootloader and crypto modules and thus I can easily do what I want to do.

Afterwards, I integrated the enet_cpsw_rawhttpserver ethernet project into this project, which ran smoothly. Even though I perform the encryption and ethernet operations in different situations (i.e. when the enet driver is opened, the sa2ul and crypto driver is not opened or vice versa) I get an error like the one below.

Enabling Clocks!
EnetUdma_openRxCh: 2086
EnetHostPortDma_open: 121
Cpsw_openInternal: 893
Cpsw_closeInternal: 984
Assertion @ Line: 984 in /home/gtbldadm/nightlybuilds/mcupsdk_internal/jenkins/mcu_plus_sdk_am64x_08_05_00_24/source/networking/enet/core/src/per/V1/cpsw.c: hCpsw->hRxRsvdFlow != NULL

When I run the enet_cpsw_raw http server example in mcu_plus_sdk alone, it works properly. I attribute this to udma. Because both crypto and enet modules use pktdma. When I activate pktdma in both modules in SysConfig, there is no problem. However, while it is running, the problem I mentioned above occurs.

Is this problem related to udma? If not, what could be the reason?

How can I use enet and crypto modules together?

Thanks...