Re:Zombie Moore's Law shows hardware is eating software
by bramen on Saturday September 24, 2016 @09:02AM
(#12570769)
How bad is debugging logic running purely on hardware nowadays? Is there anything more user-friendly than tapping specific lines and watching the output on an oscilloscope?
[ Parent
| on HN ]
Re:Zombie Moore's Law shows hardware is eating software
by dnautics on Saturday September 24, 2016 @10:50AM
(#12571120)
Usually you start at the verilog level with simulators (I've done this professionally with zero hardware experience and discovered many critical bugs in a chip that's now taped out. Of course the real engineers had to fix them.) Now that it's gone physical, after a series of very low level tests, they will take similar software and adapt it to the interface for hardware instead and repeat all the tests.
Re:Zombie Moore's Law shows hardware is eating software
by bramen on Saturday September 24, 2016 @12:37PM
(#12571551)
Ah makes sense. Thanks for the info, will look into this.
Re:Zombie Moore's Law shows hardware is eating software
by amelius on Saturday September 24, 2016 @10:06AM
(#12570960)
Yes, you can debug on an FPGA first, for example, allowing you to put the hardware-equivalent of a printf statement in places where you need them.
Or, you can configure all of your flipflops into a barrel shift register, so you can read out their contents serially (and shift their contents back in circularly).
But there are many more techniques.
Re:Zombie Moore's Law shows hardware is eating software
by bramen on Saturday September 24, 2016 @12:35PM
(#12571544)
Interesting. Thanks, you've given me a few things to read up on.
Re:Zombie Moore's Law shows hardware is eating software
by klodolph on Saturday September 24, 2016 @09:53AM
(#12570912)
How do you propose tapping a line on a piece of silicon with a 14nm feature size?