In the following sections, figures show modules used by each scenario. Internally by MessageQ, rather than directly by the application. However, the APIs for other modules are then used The ability to dynamically allocate linked list elements from a heap. Optionally use shared memory and/or gates to manage synchronization. (BIOS-to-BIOS only) This scenario adds theĪbility to pass linked list elements between processors to the Without the overhead and complexity of message-passing Scenario is best used for simple synchronization between processors Notification is minimal–typically on the order of 32 bits. (BIOS-to-BIOS only) This scenario performs A number of variations of these cases are also possible: Setup to the setup with the most functionality, the use case options areĪs follows. You can use IPC modules in a variety of combinations. Provides details of IPC GateMP support with UIO driverĮxplains details of the additional RTOS IPC transports provided viaĮxplains how to rebuild the IPC libraries if you modify the source Provides details of migrating to IPC 3.x from previous releases Section describes the modules in the ti.sdo.utils package. Section describes the modules in the ti.sdo.ipc package. IPC Debugging Tools and Techniques on AM57xx.Provides details of customizing the resource table. Memory usage of applications that use IPC. Provides hints for improving the runtime performance and shared Customizing Memory map for creating Multicore Applications on AM57xx using IPC.Create DSP and IPU firmware using PDK drivers and IPC to load from ARM Linux on AM57xx devices.IPC Training lists available IPC training.Use Cases for IPC explains the various use cases for IPC.Links to API reference documentation for static configuration ( )Īnd run-time C processing ( ) for each module. This user’s guide contains the topics in the following list.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |