> On Apr 29, 2016, at 12:07 PM, Chuck Harris <[email protected]> wrote: > > We have to sort of conclude that the failure is either > caused by bad data getting stored, or some sort of overflow > error. > > It really is pretty unlikely that the firmware has been > changed, unless you happened to accidentally start a > flash burn routine, and it wasn't qualifying packets > properly. > > If it isn't an overrun, or overflow error, then I would > suspect what you are sending to the port. I have worked > with guys that are totally flustered when doing firmware > for devices that should qualify the data they receive. > When they don't know what to do (or are too lazy to try > and figure out the right thing to do) they simply stub > out the error path and go on. Yuck! > > If you have been sending an ill formed packet, you best > stop doing that ;-)
Oh, yeah, that’s fixed. While I’m waiting for a replacement 5680A my plan of record is to try and create a simulacrum out of an xCXO (the AVR of my board is clocked from the oscillator, so it won’t work without getting 10 MHz from something) and a serial port to make absolutely sure the data is correct before trying again. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
