Blog

Category: Best practices

  • November 29, 2008
    Interrupt modules monitor multiple interrupt sources. Interrupt modules come in two flavors: level-triggered or edge-triggered.

  • October 31, 2008
    Ideally, the same IP and firmware could be used for every instantiation with little or no modification due to optional I/O signals.

  • September 30, 2008
    When an engineer on one team has a problem, there should be no barriers to prevent going to a member of the other team to discuss it.

  • August 30, 2008
    A reader brought up a useful distinction between a power-on reset and a hard reset. Some things are done only at power on.

  • July 31, 2008
    Guidelines for the control that hardware modules and firmware code should have over different types of hardware reset.

  • June 30, 2008
    Failure to catch documentation problems typically results in hours wasted on debugging that could and should have been avoided.

  • May 31, 2008
    A chicken and egg problem: How can we know whether or not a downstream master is idle without switching to that bus to check its activity?

  • March 31, 2008
    The register table from last month now indicates the access type, read/write or read-only, of the bits in the register.

  • February 28, 2008
    Documentation plays a key role in this effort since engineers must refer to it constantly to look up register and bit details.

  • January 31, 2008
    Engineers love to measure things and assign a number. But how do you measure something intangible? You can’t.