MCU-PLUS-SDK-AM263PX: Configuring MCSPI modules with different transfer modes with DMA

Hi Tollman,

I will investigate and come back to tomorrow.

Hi Tollman,

I didn't get any error after calling Drivers_open();  and Board_driversOpen(). 

I will see if I can replicate the issue on one of the MCSPI SDK examples, and let you know what I find.

Thanks. If possible, please share your CCS project for reproducing the issue.

Hi QJ,

I was able to replicate the issue on:

  TMDSCNCD263P-AM263Px Sitara Control Card

... using a modified version of SDK example:

  mcspi_loopback_dma_am263px-cc_r5fss0-0_freertos_ti-arm-clang

Procedure:

1) Imported and tested unmodified SDK example.

2) Verified SPI echo test passes:

3) Copied, SDK example, and renamed copy:

  mcspi_loopback_dma_am263px-cc_r5fss0-0_freertos_ti-arm-clang2

4) Added PMIC using a SDK example with PMIC included as a reference.

5) Retested. PMIC initialization results in error.  SPI echo test passes.

I am attaching the zipped project demonstrating the issue:

mcspi_loopback_dma_am263px-cc_r5fss0-0_freertos_ti-arm-clang2.zip

Regards,

Tollman

Thanks Tollman

I re-produced the same issue. It is a SW bug, and I will submit a bug ticket.

Hi QJ,

Can you please elaborate.

Is the symptom with using multiple distinct transfer modes in SysConfig-generated code?

Or is the issue specific to the PMIC driver?

Regards,

Tollman