[Automated-testing] Documentation: Designing for automated testing

[Milosz Wasilewski]

On Thu, 24 Oct 2019 at 12:21, Geert Uytterhoeven <geert at linux-m68k.org> wrote:
>
> Hi Milosz,
>
> On Thu, Oct 24, 2019 at 1:10 PM Milosz Wasilewski
> <milosz.wasilewski at linaro.org> wrote:
> > On Thu, 24 Oct 2019 at 10:58, Chris Fiege <cfi at pengutronix.de> wrote:
> > > now that ELCE and ATS 2019 are coming closer I wanted post a short reminder:
> > >
> > > I am collecting facts and hints about how to design an embedded hardware in
> > > a way, that embedded software development is easy:
> > >
> > > https://designing-for-automated-testing.readthedocs.io/
> > >
> > > If you think that your common use-case is missing please send me a patch or
> > > open a pull-request:
> > > https://github.com/SmithChart/Designing-for-Automated-Testing
> > >
> > > Feel free to forward this documentation to your (hardware) colleagues and
> > > your customers.
> >
> > I'm missing a requirement for unique ID. If you have more than 1 board
> > connected to common host non-unique IDs prevent from working with the
> > boards. This mainly applies to automated testing labs/farms. Unique ID
> > should apply to UART and possibly other interfaces (MAC address,
> > fastboot, DFU, etc.). I'll send a PR for UART but I'm not sure where
> > the other IDs should be mentioned.
>
> For CP210x USB-to-UART bridges, you can program the serial string
> using a special tool, or fall back to /dev/serial/by-path/, cfr.
> https://elinux.org/R-Car/Boards/Salvator-XS#Serial_Console

For UART it's usually OK. DFU or MAC addresses are more often
identical for all boards of the same type.

milosz

>
> Gr{oetje,eeting}s,
>
>                         Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds