olsndot/hw1
2018-02-20 22:01:22 +00:00
..
Socket_Arduino_Uno.3dshapes WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
Socket_Arduino_Uno.pretty WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
.gitignore hw1: gitignore gerbers 2018-02-19 21:08:44 +00:00
cubemx-pin-selector.ioc WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
hw1-cache.lib hw1: update to current 2018-02-19 21:06:16 +00:00
hw1-rescue.lib WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
hw1.cmp WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
hw1.csv hw1: update to current 2018-02-19 21:06:16 +00:00
hw1.kicad_pcb hw1: update to current 2018-02-19 21:06:16 +00:00
hw1.net hw1: use explicit 10103594-0001LF part 2017-12-31 00:02:11 +00:00
hw1.pdf hw1: update to current 2018-02-19 21:06:16 +00:00
hw1.plt WIP: hardware test partner round 1 2017-10-07 15:20:00 +00:00
hw1.pro hw1: update to current 2018-02-19 21:06:16 +00:00
hw1.sch hw1: add exampe part number for fx2la part number 2018-02-02 21:03:05 +00:00
hw1.xml hw1: update to current 2018-02-19 21:06:16 +00:00
karlp-klibs.dcm add "klibs" with new regulator 2017-11-17 23:09:07 +00:00
karlp-klibs.lib add "klibs" with new regulator 2017-11-17 23:09:07 +00:00
README hw1: notes from assembling first board. 2018-02-20 22:01:22 +00:00
signal.integrity.wisdom hw1: notes on signal integrity 2018-02-19 21:07:22 +00:00

This is a board designed to receive nucleo64 (and maybe 32) boards
to be test TARGETS.  The stm32l1 on _this_ board is reprogrammed via
one of the debug connectors, with appropriate software to be
master/slave/etc to correspond with the DUT.  All (most) communication
lines between the two boards are tapped to a 10 pin connector matching
cheap FX2based logic analysers, allowing automatic tests to be written
that use sigrok to check that the signals on the wire match expectations.


Notes on assembly hw1-a:
* 16Mhz crystal, 15pf load caps, and 3k7 i2c pullups
  (why don't I have 4k7 0603 resistors lying around? who knows!)
* A power LED wouldn't hurt.
* Adding a red/green user led wouldn't hurt for test pass/fail, even though
  it's meant to be autotest
* maybe a fet to turn on/off the i2c pull ups programatically?
  (maybe just a single jumper? is there really any need for individual control
   of the pullups?)
* move stlink connector 90° or just down and tuck it in, so we can pull the
  edge in.  It overlaps the buttons on the nucleos, and requires longer
  pins than necessary otherwise.
* Add some ground pads for test points, just in general.  Test points good,
  more test points better.