Hii Cláudio,
On Fri, 21 Feb, 2020, 4:55 AM Cláudio Maia (clrrm),
wrote:
> Hi Niteesh,
>
> Thank you for your input. Following your suggestion allowed me to boot
> successfully RTEMS from u-boot.
> Moreover, I confirm that “-O rtems" does not work for me as well.
>
Your welcome :)
I have a few
dio,
>
> I build a current BSP for the raspberry pi 2 recently (atm without SMP
> though).
>
>> -Ursprüngliche Nachricht-
>> Von: devel [mailto:devel-boun...@rtems.org] Im Auftrag von Cláudio Maia
>> Gesendet: Montag, 17. Februar 2020 21:19
>> An: dev
Hi Niteesh,
Thank you for your input. Following your suggestion allowed me to boot
successfully RTEMS from u-boot.
Moreover, I confirm that “-O rtems" does not work for me as well.
I have a few questions that I would like to ask you. What exactly is going on
when we execute “bootm 0x20 -
: Loading RTEMS applications from u-boot on Raspberry Pi 2
>
[...]
>
> ---
> For approach #2, I do the following:
>
I skip the whole mkimage step entirely and boot the elf-files directly.
So my u-boot commands look like this:
U-Boot> fatload mmc 0 0x3000 tic
Hii,
Regarding loading RTEMS images using U-Boot. It is
necessary that you provide a DTB file.
So, your commands should be
$ mkimage -A arm -O linux -T kernel -a 0x20 -e 0x200080 -d kernel.img
-C none rtems.img
Can you please let me know if -O rtems works for you. I have tried
using it but
I am currently experimenting with RTEMS and Raspberry Pi 2 with the goal of
exploring RTEMS-SMP properties (mainly scheduling and memory behaviour).
Currently, I am able to load an .img file when the default kernel.img file that
comes with Raspbian is replaced by the RTEMS aplication .img file
