Re: Bringing up MVME 197LE (88k)
Even with a dead battery you should have seen console output. I would check the serial cable, p2 adapter and 712 console port jumpers first. You could try to boot directly from the eprom which holds the 197bbug(using the DIP switches) in case the 197bug has been flashed with custom firmware(never seen this, but who knows). You can remove the 297 expansion card as 197 has its own memory soldered on the back-side. On Tuesday, June 30, 2020, r...@hack.net ryan--- via cctalk < cctalk@classiccmp.org> wrote: > > Anyone have experience with the Moto 88k VME boards? I have an MVME197LE > that I’m trying to bring up but it’s staying in BRDFAIL, while SYSCON and > RUN are green and pressing RESET appears to work. > > Nothing on console at all. (via a 712 transition module) > > Same behavior with the NVRAM removed. > > I do have the mezzanine card which has stayed affixed with an interesting > inter-board connection. (Is this separate-able? Should it function > without this DRAM?). > > > I’ll dive deep into debugging this, but if anyone has some tips or > experience they could share it would be appreciated! > > Thanks! > > -Ryan Brooks > r...@hack.net >
Re: Bringing up MVME 197LE (88k)
Some progress tonight. Getting this on console with the memory mezzanine disconnected (see below). Regardless of what I type I get the Framing Error response and no echoing. Thanks for any more insights, Ryan --- Copyright Motorola Inc. 1988 - 1994, All Rights Reserved MVME197 Debugger/Diagnostics Release Version 1.1 - 06/17/94 (06_17.14) COLD Start Local Memory Found =0400 (&67108864) WARNING: Configuration Data Failure (Invoke 'ENV' Command) WARNING: Board Configuration Data Failure MPU Clock Speed =50Mhz Initializing local memory... 002000400060008000A000C000E00100012001400160018001A001C001E00200022002400260028002A002C002E00300032003400360038003A003C003E00400 Done Idle MPU(s) : NONE 197-Bug> --Framing Error-- 197-Bug> --Framing Error-- ... > On June 30, 2020 5:36 PM Plamen Mihaylov > wrote: > > > Even with a dead battery you should have seen console output. I would > check the serial cable, p2 adapter and 712 console port jumpers first. > You could try to boot directly from the eprom which holds the > 197bbug(using the DIP switches) in case the 197bug has been flashed with > custom firmware(never seen this, but who knows). You can remove the 297 > expansion card as 197 has its own memory soldered on the back-side. > > > On Tuesday, June 30, 2020, r...@hack.net mailto:r...@hack.net ryan--- via > cctalk < cctalk@classiccmp.org mailto:cctalk@classiccmp.org > wrote: > > > > Anyone have experience with the Moto 88k VME boards? I > have an MVME197LE that I’m trying to bring up but it’s staying in BRDFAIL,... > > > > >
Re: Bringing up MVME 197LE (88k)
Make sure the configuration switch for system controller matches the slot it's in. Fixing the NVRAM seems like a good next step. Not sure I'd remove the memory mezzanine, I don't think the board can do much without it. On Mon, Jun 29, 2020 at 3:53 PM r...@hack.net ryan--- via cctalk < cctalk@classiccmp.org> wrote: > > Anyone have experience with the Moto 88k VME boards? I have an MVME197LE > that I’m trying to bring up but it’s staying in BRDFAIL, while SYSCON and > RUN are green and pressing RESET appears to work. > > Nothing on console at all. (via a 712 transition module) > > Same behavior with the NVRAM removed. > > I do have the mezzanine card which has stayed affixed with an interesting > inter-board connection. (Is this separate-able? Should it function > without this DRAM?). > > > I’ll dive deep into debugging this, but if anyone has some tips or > experience they could share it would be appreciated! > > Thanks! > > -Ryan Brooks > r...@hack.net >
Re: Bringing up MVME 197LE (88k)
A few of the self-tests I’ve seen on the 147s set BRDFAIL if the NVRAM doesn’t pass, so perhaps changing the NVRAM for a known good would be a place to start. Richard Sent from Mail for Windows 10
