Other Parts Discussed in Thread: HALCOGEN
I have a problem with using the CAN code generated by Halcogen and used by CCS. In the Halcogen build model, device programming is statically set up based on the specification via GUI. Unfortunately, there are (many) instances where the use of the device is based on configuration information that's only available after some system configurations are determined.
For instance, with the CAN device, a message box has to be configured either as transmit or as received, but not both. However, the software may determine based on some (late) "personality configuration" that the given message box would be used for transmit or receive, regardless of what Halcogen was set up (statically) to do. It seems to me that the only viable thing is to modify the canInit() code so that it can set up the message box one way or the other, based on some config flag. The Halcogen-generated code is pretty involved, so finding the right place to set the register bit(s) could be painful (and hard to maintain).
Anyone have better ideas how to work with/around this (possibly huge) limitation?