Michael Schaffner

Results 89 comments of Michael Schaffner

Discussed with @a-will - this would be a nice optimization but not needed from a functional perspective.

Discussed with @matutem - this seems to be a coverage closure exercise that can be done after M2.5. We have many TLT's that already stress the interconnected reset behaviors of...

That is a very good question. I have the feeling that some level of customization could be useful and convenient. See also this related discussion regarding documentation: https://github.com/lowRISC/opentitan/pull/19149#discussion_r1266874045

@moidx Do we even have a usecase that would not do continuous reads? Because if not I would advocate no change at this point.

Given that this is not a security IP, I am not sure this needs to be a fatal alert. On the bus side, we just send back a tlul bus...

Discussed with @a-will and we think it is fine to put this in the backlog for now, given that this is not a security IP.

Thanks for the analysis @rswarbrick. Given the priorities, I think we can accept 89.95% coverage for covergroups in this case ;). As for the signoff order, it probably makes sense...

This setup violation may be partially addressed by removal of the diffusion layer in the SRAM scrambling devices (#20855). We should wait for another PD run before optimizing things in...

Triaging this into M4. We addressed this partially by removing the S&P layer in the SRAM scrambling circuits and are now waiting for new synthesis results, which we likely won't...