[En-Nut-Discussion] Correction to previous post and more info

[Kyle Rhodes]

Harald,

Thank you for your response.  As you can see I've been at this for a
while, and have been incrementally posting as I've discovered new
information.  I have since switched to _write() and _read() with no
change.  However, in searching for other avenues of fixing the problem,
I looked at my compiler.  I had a pre-release version of avr-gcc (the
latest at the time of starting this project) and I noticed that there
was a new version available.  I installed the new version, and it seems
to have corrected the problem!  I am still having an issue with one
aspect of the program, but I think it may be a result of my desperate
attempts to get the protocol functioning.  I haven't experienced any
flakey _read() or _write() behavior.  

I'll also mention that I wouldn't expect to have any memory issues with
my program since I never malloc off the heap.  Everything I use is
statically defined, aside from a few local variables.  All in all, I
have probably 15k of RAM free.  However, I will never disagree with the
possibility of a memory leak on my part.  (believe me I've looked)  If
there's anything I hate more, it's weird problems that are not easily
explained, especially with a deadline looming over my head. :)

I will say that I went deep into the Nut/OS code to see if I could find
anything, and I didn't.  I will have to commend you on a job well done
with this fine RTOS.  The only problem is (me) making sure the most
recent tools are installed, as with any open source project.  :)


Thanks for your help,

Kyle Rhodes
Hardware / Software Engineer
gh, LLC
3000 Kent Ave
Lafayette, IN 47906
(765) 775-3776  ext 205