S
s.subbarayan
Dear all,
I am currently working on a project where we are asked to display
the error logs on the hyperterminal on the press of the key.Typically
the log should collect all the error messages and if and only if the
user presses a key on my H/W I will display it on the hyper
terminal.Note that file system is not available to me,so writing to a
file and printing it in a delayed manner is not possible in my case.
I need some inputs on how this log could be designed?what should be
best data structure to store error logs?Typically the error logs
collect info about corrupted memory regions when I run a memory test
application over the memory chips like nvram,sdram,flash.
Having a linked list which will collect data was in my mind,but only
fear for me is,having a linked list will occupy more memory,and in the
worst case if I consider the entire range of memory to be corrupted
and I need to display all the memory address along with some debug
messages,my memory will bloat and I dont have enough memory for this.
So I need some inputs what could be the best design available for such
an application?Note that I use C language and Vxworks OS.My test
application runs from the boot code so none of the OS features are
available to me,else I would have gone for vxworks LogMsg() call...
Advanced thanks for all your replys,
Regards,
s.subbarayan
I am currently working on a project where we are asked to display
the error logs on the hyperterminal on the press of the key.Typically
the log should collect all the error messages and if and only if the
user presses a key on my H/W I will display it on the hyper
terminal.Note that file system is not available to me,so writing to a
file and printing it in a delayed manner is not possible in my case.
I need some inputs on how this log could be designed?what should be
best data structure to store error logs?Typically the error logs
collect info about corrupted memory regions when I run a memory test
application over the memory chips like nvram,sdram,flash.
Having a linked list which will collect data was in my mind,but only
fear for me is,having a linked list will occupy more memory,and in the
worst case if I consider the entire range of memory to be corrupted
and I need to display all the memory address along with some debug
messages,my memory will bloat and I dont have enough memory for this.
So I need some inputs what could be the best design available for such
an application?Note that I use C language and Vxworks OS.My test
application runs from the boot code so none of the OS features are
available to me,else I would have gone for vxworks LogMsg() call...
Advanced thanks for all your replys,
Regards,
s.subbarayan