RTEMS_FATAL_SOURCE_EXCEPTION on booting PRU for beagleboneblack

[Nils Hölscher]

Hi Utkarsh,

It looks like your device tree is fine, since libbsd (using the device
tree) initializes before the network is configured.
The network config starts here
<https://github.com/nilhoel1/rtems-pru/blob/master/main.c#L356> and libbsd
initializes here
<https://github.com/nilhoel1/rtems-pru/blob/master/main.c#L329>.

The app is failing in this function
<https://github.com/nilhoel1/rtems-pru/blob/master/main.c#L63>, since the
shell has not started.
I am sorry, Inever encountered that problem, nor do I know what is causing
your kernel to crash.
Hopefully my hints will help.

Best,
Nils


On Tue, 11 Feb 2020 at 19:38, Utkarsh Rai <utkarsh.rai60 at gmail.com> wrote:

> While trying to boot the PRU app from this
> <https://github.com/nilhoel1/rtems-pru> repo. I
> encounter RTEMS_FATAL_SOURCE_EXCEPTION. The complete log goes
> something like this:-
>
> media listener: event = PARTITION ATTACH, state = INQUIRY, src =
> /dev/mmcsd-0
> media listener: event = PARTITION ATTACH, state = SUCCESS, src =
> /dev/mmcsd-0, dest = /dev/mmcsd-0-0
> media listener: event = MOUNT, state = INQUIRY, src = /dev/mmcsd-0-0
> media listener: event = MOUNT, state = SUCCESS, src = /dev/mmcsd-0-0, dest
> = /media/mmcsd-0-0
> SD: OK
> rc.conf: loading: /etc/rc.conf
> rc.conf: start: /etc/rc.conf size:165, timeout: 10
>
> *** FATAL ***
> fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
>
> R0   = 0x8064d5a8 R8  = 0x010100ae
> R1   = 0x808081c6 R9  = 0x0000000d
> R2   = 0x80807ef0 R10 = 0x00000001
> R3   = 0x00000000 R11 = 0x80807ee8
> R4   = 0x8064d5a8 R12 = 0x60000113
> R5   = 0x80807ee8 SP  = 0x806502e0
> R6   = 0x80807ee8 LR  = 0x8020eb3c
> R7   = 0x0000000d PC  = 0x8020e824
> CPSR = 0xa0000113 VEC = 0x00000004
> RTEMS version: 5.0.0.e22554535796fc29a7ed7c5e2338128e324a621d
> RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5 (599c4d7c87fa), Newlib
> d14714c69)
> executing thread ID: 0x08a010001
> executing thread name: UI1
> U-Boot SPL 2019.04-00002-gbb4af0f50f (Jul 08 2019 - 11:44:39 -0500)
> Trying to boot from MMC2
> Loading Environment from EXT4...
> ** Unable to use mmc 0:1 for loading the env **
>
> I have used the binary of this
> <https://gist.github.com/nilhoel1/90bad502dbe94eeb6dbb816f7e61e9e4>
> overlay and the relevant commands in uEnv.txt are:-
> load mmc 0 0x82000000 pru.exe.img;
> load mmc 0 0x88000000 am335x-boneblack.dtb;
> load mmc 0 0x880f0000 AM335X-PRU-UIO-00A0.dtbo;
> fdt addr 0x88000000; fdt resize 65536; fdt apply 0x880f0000; bootm
> 0x82000000 - 0x88000000;
>
> Now since the booting timeout occurs at the /etc/rc.conf I suppose the
> problem is with the device tree files. Can someone please help me out with
> this one?
>
> Regards,
> Utkarsh Rai
>
> _______________________________________________
> devel mailing list
> devel at rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200211/80f00c45/attachment.html>