2011-06-20 12:11:00     POST Tests

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

2011-06-20 12:11:00     POST Tests

James Kosin (UNITED STATES)

Message: 101491   

 

Mike,

 

If someone wanted to add POST tests, where is the correct place to add them to the source tree?  In the /post directory, or other places?  I'm guessing the /post directory and then create the structure under /post/board and /post/cpu for the blackfin?

 

Thanks,

 

James

QuoteReplyEditDelete

 

 

2011-06-20 12:52:47     Re: POST Tests

Mike Frysinger (UNITED STATES)

Message: 101492   

 

post has been redone in current git trunk to make things much simpler.  i would look there rather than trying to make the last release work.

 

in that case, you can then follow the documentation here:

https://docs.blackfin.uclinux.org/doku.php?id=bootloaders:u-boot:post#board_specific_tests

 

it should outline exactly what you need to do to add your own new post tests.

 

i dont know what tests you're looking to add, but if they're general/generic, we could look at adding them to mainline for everyone ...

QuoteReplyEditDelete

 

 

2011-06-21 08:39:56     Re: POST Tests

James Kosin (UNITED STATES)

Message: 101517   

 

Thanks Mike,

 

I had some board specific tests but wondered why the blackfin didn't have the watchdog test or cpu/cache tests defined... and just wanted to know the best place to put them in the situation I'd like to develop them and contribute.

 

James

QuoteReplyEditDelete

 

 

2011-06-21 10:25:00     Re: POST Tests

Mike Frysinger (UNITED STATES)

Message: 101520   

 

because no one wrote any yet

 

the team that does board design and low level support also writes their own POST.  but it isnt integrated into u-boot.

 

when the u-boot POST support was implemented long ago, it wasnt all that great, and about the only comprehensive test added was for memory.  there wasnt much also.

 

there is a watchdog POST, but when i looked at it, it seemed to require arch-specific code.

Attachments

    Outcomes