|
44 | 44 |
|
45 | 45 | ecudb.c / ecudb.h (1) RO / lib
|
46 | 46 |
|
47 |
| - Main driver which have all dbc frames structs / pack functions / unpack functions these source files preferably to place in lib level directory because they are RO using model and can be shared among few separated projects. |
| 47 | + Main driver which have all dbc frames structs / pack functions / unpack functions these |
| 48 | + source files preferably to place in lib level directory because they are RO using model |
| 49 | + and can be shared among few separated projects. |
48 | 50 |
|
49 | 51 | ecudb-fmon.h (2) RO / lib
|
50 | 52 |
|
51 |
| - Contains monitoring functions signatures which can be optionally called from unpack frame functions. Best option to place file beside main driver files (above). |
| 53 | + Contains monitoring functions signatures which can be optionally called from unpack |
| 54 | + frame functions. Best option to place file beside main driver files (above). |
52 | 55 |
|
53 | 56 | ecudb-fmon.c (3) app
|
54 | 57 |
|
55 |
| - User defined functions with diagnostic purpose. DLC, rolling, checksum errors can be handled automatically if dedicated configuration enabled. This file is user level source code. |
| 58 | + User defined functions with diagnostic purpose. DLC, rolling, checksum errors can be |
| 59 | + handled automatically if dedicated configuration enabled. This file is user level |
| 60 | + source code. |
56 | 61 |
|
57 | 62 | ecudb-config.h (4) app
|
58 | 63 |
|
59 |
| - This is application specific configuration file. If you have a few projects (applications) which referenced on single main driver (1,2) source file each project must have self copy of this configuration. Source code (1,2) includes this configuration. If a few dbc matrix is in use in your application then for each of (1,2) specific configuration file must be presented |
| 64 | + This is application specific configuration file. If you have a few projects |
| 65 | + (applications) which referenced on single main driver (1,2) source file each project |
| 66 | + must have self copy of this configuration. Source code (1,2) includes this |
| 67 | + configuration. If a few dbc matrix is in use in your application then for each of (1,2) |
| 68 | + specific configuration file must be presented |
60 | 69 |
|
61 | 70 | dbccodeconf.h (5) app
|
62 | 71 |
|
63 |
| - This is application specific configuration file. This file may include CanRxFrame definition, sigfloat_t typedef and |
64 |
| - binutil macros which enables rx and tx structures allocation inside binutil code. This file must be single for application, source code (4,6) includes this configuration |
| 72 | + This is application specific configuration file. This file may include CanRxFrame |
| 73 | + definition, sigfloat_t typedef and binutil macros which enables rx and tx structures |
| 74 | + allocation inside binutil code. This file must be single for application, |
| 75 | + source code (4,6) includes this configuration |
65 | 76 |
|
66 | 77 | ecudb-binutil.c / ecudb-binutil.h (6) RO / app
|
67 | 78 |
|
68 |
| - Basically this is application specific file. But it also can be used at the lib level. Depends on using. Some times there are few different modules which handle different parts of the single matrix (and single (1,2) instances) |
| 79 | + Basically this is application specific file. But it also can be used at the lib level. |
| 80 | + Depends on using. Some times there are few different modules which handle different |
| 81 | + parts of the single matrix (and single (1,2) instances) |
69 | 82 |
|
70 | 83 | canmonitorutil.h (7) lib
|
71 | 84 |
|
|
0 commit comments