On 7/4/2018 1:44 PM, smf wrote: > > On 04/07/2018 09:17, Michał Pleban wrote: >> That would be too early. We don't want to find what heppens when the CPU >> _starts_ testing the RAM. We want to find out what caused the CPU to >> _stop_ testing the RAM - that's when the error occurs. And we don't know >> when it really occurs. > Can you have it store the signals in a ring buffer until it fetches > the instruction in the failure path of the code? > Well, anything is possible, but the above sounds like a rather complicated affair. Jim -- Jim Brain brain@jbrain.com www.jbrain.comReceived on 2018-07-04 22:02:01
Archive generated by hypermail 2.2.0.