| |
|
This is the production (GA) release of IPC 1.00.01.48*
Interprocess communication mechanisms including message passing, streams, and linked lists, which work transparently in both uniprocessor and muiltiprocessor configurations.
The IPC product is comprised of three main packages
The following documentation is available:
Release notes from previous releases are also available in the relnotes_archive directory.
1.00.01.48 GA Build Release (this release).
Build Changes: The following were changed for this release
The customization of the memory maps for the above platforms was removed from the etc\config.bld.default file. Instead the etc\config.bld.default file references the custom platform packages listed above.
New Modules: The following new modules are available:
Bug Fixes and Minor Enhancements: See the
list below for abbreviated list of bug fixes and enhancements.
| ID | Headline |
| SDOCM00046958 | MessageQ message size should support more than 16 bits |
| SDOCM00053780 | CDOC: io.stream has broken link to xdc.runtime.knl.Sync module |
| SDOCM00056491 | IPC: MessageQ module does not differentiate between HIGH_PRIORITY and URGENT_PRIORITY of messages |
| SDOCM00056512 | IPC: MessageQ_get API does not return messages in FIFO manner on evmDM6467-XDS510USB and IPC 1.00.00.31 |
| SDOCM00056552 | IPC: MessageQ module does not raise assert when a wrong handle is used in MessageQ_get API |
| SDOCM00057207 | Can't open IPC 1.0.0.38 API document reference from CCSv4->help->help contents |
| SDOCM00057231 | IPC-MessageQ sprugo6.pdf: signature of MessageQ_get() in pdf file is not same as in CDOC |
| SDOCM00057235 | Stream/io ROV needs updating |
| SDOCM00057274 | GatePeterson/GateHWSem open should return Int not Status |
| SDOCM00054968 | CCSv4 : Links to xdc runtime are broken in "Help Contents" of CCSv4 for IPC Module |
| SDOCM00056333 | IPC:MessageQ_setMsgPri API is not working as expected |
| SDOCM00058631 | add CCS4 template support for multicore examples |
| SDOCM00058815 | Adding to a NameServer Instance statically in a module for 28x is broken |
| SDOCM00058629 | INameServerRemote_get return needs to be consistent with NameServer |
| SDOCM00057256 | ipc examples need to be completed. |
Interface/API changes: This release in not backward compatible with IPC 1.00.00.40 in the following areas:
This release supports the following hosts:
Windows XP SP2/SP3
Windows Vista
Linux (Redhat 4 and 5)
This release requires the following other software components and tools versions to successfully function:
| ID | Headline |
| SDOCM00058906 | Remote NameServer_get hangs if dest. not up |
| SDOCM00058860 | HeapBuf_sharedMemReq should return UInt32 not Int |
| SDOCM00058783 | Shared memory modules must check for correct memory alignment |
| SDOCM00058782 | Need to resolve reserved events config in Notify/Notify Driver |
| SDOCM00058747 | NotifyDriverLoopback should support static creation |
| SDOCM00057295 | IPC: documention issue |
| SDOCM00057277 | NameServer: ROV should show ALLOWGROWTH instead of 0xffffffff for numDynamic |
| SDOCM00057275 | ipc modules do not handle when MultiProc.Id = INVALIDID |
| SDOCM00057267 | IPC modules with shared memory need to use BitsXX instead of UIntXX |
| SDOCM00057265 | IPC/NameServer needs asynchronous support |
| SDOCM00057260 | ipc/family needs code review and full regression tests |
| SDOCM00057259 | IPC Benchmarks need be examined |
| SDOCM00057258 | IPC portion of User Guide needs updating |
| SDOCM00057257 | All IPC modules should support cacheFlag for better performance |
| SDOCM00057255 | xGConf Product View for IPC needs to be refined. |
| SDOCM00057254 | gates (Peterson and HWSem) needs code review and full regression tests |
| SDOCM00057253 | NameServerRemoteNotify needs code review and full regression tests |
| SDOCM00057251 | Notify needs code review and full regression tests |
| SDOCM00057250 | ListMP needs code review and full regression tests |
| SDOCM00057249 | SharedRegion needs code review and full regression tests |
| SDOCM00057248 | MessageQTransportShm needs code review and full regression tests |
| SDOCM00057247 | HeapMultiBuf needs code review and full regression tests |
| SDOCM00057246 | HeapBuf needs code review and full reSDOCM00057242gression tests |
| SDOCM00057245 | MessageQ needs code review and full regression tests |
| SDOCM00057244 | HeapBuf's trackMaxAllocs does not work properly |
| SDOCM00057243 | MessageQ heap management needs investigation [might require design change] |
| SDOCM00057242 | HeapMultiBuf does not work |
| SDOCM00057241 | Notify/notifyDrivers does not support static instance creation |
| SDOCM00057239 | HeapBuf does not support static instance creation |
| SDOCM00057238 | NameServerRemoteNotify does not support static instance creation |
| SDOCM00057236 | MessageQTransportShm does not support static instance creation |
| SDOCM00057049 | GatePeterson should support max protection configuration for optimization |
| SDOCM00057006 | ROV views needed for GatePeterson and GateHWSem |
| SDOCM00057005 | NotifyDriverShm should support static creation |
| SDOCM00047848 | MSGQ needs sequence # and RTA hooks |
| SDOCM00047053 | MessageQ_delete does not free memory back to user created heapMem |
All releases have 4 digits (M.mm.pp.bb). This includes GA and pre-releases (engineering, EA, beta, etc.). Pre-releases are denoted with a suffix (e.g. 1.01.00.15-eng or 1.01.00.21-beta).
This product's version follows a version format, M.mm.pp.bb, where M is a single digit Major number, mm is 2 digit minor number, pp is a 2 digit patch number, and b is an unrestricted set of digits used as an incrementing build counter.
To support multiple side-by-side installations of the product, the product version is encoded in the top level directory, ex. ipc_1_00_00_40.
Subsequent releases of patch upgrades will be identified by the patch number, ex. IPC 1.00.01.41 with directory ipc_1_00_01_41. Typically, these patches only include critical bug fixes.
Please note that version numbers and compatibility keys are NOT the same. For an explanation of compatibility keys, please refer to the 'Upgrade and Compatibility Information' section.
For technical support, contact softwaresupport@ti.com
Last updated: June 11, 2009