- To: jlarmour at redhat dot co dot uk
- Subject: MBX
- From: "amassa at cts dot com" <amassa at cts dot com>
- Date: Thu, 8 Jun 2000 11:44:37 -0700 (PDT)
- Cc: ecos-discuss at sourceware dot cygnus dot com
I sent this to you before, but I had the wrong address, so I'm resending...
I am kinda confused now. What I did was just remove the directories built
from the configuration tool and resave the same configuration I setup for my
board (40 MHz clock). After I recompiled and downloaded the stub it started
to work as I expected. It's odd because I didn't change anything. Could it
be that something didn't get compiled the first time correctly or maybe it
didn't download into flash correctly?
However, now it seems that when I try to run one of the example programs
using insight 5.0 (with the patch installed) the code will download but it
crashes quite a bit. The target will just stop communicating with insight.
This makes it difficult to debug since I have to cycle power on the MBX
board and re-download the code each time.
Is this flaky behavior typical of the MBX board - do you guys experience
similar problems or are your platforms more robust?
Thanks,
Anthony