MSP-EXP432E401Y: Configuring EPI for use under TI-RTOS Network services.

I think you can find something under this link:

e2e.ti.com/.../msp432e401y-using-qssi-or-epi-with-sd-card

Hi,

Thanks for your tip.

But when I follow the links I end up either in using an SPI device under RTOS or in a no-RTOS environment, directing the attention away from using the EPI.

What puzzles me is that despite the EPI is defined as a peripheral in the MSP432 documents (and many other devices), and the epi.c found under ti\devices\msp432e4\driverlib is characterized as a driver for the EPI module, there is no EPI driver included in the TI Drivers environment and thus, not to be found in the sysconfig tools along with all the other peripheral drivers.

Using the EPI is, besides configuring a memory mapped access, about handling interrupts and data like any of the other peripherals.
From illustrations I have seen, the EPI might be configured and handled separately from e.g., the TI-RTOS environment, but as the EPI seem "left out in the cold" I fear that  there is a subtle reason for this. Hence, I am trying to find a recommendation on how to migrate the no-RTOS driver (epi.c) into the TI-RTOS environment, but have  not succeeded yet. I have found migration description from no-rtos to no-rtos and from rtos to rtos, but not from no-rtos to rtos environment.

So, if anyone have a tip for this, I would be grateful.

Hi,

Yes, for the TI driver, it doesn't include the EPI code example. The reason is that our software team doesn't make it...

Currently, we don't have any plan to update the MSP432E SDK. So, I am sorry if you want to use it under TI-RTOS, we can't give you too much help.

For the guidance of no-rtos to rtos environment, it is the same condition.

Eason

Hi,

Thanks again for the information.
Using an RTOS is not imperative in this project, but the UDP-echo example project provided a tempting kick-off for my design.
As far as I can see, I then have two options on the MSP432:

1. Extend the UDP-echo project with a self-made configuration of the EPI.
2. Try to combine the no-RTOS lwIP with re-designed EPI SDRAM to EPI HB16 application.

The background for my application is to design a 1MHz sensor system with a DAC and 16ch simultaneously sampling ADC system running in 256 samples burst-lengths. Between the bursts, averaged sensor-data shall be delivered over a 100bit/s Ethernet.
The chosen 2 x AD7606C ADCs offers a 16-bit data-bus and must then be read at a high rate (some 20MHz).
As the MSP432E401 offers a compact Ethernet solution and an EPI + uDMA, this solution seemed a good alternative to e.g., a FPGA solution with a soft-core processor.
But the lack of EPI support makes me uncertain with respect to amount of work required to succeed compared to e.g., an FPGA solution.
An FPGA offers a very flexible interfacing of the ADC/DAC components, but requires a higher level of skill from my customer to take over the product.
If I choose to try out the MSP432, I think the option 1 would be my preferred path as a bare-metal configuration of the EPI interface appear easier than digging into the lwIP configurations.

Regarding the EPI, the example code I find is solely SDRAM oriented. Is there any application notes available for HB16 RAM/Peripheral configurations?

Eventually, if you can recommend a more suitable solution than the MSP432E401 from the TI assortment, I am interested.

Best regards
Terje

Hi Terje,

Thank you for sharing more details to me.

For MSP432, I don't see any example code for HB16 RAM. I would advise you to look into the materials for TIVA MCU (Like TM4C1294KCPDT). You can find the EPI and Ethernet in it as well. It have more materials than MSP432E series. Hope you can find the solution.

Eason.

Thanks for your understanding. Wish you good luck.