I agree, but the problem is I cannot dig inside the fopen or any other file APIs, I think Keil itself is restricting the action. I can only get the return code. And also have no idea how these file APIs are pointing to the drivers. The File configuration file itself doesn't provide sufficient information as it comes with direct sections using the configuration wizard facility of Keil.
Can you tell me where I can learn these file management APIs, linking to the driver? Also, how do I understand these standard libraries linking to the low-level drivers? As I was able to read- write directly to the memory, but it has become more like an EEPROM.
Let me know the same thing with any network protocols because it is having the same story, Directly using Network APIs provided by Keil works for me but I have no understanding of how low-level interacts with the higher layer of the protocol.
Thank you