Hi Andrew I still thinks there is a problem with the gdb stubs in redboot. I can load and run a standalone application which uses interrupts into external ram using gdb, however If I set breakpoints or try to single step the application stops and gdb becomes unresponsive.
I can burn the same application into flash and load with Redboot and this works fine. I was wondering if there are options in the configtool which should be selected but are'nt. I am not familiar with many of these settings. Best Regards Miklos > On Tue, Sep 19, 2006 at 03:29:56PM +0100, [EMAIL PROTECTED] wrote: > > Hi Andrew > > > > Ive been looking in the hal_platform_setup and it seems as though > > Redboot copies the first 64 bytes of vectors to internal SRAM. An > > then remaps the vectors to internal SRAM. > > > > What then happens if an interrupt occurs in my code, How is it > > handled by Redboot. > > > > Should I copy by vectors to this location? > > > > I am a bit confused > > Is you application an eCos application? If so eCos will do this > itself. > > However if you are writing a standalone application which does not use > eCos, you have to look after interrupts yourself. > > Andrew > Miklos Pflancer Electronics Engineer -------------------------------------------------- email : [EMAIL PROTECTED] -------------------------------------------------- dB Research Ltd Concept House Merton Road Bootle Liverpool L20 3BG UK Tel (+44)(0)151 330 0800 Fax (+44)(0)151 330 0808 -------------------------------------------------- -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
