Yes, if a known-good REX has REXMGR issues, it's probably operator error or socket contact.
However, having built lots of REXes, I recognize these symptoms as a bad flash load, and that's usually caused by assembly issues (or, at least, is usually rectified by rework). The CPLD load can be verified using iMPACT, but the flash load is *not* verified as part of the programming process; the only way I know to verify the flash load is the REXMGR checksum and by that point, REXMGR is already running and that's a very strong indication that the flash load is correct :) On Mon, May 14, 2018 at 12:02 PM, John R. Hogerhuis <[email protected]> wrote: > The simplest reasons for REX to fail are not installing REXMGR with the CALL > or poor contact between REX and the option rom bay. > > But I’m spoiled by always using a REX that was known good / tested at some > point (by Steve). > > — John.
