Bastian,
Thank you for joining this thread. Your help will be appreciated.
As I explained above, the difficult way to solve this problem is to analyze every element of the application and find the correction to the code that will make this work. There is no easy wisdom that can be shared to tell you remotely which register to change or which thread is blocking your transfers. The best I can do for that path is to recommend more study of the McBSP User Guide to understand the sequences to initialize and to restart the McBSP. For example, in the User Guide it says
[quote user="McBSP UG:"]Either of the following events clears the RFULL bit to 0 and allows subsequent transfers to be read properly:
- Reading DRR
- Resetting the receiver (RRST = 0) or the device
[/quote]
The easy wisdom to find a solution is to find an example program and try to get the serial port working with that. If it does not work and you get the RFULL in that case, It will be easier to get some discussion going about code problems. If it does work, then you have an example to compare against the custom code you have written yourself.
Another path I have used is to start disabling everything in your application, either by removing the code or disabling interrupts and such. Get the application reduced to where it is only a McBSP transfer application and see if it still fails. It will be much easier to determine if you have timing issues blocking the McBSP accesses or logic errors in the registers being used. But at your speeds, the DSP should be able to easily keep up with the McBSP data rate even using polling instead of interrupts or EDMA.
Regards,
RandyP