On 14/08/2019 07:56, mojtaba nadi wrote:
thanks Sebastian for your answer but we are new in rtems and don't know
how to use debugger.
can you help us please?
If you want to use RTEMS seriously, then I recommend to spend some time
to set up a debugger for your target. Basic tests can be made r
thanks a lot Chris we found error that say "error = kern_recvit(td, s, mp,
UIO_USERSPACE, NULL);"
we google it and if we can't find the solution, we make a other mail-list.
We wish the best for you.
On Wed, Aug 14, 2019 at 11:54 AM Chris Johns wrote:
> On 14/8/19 3:56 pm, mojtaba nadi wrote:
On 14/8/19 3:56 pm, mojtaba nadi wrote:
> thanks Sebastian for your answer but we are new in rtems and don't know how to
> use debugger.
> can you help us please?
A simple way to see the code that caused the exception is to run:
arm-rtems5-objdump -d --source my.exe | less
then search for the a
thanks Sebastian for your answer but we are new in rtems and don't know how
to use debugger.
can you help us please?
On Wed, Aug 14, 2019 at 9:35 AM Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
>
>
> On 13/08/2019 15:35, mojtaba nadi wrote:
> > *** FATAL ***
> > fatal source: 9 (R
On 13/08/2019 15:35, mojtaba nadi wrote:
*** FATAL ***
fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
R0 = 0x002d2940 R8 = 0x000b
R1 = 0x002d4080 R9 = 0x002d2940
R2 = 0x00215038 R10 = 0x002d4070
R3 = 0x002d4070 R11 = 0x
R4 = 0x0010 R12 = 0x002d4014
R5 = 0x
hi afshin
tanks for your answer but we tried many different stack-size and different
mode of making task but it didn't work.
On Tue, Aug 13, 2019 at 10:12 PM Afshin Jamaali (Arian)
wrote:
> Hi Mojtaba,
>
>
>
> You have created task1 with RTEMS_MINIMUM_STACK_SIZE. Are you sure this
> amount of s
Hi Mojtaba,
You have created task1 with RTEMS_MINIMUM_STACK_SIZE. Are you sure this amount
of stack is enough? Maybe when recvfrom() receives data and writes into the
recv_buf[] array, it corrupts the stack. Maybe it is not so, not sure.
Best Regards,
Afshin
From: users [mailto:users
