Try to load and run RTEMS Image on Cora-z7-10

[Heinz Junkes]

Yes, I can start an rtems image (RTEMS 5.1) on beaglebone (bboted by tftp in u-boot):

*** HELLO WORLD TEST ***
executing thread name: (Sep 10 2018 - 19:41:39 -0500), Build: PU  : AM335X-GP rev 2.1


But it looks to me like there is no ethernet device driver for RTEMS5.1 and LEGACY_STACK available. 
So I can't use Ethernet here.

So I have to switch to libbsd. I will now try again with RTEMS-master (6).

Viele Grüße
Heinz Junkes
--
Experience directly varies with equipment ruined.



> On 1. Jun 2022, at 22:37, Alan Cudmore <alan.cudmore at gmail.com> wrote:
> 
> I see you are trying RTEMS 5.1. I don’t think I tested that repository on RTEMS 5.1, but I do recall having a similar application working 5.1. I should be able to try a similar build on my Beaglebone.
> Were you able to successfully boot a RTEMS image from u-boot without libbsd?
> The first problem was booting the RTEMS 6 u-boot .img file, correct?
>  
> Regards,
> Alan
>  
> From: Heinz Junkes
> Sent: Wednesday, June 1, 2022 11:14 AM
> To: Alan Cudmore
> Cc: users at rtems.org
> Subject: Re: Try to load and run RTEMS Image on Cora-z7-10
>  
> I can add something directly. I found in your example (rki) how you talk to the network device. 
> I have implemented it in a similar way.
>  
> Unfortunately, I can't even get to the point.
>  
> The programme breaks off in rtems_bsd_initialize() at mi_startup()
>  
> ***** RTEMS Version: rtems-5.1.0 (ARM/ARMv4/beagleboneblack) *****
>  
> ***** Initializing network (libbsd, dhcpcd) *****
> create directory /etc
> create timer ...
> mutex init ...
> mi startup ...
>  
> *** FATAL ***
> fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
>  
> R0   = 0x00000000 R8  = 0x00000000
> R1   = 0x802ec93c R9  = 0x00000000
> R2   = 0x00000007 R10 = 0x00000064
> R3   = 0x006e6573 R11 = 0x8052e7e0
> R4   = 0x00000007 R12 = 0x01010101
> R5   = 0xfffffff7 SP  = 0x80553f30
> R6   = 0x802ec93c LR  = 0x8022fcb4
> R7   = 0x00000000 PC  = 0x8022ef68
> CPSR = 0x00000113 VEC = 0x00000004
> RTEMS version: 5.1.0
> RTEMS tools: 7.5.0 20191114 (RTEMS 5, RSB 5.1, Newlib 7947581)
> executing thread ID: 0x08b010001
> executing thread name:
>  
> Viele Grüße
> Heinz Junkes
> --
> Experience directly varies with equipment ruined.
>  
>  
>  
> > On 1. Jun 2022, at 15:30, Heinz Junkes <junkes at fhi-berlin.mpg.de> wrote:
> > 
> > Hi Alan,
> > Thanks for the feedback. Did you also use the Ethernet of the beagleboneblack in your demo. I can't see which if is implemented in the BSP.
> > 
> > Danke Heinz
> > 
> > 
> >> On 31. May 2022, at 14:43, Alan Cudmore <alan.cudmore at gmail.com> wrote:
> >> 
> >> If it helps, I have a demo where I built and ran RTEMS 6 with libbsd on the beaglebone black in January. I used specific commits from the repositories in an effort to make it reproducible, so if there was a regression that may help. My build used -O linux when creating the u-boot image file.
> >> The repo is here:
> >> https://github.com/alanc98/rtems-cfs-demo
> >> 
> >> I still have the board setup. As soon as I have time, I can build a new toolchain and BSP to see if it still works.
> >> Alan
> >> 
> > 
> > _______________________________________________
> > users mailing list
> > users at rtems.org
> > http://lists.rtems.org/mailman/listinfo/users