Hii Cláudio, On Fri, 21 Feb, 2020, 4:55 AM Cláudio Maia (clrrm), <cl...@isep.ipp.pt> 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 questions that I would like to ask you. What exactly is going > on when we execute “bootm 0x200000 - 0x1000”? > The address where we load the dtb is far apart from the one where we load > the .img, so why do we need to boot the .img 0x1000 bytes below 0x200000? > What is the relation between both, if any? > That's just the syntax for bootm. bootm ${kernel_addr} - ${fdt_addr} But, bootm ${kernel_addr} ${fdt_addr} should also work I guess but I am not sure. Can you try that and please let me know? Thank you, Niteesh. Regards, > Cláudio > > > On 18 Feb 2020, at 15:56, Niteesh G. S. <niteesh...@gmail.com> wrote: > > > > 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 0x200000 -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 got no output. > > > > U-Boot> fatload mmc 0:1 0x200000 rtems.img > > U-Boot> fatload mmc 0:1 0x1000 bcm2709-rpi-2-b.dtb or bcm2710-rpi-2-b.dtb > > The DTB file should be choosed according to the board version. > > U-Boot> bootm 0x200000 - 0x1000 > > > > Thanks, > > Niteesh. > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel