T.R | Title | User | Personal Name | Date | Lines |
---|
3282.1 | Expanding the bits | CSC32::R_BUCK | Have been authenticated and assimilated | Fri Sep 27 1996 14:37 | 6 |
3282.2 | It's decompressing | IROCZ::ALBRIGHT | She bop-he bop-a-we bop | Fri Sep 27 1996 14:40 | 6 |
3282.3 | STARS article about this | CSC32::D_PELTONEN | | Fri Sep 27 1996 21:41 | 58 |
3282.4 | We call it 'investment protection'. | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Mon Sep 30 1996 01:15 | 17 |
3282.5 | | NETCAD::MORRISON | Bob M. LKG2-A/R5 226-7570 | Mon Sep 30 1996 17:31 | 5 |
3282.6 | Clarification... | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Mon Sep 30 1996 17:54 | 32 |
3282.7 | perhaps rotating LED pattern will help? | HANNAH::SCHULLMAN | Dan Schullman | Thu Oct 03 1996 18:41 | 10 |
3282.8 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Thu Oct 03 1996 20:37 | 14 |
3282.9 | Youch! | BRETTN::HEITER | CSS Realtime Systems Engineering | Fri Nov 22 1996 18:31 | 10 |
3282.10 | use TL software | UTRTSC::KNOPPERS | Oswald Knoppers | Mon Nov 25 1996 07:02 | 5 |
3282.11 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Mon Nov 25 1996 14:01 | 25 |
3282.12 | | BRETTN::HEITER | CSS Realtime Systems Engineering | Mon Dec 23 1996 19:50 | 51 |
3282.13 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Tue Dec 24 1996 14:20 | 45 |
3282.14 | Compressed vs. uncompressed, it's all the same software | LAVC::CAHILL | Jim Cahill | Tue Dec 24 1996 14:36 | 14 |
3282.15 | | BRETTN::HEITER | CSS Realtime Systems Engineering | Tue Dec 24 1996 16:38 | 19 |
3282.16 | | UTRTSC::KNOPPERS | Oswald Knoppers | Fri Dec 27 1996 10:46 | 23 |
3282.17 | | LAVC::CAHILL | Jim Cahill | Mon Dec 30 1996 13:46 | 14 |
3282.18 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Mon Dec 30 1996 16:06 | 22 |
3282.19 | | BRETTN::HEITER | CSS Realtime Systems Engineering | Thu Apr 10 1997 20:29 | 21 |
3282.20 | Uh... the code will continue to get bigger. | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Thu Apr 10 1997 21:34 | 8 |
| RE: .19
Sounds like they really need the 2 MB Flash RAM... Sigh.
Regards,
Dave
|
3282.21 | What about alternatives? | LAVC::CAHILL | Jim Cahill | Fri Apr 11 1997 19:12 | 18 |
3282.22 | :-) | UTRTSC::KNOPPERS | Oswald Knoppers | Mon Apr 14 1997 09:37 | 9 |
| >P.S. Are you still interested in having the uncompressed image included
>on the distribution CD?
Well I would, in our test environment we keep rebooting these things so
often that the delay can be annoying.
Regards,
Oswald
|
3282.23 | Great ideas so far, keep 'em rolling... | BRETTN::HEITER | CSS Realtime Systems Engineering | Mon Apr 14 1997 16:11 | 47 |
| re: .19, larger Flash option:
That is a very attractive alternative. I just spoke with Jon Lewandowski and
this is one of the options he mentioned and would investigate. As you mentioned
Dave, the code will always get bigger (I'm a SW engineer and speak from past
history on that ;^)
re: .21, UPS, PC load of FW, uncompressed image:
Jim, yes we have a big rackmount 3.1KVA UPS from Deltec in the rack already.
This unit is large enough to run
- (2) AS2100A's,
- a VME rack with 6 interface boards,
- the 90M terminal server,
- a serial line switch box for 13 lines,
- discrete I/O and
- (2) intelligent power controllers for remote AC power cycling
capability
for about 30 minutes. The UPS also provides comprehensive line filtering for
when radar is running off a generator (which is not exactly the cleanest source
of power).
Unfortunately, the contract spec states the boot time from cold start power-up.
The issue they are seeing is that the AS2100 displays all the diagnostic
information from the built in test when it boots, so all of this information is
lost while the 90M is booting. They need this information to know what the
error is so that they can load the correct equipment on the helicopter for
repair/installation at the remote site.
In terms of using a PC, that's a great suggestion, but there would be no way
we could fit the PC into the rack, nor are we allowed to put a PC into any
of the other cabinets (there is only so much room in the shelters). I was not
aware we could serve images from a PC, so I will keep that in mind for other
opportunities. Thanks for the info.
For the uncompressed image, I do not think that we will be able to use the
option where we load the firmware from a server. But, I would have to believe
that there are plenty of others who would be able to use this image. I would
highly suggest providing this image as an option, since from what I heard here,
this would not be terribly difficult to do.
I know that this is a complex issue, but I really appreciate all of the help
and suggestions -- keep them coming!
Thanks,
Chris
|
3282.24 | | LAVC::CAHILL | Jim Cahill | Mon Apr 14 1997 16:44 | 14 |
| >The issue they are seeing is that the AS2100 displays all the diagnostic
>information from the built in test when it boots, so all of this information is
>lost while the 90M is booting.
Does the AS2100 display this information when it starts booting or when it
actually completes booting? If it's the latter, the only solution (without
the 2MB Flash) I can see is to get the DS90M to boot faster than the AS2100.
If you can modify the AS2100's startup procedure to get the network up and
running quickly, and the uncompressed load image is made available, it may
be perfectly reasonable to expect the DS90M to be up and running by the time
the AS2100 dumps out the diag info.
Jim
|
3282.25 | re 5 minutes to boot | NNTPD::"mark@nonull.sno.dec.com" | mark | Sat Apr 19 1997 16:01 | 11 |
| Hi ,
My 90M next to me takes seconds to either complete a load from
FLASH or bootp/tftp what takes me I guess 5 minutes (as I have not timed it)
is while it init's itself.
Can any one explain why 90M's take so long to get past flashing
the top and bottom 4 light alternaly during init phase?
Cheers
mark :)
[Posted by WWW Notes gateway]
|
3282.26 | | IROCZ::D_NELSON | Dave Nelson LKG1-3/A11 226-5358 | Sun Apr 20 1997 21:45 | 12 |
| RE: .25
> Can any one explain why 90M's take so long to get past flashing
> the top and bottom 4 light alternaly during init phase?
Yes. It takes that long to decompress the compressed version of the load
image. The flashing LEDs is an indication of decompression in progress.
Regards,
Dave
|
3282.27 | I WANT THE UNCOMPRESSED IMAGE!!! | TWICK::PETTENGILL | mulp | Wed Apr 30 1997 04:32 | 8 |
| >P.S. Are you still interested in having the uncompressed image included
>on the distribution CD?
I've switched to the 90M from the 90TL; we load from Infoservers so they load
in a flash.
But the 90M slllllllllllllllllllooooooooooooooooooooooooooowwwwwwwwwwwwllllllly
decompresses.
|
3282.28 | | BRETTN::HEITER | CSS Realtime Systems Engineering | Thu May 15 1997 16:52 | 17 |
| re: .24:
Jim,
The systems provide this information during the hardware restart by the console
firmware. We have the 2100A console connected to the DS90M so that when the
system boots, all of the console messages are available to be viewed remotely.
The firmware tests memory, CPU, bridges and various options and this information
is needed for the system's fault detection and isolation strategy. There are no
network drivers running on the system since we have not yet booted OVMS. OVMS
may provide additional information, but it is usually not as specific as the
console-provided info.
If the 90M is still booting while the 2100A boots, then this console information
is lost. Lockheed Martin has a restart requirement for the whole radar and the
boot of the 2100As/90M/driver loads/etc is only a part of the total starting
tasks for the mission.
|