Hi hadez,
> I've got #16 which does in fact show the slightly suspicious note > "entire side of dram chip lifted up, had to fix that first". > What I'm seeing could very well be a memory issue. > This has been resoldered by myself after I'd met this "entire side of dram chip lifted up", so from the result of test log file, #16 dram worked well at that time. See ref. to http://downloads.qi-hardware.com/hardware/milkymist_one/production/rc2/test_results/16-results Surely we haven't done with continuing 2 hours to run it. > > If you think it's a good idea, I do have access to a hot-air solder rework > station to reflow the chip myself. > Since Xiangfu's board had have the 'freeze' sometime, so i don't think that you need to use hot-air to solder firstly. However, if there's an issue with the chip itself that will definitely not > help. > This could be that indeedly if dram itself have issue. > It would be neat to have a working board on June 18th, but that's not a > hard requirement ;) > Lets just stick to whatever debugging step you think is most suitable. When producing rc2 board, the test tool on testing dram was not tested multiple times, but now the test tool it is, multiple times committed log: https://github.com/milkymist/autotest-m1/commit/4c4b2974ee60a4a5fe570d2d2accc687c42198e3 Could you do me a favor to use test tool to test drams? You can refer. to http://www.milkymist.org/test_tool/ And follows the m1 test procedure. Thanks a lot, Adam
_______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode Twitter: www.twitter.com/milkymistvj Ideas? http://milkymist.uservoice.com
