Where are you setting your initial breakpoint? Make sure you set a break point at cyg_start() or cyg_user_start() (anywhere during init before your code executes) to make sure that your code is not effecting the GDB connection. I would attempt running one of the examples/tests as well.
Which HAL are you using? How are you building your eCos kernel library (packages, settings, etc.) ? If you don't have asserts turned on, I would turn them on in your kernel configuration. They are a very handy debugging tool. On 2/15/07, Carlos Losada <[EMAIL PROTECTED]> wrote:
I previously had a problem with GDB stopping randomly, and now I have the inverse problem; it does not stop at all. Th setup includes RedBoot installed as a ROM Monitor in Flash with GDB stubs in HAL activated, and an application compiled to work with a rom monitor. The RedBoot CLI works fine. Using Eclipse/CDT I can download the application through the serial port, but GDB does not stop at the breakpoint. In fact, it does not appear to execute the program at all. Is it an eCos configuration problem? ____________________________________________________________________________________ It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. http://tools.search.yahoo.com/toolbar/features/mail/ -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
-- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
