Hi,
What is relation between config file and .c/.h files present in dev package and how to relate configuration keywords with function present in code files?
Example: CAN_OPTIONS_CAN1, CAN_BITRATE_CAN1, TRC_OPTIONS_CAN1, TRC_FILE_MAX_SZ_MB
If we update existing code or add new functions, how can we reflect those into config files?
Relation between config and .c/.h files
-
- Sales & Support
- Posts: 786
- Joined: Fri 20. Sep 2019, 13:31
Re: Relation between config and .c/.h files
Hello,
I think you are refering to something completely unrelated to PCANBasic,
can you please clearify?
Sounds to me like you are talking about the PCAN-Router Pro FD Logging Firmware,
which is in no way related to PCANBasic.
Can you confirm?
Best Regards
Marvin
I think you are refering to something completely unrelated to PCANBasic,
can you please clearify?
Sounds to me like you are talking about the PCAN-Router Pro FD Logging Firmware,
which is in no way related to PCANBasic.
Can you confirm?
Best Regards
Marvin
Re: Relation between config and .c/.h files
Sorry, I moved my query to correct category now.
Moved to Board Index-->Hardware-->PCAN-Router Pro FD
Moved to Board Index-->Hardware-->PCAN-Router Pro FD
-
- Sales & Support
- Posts: 786
- Joined: Fri 20. Sep 2019, 13:31
Re: Relation between config and .c/.h files
Hi,
The config files belong to the Logger firmware, for
which the sources are not avilable in the PEAK-DevPack.
The default firmware examples do not come with configuration files and
do not showcase how they might be used in the context of a firmware.
So if you write your own firmware, by default a config file parsing will not be implemented.
If you do not need to have configurations files in your firmware
you can simply ignore the config file altogether and only work in code.
Best Regards
Marvin
The config files belong to the Logger firmware, for
which the sources are not avilable in the PEAK-DevPack.
The default firmware examples do not come with configuration files and
do not showcase how they might be used in the context of a firmware.
So if you write your own firmware, by default a config file parsing will not be implemented.
If you do not need to have configurations files in your firmware
you can simply ignore the config file altogether and only work in code.
Best Regards
Marvin