Tool/software:
Hello,
In ti_drivers_open_close.h there is the following comment many times:
"Driver open/close - can be used by application when Driver_open() and Driver_close() is not used directly and app wants to control the various driver open/close sequences"
Until now that is precisely how our application has been working. e.g. Driver_open() is not called from the application but Drivers_mcanOpen() is called.
I have just updated the SDK from mcu_plus_sdk_am263px_09_02_00_56 to mcu_plus_sdk_am263px_10_02_00_15 to find that for the ADC there is now extra code in Driver_open() before Driver_adcOpen():
Of course, just calling Driver_adcOpen() skips this code. If this code is to be executed, then Driver_Open() must be called breaking the previously (sensible) principle for all drivers.
This obviously has a big impact on my application and forcing unnecessary effort.
<Opening Question>
- Why on earth isn't this extra code inside Driver_adcOpen()?