So I confess to relying on third parties for this information, but isn't
the board populated with 1Gb RAM after all ? Would the crash be trigged by
a kernel memory layout of 3Gb+1Gb rather than 2Gb+2Gb ?
Have you tried the kernel from 9 months ago at github
ska-sa/roach2_nfs_uboot ?
regards
Hi, Marc,
On Jul 28, 2015, at 1:34 AM, Marc Welz wrote:
So I confess to relying on third parties for this information, but isn't the
board populated with 1Gb RAM after all ?
When U-Boot starts up it reports that the system has 512 KB of memory. I
assume (uh-oh!) that uboot is detecting
So I confess to relying on third parties for this information, but isn't
the board populated with 1Gb RAM after all ? Would the crash be trigged by
a kernel memory layout of 3Gb+1Gb rather than 2Gb+2Gb ?
Certainly if the kernel thinks the layout of memory isn't what it really
is it could
Hi all,
To close out this thread, a fix is to add a mem= option to uboot's
bootargs variable ---
1. Connect a PC to the ROACH2's FTDI USB port using a usb A-B cable.
2. Open a serial console on the roach 2 using
minicom/picocom/your-favourite-serial-console. The interface settings
are
Hi all.
We were having problems with multiple sequentail progdev calls failing on
our ROACH-2 systems. We were testing multiple bof files in a loop, and
the roach would fall over and crash completely, and after the kernel
panic, it would reboot itself.
After a great deal of concentrated
5 matches
Mail list logo
