Re: [beagleboard] device tree support
On Fri, 27 Sep 2013, Saransh Jain wrote: Hello RobertCNelson, I am sorry for my previous post.I did some research on uimage and zimage and I think I may have misunderstood a few things you told... just FYI, TI's tom rini recently submitted a patch to u-boot, replacing the uImage values in am335x_evm.h with references to zImage, thus making zImage the default image format. AFAIK, there is no downside to using zImage from now on. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
On Fri, Sep 27, 2013 at 4:20 AM, Saransh Jain saransh1...@gmail.com wrote: Hello RobertCNelson, I am sorry for my previous post.I did some research on uimage and zimage and I think I may have misunderstood a few things you told.Can you please confirm if I am right now? The zreladdress is the address for the uncompressed kernel image. The loadaddress in loadzimage command is the address for compressed kernel image. The problem in using u-image for multi-platforms is that it needs an entry addres which can be outside the sdram on different platforms. The base address of the sdram for loading the uncompressed image is given to the kernel using device tree. All this research and it basicly boils down to one problem.. Say you are supporting two boards with different silicon vendors.. For board A, what was the zreladdress so you can build a uImage with mkimage?? Or do you just copy zImage and work on your real application? There is a file named Makefile.boot in arch/arm/mach-omap2. This file defines zreladdr.Is this file necessary(for zImage booting)? No, that variable was only used in the non-multiarch case when calling make uImage to create the uImage file correctly.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
On Fri, Sep 27, 2013 at 7:45 AM, Saransh Jain saransh1...@gmail.com wrote: i used the address 80008000 (-a option in mkimage) for the uImage.i used the same address as the entry address(-e option). Also can you confirm the points i said in the previous post.That would clarify a lot to me. I'll leave that issue to someone else... I believe that the -a option in mkimage is irrelevant.I think the relevent address in the mkimage command is the entry image address(-e option).This address is used by u-boot to copy the compressed uimage(but without the 64k header i.e zImage only).After this the process is the same as zimage as there is no 64k header.Can you also confirm this. All mkimage does it put a 64k wrapper header on zImage... Nothing more, nothing less.. about the multi-arch thing I think that the problem with using uImage is that the entry address may not lie in the ram space of all the boards that the kernel can support.Right??? It's not lieing it's just that each vendor is free to implements it at a different address, or where ever they want.. See my small list here: https://github.com/RobertCNelson/stable-kernel/blob/master/system.sh.sample#L33 But if this is the case the we will have to change the bootenv of u-boot as we need to load the compressed zimage/uimage somewhere in the ram first.Am I correct? Why change bootenv, the default settings in u-boot for the particular target already work out of the box.. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
Thanks RobertCNelson... Leaving the rest of the things,can you tell where does the zImage get the base address of the RAM.Is it the device tree?? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
On Fri, 27 Sep 2013, Robert Nelson wrote: On Fri, Sep 27, 2013 at 7:45 AM, Saransh Jain saransh1...@gmail.com wrote: i used the address 80008000 (-a option in mkimage) for the uImage.i used the same address as the entry address(-e option). Also can you confirm the points i said in the previous post.That would clarify a lot to me. I'll leave that issue to someone else... I believe that the -a option in mkimage is irrelevant.I think the relevent address in the mkimage command is the entry image address(-e option).This address is used by u-boot to copy the compressed uimage(but without the 64k header i.e zImage only).After this the process is the same as zimage as there is no 64k header.Can you also confirm this. All mkimage does it put a 64k wrapper header on zImage... Nothing more, nothing less.. shouldn't that be just 64-byte wrapper? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
On Fri, Sep 27, 2013 at 7:56 AM, Saransh Jain saransh1...@gmail.com wrote: Thanks RobertCNelson... Leaving the rest of the things,can you tell where does the zImage get the base address of the RAM.Is it the device tree?? It does not get the address from zImage/device tree as u-boot already knows the address, as you built it for a specific target. Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
On Thu, Sep 26, 2013 at 12:17 AM, Saransh Jain saransh1...@gmail.com wrote: Thanks RobertCNelson I asked for uimage because I also wanted to try booting using tftp which requires transferring uimage and device tree to the ram.Can I use zimage instead of uimage for tftpboot?If so,is there any change in the command for boot? tftpboot is just a media transfer command.. You just going to tfpboot some binary from a server to an andress. zImage just needs to be called by bootz address where as uImage needs bootm address Also I am not sure how the boot using uimage and zimage takes place and what difference does it make in u-boot.You said that the uimage has a load address hardcoded.So how does zimage gets the load address?Can you please elaborate? Thanks for the help. Well, the soc already knows the address... Regards, -- Robert Nelson http://www.rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
Hello RobertCNelson, I may be wrong here, but I thought that u-boot was responsible for the loadaddress of the zimage.In the u-boot patches. there is a loadzimage command which has the loadaddress as one of its arguments.So how does the soc know the address? Also if this is the case the only problem I see with uImage is one extra step of making it. Kindly clarify thisI am really confused -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] device tree support
Thanks RobertCNelson I asked for uimage because I also wanted to try booting using tftp which requires transferring uimage and device tree to the ram.Can I use zimage instead of uimage for tftpboot?If so,is there any change in the command for boot? Also I am not sure how the boot using uimage and zimage takes place and what difference does it make in u-boot.You said that the uimage has a load address hardcoded.So how does zimage gets the load address?Can you please elaborate? Thanks for the help. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
