roach1 had ppc dimms... roach2 had 'em soldered on? Jason Manley DSP Manager SKA-SA
Cell: +27 82 662 7726 Work: +27 21 506 7300 > On 19 Mar 2019, at 17:09, Marc <[email protected]> wrote: > > This is strange advice so proceed with caution: Maybe take out the > dimm, rub its contacts (gently) with an eraser and reseat it ? > > regards > > marc > > On Tue, Mar 19, 2019 at 1:59 PM Michael Peel <[email protected]> wrote: >> >> Hi Heystek, >> >> Thanks for the reply and the link. The memory error appears immediately >> after the roach is turned on, before the option to stop the autoboot >> appears. Sometimes it does continue a bit beyond that before stalling, so >> I’ll look at trying to do a uboot update when it next does that. >> >> The links to the images on the webpage don’t work (the casper svn no longer >> exists?), are the latest versions stored elsewhere now - perhaps they the >> ones on the ska-sa git? >> >> Thanks, >> Mike >> >> On 17 Mar 2019, at 14:40, Heystek Grobler <[email protected]> wrote: >> >> Hey Michael >> >> Did you try this procedure? >> >> https://casper.ssl.berkeley.edu/wiki/ROACH_kernel_uboot_update >> >> Did you manage to solve it? >> >> Heystek >> >> On Fri, Mar 15, 2019 at 5:45 PM Michael Peel <[email protected]> wrote: >>> >>> Hi all, >>> >>> I’m currently trying to set up a ROACH2 (for the first time), and have run >>> into a number of problems. The bottom line is that I’m currently getting >>> this memory error message: >>> >>> U-Boot 2011.06-rc2-00000-g2694c9d-dirty (Dec 04 2013 - 20:58:06) >>> CPU: AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133 OPB=66 EBC=66) >>> No Security/Kasumi support >>> Bootstrap Option C - Boot ROM Location EBC (16 bits) >>> 32 kB I-Cache 32 kB D-Cache >>> Board: ROACH2 >>> I2C: ready >>> DRAM: 512 MiB >>> Memory error at 00000000, wrote 00000000, read 273218ff ! >>> >>> This follows from the casperfpga software being able to connect to the >>> ROACH2, but unable to load the .fpg file onto it. That led to me attempting >>> to update the romfs using ‘run tftproot’, but it could not get an IP >>> address from the computer (DHCP/dnsmasq configuration issues on RHEL7 that >>> I still need to figure out), so it did not run the update. However, after >>> that I got a kernel panic on the onboard software, so the roach no longer >>> got to the login stage. >>> >>> I then created a USB boot drive using: >>> https://github.com/ska-sa/roach2_nfs_uboot/blob/master/roach2-debian-fs-snapshot-24-10-2012.tar.gz >>> and tried to boot the roach from that, however it stalled during the boot >>> process, and on reset I got the above error message. >>> >>> Any suggestions? >>> >>> Thanks, >>> Mike >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "[email protected]" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> To post to this group, send email to [email protected]. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "[email protected]" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. > > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].

