Forum Discussion
Altera_Forum
Honored Contributor
15 years agoHi,
I have implemented the tightly coupled memory as the shared memory. However ,I have found it is really difficult to implement the communication software program of the shared memory. Originally I used the mailboxes core and the API mailbox_pend() can automatically block when there is no message and unblock when there is a message , which is very easy to be implemented in a process. However , since now I use hardware mutex for the shared memory, there is no such API. The problem is that this is a 'mutex' not a 'samephore' which means it cann't be released by other processors! Since there is no samephore , I think I can not implment the communication in a while() loop as the classical producer&consumer problem. If Processor1 has put some data into the shared memory, Processor2 can't know when the data is ready.Even Processor2 knows, Processor1 will not know when Processor2 has finished reading the data. Am I right? I am not a CS major so there might be some misunderstanding:(