Hi Adam -- I agree that the seconds leading up to your throwing the power switch on a prototype board for the first time are jolly exciting.
In the past, when clock speeds were a lot lower and we were working with dual-in-line (DIL) packages, we used to sucket all the ICs on our prototypes. Before we first powered up the board, we pulled all of the ICs out so we could first check that there were no shorts, and then check that all of the IC sockets had power and ground on the appropriate pins.
It's a lot trickier these days with high clock speeds and surface mount technology, when the prototype board has all the ICs soldered down...
First, I always check that chip power and ground are wired up correctly using an unassembled "solder sample" board and a continuity checker. Beep...beep... Drives your cow-orkers crazy.
Next, I first power up the board using a lab power supply with current limit. I slowly raise the voltage to make sure the board is behaving itself.
Lesson learned: if you have one of those packages with a large ground pad under it, expect that the fab house forgot to put the solder paste under it when making your prototypes. Also, if possible bring the ground pad artwork out from under the chip so you can heat up the pad if you need to resolder the chip.
This reminds me of Board bring up times. Everytime a new board was populated and made ready to test, there was a new problem seen. Processor with BGA package have their own issues. Its so helpful to add as many test points when you are making those initial prototypes. EMI/EMC issues take their own time to solve. But I would say its fun, staying awake long nights sometimes no sleep till the first board is up and repeating on few boards. Its like passing some exam.
Board bring up is definitely very interesting part of the board testing. Few minor problems some times give a really long trouble and a big issues can be found easily. Overall the next interesting is the reliability testing for any product.
"Will you need any special test equipment? When will it become available to you?" Anyone ever get to the point where you are ready to test, but the equipment you needed wasn't ready for you? What did you do to punt?
What are the engineering and design challenges in creating successful IoT devices? These devices are usually small, resource-constrained electronics designed to sense, collect, send, and/or interpret data. Some of the devices need to be smart enough to act upon data in real time, 24/7. Are the design challenges the same as with embedded systems, but with a little developer- and IT-skills added in? What do engineers need to know? Rick Merritt talks with two experts about the tools and best options for designing IoT devices in 2016. Specifically the guests will discuss sensors, security, and lessons from IoT deployments.