2 ms·
> The first step was to forcibly disable 1) the display, 2) the radio, and 3) the flash chip from using the SPI bus by adding three jumper wires to tie their CE
by Gibbon1 8y ago
> The first step was to forcibly disable 1) the display, 2) the radio, and 3) the flash chip from using the SPI bus by adding three jumper wires to tie their CE pins to VCC.
A couple of things I found helpful.
Use a standard connector for in circuit programming. It just makes developing and debugging so much easier. Being able to easily swap parts of a development setup to see if the problem follows a piece of hardware will save your hair.
For AVR's where the programming interface is shared with the SPI Bus, always put pull ups on the chip selects for SPI's bus parts. As you learned those parts can fight the programmer if you reset the processor while they are holding the bus.
Also for AVR's I've seen mis-programming set the fuses to a clock setting that isn't supported by the hardware. Like programming an very low speed clock or an external clock when there is none. On our test jigs we resorted to injecting a 1MHZ clock on the xtal input pin when programming. Providing for this will be it easy to recover bricked board.
Having a command line interface for running tests is really really helpful. Use one of those USB to serial adaptors by FDDI. I found USB kind of sucks because plugging and unplugging USB ports a lot seems to often confuse OS. I've seen the US just give up on a USB port that it thinks is hosed. Either that or the drive gets messed. And you need to reboot. Using serial solves that problem.
And for small runs of boards try designing a simple loopback teststand. Just loop IO back through the test stand and use the host uP to run the tests.
C#/.net gets a lot of hate, but works really well to drive a single device under test. That allows you to slap together a simple GUI based test that you can offload onto someone else. You don't need anything but the programmer and a USB to serial adapter. You can shell out to run AVRDude.
Consider barcodes and barcode readers to keep track of boards. Failing that invest in QC tags.