verification and Testing in x-loader or u-boot is preferable?

16 views

Skip to first unread message

venkat k raju

unread,

Jul 12, 2012, 3:01:16 AM7/12/12

to android-porting, rowboat

Dear all,

i have been working on TI family custom boards.

which part is preferable for hardware interfaces,peripheral devices verification & testing with standalone ?

please anybody suggest me,i am little bit confuse.

--
thanks&Regards
k.v.raju

venkat k raju

unread,

Jul 12, 2012, 9:08:52 AM7/12/12

to row...@googlegroups.com, android-porting

Dear Jaya Kumar,

thank a lot!!!

i mean whether those Verification and testing in u-boot part or x-loader part preferable?

On Thu, Jul 12, 2012 at 6:16 PM, Jaya Kumar <jayakum...@gmail.com> wrote:

On Thu, Jul 12, 2012 at 3:01 PM, venkat k raju <kvraj...@gmail.com> wrote:
> which part is preferable for hardware interfaces,peripheral devices
> verification & testing with standalone ?
> please anybody suggest me,i am little bit confuse.

You may want to clarify your question. Verification and testing of
what specific parts? If you mean memory, then I think yes, it is not
unusual to include mtest in u-boot to do basic memory validation. For
peripherals like audio, video, USB, I'm more used to diagnostics being
run once the target is fully booted into rowboat.

--
You received this message because you are subscribed to the Google Groups "rowboat" group.
To post to this group, send email to row...@googlegroups.com.
To unsubscribe from this group, send email to rowboat+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rowboat?hl=en.