Am 18.03.2017 um 12:59 schrieb Michael Mrozek shop@dragonbox.de:
Am Sat, 18 Mar 2017 11:58:30 +0100 hat "H. Nikolaus Schaller" hns@goldelico.com geschrieben:
Nikolaus already has a collection of scripts for testing and notaz already adopted the input tester.
Yes, especially the hw-test tool: http://git.goldelico.com/?p=gta04-kernel.git;a=blob;f=Letux/root/hw-test;h=0...
Thanks for the link.
I use this for the GTA04 to create test reports like this: http://www.gta04.org/serial.php?serial=5285-0050 But it is not as fully automatic as it should be to hand over to the production facility.
Well, writing scripts to mostly automate that is what I can do.
My tool could also start automatically right after booting, but since it includes an upload to the server to store the MAC and IMEI addresses and requires manually typing in some serial number, it would also need to set up a test PC...
You may wonder why I read out the MAC and IMEI addresses? This is to print the individual device label since it is handy to have these printed somewhere without opening or booting the device. It also makes the devices better traceable for production issues, repair, warranty etc. But AFAIsee it is not necessary to do so.
I can work on the test and scripts file, but I need someone who can create the basic filesystem for booting and testing. Who can help me there? :)
You could try:
http://download.goldelico.com/letux-debian-rootfs/latest-minimal.tbz and mix with latest u-boot, kernel. In other words:
DEV=/dev/sdd makesd pyra -r debian This is currently still a Debian Jessie and sysvinit (8.7) but upgrade to Debian 9.0 systemd is in the works. I think X11 is installed but no GUI. So you can either apt-get install lxde or xfce4 if you need.
That's probably not what we can use for the mass production, as I can't imagine Debian booting up in 2 seconds.
Yes, it indeed takes longer. It typically needs ~30 seconds up to X11.
But I don't know how much the networking stack and low console RS232 speed is influencing. Or checking the SD card rootfs for integrity. BTW: systemd is booting much faster.
If you want 2 seconds it is a real challenge. U-Boot already waits 2 seconds until it starts the boot script. Maybe you can use the SPL Falcon mode (which makes SPL load and start a RAM image of the kernel+FTD bypassing the whole U-Boot stuff - basically you cache the RAM before "Starting kernel...").
The card on the Pandora starts with the tests immediately after loading the kernel, there's no OS that needs to be booted.
One thing we need to test the display is to load the full DSS/DSI/MIPI stuff. Or we have no display. That is different from the Pandora where it is possible to use the display in U-Boot. If you use Falcon mode you already have a kernel with DSS support.
Then you can remove drivers and things from the boot process that are not needed.
Wrong idea: We shouldn't even have a real boot process there, as that takes too long.
You are right... I am currently flashing and testing a tiny fraction of the Pyra quantity of GTA04A5 boards and it takes quite boring time waiting...
This could be used for setting up such a test pretty fast, but I'd rather start with the "real" test SD Card (for the mass production) right away, otherwise he have to do it twice.
I see. Please feel free to take my scripts as blueprints for controlling the peripherals.
BR, Nikolaus