Hi everyone,
For the past couple of weeks, I have been looking into the Source Code
of Uboot to understand how it made the bootable binary. After some
struggle I figured out the entry part into Bootloader(entry.S) and can
now make good sense of it. However I am trying to understand the
values that were present in the .config files of uboot. Can you tell
me where those values are fetched from? And what does it take to write
one of that kind(like omap3_beagle.config) from scratch for a new
board(of course for the processor core that is supported by Uboot
already)? Like what parameters should be identified etc and which ones
are mandatory?
Looking forward for your responses.
Thanks very much,
Vamsi
Hi Vamsi,
Hi everyone,
For the past couple of weeks, I have been looking into the Source Code
of Uboot to understand how it made the bootable binary. After some
struggle I figured out the entry part into Bootloader(entry.S) and can
now make good sense of it. However I am trying to understand the
values that were present in the .config files of uboot. Can you tell
me where those values are fetched from? And what does it take to write
one of that kind(like omap3_beagle.config) from scratch for a new
board(of course for the processor core that is supported by Uboot
already)? Like what parameters should be identified etc and which ones
are mandatory?
Looking forward for your responses.
A good starting point would be to start reading what's in the u-boot
doc folder.
Afterwards you might might want to ask on the u-boot mailing list:
http://lists.denx.de/mailman/listinfo/u-boot
You might also want to outsource u-boot porting to someone else in
order to minimize time to market.
I'm sure the guys from DENX will be able to give you a quote for such
activities.
Regards,
Robert
Hello Robert,
Thanks for your response and suggestion. I did ask this question on Uboot forum but there was no response. I am still a student trying to figure out how the Uboot binary really works. I now have fairly good understanding about it.
Vamsi