Lines Matching full:memory

2 hardware, or when using a sloppy port on some board, is memory errors.
4 incorrect initialization of the memory controller.  So it appears to
5 be a good idea to always test if the memory is working correctly,
8 U-Boot implements 3 different approaches to perform memory tests:
14    memory banks on this piece of hardware.  The code is supposed to be
17    catch 99% of hardware related (i. e. reliably reproducible) memory
23    This is probably the best known memory test utility in U-Boot.
35      no knowledge about memory ranges that may be in use for other
46      system memory) and for U-Boot (code, data, etc. - see above;
47      these are usually at the very upper end of system memory).  But
56    especially not in production.  If you really need a memory test,
59 3. The most thorough memory test facility is available as part of the
60    POST (Power-On Self Test) sub-system, see "post/drivers/memory.c".
62    If you really need to perform memory tests (for example, because
69 It should pointed out that _all_ these memory tests have one
71 that memory errors can be found by writing to and reading from memory.
81 efficient, memory test like that.  The best known test case to stress
90 memory problems on a specific board.  The code is pretty much board