Usually dram test executed not on whole sdram
Anyone knows why in the u-boot normally the dram test is not executed on the whole DRAM? For example a lot boards that have 16MB specify start_address = 1MB and end_addr = 15MB. If the u-boot is executing in flash the DRAM can be written completely I think!
Bye,
Antonio.
Quoted 4 lines · In message <[email protected]> you wrote:
Anyone knows why in the u-boot normally the dram test is not executed on the whole DRAM? For example a lot boards that have 16MB specify
start_address= 1MB andend_addr= 15MB. If the u-boot is executing in flash the DRAM can be written completely I think!
The "mtest" can only be run after relocation to RAM, so you have to leave out the memory needed ofr exception vectors, U-Boot code, malloc arena, stack, etc.
For the POST tests no such restriction exists.
But you are on the wrong track. A memory test will NOT detect your problem, as it is exercising pleain read / write accesses only, while your problem is most probably with burst mode accesses. Please read the FAQ!
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Success in marriage is not so much finding the right person as it is being the right person.
Thank you for your help Wolfgang,
I disabled burst mode in ORx register of MPC880 and everything is fine. The UPM table has to be double checked.
Now I want to look for a dram test that exercise the burst mode. It could be really useful in debugging these problems.
Thank you very much,
Bye.
Wolfgang Denk Scrive:
Quoted 27 lines
Quoted 4 lines · In message <[email protected]> you wrote:
Anyone knows why in the u-boot normally the dram test is not executed on the whole DRAM? For example a lot boards that have 16MB specify
start_address= 1MB andend_addr= 15MB. If the u-boot is executing in flash the DRAM can be written completely I think!The "mtest" can only be run after relocation to RAM, so you have to leave out the memory needed ofr exception vectors, U-Boot code, malloc arena, stack, etc.
For the POST tests no such restriction exists.
But you are on the wrong track. A memory test will NOT detect your problem, as it is exercising pleain read / write accesses only, while your problem is most probably with burst mode accesses. Please read the FAQ!
Best regards,
Wolfgang Denk
Signature · 4 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Success in marriage is not so much finding the right person as it is being the right person.
Quoted 3 lines · In message <[email protected]> you wrote:
I disabled burst mode in ORx register of MPC880 and everything is fine. The UPM table has to be double checked.
I repeat: please READ the FAQ! The UPM table is just half of the story, and often NOT the culprit.
Quoted 2 lines
Now I want to look for a dram test that exercise the burst mode. It could be really useful in debugging these problems.
See examples/test_burst.* - but don't expect that it will be usable out of the box, or without a *deep* understanding of the relevant technical details.
It is much easier and more straightforward just to read the chip manufacturer's manual for your RAM chips and implement the documented init sequence to the letter.
This is a RTFAQ and RTFM job.
Best regards,
Wolfgang Denk
Signature · 3 lines
Software Engineering: Embedded and Realtime Systems, Embedded Linux Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de Hacking's just another word for nothing left to kludge.