English subtitles

← Checking consideration summary cs348 unit5new

Get Embed Code
1 Language

Showing Revision 1 created 04/14/2013 by Cogi-Admin.

  1. Let's summarize our checking considerations. Firstly, we want to do the
  2. checking at the high level. We want to check transactions, we don't want to
  3. check bits and bytes. We have a high level Testbench language, which enables us
  4. to do this very efficiently and it is sufficient for the purposes we, we need.
  5. If we were to implement everything at bit level, our checking would become very
  6. complex and it's complex enough already and it would take up too much time. The
  7. second consideration is to separate the data checking from the interface and
  8. protocol checking. This is because of reuse. If you separate those checks, you
  9. can use the interface checks every time you have a device which has this
  10. interface. And this happens a lot in modern hardware designs. There's a lot of
  11. reuse in the, on the design side. And specially, standardized interfaces are
  12. very popular because it enables Plug and Play. So, if you can separate the
  13. interface checks from the data checks, which are very specific to a device, you
  14. can reuse them much much easier. The last consideration is to separate the
  15. checking from the driving and generation. again, this is a reuse consideration.
  16. So often, you have a check in a device on a, on a smaller block and you move
  17. that block into a subsystem, which happens quite a lot. In this case, now,
  18. other blocks will drive the block we've just verified, and you want to reuse
  19. the checks. So, if the checks rely on the traffic generation, you cannot do
  20. that, because now the traffic comes from other devices. If they are all, if
  21. they are, however, separated, you can very easily just switch off the traffic
  22. generation and keep your checking as it was. In this unit, we will start by
  23. looking at data checking first, and later on, we'll look at the interface and
  24. protocol checks.