On Tue, Mar 5, 2019 at 9:01 PM Clemens Koller <clemens.ml@xxxxxxx> wrote: > > Yes, this really smells like memory timing issues. > Did you try the more extensive memory test of the latest u-boot? The regular one is quite naive. This is usually *not* enabled as default. Unfortunately I was unable to get the latest (or any other upstream) u-boot running on my board and even on Jetson TK1 kit. Although it seems that the u-boot has support for Jetson TK1 in mainline but don't know why its not working. The mtest command in the Nvidia's downstream version of u-boot did not report any errors. > Then, a Shmoo plot with different memory timing/voltage/temperature might be useful as well as a PCB layout review. Tried running Shmoo test again but it generated the BCT file with same parameters again. So it didn't seem to work. I also stopped u-boot at command line and checked using oscilloscope if there's some activity at data lines between DDR and TK1 processor. There was no activity on data lines which made me believe that when u-boot is in idle state, there's no peripheral (or DMA) writing to memory which might be corrupting the memory used by kernel as suggest by Thierry Reding. Can anyone give some other suggestion as it seems I'm running out of options to test :(
