I have a test program (mostly TI decoder test program) that uses various file I/O operations. All is fine, this is a non-Bios-based program.
I use that same program in my BIOS-based code and there are a few problems - the most obvious is that an fopen for a read ("r") will succeed even for a file that is not there.
Note - I saw an old E2E posting about a similar issue - it says a problem with file I/O can be not enough heap. I tested the heap via malloc - I can malloc over 2mbytes (somewhere towards 20mbytes it finally fails).
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.