This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: How to run ECO 3.0 on STM32
- From: Chris Holgate <chris at zynaptic dot com>
- To: kishore Srimat <kishorestp at gmail dot com>
- Cc: John Dallaway <john at dallaway dot org dot uk>, ecos-discuss at ecos dot sourceware dot org
- Date: Tue, 04 Aug 2009 12:54:16 +0100
- Subject: Re: [ECOS] Re: How to run ECO 3.0 on STM32
- References: <ab2643f10907271051r1b7d3be7x842a851c672a8456@mail.gmail.com> <ab2643f10907291037l522859cew679773694c705803@mail.gmail.com> <4A70A606.5060309@dallaway.org.uk> <ab2643f10907291433h8529d92qaf0e0b044367078@mail.gmail.com> <4A7156FF.9030206@dallaway.org.uk> <ab2643f10907301554r3d2b05e4h12e1a42d3ea8510a@mail.gmail.com> <4A72AAD3.70006@dallaway.org.uk> <ab2643f10908031505q33970e92k7b0d8631c4a0e11b@mail.gmail.com>
Hi Kishore,
kishore Srimat wrote:
> I tried to run with gdb but i constantly getting this error "Program
> recieved signal SIGBUS, bus error". And some times it freezes at the
> "Continuing".
Generally speaking, you should interpret the SIGBUS error the same way
as a UNIX segmentation fault - ie, you're trying to read or write to an
area of memory which is not there.
There is an extra quirk with the STM32 in that you can see similar
errors if the DMA controller attempts to access off-chip memory. You
will see this if you are doing a default RAM based build and enabling
the SPI drivers without specifying a suitable DMA bounce buffer.
> I tried to reset the board as it was suggested before running the
> example but no use. Any thoughts people ? Does anybody seen similar
> error ?
If it's not the SPI driver / DMA controller causing the error then the
chances are it's a null pointer dereference or similar bug in your
application. Try setting a breakpoint on cyg_user_start and take it
from there.
Chris.
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss