Documentation
- Filter by
- Categories
- Tags
- Authors
- Show all
- All
- Aeronautics
- Agriculture
- Automotive
- Best Practices
- Cities
- Embedded Systems
- Energy
- Environment
- Law Enforcement
- Litigation
- Medicine
- Military
- Principles
- Technology
- Work
- All
- 3-D printing
- 3D printing
- A380
- Abort
- Accellera
- Afterthought
- Agriculture
- Airbus
- Aircraft
- Airplanes
- Albert Einstein
- Ambassadors
- Apollo
- app
- Apple
- apps
- Archaeology
- Arduino
- artificial intelligence
- Assembly
- ATMs
- Automobiles
- Autonomous car test case
- Autonomous cars
- Autonomous chairs
- Autonomous trucks
- Balance
- Biometrics
- Bit assignments
- Bit types
- Bitwise
- Block ID
- Block version
- blood pressure
- Blueprint
- Book
- Brain
- Brainstorming
- Bridge
- Buffers
- Byte swap
- C
- cancer
- Captain Chesley Sullenberger
- Captain Sully
- Cash
- Chip ID
- Chip version
- cockroaches
- Code
- Coding
- Cold War
- Collaboration
- Comments
- communication
- Compatibility
- Computer programming
- Computers
- Consultant
- Consulting
- Contingencies
- Controlled development
- Copyright
- Countdown counters
- Countdown timers
- Counters
- Countup counters
- CPU
- CRC
- Credit cards
- crops
- cryptography
- csrCompiler
- CSS
- Current measurement
- Cyberbullying
- Danielle Sacks
- Deaths
- Debug code
- Debug code causing failures
- Debug hooks
- Debugging tricks
- Delay
- detection
- Device Drivers
- DMA
- doctor
- Doctors
- Documentation
- Dones
- Driverless cars
- Drones
- Edge-triggered interrupts
- education
- electrodes
- Embedded
- Embedded software
- Embedded systems
- Enable
- Endianness
- energy
- Engineering
- Environment
- ethics
- Executable code
- Expert
- Expert witness
- Extension cable
- Extra logic
- FAA
- Fake news
- farms
- Fast Company
- Firearms
- Firmware
- Food
- Football
- Forensics
- fraud
- Freeway
- Future
- Gadi Amit
- Geniuses
- GPS
- Green
- Green programming
- Growth
- Guns
- Halt
- Hard reset
- Hardware
- Hardware/firmware
- Hardware/Firmware Interface Design
- health
- Healthcare
- HIPPA
- Holograms
- Hooks
- Hoover Dam
- Horizontal expert
- HP 12C
- HTML
- hydroelectricity
- I/O Signals
- I2C
- Impacts
- Infringement
- Initial design
- Injuries
- Innovations
- insurance
- Intangible benefits
- Intellectual property
- Internet of Things
- Internet security
- Interrupt module
- Interrupts
- Inventions
- IoT
- IP Litigation
- iPhone
- JavaScript
- Jet Blue
- Kids
- language
- LaserJet
- Late changes
- Level-triggered interrupts
- Lighting
- Litigation
- Mars Climate Orbiter
- Masks
- Medical
- medicine
- microcontrollers
- Military
- Movie
- Native Languages
- Networking
- Nissan
- Organizational barriers
- Oscilloscope
- Palm Zire
- Paper shredder
- Parity
- Patent
- Patents
- Phone
- Plagiarism
- Planning ahead
- Platform-specific code
- Police
- Polling
- pollution
- Prevention
- Principles
- Printer
- Printers
- Printing
- Product specific
- Product support
- Programming
- pyramids
- Quality programming
- Raspberry Pi
- Read modify write
- Register design tools
- Registers
- Research Disclosure
- Resets
- Reverse assembly
- Road construction
- Robat
- robots
- Robust code
- Safety
- Safety net
- Safety-critical
- Security
- Self configuration
- Self-driving cars
- Sensor
- Sensors
- Signoffs
- Simulations
- Simulators
- Smart home
- Smart technology
- Smartwatch
- Soccer
- Software
- Software IP
- Software program
- Software programming
- Solar power
- Source code
- Specifications
- SpectaReg
- Spiderman
- Standards
- stress
- Sully
- Superblock
- Supersuit
- Surgery
- Switch
- Technology
- Teens
- Tesla
- Tesla Autopilot
- Test hooks
- Testing
- Timers
- Trade secrets
- translation
- Uber
- US Airways 1549
- USB cable
- USB extension cable
- UVM
- Verification
- Vertical expert
- Virtual reality
- Visibility
- Voltage drop
- Watch
- weeds
- Windows programmers
- Youth
November 30, 2006
Published by Gary Stringham at November 30, 2006
Categories
A common question engineers often wrestle with is how long hardware will take to do a requested task so firmware can take the next step. Engineers implement different designs (both in hardware and firmware) depending on the length of time, and these designs have varying impacts on hardware and firmware […]
Do you like it?
April 30, 2007
Published by Gary Stringham at April 30, 2007
Categories
In a survey I conducted of several firmware engineers, lack of good documentation of hardware was the number one complaint. It is because firmware engineers so heavily rely on the hardware documentation to correctly do their job. Some of the engineers said that wrong documentation is worse than no documentation […]
Do you like it?
February 28, 2008
Published by Gary Stringham at February 28, 2008
Categories
Much of firmware development focuses on interfacing with registers. Documentation plays a key role in this effort since engineers must refer to it constantly to look up register and bit details. In particular, engineers need to generate or decode hex numbers, where the value of each bit must be clearly […]
Do you like it?
March 31, 2008
Published by Gary Stringham at March 31, 2008
Categories
Last month’s newsletter discussed some best practices for documenting register layouts, illustrating key points with a sample register diagram. One reader, Joel Saks, noted that my register diagram did not clearly indicate whether the bits were read/write bits or read-only bits. Joel makes an excellent point and also exposes one […]
Do you like it?
June 30, 2008
Published by Gary Stringham at June 30, 2008
Categories
We have all dealt with the pain of inaccurate and out-of-date register information. Registers and bits are modified in hardware but the documents are not updated. Documents are updated but firmware is not changed. Or typos are introduced along the way. Failure to catch these problems typically results in hours […]
Do you like it?
January 30, 2010
Published by Gary Stringham at January 30, 2010
Categories
In the last two articles (here and here,) I discussed the dangers of read-modify-write operations on registers that create exposure to collision and corruptions by firmware. I discussed certain firmware and CPU techniques that can reduce these dangers, but not completely eliminate them. As promised, this month I will discuss […]
Do you like it?
July 14, 2010
Published by Gary Stringham at July 14, 2010
Categories
A comment in the GABEonEDA blog entry “Accellera Works Toward a Unified Verification Methodology (UVM)” recently caught my attention: Silicon respins due to design errors not only have not diminished in number, they have actually increased. This is an indication that complexity has grown more than the ability of verification […]
Do you like it?
January 31, 2011
Published by Gary Stringham at January 31, 2011
Categories
While living in Germany, I heard the following joke: Question: What do you call someone who speaks three languages? Answer: Trilingual. Q: What do you call someone who speaks two languages? A: Bilingual. Q: What do you call someone who speaks one languages? A: An American. If you were born […]
Do you like it?