Development kit suggestions

We must assume that your stated, "26 lines" includes various strobe and chip select signals as well as data.  Is this correct?  Except for the external bus Stellaris MCUs - these top out @ 8 bit ports.  This implies that if writing to the Stellaris you could present your parallel data across multiple Stellaris 8-bit Ports - but would have to provide multiple strobe signals - so that each port could capture your data.  Is this a deal-breaker for your Ap?

Our group employ Stellaris & other ARM MCUs - some support up to 16 bits parallel data w/in a single GPIO parallel transaction (call it a port) - which still may be limiting to you.

We have designed wide, parallel bus "transactors" - this usually is the realm of FPGAs which provide the great flexibility and hi-speed which may be more appropriate...

Hi,

What we are trying to achieve here is a communication between a micro-controller and a neural networks chip. This chip has a total 26 control signals which would be required for communication, 16 bit bidirectional data bus, bidirectional 5-bit register address and a data strobe signal, a ready signal (which will be provided to the controller form the chip), and two other signals. Apart form above mentioned signals we have a 4 other signals which we would need (chip select, stand by, daisy Chan in and daisy chain out ). 

Then there are some output signal form the chip that we would need to know about ( 4 signals ). Our operating frequency is 27 MHz, and timing is a critical factor. 

So, keeping above factors in mind do you have a suggestions for us ?

Regards

Avinash

This level of detail/effort best handled by officialdom.   Your link or brief posting of device's timing chart goes far to prevent waste of time/effort...