[EXT_EP-9269] NVS top level defines NVS_lock and NVS_unlock APIs but do not connect them to the appropriate function pointer. Created: 04/Dec/18 Updated: 19/Feb/20 Resolved: 04/Dec/18 |
|
| Status: | Fixed |
| Project: | Embedded Software & Tools |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | TI User | Assignee: | TI User |
| Resolution: | Fixed | Votes: | 0 |
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Product: | TI Device Drivers |
| Internal ID: | TIDRIVERS-3423 |
| Found In Release: | 3.70.00 |
| Fix In Release: | CORESDK_4_10_00 |
| Release Notes: | The NVS.h defines NVS_lock() and NVS_unlock() as well as function pointer entries for these. The NVS.c file however, does not implement these functions even though device specific implementations exist. The only driver that seems to not implement these is the CC32XX version, while all others actually have these implemented and present in the function pointer table. As documentation suggest costumers should use these functions, they should be properly implemented on the top-level or a comment should be added that these APIs are not meant to be used. |
| Description |
|
NVS top level defines NVS_lock and NVS_unlock APIs but do not connect them to the appropriate function pointer. |