[Arm-netbook] Crowsupply update

Luke Kenneth Casson Leighton lkcl at lkcl.net
Tue Jan 9 13:41:57 GMT 2018

crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68

On Tue, Jan 9, 2018 at 1:04 PM, Pičugins Arsenijs <crimier at yandex.ru> wrote:
>>  software-wise i need something that does nothing more complex than
>> mount stuff on a micro-sd card, show boot messages on both screens,
>> and maybe has 2 keyboards plugged in (one into each USB socket) so
>> that they can bash some keys and see that crud comes up on-screen for
>> each.
>>  going beyond that... testing I2C, UART and the GPIO.... *sigh*...
>> that involves writing some software.
> Speaking about I2C, UART and GPIO testing - it sounds easy.
> I don't yet know which defects you'd want to cover with tests
> (mechanical, soldering, faulty parts, maybe all of them), but,
> as far as my research goes, you can test both UART and GPIOs
> with a loopback test, and I2C could be tested using a simple
> device - such as an EEPROM.

 funny but there's an EEPROM on-board the Micro-desktop PCB... :)

> Now, I don't have as much testing experience, but I've done a couple
> of DIY jigs - not automated, but that's yet to come - and I've been
> thinking about a way to make testing jigs. First thing is - it's best if
> the test program runs on the computer card itself. I see that's
> what you plan to do, and, if I'm not mistaken, cards are going to boot
> from a MicroSD card anyway - which is what's needed.

 yyep.  there's two.

> If you want to test USB, you don't even need to have engineers
> mash on the keyboard, attach two USB devices with unique
> IDs (say, CP2012 - you can program those through USB connection)

 ha good idea.

 could someone put these things into the testing page?


More information about the arm-netbook mailing list