• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 310 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Reason for maintaining an old version u-boot

Qian Huang
Prodigy 130 points

Hello,

I'm working on porting u-boot to customized board with omap4430, and there's something confusing me.

Das-uboot mainline has kept updating, but TI official source tree is still maintaining an old version  u-boot.

Is there any reason for this?

Just curious, thank you.

  • 0
    TI__Intellectual 805 points

    Hi Qian,

    Generally u-boot does not contain any "magic" functionality as it kernel supports. As you know it's major functionality is to load kernel, to provide UART communication,to load the DSS in order to display sample image.. If I recall correctly, It has been developed "once" and eventually is modified when bugs/issues comes up.

  • 0 in reply to Georgi Georgiev XID
    Prodigy 130 points

    Hi Georgi, many thanks for your reply.

    I agree that u-boot is developed mainly for kernel loading, but there are still some changes improving for ARM-based CPUs including omap in mainline.

    Sometimes hardware issues such as unstable power source or low tolerance of frequency bias might be solved (or, avoided, precisely) by these tiny improvements.

    On the other hand, some built-in functions of TI's official u-boot (mtest, fatload, md...etc.) have been unworkable for a long time ( I've test these functions on blaze and pandaboard), I guess TI software teams spent most of their effort on loading kernel instead of peripheral functions.

    Or maybe I'm wrong, do you still follow the mainline u-boot commits and patches if needed?

  • 0 in reply to Qian Huang
    TI__Intellectual 805 points

    Hello Qian,

    Could you make sure you are on same u-boot branch as 4AJ.2.4 is? I tried mtest,fatload,md and works with Blaze board. Probably you are missing/mistaking something during the porting..

    Apart of this, the branch thats still developing is "omap4_dev", and the last commit is from 27 Feb 2013 "OMAP4: charger: Cancel charging if chip is not detected" . You can find it here.