Contents

Overview

Release Notes

[expand all]
SANTARO Windows Embedded Compact 7 10.1r442-0

Release Information

BSP Version10.1r442
Configuration0
Release Date20.10.2017
Released byClemens Terasa
Verified byMarc-Oliver Westerburg

Release Content

Reason for the Release Fixed EXC3000 touch detection issue
Windows Embedded Version Embedded Compact 7
Windows Embedded License C7P1
Windows Embedded Update Update 60 (June 2016)
BSP Supplier version r954
Supported Hardware Product SANTARO
Processor Typ x2, x4
PCB Revisions 1.1.1, 1.2

Build Software

Tested build host OS Windows XP SP3 (x86)
IDE Visual Studio 2008
Build system Platform Builder 7.0

Required Software for SDK

Visual Studio 2008 Version 9.0.30729.1 SP (including Service Pack 1) or higher
SDK SANTARO (i.MX6) SDK CE7 10.1r442 or later

Recommended Software

ActiveSync Microsoft Windows Mobile Device Center (Windows Vista / Windows 7)
Bootloader Garz & Fricke Flash-N-Go Boot v9.0r3476 or higher
eBoot for Windows CE7 10.1r442
Service Mode Garz & Fricke Flash-N-Go System v7.0 or higher

Compatibility breaking changes and severe bugs

IP-Settings The IP Settings in EBoot are ignored in Windows since version 8.0r275.
The MAC address however will be propagated as before, and needs to be configured in EBoot.
This has the consequence, that the default IP 192.168.1.1 will be used.
By default the DHCP is disabled.
Bootlogo Because of Bug #17504 with slow loading of the Bootlogo, the logo is currently shown quite late.
This may be improved in future versions.

1 Windows Embedded Compact 7 Components SKU Comparison

Changes since version 10.0r416

Fixed Error(s)

Added Feature(s)

Note: For a complete change list of all releases, please scroll down to [Change History].

Known Restrictions


Included Packages

Garz & Fricke Packages

Package nameDescription
resetResets the device.
discovery serviceProviding device information via ethernet for the G&F Device Control Center
toolboxA command line tool with several useful functions for Windows CE devices.
autocopyAutomatically copy files.
autostartAutomatically start executables on device insertion.

Hardware Support

Audio

Features

  • SGTL5000 Sound device
  • Playback on internal/external speaker and line-out
  • Recording from microphone or line-in (selectable via capsrc)
  • Playback levels adjustable via OS controls

Known Restrictions

  • Crackling sound on Boot (#21258)

  • Crackling sound on Boot (#21259)

CE7 7.0r246(01.06.2016)

Tests [Sum: 4, OK: 4]

The Audio iMX6 Reference Manual (IMX6DQRM Rev 2, 06/2014) describes several Audio features.
Chapter 16 describes the Digital Audio Multiplexer (AUDMUX) in detail.

The hardware codec on the SANTARO is the SGTL5000XNAA3.

There are two audio outputs, the external on X8 and the internal on X9 or X10, and the MIC and line_in also on X8.

We want support the usual audio formats: WAV PCM, MP3

Test line_in recording looped with line_out (#16245)
Tested by Clemens Terasa on 30.05.2016

Recording via Line In mono (looped with line out)

// Selecting the capture source first
\> CapSrc.exe -s Line In
// Set volume to max
\> CapSrc.exe FFFF
// Start 5s recording and play file
\> start wavrec
\> wavplay
// test output
\> wavplay wavrec.wav
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Test MP3 sound output (#16243)
Tested by Clemens Terasa on 30.05.2016

Test

  1. Load the 440Hz-5sec.mp3 file from http://support.garz-fricke.com/projects/TestFiles/Audio/ to the device root.
  2. Execute
    start ceplayit 440Hz-5sec.mp3
    

Validation
The test succeeds if the file is played and you can hear sound.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Test Microphone input (#16244)
Tested by Clemens Terasa on 30.05.2016

Record a sample using the microphone.

  1. Make sure audio output works.
  2. Connect microphone with X8 connector.
  3. Using soundrec to record 5 seconds(mono):
    \> capsrc -d 0 -s Microphone
    \> capsrc FFFF
    // Recored 5 seconds
    \> wavrec
    \> wavplay wavrec.wav
    
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Test wave support (#16242)
Tested by Clemens Terasa on 30.05.2016

Test the sound with wave support.

Audio files can be found under:
http://support.garz-fricke.com/projects/TestFiles/Audio/

Using Waveplay:

waveplay 20Hz-20kHz_log_sweep_20sec.wav
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added audio recording support. (#12793)

  • Added wave playback support. (#12577)

Tests [Sum: 4, OK: 4]

The Audio iMX6 Reference Manual (IMX6DQRM Rev 2, 06/2014) describes several Audio features.
Chapter 16 describes the Digital Audio Multiplexer (AUDMUX) in detail.

The hardware codec on the SANTARO is the SGTL5000XNAA3.

There are two audio outputs, the external on X8 and the internal on X9 or X10, and the MIC and line_in also on X8.

We want support the usual audio formats: WAV PCM, MP3

Test MP3 sound output (#12073)
Tested by Clemens Terasa on 16.02.2016

Test

  1. Extract the files in the Naviplayer.7z on the device. Use the Foldername \Naviplayer
  2. Place a MP3 file on the device.
  3. Execute
    \Naviplayer\Naviplayer.exe myfile.mp3
    

Validation
The test succeeds if the file is played and one can hear sound.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Test wave support (#12072)
Tested by Clemens Terasa on 29.02.2016

Test the sound with wave support.

Audio files can be found under:
http://support.garz-fricke.com/projects/TestFiles/Audio/

Using Waveplay:

waveplay 20Hz-20kHz_log_sweep_20sec.wav
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Test Microphone input (#12074)
Tested by Clemens Terasa on 16.02.2016

Record a sample using the microphone.

  1. Make sure audio output works.
  2. Connect microphone with X8 connector.
  3. Using soundrec to record 5 seconds(mono):
    \> capsrc -d 0 -s Microphone
    \> capsrc FFFF
    // Recored 5 seconds
    \> wavrec
    \> wavplay wavrec.wav
    
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Test line_in recording looped with line_out (#12075)
Tested by Clemens Terasa on 16.02.2016

Recording via Line In mono (looped with line out)

// Selecting the capture source first
\> CapSrc.exe -s Line In
// Set volume to max
\> CapSrc.exe FFFF
// Start 5s recording and play file
\> start wavrec
\> wavplay
// test output
\> wavplay wavrec.wav
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

CAN

Features

  • Baud rates 20kBis/s to 1000kBis/s
  • Basic frames
  • Extended frames
  • Sending and receiving RTR messages
  • A Garz & Fricke CAN_API for simple software development

Known Restrictions

  • No restrictions known.

CE7 3.0r89(01.02.2016)

Added Feature(s)

  • Added Garz and Fricke FlexCAN driver. (#11987)

  • Added support for the the Garz and Fricke CAN API. (#11988)

Tests [Sum: 3, OK: 3]
Perform Test

Test Environment:

  • Device connected to a PCAN USB adapter.
  • Windows PC running the PCANview application.
  • In-house test tool CanApiTest
CAN1: Baudrate test (#12077)
Tested by Clemens Terasa on 01.02.2016
Baud rates
  • 1000kbit/s
  • 500kbit/s
  • 250kbit/s
  • 125kbit/s
  • 100kbit/s
  • 50kbit/s
  • 20kbit/s
Setup
  1. Connect PC-PCAN dongle with your PC and the GuF Device
  2. Install and start the PCAN-View tool.
  3. Configure a periodic message to send with a period of 200 ms and start it
Test procedure

For each baudrate (1000-20) do:

  1. Set the PCAN-View baud rate to
  2. On the device execute “@CanApiTest receive -b -t 2000 1@”
  3. On the device execute “@CanApiTest send -b -d 0xaa -t 1000 1@”

Test Conditions
  1. The test fails if no messages are received on the device in step 2.
  2. The test fails if no messages are received on the PC in step 3.
Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK

CAN1: Test extended frames (#12078)
Tested by Clemens Terasa on 01.02.2016
Setup
  1. Connect PC-PCAN dongle with your PC and the GuF Device
  2. Install and start the PCAN-View tool.
  3. Configure a periodic extended message to send with a period of 200 ms and start it
Test procedure
  1. Set the PCAN-View baud rate to 250kBit/s
  2. On the device execute “@CanApiTest send -b 250 -d 0xaa -e -t 1000 1@”
  3. On the device execute “@CanApiTest receive -b 250 -e -t 2000 1@”
Test Conditions
  1. The test fails if no messages are received on the device in step 2.
  2. The test fails if no messages are received on the PC in step 3.
Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK

CAN1: Test RTR messages (#12079)
Tested by Clemens Terasa on 01.02.2016
Setup
  1. Connect PC-PCAN dongle with your PC and the GuF Device
  2. Install and start the PCAN-View tool.
Test procedure

Test RTR request:

  1. Set the PCAN-View baud rate to 250
  2. On the device execute “@CanApiTest send -rtr -b 250 -d 0xaa 1@”
  3. Verify with the PCAN-View tool that the RTR message was correctly received and marked as RTR request.

Test RTR response:

  1. Set the PCANView baud rate to 250
  2. Send with PCAN-View periodic RTR messages to 0×45 with a period of 200 ms.
  3. On the device execute “@CanApiTest send -prtrr -b 250 -d 0xaa -i 0×45 1@”
  4. Verify with the PCAN-View tool that the RTR response was sent by the GuF device.
Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK

Capacitive Touch - EDT-M06 I2C

Features

  • EDT multi touch controller.
  • Controller driver for EPxxxM06 sensor variants.
  • Windows CE supports up to 2 touch points.

Known Restrictions

  • No restrictions known.

CE7 9.0r387(07.09.2016)

Tests [Sum: 5, OK: 4, Untested: 1]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The files used for this test is rbtouch-edt-ft5x06-v00-r3515.xml
Touchscreen calibration (#20130)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

Untested

Comment

The calibration data comes from the XML -Touch settings and cannot be calibrated.
Import the correct XML file in Flash-N-Go System.

Multitouch Test (#20131)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#20132)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Validate rotated touchscreen support (#20133)
Tested by Clemens Terasa on 14.09.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Check the booting behavior while keeping the display touched (#20134)
Tested by Clemens Terasa on 14.09.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

CE7 8.0r275(04.07.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Check the booting behavior while keeping the display touched (#17487)
Tested by Clemens Terasa on 04.07.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Comment

Tested with revision r275.

Multitouch Test (#17484)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Comment

Tested with revision r275.

Test single touch with 'drawing' with 'CeTouchView' (#17485)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Comment

Tested with revision r275.

Validate rotated touchscreen support (#17486)
Tested by Clemens Terasa on 04.07.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Comment

Tested with revision r275.

Touchscreen calibration (#17483)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3129R: SANTARO x2 7.0 OF PCT V1.2, S/N: 01752360
Status

OK

Comment

Tested with revision r275.

Capacitive Touch - EXC3000 I2C

Features

  • EXC3000 capacitive multi touch controller.
  • Windows CE supports up to 2 touch points.

Known Restrictions

  • EXC3000 touch misses the touch up signal (#19068)Solved in ‘CE2013 4.0r404’

CE7 10.1r442(24.10.2017)

Fixed Error(s)

  • Fix a detection bug for EXC3000 by increasing the reset-to-ready wait time. (#28229)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The files used for this test is rbtouch-eeti-exc3000-v11-r3637.xml
Check the booting behavior while keeping the display touched (#28240)
Tested by Clemens Terasa on 20.10.2017

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

Validate rotated touchscreen support (#28239)
Tested by Clemens Terasa on 20.10.2017

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#28238)
Tested by Clemens Terasa on 20.10.2017

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

Multitouch Test (#28237)
Tested by Clemens Terasa on 20.10.2017

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

Touchscreen calibration (#28236)
Tested by Clemens Terasa on 20.10.2017

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

CE7 10.0r416(10.03.2017)

Fixed Error(s)

  • Fixed touch-up bug with EXC3000 I2C controllers. (#20145)

Tests [Sum: 5, OK: 4, Untested: 1]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The files used for this test is rbtouch-eeti-exc3000-v07-r3589.xml
Multitouch Test (#23106)
Tested by Clemens Terasa on 09.03.2017

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#23107)
Tested by Clemens Terasa on 09.03.2017

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

OK

Validate rotated touchscreen support (#23108)
Tested by Clemens Terasa on 09.03.2017

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

OK

Check the booting behavior while keeping the display touched (#23109)
Tested by Clemens Terasa on 09.03.2017

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

OK

Touchscreen calibration (#23105)
Tested by Clemens Terasa on 09.03.2017

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

Untested

Comment

The touch calibration is not stored and should be imported from the XML configuration.

CE7 9.0r387(07.09.2016)

Tests [Sum: 5, Failed: 5]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The files used for this test is rbtouch-eeti-exc3000-v00-r3502.xml
Touchscreen calibration (#20118)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:

Status

Failed

Multitouch Test (#20119)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:

Status

Failed

Test single touch with 'drawing' with 'CeTouchView' (#20120)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:

Status

Failed

Validate rotated touchscreen support (#20121)
Tested by Clemens Terasa on 15.09.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:

Status

Failed

Check the booting behavior while keeping the display touched (#20122)
Tested by Clemens Terasa on 15.09.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:

Status

Failed

CE7 8.0r275(04.07.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Test single touch with 'drawing' with 'CeTouchView' (#17473)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Multitouch Test (#17472)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Validate rotated touchscreen support (#17474)
Tested by Clemens Terasa on 04.07.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Check the booting behavior while keeping the display touched (#17475)
Tested by Clemens Terasa on 04.07.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Touchscreen calibration (#17471)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN: 01724586

Status

OK

Comment

Tested with revision r275.

CE7 7.0r246(01.06.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Touchscreen calibration (#16187)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:01724586

Status

OK

Comment

Tested with revision r245.

Test single touch with 'drawing' with 'CeTouchView' (#16189)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:01724586

Status

OK

Comment

Tested with revision r245.

Validate rotated touchscreen support (#16190)
Tested by Clemens Terasa on 31.05.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:01724586

Status

OK

Comment

Tested with revision r245.

Check the booting behavior while keeping the display touched (#16191)
Tested by Clemens Terasa on 31.05.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:01724586

Status

OK

Comment

Tested with revision r245.

Multitouch Test (#16188)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3230R SANTARO x2 19.0 SG MDB V1.2, SN:01724586

Status

OK

Comment

Tested with revision r245.

Capacitive Touch - EXC7200 I2C

Features

  • EXC7200 capacitive multi touch controller.
  • Windows CE supports up to 2 touch points.

Known Restrictions

  • Slow initial touch wake up or reset (#22989)

CE7 9.0r387(07.09.2016)

Tests [Sum: 5, OK: 4, Untested: 1]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The file used for this test is rbtouch-eeti-exc7200-v01-r3496.xml
Touchscreen calibration (#20112)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 01680449

Status

Untested

Comment

The calibration data comes from the XML -Touch settings and cannot be calibrated.
Import the correct XML file in Flash-N-Go System.
Please consult the Garz & Fricke support team if there are issues with the calibration.

Test single touch with 'drawing' with 'CeTouchView' (#20114)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 01680449

Status

OK

Multitouch Test (#20113)
Tested by Clemens Terasa on 14.09.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 01680449

Status

OK

Validate rotated touchscreen support (#20115)
Tested by Clemens Terasa on 14.09.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 01680449

Status

OK

Check the booting behavior while keeping the display touched (#20116)
Tested by Clemens Terasa on 14.09.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3125R: SANTARO x2 7.0 SG, S/N: 01680449

Status

OK

CE7 8.0r275(04.07.2016)

Added Feature(s)

  • Added EDT-M06 touch variant support. (#17502)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Touchscreen calibration (#17465)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

Check the booting behavior while keeping the display touched (#17469)
Tested by Clemens Terasa on 04.07.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

Validate rotated touchscreen support (#17468)
Tested by Clemens Terasa on 04.07.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

Test single touch with 'drawing' with 'CeTouchView' (#17467)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

Multitouch Test (#17466)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

CE7 7.0r246(01.06.2016)

Added Feature(s)

  • Added EETI EXC7200 USB touch support. (#15970)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Test single touch with 'drawing' with 'CeTouchView' (#16183)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 016080449

Status

OK

Comment

Tested with revision r245.

Check the booting behavior while keeping the display touched (#16185)
Tested by Clemens Terasa on 30.05.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3125R: SANTARO x2 7.0 SG, S/N: 016080449

Status

OK

Comment

Tested with revision r245.

Validate rotated touchscreen support (#16184)
Tested by Clemens Terasa on 30.05.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 016080449

Status

OK

Comment

Tested with revision r245.

Touchscreen calibration (#16181)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 016080449

Status

OK

Comment

Tested with revision r245.

Multitouch Test (#16182)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3125R: SANTARO x2 7.0 SG, S/N: 016080449

Status

OK

Comment

Tested with revision r245.

CE7 6.0r183(05.04.2016)

Added Feature(s)

  • Added support for EETI EXC7200 touch. (#12684)

  • Added the touchc touch calibration tool. (#13460)

  • Added the touch test tools cetouchview.exe and etcha.exe to the image. (#13622)

  • Added touch driver abstraction for per-touch configurations. (#13459)

  • Code changes for EDT touch M06 variants. Still unsupported though. (#13451)

Tests [Sum: 2, OK: 2]
Perform Test

Test Environment:

  1. Select the correct display in Eboot.
  2. The touch should be probed by the OS.
Multitouch Test (#13757)
Tested by Clemens Terasa on 30.03.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate single touch: Draw some lines
    2. Validate multi touch: Draw circles using two fingers
    3. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Touchscreen calibration (#13756)
Tested by Clemens Terasa on 30.03.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Capacitive Touch - EXC7200 USB

Features

  • EXC7200 capacitive multi touch controller.
  • Connected to internal USB port.
  • Windows CE supports up to 2 touch points.

Known Restrictions

  • USB-Touch does not work after keeping the display touched while booting (#20140)

CE7 9.0r387(07.09.2016)

Tests [Sum: 5, Failed: 1, OK: 4]

Test Environment:

  1. Install the correct XML-Touch-Configuration file.
  2. The files should be found under http://support.garz-fricke.com/projects/Santaro/Configuration/.
  3. The files used for this test is rbtouch-eeti-exc7200-usb-v01-r3496.xml
Touchscreen calibration (#20124)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3130R: SANTARO x2 7.0 BX PCT V1.2, S/N: 01724719

Status

OK

Multitouch Test (#20125)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3130R: SANTARO x2 7.0 BX PCT V1.2, S/N: 01724719

Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#20126)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3130R: SANTARO x2 7.0 BX PCT V1.2, S/N: 01724719

Status

OK

Validate rotated touchscreen support (#20127)
Tested by Clemens Terasa on 15.09.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3130R: SANTARO x2 7.0 BX PCT V1.2, S/N: 01724719

Status

OK

Check the booting behavior while keeping the display touched (#20128)
Tested by Clemens Terasa on 15.09.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3130R: SANTARO x2 7.0 BX PCT V1.2, S/N: 01724719

Status

Failed

Causing issue(s)
  1. USB-Touch does not work after keeping the display touched while booting (#20140)

CE7 8.0r275(04.07.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  1. Select the correct display in Eboot.
  2. Select the USB touch in Eboot.
  3. Depending on the assembly of your device it may be necessary to select “USB rotated” in EBoot.
Test single touch with 'drawing' with 'CeTouchView' (#17479)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-2590R: SANTARO x2 10.4 OF AMP, S/N: 01413584 (USB rotated)
Status

OK

Comment

Tested with revision r275.

Validate rotated touchscreen support (#17480)
Tested by Clemens Terasa on 04.07.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device
  1. 900-2590R: SANTARO x2 10.4 OF AMP, S/N: 01413584 (USB rotated)
Status

OK

Comment

Tested with revision r275.

Check the booting behavior while keeping the display touched (#17481)
Tested by Clemens Terasa on 04.07.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device
  1. 900-2590R: SANTARO x2 10.4 OF AMP, S/N: 01413584 (USB rotated)
Status

OK

Comment

Tested with revision r275.

Touchscreen calibration (#17477)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-2590R: SANTARO x2 10.4 OF AMP, S/N: 01413584 (USB rotated)
Status

OK

Comment

Tested with revision r275.

Multitouch Test (#17478)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-2590R: SANTARO x2 10.4 OF AMP, S/N: 01413584 (USB rotated)
Status

OK

Comment

Tested with revision r275.

CE7 7.0r246(01.06.2016)

Tests [Sum: 5, OK: 4, Untested: 1]

Test Environment:

  1. Select the correct display in Eboot.
  2. Select the USB touch in Eboot.
  3. Depending on the assembly it may be necessary to select USB rotated.
Multitouch Test (#16194)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Run the touch test tool cetouchview.
  2. Validate multi touch: Draw circles using two fingers
  3. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device

900-3130R: SANTARO x2 10.4 BX PCT V1.2, S/N: 01724719

Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#16195)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3130R: SANTARO x2 10.4 BX PCT V1.2, S/N: 01724719

Status

OK

Validate rotated touchscreen support (#16196)
Tested by Clemens Terasa on 31.05.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device

900-3130R: SANTARO x2 10.4 BX PCT V1.2, S/N: 01724719

Status

OK

Check the booting behavior while keeping the display touched (#16197)
Tested by Clemens Terasa on 31.05.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device

900-3130R: SANTARO x2 10.4 BX PCT V1.2, S/N: 01724719

Status

OK

Touchscreen calibration (#16193)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3130R: SANTARO x2 10.4 BX PCT V1.2, S/N: 01724719

Status

Untested

Comment

The EETI EXC7200 USB controller cannot be persistently calibrated. It is calibrated by its firmware.
One can call touchc but it is not stored persistently.

Capacitive Touch - SIS92xx I2C

Features

  • Support for SIS92xx family capacitive multi touch controllers.
  • Windows CE supports up to 2 touch points.

Known Restrictions

  • No restrictions known.

CE7 9.0r387(07.09.2016)

Added Feature(s)

  • Added support for SIS92xx touch controllers. (#17276)

Tests [Sum: 5, OK: 4, Untested: 1]

Test Environment:

  1. Select the correct display in Eboot or install the correct XML file in Flash-N-Go System.
  2. The touch should be probed by the OS.
  3. Tested with rbtouch-sis9255-v00.xml Touch-XML file.
Multitouch Test (#20070)
Tested by Clemens Terasa on 13.09.2016

Test:

  1. If not already calibrated correctly execute calibration tool touchc on the device and perform the calibration.
  2. Save the calibration via the shell command savereg -n.
  3. Run the touch test tool cetouchview.
    1. Validate multi touch: Draw circles using two fingers
    2. Check handling of more than two fingers. The two finger behavior should persist.

Verification:

The touch test tool has to be executed without any errors.
The dots have to be under the finger tip at all times.
The touch state should be in a consistent state at all times. No circles should be possible when touching with one finger.

Device
  1. 900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285
Status

OK

Validate rotated touchscreen support (#20072)
Tested by Clemens Terasa on 13.09.2016

Test:

Enter on the console the command for 90° rotation:

disp -r 1

Verification:

Check whether the touch behavior is still working. Just drag the select box on the desktop.

Device
  1. 900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285
Status

OK

Check the booting behavior while keeping the display touched (#20073)
Tested by Clemens Terasa on 13.09.2016

Test:

Check the touch driver initialization while keeping the display touched on boot.

Verification:

  1. Keep the display touched and boot the device
  2. Verify that the system boots correctly
  3. Verify that the touch still works as expected:
    1. Start a touch painting tool and write your name without any failures of the touch drawings.
Device
  1. 900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285
Status

OK

Touchscreen calibration (#20069)
Tested by Clemens Terasa on 13.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285
Status

Untested

Comment

The calibration data comes from the XML-Touch settings and cannot be calibrated.
Import the correct XML file in Flash-N-Go System.
Please consult the Garz & Fricke support team if there are issues with the calibration.

Test single touch with 'drawing' with 'CeTouchView' (#20071)
Tested by Clemens Terasa on 13.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285
Status

OK

Digital I/O

Features

  • 2 galvanically isolated inputs
  • 2 galvanically isolated outputs
  • GPIOs with selectable direction

Known Restrictions

  • No restrictions known.

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added pingroup feature to the Digital IO driver. (#12732)

Tests [Sum: 2, OK: 2]
Perform Test

Test Environment:

The Digital I/O interface uses a Registry key for the reservation of the GPIO pins.
It may be neccessary depending on the hardware variant to edit the Registry.
For information about the hardware variants consult the hardware manuals for the SANTARO devices.

The Registry Key can be found under HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIOFreescale.
Especially the “PinFreeMaskP4” is of interest for SANTARO.

Possible Registry settings for this value are:

  • Default mode (I2C2): "PinFreeMaskP4"=dword:003F0FE0
  • Mode 1 (I2C2+SPI): "PinFreeMaskP4"=dword:003F0800
  • Mode 2 (GPIO): "PinFreeMaskP4"=dword:003F3FE0
  • Mode 3 (GPIO+SPI): "PinFreeMaskP4"=dword:003F3800

The Registry Keys may be set via the toolbox tool.
Do not forget to explititly save the registry with savereg -n and to reset the device.

Select mode 2 example via a telenet connection:

toolbox reg set HKLM\drivers\Builtin\DioFreescale PinFreeMaskP4 d 0x003F3FE0
savereg -n
reset

Test Setup:

  • Bridge the power signals
    Vin+ VDD_DIO
    Vin- GND_DIO
  • Shorten the outputs with the inputs
    DIG_IN1 DIG_OUT1
    DIG_IN2 DIG_OUT2
Testing DIG_IN2 with DIG_OUT2 (#13028)
Tested by Clemens Terasa on 25.02.2016

Test:

Level Step 1: set output Step 2: validate input
High Enter:
dio -o 5 -p 25 -w 1
Enter:
dio -o 5 -p 23 -r
Expected Output:
dio: Setting port 5, pin 25 output to 1... done.
Expected Output:
dio: reading port 5, pin 23... has value 1
Low Enter:
dio -o 5 -p 25 -w 0
Enter:
dio -o 5 -p 23 -r
Expected Output:
dio: Setting port 5, pin 25 output to 0... done.
Expected Output:
dio: reading port 5, pin 23... has value 0
Device

900-3045R SANTARO x2 V1.2 FBG SN: 01679855

Status

OK

Testing DIG_IN1 with DIG_OUT1 (#13027)
Tested by Clemens Terasa on 25.02.2016

Test:

Level Step 1: set output Step 2: validate input
High Enter:
dio -o 1 -p 17 -w 1
Enter:
dio -o 5 -p 24 -r
Expected Output:
dio: Setting port 1, pin 17 output to 1... done.
Expected Output:
dio: reading port 5, pin 24... has value 1
High Enter:
dio -o 1 -p 17 -w 0
Enter:
dio -o 5 -p 24 -r
Expected Output:
dio: Setting port 1, pin 17 output to 0... done.
Expected Output:
dio: reading port 5, pin 24... has value 0
Device

900-3045R SANTARO x2 V1.2 FBG SN: 01679855

Status

OK

CE7 3.0r89(01.02.2016)

Added Feature(s)

  • Add Garz & Fricke Digital IO driver.
    Currently the driver supports the external DIOs only. (#12433)

  • Added Garz & Fricke Digital IO API support.
    The API has currently no pin reservation and pin group support. (#11984)

Tests [Sum: 2, OK: 2]
Perform Test

Test Environment:

The Digital I/O interface uses a Registry key for the reservation of the GPIO pins.
It may be neccessary depending on the hardware variant to edit the Registry.
For information about the hardware variants consult the hardware manuals for the SANTARO devices.

The Registry Key can be found under HKEY_LOCAL_MACHINE\Drivers\BuiltIn\DIOFreescale.
Especially the “PinFreeMaskP4” is of interest for SANTARO.

Possible Registry settings for this value are:

  • Default mode (I2C2): "PinFreeMaskP4"=dword:003F0FE0
  • Mode 1 (I2C2+SPI): "PinFreeMaskP4"=dword:003F0800
  • Mode 2 (GPIO): "PinFreeMaskP4"=dword:003F3FE0
  • Mode 3 (GPIO+SPI): "PinFreeMaskP4"=dword:003F3800

The Registry Keys may be set via the toolbox tool.
Do not forget to explititly save the registry with savereg -n and to reset the device.

Select mode 2 example via a telenet connection:

toolbox reg set HKLM\drivers\Builtin\DioFreescale PinFreeMaskP4 d 0x003F3FE0
savereg -n
reset

Test Setup:

  • Bridge the power signals
    Vin+ VDD_DIO
    Vin- GND_DIO
  • Shorten the outputs with the inputs
    DIG_IN1 DIG_OUT1
    DIG_IN2 DIG_OUT2
Testing DIG_IN1 with DIG_OUT1 (#12489)
Tested by Clemens Terasa on 01.02.2016

Test:

Level Step 1: set output Step 2: validate input
High Enter:
dio -o 1 -p 0 -w 1
Enter:
dio -o 1 -p 2 -r
Expected Output:
dio: Setting port 1, pin 0 output to 1... done.
Expected Output:
dio: reading port 1, pin 2... has value 1
High Enter:
dio -o 1 -p 0 -w 0
Enter:
dio -o 1 -p 2 -r
Expected Output:
dio: Setting port 1, pin 0 output to 0... done.
Expected Output:
dio: reading port 1, pin 2... has value 0
Device

900-2894R SANTARO x2 8.4 OF NL11C SN: 01689105

Status

OK

Testing DIG_IN2 with DIG_OUT2 (#12490)
Tested by Clemens Terasa on 01.02.2016

Test:

Level Step 1: set output Step 2: validate input
High Enter:
dio -o 1 -p 3 -w 1
Enter:
dio -o 1 -p 1 -r
Expected Output:
dio: Setting port 1, pin 3 output to 1... done.
Expected Output:
dio: reading port 1, pin 1... has value 1
Low Enter:
dio -o 1 -p 3 -w 0
Enter:
dio -o 1 -p 1 -r
Expected Output:
dio: Setting port 1, pin 3 output to 0... done.
Expected Output:
dio: reading port 1, pin 1... has value 0
Device

900-2894R SANTARO x2 8.4 OF NL11C SN: 01689105

Status

OK

Display

Features

  • Support for LVDS displays
  • Configurable via registy settings
  • Backlight can be adjusted via Windows backlight control
  • The backlight has a granularity of 256 luminance steps
  • Dual-LVDS support for higher resolutions.

Known Restrictions

  • GuruCE-r954 integration: Missing LVDS power sequence (#14077)Solved in ‘CE2013 1.0r226’

  • IPU debug messages are flooding the debug output (#15897)Solved in ‘CE2013 1.0r226’

CE7 10.0r416(10.03.2017)

Added Feature(s)

  • Added support for Display DataImage FG0700W0DSSWAGL1 (also in SCX0700C48GGU65) (#23044)

Tests [Sum: 1, OK: 1]

Test Environment:

  • Load the display configuration file for the correct display.
  • Booting up the test device.
Simple display test for the DataImage SCX0700C48GGU65 (#23103)
Tested by Clemens Terasa on 09.03.2017

Test:

  1. Import the rbdisp-dataimage-SCX0700C48GGU65-r3587.xml via Flash-N-Go System
  2. Reboot to Windows.
  3. Deploy Telefunken_FuBK_test_pattern_1024x600_01.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_1024x600_01.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-3542R SANTARO x2 7.0 BX PCT 1K V1.2 (SN: 01934846)

Status

OK

CE7 7.0r246(01.06.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  • Load the display configuration file for the correct display.
  • Booting up the test device.
Simple display test for the Ampire AM-800600K2 (#16211)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Boot to EBoot.
  2. Select the LVDS0 AM-800600K2TMQW 800x600 in the EBoot display menu, save and reset the device.
  3. Deploy Telefunken_FuBK_test_pattern_800x600.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_800x600.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-2573R SANTARO x2 10.4” BX V1.1 (SN: 01340114)

Status

OK

Comment

Tested with revision r245.

Simple display test for the LG LB070WV8 (#16214)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Boot to EBoot.
  2. Select the LVDS0 LG LB070WV8 800x480 in the EBoot display menu, save and reset the device.
  3. Deploy Telefunken_FuBK_test_pattern_800x480_04.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_800x480_04.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-3125R SANTARO x2 7.0 SG IPS V1.2 (SN: 01680449)

Status

OK

Simple display test for the AUO G190EG01 (#16213)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Boot to EBoot.
  2. Select the DLVDS AUO G190EG01 1280x1024 in the EBoot display menu, save and reset the device.
  3. Deploy Telefunken_FuBK_test_pattern_1280x1024_01.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_1280x1024_01.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2 (SN: 01724586)

Status

OK

Simple display test for the Ampire AM-800480R3 (#16212)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Boot to EBoot.
  2. Select the LVDS0 Ampire 800x480 in the EBoot display menu, save and reset the device.
  3. Deploy Telefunken_FuBK_test_pattern_800x480_04.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_800x480_04.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-3128R SANTARO x2 7.0” BX (SN: 01746397)

Status

OK

Simple display test for the NL8060BC21-11C (#16210)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Boot to EBoot.
  2. Select the LVDS0 NL8060BC21-11C 800x600 in the EBoot display menu, save and reset the device.
  3. Deploy Telefunken_FuBK_test_pattern_800x600.png to the device i.e. via FTP to the root folder.
  4. Deploy ShowPic.exe to the device i.e. via FTP to the root folder.
  5. Execute via TELNET:
    ShowPic.exe Telefunken_FuBK_test_pattern_800x600.png
    

Verification:

  1. The test should show a classic test screen.
  2. The circle should not be an oval and should be in the center of the screen.
  3. The grid in the background should show squares and not rectangles.
  4. The image should look like this:
Device

900-2894R SANTARO x2 8.4” OF NL11C (SN: 01689105)

Status

OK

Comment

Tested with revision r245.

CE7 6.0r183(05.04.2016)

Fixed Error(s)

  • Added special LDB clock change handling. (#13838)

Added Feature(s)

  • Added support for the 7.” LG LB070WV8 Display. (#12683)

Tests [Sum: 4, OK: 4]
Perform Test

Test Environment:

  • Load the display configuration file for the correct display.
  • Booting up the test device.
Change backlight with the Windows display application (#13483)
Tested by Clemens Terasa on 23.03.2016

Test:

  1. Using a USB-Mouse or the touchscreen navigate to:
    MyDevice -> ControlPanel -> Display -> Backlight -> Advanced
    
  2. Move the AC slider down and up again.

Verification:

The brightness gets lower and high again.

Device
  1. 900-3125R: SANTARO x2 7.0 SG IPS, S/N: 01680449
Status

OK

Display Resolution (#13486)
Tested by Clemens Terasa on 23.03.2016

Test:

  1. Start the TestResolution tool for testing purposes.
  2. Look at the screen:

Verification:

  1. A label displaying the correct resolution is visible.
  2. The edges should show a blue and a red rectangle.
  3. The outer rectangle is the red one.
  4. Some edges might appear purple. This is due to the narrow red and blue pixels. It is OK.
  5. You should not see a green rectangle. It is normally rendered out of bounds.
  6. The app closes after 5 seconds.
Device
  1. 900-3125R: SANTARO x2 7.0 SG IPS, S/N: 01680449
Status

OK

24bit RGB color support (#13489)
Tested by Clemens Terasa on 23.03.2016

Test:

  1. Configure the RGB_24bits_palette_color_test_chart.png as background image.
    1. Copy the RGB_24bits_palette_color_test_chart.png to the device by FTP or by USB-Stick.
    2. In the My Device -> Control Panel -> Display select the RGB_24bits_palette_color_test_chart.png as background.
  2. Close all windows and look at the Desktop background.

Verification:

  1. There should be banding visible in the color gradients.
  2. All colors should have the same banding levels as all colors have the same bit-depth.
  3. The image should look like this:
  4. It should not look like the following: (Note the banding.)
Device

900-3125R SANTARO 7.0” SG IPS (SN: 01680449)

Status

OK

Measure display power sequence (#13490)
Tested by Clemens Terasa on 23.03.2016

The display power sequence needs to be verified when changes are done to the relevant parts of the code.

1. Environment

The measurement needs to be done with an oscilloscope directly on the decoded signals on the display.
The 7.0” display tested is the LG LB070WV8 (090-0311R).

1.1. Setup

Connect the display to the device to test.
Connect the oscilloscope channel to:

  • the backlight enable or PWM line
  • the pixel clock
  • the display enable line

The probes are connected directly with the connectors.

Setup the oscilloscope to trigger on the display enable, falling edge, at about 10% off the screen.
Setup the horizontal resolution to 500ms/div, voltage scale should be set to 2V/Div ( 1V/DIV will also work).
The Trigger should be set to normal.

Load the appropriate display configuration: rbdisp-lg-wvga-lb070WV8-003.xml.
The contained power sequence is:

<power_sequence
    PowerOnToSignalOn="50"
    PowerOnToBacklightOn="250"
    BacklightOffBeforePowerOff="200"
    SignalOffBeforePowerOff="0"
    PowerOffToPowerOn="500" />

2. Execution

2.1. Reboot Test

  • Start the oscilloscope measurement and power up the device.
  • Wait for the oscilloscope to finish the measurement.
  • Save the result image and attach to this ticket.

See the following image for an example result:

Purple: the backlight enable
Yellow: the pixel clock
Green: the display enable line

2.1.1 Evaluate the result

Nr. Name Description Expected result
1. PowerOnToSignalOn Rising edge of display enable to first clock cycle of display clock >50ms,
2. PowerOnToBacklightOn Rising edge of display enable to rising edge of backlight on >250ms,
Device

900-3125R SANTARO 7.0” SG (SN: 01680449)

Status

OK

CE7 5.0r138(26.02.2016)

Fixed Error(s)

  • Fixed Display power switching error. (#12287)

Added Feature(s)

  • Added display power sequence. (#12809)

  • Added support for the Ampire AM800600K2TMQW display. (#12719)

  • Added the disp.exe tool to rotate the display. (#12578)

Tests [Sum: 5, OK: 5]
Perform Test

Test Environment:

  • Select the correct Display setting in the EBoot bootloader.
    [G] Display mode -> [2] LVDS0 -> [3] LVDS0 AM-800600K2TMQW 800x600 -> [X] Return to Display menu ->  [X] Return to Main menu ->  [S] Save settings
    
  • Booting into the OS.
Display Resolution (#12725)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Start the TestResolution tool for testing purposes.
  2. Look at the screen:

Verification:

  1. A label displaying the correct resolution is visible.
  2. The edges should show a blue and a red rectangle.
  3. The outer rectangle is the red one.
  4. Some edges might appear purple. This is due to the narrow red and blue pixels. It is OK.
  5. You should not see a green rectangle. It is normally rendered out of bounds.
  6. The app closes after 5 seconds.
Device

900-3127R SANTARO 10.4” OF (SN: 01689129)

Status

OK

Change backlight with the Windows display application (#12722)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Using a USB-Mouse or the touchscreen navigate to:
    MyDevice -> ControlPanel -> Display -> Backlight -> Advanced
    
  2. Move the AC slider down and up again.

Verification:

The brightness gets lower and high again.

Device

900-3127R SANTARO 10.4” OF (SN: 01689129)

Status

OK

18bit RGB color support (#12724)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Configure the RGB_24bits_palette_color_test_chart.png as background image.
    1. Copy the RGB_24bits_palette_color_test_chart.png to the device by FTP or by USB-Stick.
    2. In the My Device -> Control Panel -> Display select the RGB_24bits_palette_color_test_chart.png as background.
  2. Close all windows and look at the Desktop background.

Verification:

  1. There should be banding visible in the color gradients.
  2. All colors should have the same banding levels as all colors have the same bit-depth.
  3. The image should look like this:
Device

900-3127R SANTARO 10.4” OF (SN: 01689129)

Status

OK

Backlight enabled after boot (#12721)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Boot the device with the correct setting selected in the eBoot bootloader display pane.
  2. Look at the display.

Verification:

If you see the Windows Desktop or the calibration screen clearly the backlight is activated.
This is the correct behavior.

Device

900-3127R SANTARO 10.4” OF (SN: 01689129)

Status

OK

Measure Display power sequence (#12727)
Tested by Clemens Terasa on 29.02.2016

The display power sequence needs to be verified when changes are done to the relevant parts of the code.

1. Environment

The measurement needs to be done with an oscilloscope directly on the decoded signals on the display.
The 10.4” display tested is the AM800600K2TMQW (090-0462R).

1.1. Setup

Connect the display to the device to test.
Connect the oscilloscope channel to:

  • the backlight enable or PWM line
  • the pixel clock
  • the display enable line

The probes are connected directly with the connectors.

Setup the oscilloscope to trigger on the display enable, falling edge, at about 10% off the screen.
Setup the horizontal resolution to 500ms/div, voltage scale should be set to 2V/Div ( 1V/DIV will also work).
The Trigger should be set to normal.

Load the appropriate display configuration: rbdisp-ampire-svga-am800600K2TMQW.xml.
The contained power sequence is:

<power_sequence
 PowerOnToSignalOn="20"
 PowerOnToBacklightOn="220"
 BacklightOffBeforePowerOff="220"
 SignalOffBeforePowerOff="20"
 PowerOffToPowerOn="500" />

2. Execution

2.1. Reboot Test

  • Start the oscilloscope measurement and power up the device.
  • Wait for the oscilloscope to finish the measurement.
  • Save the result image and attach to this ticket.

See the following image for an example result:

Purple: the backlight enable
Yellow: the pixel clock
Green: the display enable line

2.1.1 Evaluate the result

Nr. Name Description Expected result
1. PowerOnToSignalOn Rising edge of display enable to first clock cycle of display clock >20ms,
2. PowerOnToBacklightOn Rising edge of display enable to rising edge of backlight on >220ms,
Device

900-3127R SANTARO 10.4” OF (SN: 01689129)

Status

OK

CE7 3.0r89(01.02.2016)

Added Feature(s)

  • Added support for the 8.4” NLT NL8060BC21-11C Display. (#12425)

CE7 1.0(18.12.2015)

Added Feature(s)

  • Added Ampire AM800480R3TMQW-TACH Display support. (#11963)

Ethernet

Features

  • FEC (Fast Ethernet Controller) with 100 Mbps

Known Restrictions

  • Ethernet disconnect is not recognized properly (#16246)

  • Exception with from TCPIP when DHCP is disabled and connected to the DHCP network (#19063)Solved in ‘CE2013 4.0r404’

  • GuruCE-r954 integration: Ethernet won’t initialize correctly (#14040)Solved in ‘CE2013 1.0r226’

CE7 9.0r387(07.09.2016)

Fixed Error(s)

  • Fixed TCPIP Exception error by updating Windows CE7 to Update 60 (June 2016). (#20054)

Tests [Sum: 3, OK: 3]

Ethernet tests

100Mbit Full Duplex (#20089)
Tested by Clemens Terasa on 13.09.2016

Use a managed switch to test 100MBit.

  1. Connect the Ethernet port of the SANTARO directly to a PC supporting 100Mbit/s
  2. Configure the device in eboot to the Network supplied by your PC.
  3. Check the Network properties in the control panel app.
  4. In this test the PC has the IP 192.168.1.100 and is also the gateway
  5. The SANTARO is configured to the IP 192.168.1.1.

Use Ping to test the validity of the Ethernet connection:

ping 192.168.1.100

The test succeeds if a network device is found and the ping test has no losses.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Test the IPv4 stack (#20090)
Tested by Clemens Terasa on 13.09.2016

The ordinary way is to use the IPv4 network stack.

  1. Connect to a IPv4 network or development PC directly
  2. Configure a static IP and test the network using iptest and ping
  3. Assuming Development PC has the IP address 192.168.1.100
  4. Assuming the SANTARO device configured to 192.168.1.1 in Eboot using the Gateway of the PC
  5. Use the common Subnet mask of 255.255.255.0
  6. The development PC needs an enabled ECHO server.

Test procedure

  1. Connect to the device using TELNET or use the command prompt.
  2. Execute the following on the device:
     iptest  -l 5000 -n 50000 -f 64 -c 4 192.168.1.100
    

The test fails if the error rate is above 1%.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Comment

Measured a speed of about 10565 KBytes/s.

Test hot-plugging and measure DHCP get-lease-time (#20091)
Tested by Clemens Terasa on 13.09.2016

Preliminaries

  1. Connect the SANTARO to a network with a running DHCP server.
  2. Configure your device to use DHCP. Before Release 8.0 this had to be done in EBOOT. Since Release 8.0 set this in Windows via the GUI or via the commands:
    toolbox reg  set HKLM\Comm\ENET1\Parms\Tcpip EnableDHCP d 1
    savereg -n
    ndisconfig adapter rebind ENET1
    

Test procedure

  1. Disconnect the Ethernet cable before booting the device
  2. Boot up the device.
  3. Open the Ethernet Systray app.
  4. Connect the Ethernet interface with an DHCP network
  5. Measure the time of the IP change in the application (with a stop watch).
  6. Disconnect the Ethernet
  7. Measure the time of the windows systray change.

Test conditions

The test fails if no DHCP connection could be established or if the get lease time is above 30 seconds.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

CE7 8.0r275(04.07.2016)

Tests [Sum: 3, OK: 3]

Ethernet tests

100Mbit Full Duplex (#17496)
Tested by Clemens Terasa on 04.07.2016

Use a managed switch to test 100MBit.

  1. Connect the Ethernet port of the SANTARO directly to a PC supporting 100Mbit/s
  2. Configure the device in eboot to the Network supplied by your PC.
  3. Check the Network properties in the control panel app.
  4. In this test the PC has the IP 192.168.1.100 and is also the gateway
  5. The SANTARO is configured to the IP 192.168.1.1.

Use Ping to test the validity of the Ethernet connection:

ping 192.168.1.100

The test succeeds if a network device is found and the ping test has no losses.

Device

900-3230R: SANTARO x2 19.0 SG, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Test the IPv4 stack (#17497)
Tested by Clemens Terasa on 04.07.2016

The ordinary way is to use the IPv4 network stack.

  1. Connect to a IPv4 network or development PC directly
  2. Configure a static IP and test the network using iptest and ping
  3. Assuming Development PC has the IP address 192.168.1.100
  4. Assuming the SANTARO device configured to 192.168.1.1 using the Gateway of the PC
  5. Use the common Subnet mask of 255.255.255.0
  6. The development PC needs an enabled ECHO server.

Test procedure

  1. Connect to the device using TELNET or use the command prompt.
  2. Execute the following on the device:
     iptest  -l 5000 -n 50000 -f 64 -c 4 192.168.1.100
    

The test fails if the error rate is above 1%.

Device

900-3230R: SANTARO x2 19.0 SG, SN: 01724586

Status

OK

Comment

Tested with revision r275.

Test hot-plugging and measure DHCP get-lease-time (#17498)
Tested by Clemens Terasa on 04.07.2016

Preliminaries

  1. Connect the SANTARO to a network with a running DHCP server.
  2. Configure your device to use DHCP. Before Release 8.0 this had to be done in EBOOT. Since Release 8.0 set this in Windows via the GUI or via the commands:
    toolbox reg  set HKLM\Comm\ENET1\Parms\Tcpip EnableDHCP d 1
    savereg -n
    ndisconfig adapter rebind ENET1
    

Test procedure

  1. Disconnect the Ethernet cable before booting the device
  2. Boot up the device.
  3. Open the Ethernet Systray app.
  4. Connect the Ethernet interface with an DHCP network
  5. Measure the time of the IP change in the application (with a stop watch).
  6. Disconnect the Ethernet
  7. Measure the time of the windows systray change.

Test conditions

The test fails if no DHCP connection could be established or if the get lease time is above 30 seconds.

Device

900-3230R: SANTARO x2 19.0 SG, SN: 01724586

Status

OK

Comment

Tested with revision r275.

CE7 7.0r246(01.06.2016)

Tests [Sum: 3, Failed: 1, OK: 2]

Ethernet tests

Test hot-plugging and measure DHCP get-lease-time (#16121)
Tested by Clemens Terasa on 30.05.2016

Preliminaries

  1. Connect the SANTARO to a network with a running DHCP server.
  2. Configure your device to use DHCP in EBOOT, and set a valid MAC address.

Test procedure

  1. Disconnect the Ethernet cable before booting the device
  2. Boot up the device.
  3. Open the Ethernet Systray app.
  4. Connect the Ethernet interface with an DHCP network
  5. Measure the time of the IP change in the application (with a stop watch).
  6. Disconnect the Ethernet
  7. Measure the time of the windows systray change.

Test conditions

The test fails if no DHCP connection could be established or if the get lease time is above 30 seconds.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

Failed

Causing issue(s)
  1. Ethernet disconnect is not recognized properly (#16246)
Comment

The disconnect event is not recognized. As a workaround use the renew button in the TCP/IP app.

Test the IPv4 stack (#16120)
Tested by Clemens Terasa on 30.05.2016

The ordinary way is to use the IPv4 network stack.

  1. Connect to a IPv4 network or development PC directly
  2. Configure a static IP and test the network using iptest and ping
  3. Assuming Development PC has teh IP address 192.168.1.100
  4. Assuming the SANTARO device configured to 192.168.1.1 in Eboot using the Gateway of the PC
  5. Use the common Subnet mask of 255.255.255.0
  6. The developemnt PC needs an enabled ECHO server.

Test procedure

  1. Connect to the device using TELNET or use the command prompt.
  2. Execute the following on the device:
     iptest  -l 2048 -n 50000 -f 64 -c 4 192.168.1.100
    

The test fails if the error rate is above 1%.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Measured a speed of about 7400 KBytes/s.

100Mbit Full Duplex (#16119)
Tested by Clemens Terasa on 30.05.2016

Use a managed switch to test 100MBit.

  1. Connect the Ethernet port of the SANTARO directly to a PC supporting 100Mbit/s
  2. Configure the device in eboot to the Network supplied by your PC.
  3. Check the Network properties in the control panel app.
  4. In this test the PC has the IP 192.168.1.100 and is also the gateway
  5. The SANTARO is configured to the IP 192.168.1.1.

Use Ping to test the validity of the Ethernet connection:

ping 192.168.1.100

The test succeeds if a network device is found and the ping test has no losses.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added Ethernet PHY reset at boot time. (#11978)

CE7 4.0r107(05.02.2016)

Tests [Sum: 3, OK: 3]

Ethernet tests

100Mbit Full Duplex (#12061)
Tested by Clemens Terasa on 05.02.2016

Use a managed switch to test 100MBit.

  1. Connect the Ethernet port of the SANTARO directly to a PC supporting 100Mbit/s
  2. Configure the device in eboot to the Network supplied by your PC.
  3. Check the Network properties in the control panel app.
  4. In this test the PC has the IP 192.168.1.100 and is also the gateway
  5. The SANTARO is configured to the IP 192.168.1.1.

Use Ping to test the validity of the Ethernet connection:

ping 192.168.1.100

The test succeeds if a network device is found and the ping test has no losses.

Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Test hot-plugging and measure DHCP get-lease-time (#12066)
Tested by Clemens Terasa on 05.02.2016

Preliminaries

  1. Connect the SANTARO to a network with a running DHCP server.
  2. Configure your device to use DHCP in EBOOT, and set a valid MAC address.

Test procedure

  1. Disconnect the Ethernet cable before booting the device
  2. Boot up the device.
  3. Open the Ethernet Systray app.
  4. Connect the Ethernet interface with an DHCP network
  5. Measure the time of the IP change if the app.
  6. Disconnect the Ethernet
  7. Measure the time of the windows systray change.

Test conditions

The test fails if no DHCP connection could be established or if the get lease time is above 30 seconds.

Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Test the IPv4 stack (#12062)
Tested by Clemens Terasa on 05.02.2016

The ordinary way is to use the IPv4 network stack.

  1. Connect to a IPv4 network or development PC directly
  2. Configure a static IP and test the network using iptest and ping
  3. Assuming Development PC has teh IP address 192.168.1.100
  4. Assuming the SANTARO device configured to 192.168.1.1 in Eboot using the Gateway of the PC
  5. Use the common Subnet mask of 255.255.255.0
  6. The developemnt PC needs an enabled ECHO server.

Test procedure

  1. Connect to the device using TELNET or use the command prompt.
  2. Execute the following on the device:
     iptest  -l 5000 -n 50000 -f 64 -c 4 192.168.1.100
    

The test fails if the error rate is above 1%.

Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Comment

Measured a sped of about 7900 KBytes/s.

CE7 3.0r89(01.02.2016)

Tests [Sum: 3, OK: 3]

Ethernet tests

Network Initialization test (#12058)
Tested by Bernd Mierzowski on 01.02.2016

Thsi test is designed to test the network initialization:
It is intedned for testing:

  1. PHY initialization
  2. Network stack initialization

TODO: define specific tests and measurements

Device
  1. 900-3128R: SANTARO x2 7.0 BX SN 01746459
Status

OK

Verify the MAC address configured in the Bootloader (#12065)
Tested by Bernd Mierzowski on 01.02.2016

The Windows CE OS should use the MAC configured in the Bootloader.

  1. Configure a MAC address in the bootloader.
  2. Boot into OS
  3. Review the mach address using the network details.
  4. Reboot into the bootloader
  5. Configure another MAC address in the bootloader.
  6. Boot into OS
  7. Review the mach address using the network details.
Device
  1. 900-3128R: SANTARO x2 7.0 BX SN 01746459
Status

OK

Verify UDP broadcast packages (#12440)
Tested by Bernd Mierzowski on 01.02.2016

WE need to verify that broadcast packages sent via UDP protokol are leaving the device and will be available in the network.
On that purpose a small test application should send UDP broadcast packages and the network traffic should be checked e.g. with wireshark.

Test process:

  • Connect the device with a test PC with an ethernet cable. Ensure that both are in the same network.
  • Start WireShark on your PC, adapt the filter settings if desired and start capturing.
  • Send an UDP local-broadcast message from the device.
  • Check whether an UDP Package will be retrieved by your PC.
Test application code snippet
UdpClient client = new UdpClient();
IPEndPoint ip = new IPEndPoint(IPAddress.Parse("192.168.1.255"), 15000);
byte[] bytes = Encoding.ASCII.GetBytes("Foo");
client.Send(bytes, bytes.Length, ip);
client.Close();
Console.WriteLine("SendUDP end");
Device
  1. 900-3128R: SANTARO x2 7.0 BX SN 01746459
Status

OK

CE7 1.0(18.12.2015)

Added Feature(s)

  • Added SMSC LAN8720A Ethernet Phy support. (#12153)

FTDI

Features

  • USB to Serial port converter on COM6

Known Restrictions

  • An FTDI device is not always detected correctly on hot-plug (#17574)

CE7 8.0r275(04.07.2016)

Tests [Sum: 1, OK: 1]

Test Environment:

  • Connect a serial cross-link cable from the device to the USB serial dongle.

Used Tools:

  • USB serial dongle with FTDI chipset.
Simple serial test (#17494)
Tested by Clemens Terasa on 04.07.2016

Task

  1. Using the RS485Test tool send and receive signals.
  2. One can use the same executable on a Windows PC and on the device.
  3. An USB-FTDI serial converter connected to the USB port.
  4. Suppose we use COM1 as COM port connected to the COM6 port on the device.
  5. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Start the PC in client mode (waiting for messages)

  1. On the PC execute
    RS485Test_2.1.1406.exe -p COM1 -c
    
  2. On the SANTARO execute
    RS485Test_2.1.1406.exe -p COM6 -s
    

Test conditions

  1. If the the test output says “OK” this tests succeeds.
Device
  • 900-3125R: SANTARO x2 7.0 SG, S/N: 01680449
Status

OK

Comment

Tested with revision r275.

GPU

Features

  • OpenGL ES 2
  • OpenVG
  • OpenCL

Known Restrictions

  • No restrictions known.

CE7 5.0r138(26.02.2016)

Tests [Sum: 0]

The iMX6 has modules for different types of hardware accelerated graphics.

The Quad and Dual variants have the VIVANTE modules

  • GC2000 for 3D acceleration (OpenGL-ES 1.1, 2.0 & 3.0)
  • GC355 for vector graphics (OpenVG 1.1)
  • GC320 for 2D acceleration

The Solo and Dual-Lite variants use teh VIVANTE modules

  • GC880 for 3D (OpenGL-ES 1.1, 2.0 & 3.0)
  • GC320 for 2D

The GuruCE BSP contains several test programs.

  • No specific test cases executed in this version.

MDB

Features

  • Serial port with MDB (Multi Drop Bus) transceiver on COM2
  • Only available on special hardware assembly option
  • Device acts as MDB master
  • A programming interface MDBApi.dll for accessing MDB clients

Known Restrictions

  • No restrictions known.

CE7 7.0r246(01.06.2016)

Added Feature(s)

  • Added MDB-Master support including the MDB-Karl-test. (#16061)

Tests [Sum: 2, OK: 2]

Test Environment:

  1. Garz & Fricke Karl2 device connected to the SANTARO second serial port and supplied with 20V with a common ground with the SANTARO.
  2. Set the Registry Settings for COM2 via telnet and reboot:
    toolbox reg set HKLM\drivers\builtin\COM2 Support9bitMode d 1
    toolbox reg set HKLM\drivers\builtin\COM2 UseDMA d 0
    savreg -n
    reset
    

Used Tools:

  • MDB-Karl-Test
Check the maximum MDB ACK response time (#16124)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Measure the MDB TX und RX lines with an oscilloscope.
  2. Connect the Karl 2 with the SANTAROs second UART port.
  3. Set the vertical scale to 2V/div and the horizontal 5ms/div.
  4. Set the trigger to single trigger on a falling edge of the RX signal.
  5. Start the measurement
  6. Execute on the device (i.e. via TELNET)
    MDB-KarL-Test.exe
    

Verification:

  • The ACK response time must be less than 5ms.

Optional:

  • Attach a scope image.
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2 (SN: 01724586)

Status

OK

Comment

The response time is less than 1ms.

Test a simple transaction (#16123)
Tested by Clemens Terasa on 30.05.2016

Test:

Test a simple transaction using a Karl2:

  1. Powerup the device
  2. Configure the COM2 as MDB port using the 9-Bit mode and disabling the DMA.
  3. Execute (i.e via Telnet)
    MDB-Karl-Test
    

Verification:

  1. The Karl2 should flash with the green and res LED several times.
  2. The output should look like
    Opening COM2: for MDB
    Setting MDB configuration
    Old MDB settings: character timeout: 5, reset time: 100
    New MDB settings: character timeout: 200, reset time: 4000
    Asserting wakeup line
    Resetting the MDB bus
    Sending reset command to client
    Received ACK from client
    Sending poll command to client
    Received 1 bytes from client: 0x00
    Sending config command to client
    Received 8 bytes from client: 0x01 0x83 0x00 0x49 0x01 0x02 0x25 0x01
    Received 34 bytes from client: 0x09 0x47 0x55 0x46 0x39 0x30 0x30 0x30 0x30 0x30
     0x30 0x30 0x30 0x30 0x30 0x31 0x4b 0x61 0x72 0x4c 0x20 0x30 0x32 0x2e 0x32 0x31
     0x20 0x20 0x02 0x03 0xc0 0x00 0x00 0x06
    
Device

900-3230R SANTARO x2 19.0 SG MDB V1.2 (SN: 01724586)

Status

OK

Comment

Tested with revision r245.

Matrix Keyboard

Features

  • Keypad connector with GPIOs
  • Matrix keyboard capable keypad driver.

Known Restrictions

  • No restrictions known.

CE7 7.0r246(01.06.2016)

Tests [Sum: 2, OK: 2]

Test Environment:

  • Matrix keyboard connected to the keypad connector.

Used Tools:

  • InputTest (http://support.garz-fricke.com/projects/TestFiles/WinCE/InputTest.exe)
Test the matrix keyboard configuration (#16179)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Connect the matrix keypad to the keypad connector.
  2. Copy a customized MatrixKey.cfg configuration file to the FlashDisk partition on the device.
  3. Set the config file path in the registry using:
    toolbox reg set HKLM\HARDWARE\devicemap\keybd ConfigFile s "\FlashDisk\MatrixKey.cfg"
    
  4. Reboot the device.
  5. Deploy InputTest to the device (i.e. via FTP)
  6. Execute (i.e. via Telnet):
    InputTest
    
  7. Press the all keys on the keypad.

Verification:

The test succeeds if all keys are recognized correctly and the characters are written to the input panel.

Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK

Comment

Tested with revision r245.

Matrix keyboard (#16178)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Connect the Matrix keyboad with the device.
  2. Deploy the InputTest executable to the device.
  3. Execute (i.e. via Telnet):
    InputTest
    
  4. Press some keys on the matrix keyboard.

Verification:

  1. The Input field should show characters. Note: These may be different from the actual keypad, but can be configured using the MatrixKey.cfg on the device. The Path to the file my be altered by the following Registry key HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD\ ConfigFile
Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK

Comment

Tested with revision r245.

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added matrix keyboard support. (#12576)

Tests [Sum: 1, OK: 1]

Das Matrix Keypad wird über die DigitalIO API angesprochen.
Es benötigt zusätzlich support im OS.

Test the keypad driver (#12735)
Tested by Clemens Terasa on 25.02.2016

Test:

  1. Connect the matrix keypad to the keypad connector.
  2. Copy a customized MatrixKey.cfg configuration file to the FlashDisk partition on the device.
  3. Set the config file path in the registry using:
    toolbox reg set HKLM\HARDWARE\devicemap\keybd ConfigFile s "\FlashDisk\MatrixKey.cfg"
    
  4. Reboot the device.
  5. Open the “Run…” dialog from the start menu.
  6. Press the all keys on the keypad.

Verification:

The test succeeds if all keys are recognized correctly and the characters are written to the dialog input panel.

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

OpenCL

Features

  • Support for OpenCL 1.1

Known Restrictions

  • No restrictions known.

CE7 5.0r138(26.02.2016)

Tests [Sum: 1, OK: 1]
Perform Test

Used Tools:

  • Open CL test tools supplied with a image.
Test OpenCL (#12038)
Tested by Clemens Terasa on 26.02.2016

OPEN-CL

NOTE: OpenCL is not supported on the iMX6 Solo and Dual-Lite.

  1. Show OpenCL info:
    cl_info
    

    No command line options.
  2. FFT calculation:
    cl_fft 65536
    

    Specify command line option “fft_length” >= 16 and
  3. Threadwalker: cl_threadwalker
    cl_threadwalker 0
    cl_threadwalker 1
    cl_threadwalker 2
    cl_threadwalker 3
    cl_threadwalker 4
    cl_threadwalker 5
    

    Specify command line option “test_case” >= 0 and

Verification

  1. The test succeeds if all test cases run successfully without any hangs or errors.
Device

900-3128R Santaro x2 7.0 BX (SN: 01746397)

Status

OK

OpenGL ES

Features

  • Support for OpenGL ES 1.0
  • Support for OpenGL ES 2.0

Known Restrictions

  • The OpenGL XAML renderer does not work correctly (#13105)

  • The OpenGL XAML renderer is not working (#15862)

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added the OpenGL based XAML renderer. (#13103)

Tests [Sum: 1, OK: 1]
Perform Test

Test Environment:

  • Device with a screen

Used Tools:

  • OpenGL programs supplied with the image
Test OpenGL features (#12036)
Tested by Clemens Terasa on 26.02.2016

OPENGL-ES 1.1

  • Rotating Three Color Triangle: es11_tut1
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut1 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Rotating Six Color Cube: es11_tut2
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut2 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Rotating Multi-Textured Cube: es11_tut3
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut3 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Lighting and Fog: es11_tut4
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut4 -w 800 -h 480 -f 1000
    

    Press SPACE to pause, ENTER to add green fog and ESC to exit.
  • Blending and Bit-mapped Fonts: es11_tut5
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut5 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Particles Using Point Sprites: es11_tut6
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut6 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Vertex Buffer Objects: es11_tut7
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es11_tut7 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.

OPENGL-ES 2.0

  • Rotating Three Color Triangle: es20_tut1
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es20_tut1 -w 800 -h 480 -f 1000
    

    Press SPACE to pause, ENTER to change between ORTHO and PERSPECTIVE projection and ESC to exit.
  • Rotating Six Color Cube: es20_tut2
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es20_tut2 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Rotating Reflecting Ball: es20_tut3
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es20_tut3 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.
  • Rotating Refracting Ball: es20_tut4
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    es20_tut4 -w 800 -h 480 -f 1000
    

    Press SPACE to pause and ESC to exit.

Verification

  1. All test should run and show a window.
  2. All tests should have a frame rate of above 100 fps.
Device

900-3128R Santaro x2 7.0 BX (SN: 01746397)

Status

OK

OpenVG

Features

  • Support for OpenVG 1.1

Known Restrictions

  • No restrictions known.

CE7 5.0r138(26.02.2016)

Tests [Sum: 1, OK: 1]
Perform Test

Test Environment:

  • Device with a screen

Used Tools:

  • OpenVG tools supplied with the image
Test OpenVG features (#12037)
Tested by Clemens Terasa on 26.02.2016

OPEN-VG

  1. Spinning & Scaling Tiger: vg_tiger
    Without command line options this runs in a window. To run full-screen specify the screen resolution
    as follows:
    vg_tiger –w 800 –h 480
    

    Press ESC to exit.

Validation

  1. Scaling and rotating tiger is visible on the screen.
Device

900-3128R Santaro x2 7.0 BX (SN: 01746397)

Status

OK

RS232

Features

  • Serial port with RS232 transceiver on COM1
  • RTC/CTS support
  • Configured as serial debug port per default (115200, 8N1)

Known Restrictions

  • Parity modes ‘mark’ and ‘space’ are not supported. No hardware support available. (#12648)

  • Parity modes ‘mark’ and ‘space’ are not supported. No hardware support available. (#15932)

CE7 6.0r183(05.04.2016)

Tests [Sum: 2, Failed: 1, OK: 1]

Verify RS232 features like:

  1. Flow control( RTS, CTS, hardware, Xon/Xoff)
  2. Data bit length (8bit)
  3. Parity
  4. stop bits
  5. measure speeds and inter symbol intervals.
Verify parity check "none", "even" and "odd" (#12649)
Tested by Clemens Terasa on 04.04.2016

Verify the parity checks

  1. Odd
  2. Even

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. Measure and attach scope pictures of Tx signal.
  3. One can use the same executable on a Windows PC and on the device.
  4. Suppose we use COM1 as COM port connected to the second COM port on the device.
  5. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. The only scope line Tx is set to set to 5.0V per div Set time div to 50us/div
  6. Set scope trigger to Tx line
  7. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Send a message with no parity bit (default)

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -pa None -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa None -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with odd parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -pa Odd -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Odd -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with even parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -pa Even -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Even -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with mark parity bit

Test conditions

Following conditions are necessary to pass the test

  1. For each test the output on the device shows “Ok” at the end of the message sending task. Similar to the following:
    \> RS485Test_2.1.1406.exe -p COM2 -db 8 -pa None -s -d 8
    Configuration:
    Mode:           RS485Test.Server
    ...
    Ok
    
Device

900-3125R SANTARO x2 7.0 SG (SN: 01680449)

Status

OK

Comment

The parity options “Mark” and “Space” threw exceptions on SANTARO.

Verify parity check "mark" and "space" (#12810)
Tested by Clemens Terasa on 04.04.2016

Verify the parity checks

  1. mark
  2. space

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. Measure and attach scope pictures of Tx signal.
  3. One can use the same executable on a Windows PC and on the device.
  4. Suppose we use COM1 as COM port connected to the second COM port on the device.
  5. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. The only scope line Tx is set to set to 5.0V per div Set time div to 50us/div
  6. Set scope trigger to Tx line
  7. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Send a message with mark parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -pa Mark -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Mark -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with space parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -pa Space -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Space -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Test conditions

Following conditions are necessary to pass the test

  1. For each test the output on the device shows “Ok” at the end of the message sending task. Similar to the following:
    \> RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Mark -s -d 8
    Configuration:
    Mode:           RS485Test.Server
    ...
    Ok
    
Device

900-3125R SANTARO x2 7.0 SG (SN: 01680449)

Status

Failed

Comment

The parity options “Mark” and “Space” threw exceptions on SANTARO.

CE7 4.0r107(05.02.2016)

Fixed Error(s)

  • Fixed muxing issue for RS232 RTS and CTS signals. (#12432)

Tests [Sum: 5, Failed: 1, OK: 4]

Verify RS232 features like:

  1. Flow control( RTS, CTS, hardware, Xon/Xoff)
  2. Data bit length (8bit)
  3. Parity
  4. stop bits
  5. measure speeds and inter symbol intervals.
Verify parity check (#12019)
Tested by Clemens Terasa on 05.02.2016

Verify the parity checks

  1. Odd
  2. Even
  3. mark
  4. space

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. Measure and attach scope pictures of Tx signal.
  3. One can use the same executable on a Windows PC and on the device.
  4. Suppose we use COM1 as COM port connected to the second COM port on the device.
  5. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. The only scope line Tx is set to set to 5.0V per div Set time div to 50us/div
  6. Set scope trigger to Tx line
  7. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Send a message with no parity bit (default)

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa None -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa None -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with odd parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Odd -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Odd -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with even parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Even -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Even -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with mark parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Mark -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Mark -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with space parity bit

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Space -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -pa Space -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Test conditions

Following conditions are necessary to pass the test

  1. For each test the output on the device shows “Ok” at the end of the message sending task. Similar to the following:
    \> RS485Test_2.1.1406.exe -p COM2 -db 8 -pa None -s -d 8
    Configuration:
    Mode:           RS485Test.Server
    ...
    Ok
    
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

Failed

Causing issue(s)
  1. Parity modes ‘mark’ and ‘space’ are not supported. No hardware support available. (#12648)
Comment

The parity options “Mark” and “Space” threw exceptions on SANTARO.

Verify Flow control (#12017)
Tested by Clemens Terasa on 05.02.2016

Verify the flow control features:

Connect a scope with all the RS232 of lines of the serial:

  1. TX
  2. RX
  3. RTS
  4. CTS

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. Measure and attach scope pictures of RTS signals compared to the messages
  3. Measure and attach scope pictures of CTS signals compared to the messages
  4. One can use the same executable on a Windows PC and on the device.
  5. Suppose we use COM1 as COM port connected to the second COM port on the device.
  6. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. All scope lines set to 10.V per div Set time div to 10ms/div
  7. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Start the PC in client mode (waiting for messages)

  1. Set scope trigger to CTS line
  2. On the PC execute:
    RS485Test_2.1.1406.exe -c  -p COM1 -rts
    
  3. Take scope snapshot

Send a message using the SANTARO

  1. Set scope trigger to RTS line
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -s  -p COM2 -rts -d 128
    
  3. Take scope snapshot

Send a killing message using the SANTARO

  1. Set scope trigger to RTS line
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -s  -p COM2 -rts -d 128 -k
    
  3. Take scope snapshot

Test conditions

Following conditions are necessary to pass the test

  1. The RTS line is set high during a send message.
  2. The RTS line is set low before and after sending a message
  3. The on the device shows “Ok” at the end of the message sending task. Similar to the following:
    \> RS485Test_2.1.1406.exe -s  -p COM2 -rts -d 128
    Configuration:
    Mode:           RS485Test.Server
    Baud Rate:      115200
    Serial Port:    COM2
    Bytes to send:  128
    Timeout in ms:  500
    Stop client:    False
    The value is 128
    204
    128
    0
    0
    0
    Sending ping message.
    Waiting 500 milliseconds for the pong message
    numberOfReceivedBytes: 128
    Ok
    
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Data bit length (#12018)
Tested by Clemens Terasa on 05.02.2016

RS232 has the option to send different data lengths.

  1. Test 7bit
  2. Test 8bit

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. One can use the same executable on a Windows PC and on the device.
  3. Suppose we use COM1 as COM port connected to the second COM port on the device.
  4. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. All scope lines set to 10.V per div Set time div to 50is/div
  5. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Start the PC in client mode (waiting for messages)

  1. On the SANTARO execute
    RS485Test_2.1.1406.exe -p COM2 -db 7 -s -d 8
    
  2. Take scope snap shot
  3. On the SANTARO execute
    RS485Test_2.1.1406.exe -p COM2 -db 8 -s -d 8
    
  4. Take scope snap shot

Test conditions

  1. Compare the snap shots:
    1. One symbol should be about 8.68 microseconds.
    2. So the difference between the one start bit and the other should be about 86.8 microseconds for 8 bit and 78.12 microseconds for 7 bit.
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Verify Stop-bits (#12020)
Tested by Clemens Terasa on 05.02.2016

Verify the usage of the stop bits and measure.

  1. 1 bit
  2. 2 bit

Task

  1. Using the RS485Test tool send and receive signals. See ce-tools:source:/trunk/TestStand/RS485Test
  2. Measure and attach scope pictures of Tx signal.
  3. One can use the same executable on a Windows PC and on the device.
  4. Suppose we use COM1 as COM port connected to the second COM port on the device.
  5. All scope connections are referring to the pinout of the SANTARO. Thus Tx is meant to be the transmission line of the SANTARO. The only scope line Tx is set to set to 5.0V per div Set time div to 50us/div
  6. Set scope trigger to Tx line
  7. Supposing the default settings of RS485Test tool:
    1. Baud Rate: 115200
    2. Timeout in ms: 500

Test procedure

Send a message with one stop bit (default)

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -sb One -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -sb One -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Send a message with 2 stop bits

  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM1 -db 8 -sb Two -c
    
  2. On the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM2 -db 8 -sb Two -s -d 8
    
  3. Take scope snapshot
  4. Kill the PC process

Test conditions

Following conditions are necessary to pass the test

  1. For each test the output on the device shows “Ok” at the end of the message sending task. Similar to the following:
    \> RS485Test_2.1.1406.exe -p COM2 -db 8 -sb One -s -d 8
    Configuration:
    Mode:           RS485Test.Server
    ...
    Ok
    
  2. The stop bits should be visible on the scope images.
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Measure baud rates (#12022)
Tested by Clemens Terasa on 05.02.2016

We want to support following baud rates:

  • 4800
  • 9600
  • 19200
  • 38400
  • 57600
  • 115200

Use the RS485Test to do this. It can be found in the CE-Tools.

Connect the RS232 with the device.

For each baud rate BAUDRATE do

  1. On the PC execute
    RS485Test -c -p %PCPORT% -b %BAUDRATE%"
    
  2. On the SANTARO execute
    RS485Test -s -p %SANTAROPORT% -b %BAUDRATE% -t 2000 -d 32
    
  3. On the SANTARO execute the following to kill the PC listener.
    RS485Test -s -p %SANTAROPORT% -b %BAUDRATE% -t 2000 -d 32 -k
    

Test conditions

  1. Each test have to output an “Ok” at the end of each message send in step 2 to pass the test. It should look similar to the following
    \> RS485Test -s -p COM2 -b 9600 -t 2000 -d 32
    Configuration:
    Mode:           RS485Test.Server
    Baud Rate:      9600
    Serial Port:    COM2
    Bytes to send:  32
    Timeout in ms:  2000
    Stop client:    False
    The value is 32
    204
    32
    0
    0
    0
    Sending ping message.
    Waiting 2000 milliseconds for the pong message
    numberOfReceivedBytes: 32
    Ok
    
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

Comment

Tested with Port COM2.

RS485

Features

  • Serial port with RS485 transceiver on COM4
  • Full-duplex support
  • Switchable to half-duplex via registry key HKLM/drivers/builtin/COM4/HalfDuplex
  • Optional galvanically isolation

Known Restrictions

  • No restrictions known.

CE7 6.0r183(05.04.2016)

Tests [Sum: 2, OK: 2]
Perform Test

Test Environment:

  1. Connect the serial port to a PC via an RS485/RS232-converter.
    1. Use a a 1-to-1 RS485 cable.
  2. Setup the Half-Duplex with termination Jumper as:
    1. 1: ON
    2. 2: OFF
    3. 3: OFF
    4. 4: ON
  3. Cable connected like:
    1. TRX+: RS485_A/RS485_Y
    2. TRX-: RS485_B/RS485_Z
  4. Use on the test device the COM4 interface with GuF test tool RS485Test.exe

Used Tools:

  • RS485/RS232 Converter
  • For Full-Duplex use a loopback cable.
RS422 (full-duplex) (#13849)
Tested by Clemens Terasa on 05.04.2016

Test:

  • Use a loopback RS485 cable.
  • Execute:
    RS485Test_2.1.1406.exe  -p COM4 -s
    

Verification:

  • The test succeeds if the output ends with Ok
Device

900-3125R SANTARO x2 7.0 sensoglass (SN:01680449)

Status

OK

RS485 (half-duplex) (#13848)
Tested by Clemens Terasa on 05.04.2016
Setup
  1. Using the RS485Test tool send and receive signals.
  2. One can use the same executable on a Windows PC and on the device.
  3. Suppose we use COM5 as COM port connected to the second COM port on the device.
  4. Using the SysBase CS-4289AT select
    1. SW1: On (RS485-2W)
    2. SW2: Off
    3. SW3: Off
    4. SW4: On (Terminal Reg-2W)
Test procedure
  1. On the PC execute:
    RS485Test_2.1.1406.exe -p COM5 -c
    
  2. On the SANTARO execute:
    toolbox reg set HKLM\drivers\builtin\COM4 HalfDuplex d 1
    reset
    
  3. After reset on the SANTARO execute:
    RS485Test_2.1.1406.exe -p COM4 -s
    
  4. Kill the PC process
Validation
  1. The test succeeds if the program outputs “OK”.
Device

900-3125R SANTARO x2 7.0 sensoglass (SN:01680449)

Status

OK

CE7 3.0r89(01.02.2016)

Added Feature(s)

  • Supporting RS485 Full Duplex Mode on COM4 (#12424)

RTC

Features

  • Battery-backed RTC PCF8563 on I2C1.
  • Accessible via the GFRTCSync tool.
  • The RTC uses UTC internally, while system time is in the timezone selected for the OS.

Known Restrictions

  • Clock output of the RTC drains the Battery (#15003)Solved in ‘CE2013 1.0r226’

CE7 7.0r246(01.06.2016)

Tests [Sum: 4, OK: 4]

Test Environment:

  • Test device with RTC battery equipped.
  • Access to the serial console of the test device.
  • Voltcraft VC840 Multimeter (as frequency meter)
  • The RTC tests are made with the time service disabled.
    services unregister TIMESVC
    savereg -n
    reset
    
Verify the the RTC time is used as system time (#16455)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Connect to the device using telnet.
  2. In telnet use following commands to show the date and time:
    \> date 02-06-2016
    \> time 09:00:00
    
  3. Reset the device
    reset
    
  4. Wait for a the OS to boot and execute:
    \> date /t
    \> time /t
    
  5. Validate a plausible date and time.

Verification:

The time has to be plausible compared to the set date 6th February 2016 at 9 AM.

Device

900-3230R SANTARO x2 19.0 SG MDB, SN: 01724586

Status

OK

Comment

Tested with revision r245.

Validate disable of Clkout to save battery life (#16454)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Connect the frequency meter to Pin 7 of IC28 and to the GND of the device(e.g. to the frame of the usb-port)
  2. Remove the battery
  3. Power up the device

Verification:

  1. The tests fails if the measured frequency is greater than 0 Hz after the boot procedure is finished (during the boot process there may be a measured frequency of 32 khz)
Device

900-3045R FBG SANTARO x2 V1.2 SN: 01679855

Status

OK

Check the RTC leap year behavior (#16461)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Set the correct date for a leap year:
    \> date 02-28-2020
    
  2. Set the correct time (shortly before the next day), e.g:
    \> time 23:59:50
    
  3. Power of the device
  4. Wait some time to ensure that the device should display the next day
  5. Power on the device

Verification:

If the device shows February 29 with a time fitting to the wait time.

Device

900-3230R SANTARO x2 19.0 SG MDB, SN: 01724586

Status

OK

Comment

Tested with revision r245.

Set the RTC time by setting the system time (#16453)
Tested by Clemens Terasa on 31.05.2016

Test:

  1. Setting the system time should also set the RTC.
  2. Connect to the device using telnet.
  3. In telnet use following commands to show the date and time:
    \> date /t
    Wednesday, February 03, 2016
    \> time /t
    12:01:09 PM
    
  4. Validate the RTC with the GFRTCsync tool on the device.
    \> GFRTCsync
    ...
    Current RTC time (UTC): 2016-02-03 11:01:15
    Current local time: 2016-02-03 12:01:15
    
  5. Set the date and time with the common date time tools.
    \> date 02-06-2016
    \> time 09:00:00
    
  6. Validate the RTC with the GFRTCsync tool on the device.
    \> GFRTCsync
    ...
    Current RTC time (UTC): 2016-02-06 08:00:05
    Current local time: 2016-02-06 09:00:05
    

Verification:

If the time in Windows is shown correctly as set.
This also means that the time is shown correctly in the Windows CE Systray.

Device

900-3230R SANTARO x2 19.0 SG MDB, SN: 01724586

Status

OK

Comment

Tested with revision r245.

CE7 4.0r107(05.02.2016)

Added Feature(s)

  • Added GFRTCSync tool to synchronize the system time with the external PCF8563 RTC. Will be startet with init. (#12561)

  • Added NTP support. (#12589)

  • Set time zone to Western European Time. (#12585)

SD-Card

Features

  • ESDHC Controller
  • Memory card accessible via block device /SD.

Known Restrictions

  • Problems booting while SD card is plugged in (#15398)Solved in ‘CE2013 1.0r226’

CE7 7.0r246(01.06.2016)

Tests [Sum: 5, OK: 5]

Test Environment:

  • SD Card with fresh formatted FAT32 partition plugged in.
  • Serial line connected.
  • Tools manually deployed using FTP.
  • Tools manually called using Telnet.

Used Tools from Windows Platform builder installation:

  • tux.exe
  • kato.dll
  • fsdtst.dll
  • tux.exe
  • Fsperflog.dll
  • ceperf.dll
  • perfscenario.dll
SD-Card: Automatic mounting on boot (#16656)
Tested by Clemens Terasa on 01.06.2016

Test:

  1. Shut down the device.
  2. Plug-in a formatted FAT32 partitioned SD-Card.
  3. Boot up the device.
  4. With telnet execute:
    dir \
    

Verification:

  1. You see a dir entry like
    12/12/12  02:00p    <DIR>                    SD
    
Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

SD-Card: Automatic mounting on hot-plug (#16657)
Tested by Clemens Terasa on 01.06.2016

Test:

  1. Remove the SD-Card from the SD-Slot if it’s plugged in.
  2. Boot up the device.
  3. Plug-in a formatted FAT32 partitioned SD-Card.
  4. With telnet execute:
    dir \
    

Verification:

  1. You see a dir entry like
    12/12/12  02:00p    <DIR>                    SD
    
Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

SD-Card write test (#16661)
Tested by Clemens Terasa on 01.06.2016

Test:

Use the testfs.exe tool to write some data to an inserted SD-Card.

Call the following to write 32 MB

testfs -n 32 -b 1048576 -wo "\SD\"

Verification:

The average speed should be greater than 2000000 bytes/s

Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

Comment

Output:

\> testfs -n 32 -b 1048576 -wo "\SD\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\SD\ :: Path: "\SD\" exists
\SD\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\SD\\ :: testfs0: *********************************
\SD\\ :: testfs0: *** Write statistics for "\SD\\"
\SD\\ :: testfs0: *** complete time: 14259 msec, throughput 2353210 bytes/sec
\SD\\ :: testfs0: *** min: 967321 bytes/sec (1084 msec)
\SD\\ :: testfs0: *** avg: 2919868 bytes/sec (434 msec)
\SD\\ :: testfs0: *** max: 4405781 bytes/sec (238 msec)
\SD\\ :: testfs0: *********************************
\SD\\ :: testfs0: reading 33554432 bytes...
\SD\\ :: testfs0: file \SD\\testfs0.tst deleted.
\SD\\ :: testfs0: performance test finished.
\SD\\ :: EXIT
SD-Card read test (#16662)
Tested by Clemens Terasa on 01.06.2016

Test:

Use the testfs.exe tool to write some data to an inserted SD-Card.

Call the following to read 32 MB

testfs -n 32 -b 1048576 -ro "\SD\"

Verification:

The average speed should be greater than 1000000 bytes/s

Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

Comment
\> testfs -n 32 -b 1048576 -ro "\SD\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\SD\ :: Path: "\SD\" exists
\SD\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\SD\\ :: testfs0: ReadFile not all bytes read: is 102400, should 1048576, left 33554432 , LastError=183
\SD\\ :: testfs0: *********************************
\SD\\ :: testfs0: *** Read statistics for "\SD\\"
\SD\\ :: testfs0: *** complete time: 36 msec, throughput 932067555 bytes/sec
\SD\\ :: testfs0: *** min: 40329846 bytes/sec (26 msec)
\SD\\ :: testfs0: *** avg: 1260306 bytes/sec (0 msec)
\SD\\ :: testfs0: *** max: 4294967295 bytes/sec (0 msec)
\SD\\ :: testfs0: *********************************
\SD\\ :: testfs0: file \SD\\testfs0.tst deleted.
\SD\\ :: testfs0: performance test finished.
\SD\\ :: EXIT
SD-Card: CTK File System tests (#16655)
Tested by Clemens Terasa on 01.06.2016

Test:

  1. Deploy the test files:
    1. tux.exe
    2. Kato.dll
    3. Fsdtst.dll
  2. Execute:
    tux -o -d fsdtst -c "-p SDMemory  -zorch" -f TestResult.txt
    
  3. Inspect the the last lines of the TestResult.txt file. It should look like :
    *** ==============================================================
    *** SUITE SUMMARY
    ***
    *** Passed:              41
    *** Failed:               0
    *** Skipped:              1
    *** Aborted:              0
    *** Informative:          0
    *** -------- ---------
    *** Total:               42
    ***
    *** Cumulative Test Execution Time: 0:07:44.491
    *** Total Tux Suite Execution Time: 0:07:52.099
    *** CPU Idle Time:                  0:04:47.928
    *** ==============================================================
    

Verification:

  • The test succeeds if not tests-cases of the CTK test suite failed.
  • There may be 1 test case that skipped besause the test case tests for non applicable FAT12/FAT16 features.
Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

Comment
PID:07CB005F TID:0742005E *** ==============================================================
PID:07CB005F TID:0742005E *** SUITE SUMMARY
PID:07CB005F TID:0742005E ***
PID:07CB005F TID:0742005E *** Passed:         41
PID:07CB005F TID:0742005E *** Failed:          0
PID:07CB005F TID:0742005E *** Skipped:         1
PID:07CB005F TID:0742005E *** Aborted:         0
PID:07CB005F TID:0742005E *** -------- ---------
PID:07CB005F TID:0742005E *** Total:          42
PID:07CB005F TID:0742005E ***
PID:07CB005F TID:0742005E *** Cumulative Test Execution Time: 0:40:24.122
PID:07CB005F TID:0742005E *** Total Tux Suite Execution Time: 0:40:31.782
PID:07CB005F TID:0742005E *** CPU Idle Time:                  0:30:44.102
PID:07CB005F TID:0742005E *** ==============================================================

Touch - resistive

Features

  • STMPE610 4-wire resistive touch controller

Known Restrictions

  • The resitive touch is not working when the device is rebooting from Flash-N-Go (#19683)

CE7 9.0r387(07.09.2016)

Tests [Sum: 2, OK: 2]

Test Environment:

  • Install the touch config via Flash-N-Go System.
  • The correct configuration should be found in http://support.garz-fricke.com/projects/Santaro/Configuration/
  • The tested configuration is rbtouch-stmpe-v00-r3496.xml
Touchscreen calibration (#20109)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-3128R: SANTARO x2 7.0 BX, S/N: 01746397

Status

OK

Test single touch with 'drawing' with 'CeTouchView' (#20110)
Tested by Clemens Terasa on 15.09.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-3128R: SANTARO x2 7.0 BX, S/N: 01746397

Status

OK

CE7 8.0r275(04.07.2016)

Tests [Sum: 2, OK: 2]

Test Environment:

  • Install the touch config via Flash-N-Go System.
Touchscreen calibration (#17489)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746397
Status

OK

Comment

Tested with revision r275.

Test single touch with 'drawing' with 'CeTouchView' (#17490)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746397
Status

OK

Comment

Tested with revision r275.

CE7 7.0r246(01.06.2016)

Tests [Sum: 2, OK: 2]

Test Environment:

  1. Install the touch config via Flash-N-Go System.
  2. Select “I2C” in the eboot menu.
Test single touch with 'drawing' with 'CeTouchView' (#16439)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Start CeTouchView.exe
  2. Enable ‘trace’ in the tool settings

Verification:

Write your name on the screen without any failures of the touch drawings.

Device

900-2894R: SANTARO x2 8.4 OF NL11C, S/N: 01689105

Status

OK

Comment

Tested with revision r245.

Touchscreen calibration (#16438)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Execute calibration executing touchc application on the device.
  2. On the touch GUI on the device screen, do calibration with a touch pen for capacitive touchscreens as precise as possible.
  3. Save the calibration via the shell command savereg -n.
  4. Run the touch test tool cetouchview and validate the touch functionality.
  5. Restart the device.
  6. Rerun the resistive touch test tool cetouchview and validate that the touch is behaving as before the restart (Step 4).

Verification:

In both cases, before and after the restart of the device, the touch test tool has to be executed without any errors.
The dots have to be under the pen tip at all times.

Device

900-2894R: SANTARO x2 8.4 OF NL11C, S/N: 01689105

Status

OK

Comment

Tested with revision r245.

CE7 4.0r107(05.02.2016)

Fixed Error(s)

  • Added filters to resitive STMPE610 touch driver to remove ghost samples. (#12599)

CE7 1.0(18.12.2015)

Added Feature(s)

  • Added basic support for the on-board STMPE6100 resistive touch controller. (#11971)

USB-Host

Features

  • USB 2.0 high-speed controller (480 Mbps)
  • Support for input devices (mouse, keyboard)

Known Restrictions

  • No restrictions known.

CE7 7.0r246(01.06.2016)

Tests [Sum: 3, OK: 3]

Test Environment:

  1. Boot the device to the OS.

Used Tools:

  1. USB Stick (Type: sandisk cruzer 2GB SDCZ36-002G)
    1. Create one partition with a FAT32 file system.
  2. USB Mouse (Type: LENOVO Model U0025-O)
  3. USB Keyboard (Type: Lenovo KU-0225)
USB Stick write test (#16133)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to write 32 MB

testfs_ce7 -n 32 -b 1048576 -wo "\USBDisk\"

Verification:

The average speed should be greater than 2000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with r243.

USB Stick read test (#16134)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to read 32 MB

testfs_ce7 -n 32 -b 1048576 -ro "\USBDisk\"

Verification:

The average speed should be greater than 1000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with r243.

Test Hot-plugging of different USB devices (#16132)
Tested by Clemens Terasa on 30.05.2016

Insert after each other the following devices:

Device Validation Condition
USB Stick A folder “USBDisk” is automatically added to the root within 2 seconds.
USB Mouse The mouse cursor has be come visible and the right and left button clicks are working.
USB Keyboard Open the “Run…” dialog and type in some test words.
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with r243.

CE7 6.0r183(05.04.2016)

Fixed Error(s)

  • Fixed USB Host issue with hot plugging. (#13742)

Tests [Sum: 3, OK: 3]
Perform Test

Test Environment:

  1. Boot the device up

Used Tools:

  1. USB Stick (Type: sandisk cruzer 2GB SDCZ36-002G)
    1. Create one partition with a FAT32 file system
  2. USB Mouse (Type: LENOVO Model U0025-O)
  3. USB Keyboard (Type: Lenovo KU-0225)
USB Stick write test (#13823)
Tested by Clemens Terasa on 04.04.2016

Test:

Use the testfs.exe tool to write some data to a attached USB stick.

Call the following to write 32 MB

testfs -n 32 -b 1048576 -wo "\Hard Disk\"

Verification:

The average speed should be greater than 2000000 bytes/s

Device

900-3125R: SANTARO x2 7.0 sensoglass, S/N: 01680449

Status

OK

Comment
\> testfs -n 32 -b 1048576 -wo "\Hard Disk\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\Hard Disk\ :: Path: "\Hard Disk\" exists
\Hard Disk\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: *** Write statistics for "\Hard Disk\\"
\Hard Disk\\ :: testfs0: *** complete time: 13774 msec, throughput 2436070 bytes/sec
\Hard Disk\\ :: testfs0: *** min: 2004925 bytes/sec (523 msec)
\Hard Disk\\ :: testfs0: *** avg: 2609580 bytes/sec (423 msec)
\Hard Disk\\ :: testfs0: *** max: 3371627 bytes/sec (311 msec)
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: reading 33554432 bytes...
\Hard Disk\\ :: testfs0: file \Hard Disk\\testfs0.tst deleted.
\Hard Disk\\ :: testfs0: performance test finished.
\Hard Disk\\ :: EXIT
USB Stick read test (#13824)
Tested by Clemens Terasa on 04.04.2016

Test:

Use the testfs.exe tool to write some data to a attached USB stick.

Call the following to read 32 MB

testfs -n 32 -b 1048576 -ro "\Hard Disk\"

Verification:

The average speed should be greater than 1000000 bytes/s

Device

900-3125R: SANTARO x2 7.0 sensoglass, S/N: 01680449

Status

OK

Comment
\> testfs -n 32 -b 1048576 -ro "\Hard Disk\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\Hard Disk\ :: Path: "\Hard Disk\" exists
\Hard Disk\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: *** Read statistics for "\Hard Disk\\"
\Hard Disk\\ :: testfs0: *** complete time: 24855 msec, throughput 1350007 bytes/sec
\Hard Disk\\ :: testfs0: *** min: 1361787 bytes/sec (770 msec)
\Hard Disk\\ :: testfs0: *** avg: 1362784 bytes/sec (769 msec)
\Hard Disk\\ :: testfs0: *** max: 1365333 bytes/sec (768 msec)
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: file \Hard Disk\\testfs0.tst deleted.
\Hard Disk\\ :: testfs0: performance test finished.
\Hard Disk\\ :: EXIT
Automatic mounting of USB devices (#13822)
Tested by Clemens Terasa on 05.04.2016

Test:

Insert after each other the following devices:

Device Validation Condition
USB Stick Not later than 2 second in the explorer a folder “Hard Disk” has to be automatically added.
USB Mouse The mouse cursor has be come visible and the right and left button clicks are working.
USB Keyboard Open the “Run…” dialog and type in some test words.
Device

900-3125R: SANTARO x2 7.0 sensoglass, S/N: 01680449

Status

OK

CE7 5.0r138(26.02.2016)

Tests [Sum: 3, OK: 3]
Perform Test

Test Environment:

  1. Boot the device up

Used Tools:

  1. OTG cable (micro USB to USB-A socket)
  2. USB Stick (Type: sandisk cruzer 2GB SDCZ36-002G)
    1. Create one partition with a FAT32 file system
  3. USB Mouse (Type: LENOVO Model U0025-O)
  4. USB Keyboard (Type: Lenovo KU-0225)
USB Stick write test (#12695)
Tested by Clemens Terasa on 11.02.2016

Test:

Use the testfs.exe tool to write some data to a attached USB stick.

Call the following to write 32 MB

testfs -n 32 -b 1048576 -wo "\Hard Disk\"

Verification:

The average speed should be greater than 5000000 bytes/s

Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746397
Status

OK

Comment
\> testfs -n 32 -b 1048576 -wo "\Hard Disk\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\Hard Disk\ :: Path: "\Hard Disk\" exists
\Hard Disk\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: *** Write statistics for "\Hard Disk\\"
\Hard Disk\\ :: testfs0: *** complete time: 11773 msec, throughput 2850117 bytes
/sec
\Hard Disk\\ :: testfs0: *** min: 823058 bytes/sec (1274 msec)
\Hard Disk\\ :: testfs0: *** avg: 6331790 bytes/sec (367 msec)
\Hard Disk\\ :: testfs0: *** max: 13797052 bytes/sec (76 msec)
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: reading 33554432 bytes...
\Hard Disk\\ :: testfs0: file \Hard Disk\\testfs0.tst deleted.
\Hard Disk\\ :: testfs0: performance test finished.
\Hard Disk\\ :: EXIT
Automatic mounting of USB devices (#12694)
Tested by Clemens Terasa on 11.02.2016

Test:

Insert after each other the following devices:

Device Validation Condition
USB Stick Not later than 2 second in the explorer a folder “@Hard Disk@” has to be automatically added.
USB Mouse The mouse cursor has be come visible and the right and left button clicks are working.
USB Keyboard Open the “Run…” dialog and type in some test words.
Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746397
Status

OK

USB Stick read test (#12696)
Tested by Clemens Terasa on 11.02.2016

Test:

Use the testfs.exe tool to write some data to a attached USB stick.

Call the following to read 32 MB

testfs -n 32 -b 1048576 -ro "\Hard Disk\"

Verification:

The average speed should be greater than 10000000 bytes/s

Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746397
Status

OK

Comment
\> testfs -n 32 -b 1048576 -ro "\Hard Disk\"
 :: testfs Version 1.3.9062 Mon Dec 16 08:49:11 2013
\Hard Disk\ :: Path: "\Hard Disk\" exists
\Hard Disk\\ :: testfs0: starting 33554432 bytes (32 * 1048576)...
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: *** Read statistics for "\Hard Disk\\"
\Hard Disk\\ :: testfs0: *** complete time: 2117 msec, throughput 15849991 bytes
/sec
\Hard Disk\\ :: testfs0: *** min: 15420235 bytes/sec (68 msec)
\Hard Disk\\ :: testfs0: *** avg: 15858310 bytes/sec (66 msec)
\Hard Disk\\ :: testfs0: *** max: 15887515 bytes/sec (66 msec)
\Hard Disk\\ :: testfs0: *********************************
\Hard Disk\\ :: testfs0: file \Hard Disk\\testfs0.tst deleted.
\Hard Disk\\ :: testfs0: performance test finished.
\Hard Disk\\ :: EXIT

CE7 1.0(18.12.2015)

Added Feature(s)

  • Added external USB Host port support. (#12217)

USB-Internal

Features

  • USB 2.0 high-speed controller (480 Mbps)
  • Support for input devices (mouse, keyboard)

Known Restrictions

  • No restrictions known.

CE7 7.0r246(01.06.2016)

Added Feature(s)

  • Added internal USB support. (#15968)

Tests [Sum: 3, OK: 3]

Test Environment:

  1. Boot the device up
  2. Use a special cable for the internal USB connector (X11) to USB Type A jack)

Used Tools:

  1. USB Stick (Type: sandisk cruzer 2GB SDCZ36-002G)
    1. Create one partition with a FAT32 file system
  2. USB Mouse (Type: LENOVO Model U0025-O)
  3. USB Keyboard (Type: Lenovo KU-0225)
USB Stick read test (#16176)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to read 32 MB

testfs_ce7 -n 32 -b 1048576 -ro "\USBDisk\"

Verification:

The average speed should be greater than 1000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Test Hot-plugging of different USB devices (#16174)
Tested by Clemens Terasa on 30.05.2016

Test:

Insert after each other the following devices:

Device Validation Condition
USB Stick A folder “USBDisk” is automatically added to the root within 2 seconds.
USB Mouse The mouse cursor has be come visible and the right and left button clicks are working.
USB Keyboard Open the “Run…” dialog and type in some test words.
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

USB Stick write test (#16175)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to write 32 MB

testfs_ce7 -n 32 -b 1048576 -wo "\USBDisk\"

Verification:

The average speed should be greater than 2000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

USB-OTG

Features

  • USB 2.0 high-speed controller (480 Mbps)
  • Support for input devices (mouse, keyboard)

Known Restrictions

  • ActiveSync does not work with USB-OTG port (#13032)

CE7 7.0r246(01.06.2016)

Tests [Sum: 3, OK: 3]

Test Environment:

  1. Boot the device up
  2. Use a OTG-cable (micro-USB to USB Type A jack).

Used Tools:

  1. USB Stick (Type: sandisk cruzer 2GB SDCZ36-002G)
    1. Create one partition with a FAT32 file system
  2. USB Mouse (Type: LENOVO Model U0025-O)
  3. USB Keyboard (Type: Lenovo KU-0225)
USB Stick write test (#16171)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to write 32 MB

testfs_ce7 -n 32 -b 1048576 -wo "\USBDisk\"

Verification:

The average speed should be greater than 2000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Test Hot-plugging of different USB devices (#16170)
Tested by Clemens Terasa on 30.05.2016

Test:

Insert after each other the following devices:

Device Validation Condition
USB Stick A folder “USBDisk” is automatically added to the root within 2 seconds.
USB Mouse The mouse cursor has be come visible and the right and left button clicks are working.
USB Keyboard Open the “Run…” dialog and type in some test words.
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with r243.

USB Stick read test (#16172)
Tested by Clemens Terasa on 30.05.2016

Test:

Use the testfs_ce7.exe tool to write some data to a attached USB stick.

Call the following to read 32 MB

testfs_ce7 -n 32 -b 1048576 -ro "\USBDisk\"

Verification:

The average speed should be greater than 1000000 bytes/s

Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

CE7 5.0r138(26.02.2016)

Added Feature(s)

  • Added first USB-OTG support. (#12574)

  • Added support for USB OTG port. (#12681)

Video

Features

  • Hardware-accelerated playback of videos using the VPU via Windows Media Player
  • Supported video formats: MPEG2 (H.262), MPEG4 ASP (H.263), MPEG4 AVC (H.264)

Known Restrictions

  • Video file with MPEG-1 MPG does not play. (#13102)

  • Video file with MPEG-1 MPG does not play. (#15930)

  • Video file with MPEG-2 MPG does not play. (#13100)

  • Video file with MPEG-2 MPG does not play. (#15928)

  • Video file with MPEG-4 MP4 does not play. (#13099)

  • Video file with MPEG-4 MP4 does not play. (#15927)

  • Video file with WMV does not play. (#15929)

  • Video file with h246 MP4 does not play. (#15926)

  • Video file with h264 MP4 does not play. (#13098)

CE7 7.0r246(01.06.2016)

Fixed Error(s)

  • Support for WMV videos. (#13101)

CE7 6.0r183(05.04.2016)

Fixed Error(s)

  • Removed the legacy Windows Media Player OCX functionality.
    Using this corrupted the results of file read operations. (#13839)

Tests [Sum: 1, OK: 1]

According to AMF-CSD-D0423-iMX6x_VPU_GFAE_Lecture_Demo_final_removeSomeSlides.pptx from https://community.freescale.com/docs/DOC-95595 several video formats are supported by the hardware.

However many stream and container format combinations are possible. And probably some will not work.
Several videos with different setups can be found under http://support.garz-fricke.com/projects/TestFiles/Videos/.

MediaInfo is a tool that analyses the contents of a media file.
It may be useful to determine the supported codecs and file types.

Test WMV (#13855)
Tested by Clemens Terasa on 05.04.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the WMV3-640x272-3524kbps-hp-phoenix.wmv file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3125R SANTARO 7.0 SG OF (SN: 01680449)

Status

OK

CE7 5.0r138(26.02.2016)

Tests [Sum: 5, Failed: 5]

According to AMF-CSD-D0423-iMX6x_VPU_GFAE_Lecture_Demo_final_removeSomeSlides.pptx from https://community.freescale.com/docs/DOC-95595 several video formats are supported by the hardware.

However many stream and container format combinations are possible. And probably some will not work.
Several videos with different setups can be found under http://support.garz-fricke.com/projects/TestFiles/Videos/.

MediaInfo is a tool that analyses the contents of a media file.
It may be useful to determine the supported codecs and file types.

Test WMV (#13096)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the WMV3-640x272-3524kbps-hp-phoenix.wmv file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3127R SANTARO 10.4 OF (SN: 01689129)

Status

Failed

Test MPEG-1 MPG (#13097)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the Pixar_MovieFortheBirds-640x336-mpeg1.mpg file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3127R SANTARO 10.4 OF (SN: 01689129)

Status

Failed

Test h246 MP4 (#13093)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the cc-BigBuckBunny-800x448-1000KBit-h264-stereo.mp4 file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3127R SANTARO 10.4 OF (SN: 01689129)

Status

Failed

Test MPEG-4 MP4 (#13094)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the cc-BigBuckBunny-640x352-2000KBit-mpeg4-stereo.mp4 file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3127R SANTARO 10.4 OF (SN: 01689129)

Status

Failed

Test MPEG-2 MPG (#13095)
Tested by Clemens Terasa on 29.02.2016

Test:

  1. Use a SANTARO device with a connected display and speaker.
  2. Deploy the cc-BigBuckBunny-800x448-1000KBit-mpeg2-stereo.mpg file to the device (i.e. via FTP).
  3. Browse in the explorer to the file location and double click it.
  4. View the video

Verification:

  1. The Windows Media player starts
  2. The player plays the file.
  3. No video artifacts are visible
  4. The sound is playing.
  5. The whole file is played.
Device

900-3127R SANTARO 10.4 OF (SN: 01689129)

Status

Failed


Mandatory Tests

Boot and reset

Features

  • Boot up Time below 30 seconds.

Known Restrictions

  • Boot times need improvement (#15919)

CE7 10.1r442(24.10.2017)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are measured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Device Power on (#28234)
Tested by Clemens Terasa on 20.10.2017

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
6 kernel splash 00:10.1s
12 first available usable GUI 00:20.4s
Device

900-3747R SANTARO x2 7.0 SG IPS V1.2 (SN: 02118557)

Status

OK

CE7 10.0r416(10.03.2017)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are measured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Device Power on (#23111)
Tested by Clemens Terasa on 10.03.2017

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
6 kernel splash 00:09.83s
12 first available usable GUI 00:20.39s
Device

900-3542R SANTARO x2 BX PCT 1K V1.2, SN: 01934846

Status

OK

CE7 9.0r387(07.09.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are measured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Device Power on (#20079)
Tested by Clemens Terasa on 13.09.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
6 kernel splash 00:10.4s
12 first available usable GUI 00:21.3s
Device

900-3125R SANTARO x2 7.0 SG IPS V1.2, SN: 01680449

Status

OK

CE7 8.0r275(04.07.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are meashured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Device Power on (#17463)
Tested by Clemens Terasa on 04.07.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
6 kernel splash 00:11.3s
12 first available usable GUI 00:25.2s
Device

900-3125R SANTARO x2 7.0 SG IPS V1.2, SN: 01680449

Status

OK

CE7 7.0r246(01.06.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are meashured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Deivce Power on (#16651)
Tested by Clemens Terasa on 01.06.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
12 first available usable GUI 00:25.1s
Device

900-3125R SANTARO x2 7.0 SG, SN: 01680449

Status

OK

CE7 6.0r183(05.04.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are measured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Devices:
Measure boot time from device Power on (#13813)
Tested by Clemens Terasa on 05.04.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
12 first available usable GUI 00:24.7s
Device

900-3125R SANTARO x2 7.0 sensoglass (SN: 01680449)

Status

OK

CE7 5.0r138(26.02.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are measured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Devices:
Measure Boot Time from Deivce Power on (#13114)
Tested by Clemens Terasa on 26.02.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
12 first available usable GUI 00:17.4s
Device

900-3127R SANTARO x2 10.4 OF (SN: 01689129)

Status

OK

CE7 4.0r107(05.02.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are meashured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Devices:
Measure Boot Time from Deivce Power on (#12641)
Tested by Clemens Terasa on 05.02.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
12 first available usable GUI 00:17.0s
Device

900-3128R SANTARO x2 7.0 Bx (SN: 01756397)

Status

OK

CE7 3.0r89(01.02.2016)

Tests [Sum: 1, OK: 1]
Definitions

We use the following definitions to express our boot time behavior.
This is an adjusted version of the Boot-up Time Definition Of Terms.

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
2 bootloader starts
3 bootloader splash
4 kernel decompression starts
5 kernel start
6 kernel splash
7 user start
8 user splash
9 RC script start
10 application start
11 first available usable console
12 first available usable GUI
Test Environment
  • Manually measured using a stop watch
  • Measuring begins at power on and is zero reference point.
  • Not all times are applicable for all devices:
    • This means not all values are meashured and left open in this case.
  • Times are measured with the second and consecutive boots to reduce the effect of the first boot initialization
  • Standard installation without any Add-On packages installed
Used Tools
  • Stop Watch
Measure Boot Time from Deivce Power on (#12467)
Tested by Nils Grimm on 01.02.2016

Measured these times:

Boot Step Description measured time (mm:ss.t)
1 power on 00:00.0s
12 first available usable GUI 00:16.7s
Device

900-2894R SANTARO x2 8.4 OF NL11C (SN:01689105)

Status

OK


System Services

Bootloader

Features

  • Flash-N-Go Boot compatible
  • Uses ATAGs from Flash-N-Go boot.
  • Selectable features like MAC address and display.
  • Promotes version information to Windows.

Known Restrictions

  • EBoot: Image loading from FAT is too slow (#16200)

  • EBoot: Image loading from FAT is too slow (#17504)

  • GuF-XML configuration cannot be written back (#19066)

  • Problem initializing Display in EBoot due to corrupted memory coming from FnGBoot (#17914)Solved in ‘CE2013 3.0r368’

CE7 10.1r442(24.10.2017)

Added Feature(s)

  • Made Eboot XML-parsing more gracious (#28230)

CE7 9.0r387(07.09.2016)

Fixed Error(s)

  • Fixed EBoot memory corruption by updating the Flash-N-Go Boot dependency to version 9.0. The cache issue was solved in Flash-N-Go Boot. (#17585)

Added Feature(s)

  • Autoinit: Propagate the force_autoinit setting form XML to the Windows Registry (#19686)

CE7 8.0r275(04.07.2016)

Added Feature(s)

  • Added Windows image loading from FAT32 partition. Not used by default because of Bug #16200. (#15965)

  • Disabled the propagation of IP settings from EBoot to Windows. This enables the possibility to change the TCP/IP settings persistently. (#17159)

CE7 7.0r246(01.06.2016)

Fixed Error(s)

  • Fixed boot issue with older eMMC ICs and SANTARO board revisions by reducing the EBoot image size. (#16017)

CE7 6.0r183(05.04.2016)

Added Feature(s)

  • Get and parse ATAGS form the Flash-N-Go Boot bootloader. (#12781)

  • Publish Flash-N-Go Boot version to the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\FnGBoot\. (#12782)

  • Publish the EBoot version to the Registry to HKEY_LOCAL_MACHINE\software\eboot. (#12789)

Tests [Sum: 0]

Test Environment:

  1. A device with a fresh installation of the OS.

Used Tools:

  • Eboot
  • Telnet
  • toolbox (installed)
  • No specific test cases executed in this version.

CE7 5.0r138(26.02.2016)

Fixed Error(s)

  • Added simulation of the early DCD execution. (#12562)

CE7 4.0r107(05.02.2016)

Fixed Error(s)

  • Added version information to EBoot. (#12559)

CE7 3.0r89(01.02.2016)

Added Feature(s)

  • Added Flash-N-Go boot support. FnGBoot starts EBoot bootloader. EBoot then configures the settings and starts Windows. (#12457)

CE7 1.0(18.12.2015)

Added Feature(s)

  • Added initial board support with catalog, project and board configuration files. (#12135)

Bootlogo

Features

  • Display BMP file during boot using Eboot.

Known Restrictions

  • No restrictions known.

CE7 8.0r275(04.07.2016)

Added Feature(s)

  • Changed the befault background color for boot logos to black. (#16215)

Tests [Sum: 1, OK: 1]

Test Environment:

  • Install the bootlogo via the OS-Install-Script in Flash-N-Go System.
  • Install the OS with the -i parameter. I.e.:
    export TFTP=192.168.1.100; curl tftp://$TFTP/SANTARO_CE7P-8.0r275-0_fng_ce7_install.sh | sh -s -- -i GF_Bootlogo_Santaro.bmp
    

Used Tools:

  • Use the bootlogo GF_Bootlogo_Santaro.bmp
  • Stop clock.
Show splashscreen on boot (#17506)
Tested by Clemens Terasa on 04.07.2016

Test:

  1. Power off the device.
  2. Wait 5 seconds.
  3. Power on the device, at the same time start the stop clock.

Verification:

  1. The installed boot logo should be displayed.
  2. Stop the stop clock and report the measured time in the test comment.
Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01680449
Status

OK

Comment

The Splash screen comes up after 11.3 seconds.
This is longer than the targeted 5s.
This is related to the #17504 Bug.

FTP Server

Features

  • Download and upload files from/to the root file system of the device using an FTP client.

Known Restrictions

  • No restrictions known.

CE7 6.0r183(05.04.2016)

Added Feature(s)

  • Added the ntlmadmin tool to manage users for services like FTP and TELNET. (#12688)

Tests [Sum: 2, OK: 2]
Perform Test

Test Environment:

  • An Ethernet connected device.
  • An valid IP configuration for the Desltop and device.

Used Tools:

  • Desktop Windows FTP client (i.e. Filezilla).
  • Test File: foobar.bin (Md5Sum: f1c9645dbc14efddc7d8a322685f26eb)
Upload the test file to the device (#13829)
Tested by Clemens Terasa on 04.04.2016

Test:

  1. Connect via an FTP program (i.e. Filezilla) to the device.
  2. Upload the test file.

Verification:

The upload should work without any errors.

Device
  1. 900-2894R: SANTARO x2 8.4 OF NL11C, S/N: 01689105
Status

OK

Test FTP authentication (#13831)
Tested by Clemens Terasa on 05.04.2016

Test:

  1. Start the device.
  2. Connect via telnet.
  3. Execute the following commands on the device:
    ntlmadmin adduser foo bar
    toolbox reg set HKEY_LOCAL_MACHINE\COMM\FTPD "IsEnabled" d 1
    toolbox reg set HKEY_LOCAL_MACHINE\COMM\FTPD "UseAuthentication" d 1
    toolbox reg set HKEY_LOCAL_MACHINE\COMM\FTPD "AllowAnonymous" d 0
    toolbox reg set HKEY_LOCAL_MACHINE\COMM\FTPD "AllowAnonymousUpload" d 0
    toolbox reg set HKEY_LOCAL_MACHINE\COMM\FTPD "AllowAnonymousVroots" d 0
    savereg -n
    services stop FTP0:
    services start FTP0:
    
  4. Try to connect with an FTP program (FileZilla) from the development PC as anonymous. (This is intended to fail.)
  5. Try to connect with an FTP program (FileZilla) from the development PC as user “foo” with the password “bar”.

Verification:

  1. The test fails if the FTP program connects using anonymous.
  2. The test fails if the FTP program fails to connect using the “foo” user
Device
  1. 900-2894R: SANTARO x2 8.4 OF NL11C, S/N: 01689105
Status

OK

GuF Services

Features

  • Automatic copy of files in storage-device>\@autocopy@ to the root-file-system.
  • Automatic execution of binaries on system boot or on insertion of external data storage devices.
  • Executes all binaries and batch files in the storage-device>\@Autostart@ folder
  • Executes all binaries in the storage-device>\@Autoinit@ folder once if “md5sums.txt” is present and valid.

Known Restrictions

  • No restrictions known.

CE7 9.0r387(07.09.2016)

Tests [Sum: 7, OK: 7]

Test Environment:

  • The test device

Used Tools:

  • USB-Stick
  • SD-Card
  • internal Flashdisk folder.
Automatic copy SD-Card (#20081)
Tested by Clemens Terasa on 13.09.2016

Test:

SD-Card Preparation:

  1. create a folder autocopy in the SD-Card root directory.
  2. Store the test file foobar.bin in the just created folder autocopy

Test 1:

  1. Boot up the device
  2. Insert the SD-Card.
  3. copy the newly created file foobar.bin from the root folder of the device on the PC.
  4. Make a file compare.

Test 2:

  1. Delete the test file foobar.bin in the root folder
  2. Turn the device off.
  3. Insert the SD-Card.
  4. Turn on the device and wait until device has been booted up.
  5. copy the newly created file foobar.bin from the root folder of the device on the PC.
  6. Make a file compare.

Verification:

Both file compares should show no errors.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Automatic copy Flashdisk (#20083)
Tested by Clemens Terasa on 13.09.2016

Test:

Internal Flashdisk Preparation:

  1. create a folder autocopy in the Flashdisk root directory.
  2. Store the test file foobar.bin in the just created folder autocopy

Test 2:

  1. Turn the device off.
  2. Turn on the device and wait until device has been booted up.
  3. copy the newly created file foobar.bin from the root folder of the device on the PC.
  4. Make a file compare.

Verification:

The file compare should show no errors.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Automatic application start from USB-Stick (#20085)
Tested by Clemens Terasa on 13.09.2016

Test:

USB-Stick Preparation:

  1. Create a folder Autostart in the USB-Stick root directory.
  2. Store the test application TestResolution.exe in the just created folder Autostart
  3. Store the SetRegTest.bat in the Autostart directory

Test 1 (hot-plug):

  1. Boot up the device
  2. Insert the USB-Stick.
  3. The test application TestResolution.exe will show a GUI window after start.
  4. Test for the created Registry Key using toolbox reg show HKLM\
  5. Delete the created Registry Key using toolbox reg del HKLM\ SetRegTest

Test 2 (bootup):

  1. Turn the device off.
  2. Insert the USB-Stick.
  3. Turn on the device and wait until device has been booted up.
  4. The test application TestResolution.exe will show a GUI window after start.
  5. Test for the created Registry Key using toolbox reg show HKLM\
  6. Delete the created Registry Key using toolbox reg del HKLM\ SetRegTest

Verification:

  1. In both cases the test application TestResolution.exe has to show the test screen.
  2. The Registry should contain a string key named HKEY_LOCAL_MACHINE\SetRegTest with the value “Success!”
Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Automatic application start from SD-Card (#20084)
Tested by Clemens Terasa on 13.09.2016

Test:

SD-Card Preparation:

  1. create a folder Autostart in the SD-Card root directory.
  2. Store the test application TestResolution.exe in the just created folder Autostart
  3. Store the SetRegTest.bat in the Autostart directory

Test 1 (hot-plug):

  1. Boot up the device
  2. Insert the SD-Card.
  3. The test application TestResolution.exe will show a GUI window after start.
  4. Test for the created Registry Key using toolbox reg show HKLM\
  5. Delete the created Registry Key using toolbox reg del HKLM\ SetRegTest

Test 2 (bootup):

  1. Turn the device off.
  2. Insert the SD-Card.
  3. Turn on the device and wait until device has been booted up.
  4. The test application TestResolution.exe will show a GUI window after start.
  5. Test for the created Registry Key using toolbox reg show HKLM\
  6. Delete the created Registry Key using toolbox reg del HKLM\ SetRegTest

Verification:

  1. In both cases the test application TestResolution.exe has to show the test screen.
  2. The Registry should contain a string key named HKEY_LOCAL_MACHINE\SetRegTest with the value “Success!”
Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Automatic copy USB-Stick (#20082)
Tested by Clemens Terasa on 13.09.2016

Test:

USB-Stick Preparation:

  1. create a folder autocopy in the USB-Stick root directory.
  2. Store the test file foobar.bin in the just created folder autocopy

Test 1:

  1. Boot up the device
  2. Insert the USB-Stick.
  3. copy the newly created file foobar.bin from the root folder of the device on the PC.
  4. Make a file compare.

Test 2:

  1. Delete the test file foobar.bin in the root folder
  2. Turn the device off.
  3. Insert the USB-Stick.
  4. Turn on the device and wait until device has been booted up.
  5. copy the newly created file foobar.bin from the root folder of the device on the PC.
  6. Make a file compare.

Verification:

Both file compares should show no errors.

Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Automatic application start from Flashdisk (#20086)
Tested by Clemens Terasa on 13.09.2016

Test:

Internal Flashdisk Preparation:

  1. Create a folder Autostart in the Flashdisk root directory.
  2. Store the test application TestResolution.exe in the just created folder Autostart
  3. Store the SetRegTest.bat in the Autostart directory

Test 1 (bootup):

  1. Turn the device off.
  2. Turn on the device and wait until device has been booted up.
  3. The test application TestResolution.exe will show a GUI window after start.
  4. Test for the created Registry Key using toolbox reg show HKLM\
  5. Delete the created Registry Key using toolbox reg del HKLM\ SetRegTest

Verification:

  1. The test application TestResolution.exe has to show the test screen.
  2. The Registry should contain a string key named HKEY_LOCAL_MACHINE\SetRegTest with the value “Success!”
Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

One-time auto-initialization start from hidden OS partition (#20087)
Tested by Clemens Terasa on 13.09.2016

Test:

Install the OS form Flash-N-Go System using the --AI parameters

  1. Put the OS files into your TFTP-Server folder
  2. Put the batch file named wavtest.bat with the following content into your TFTP-Server folder
    wavplay.exe
    
  3. Put the batch file named wavtest_md5sums.txt with the following content into your TFTP-Server folder
  4. Boot the SANTARO into Flash-N-Go System via calling bootselect alternative or via the BootMode switch (aka ClearAll button.)
  5. Using a serial line or telnet on your SANTARO booted into Flash-N-Go execute the following:
    export TFTP=<Your-IP>; curl tftp://$TFTP/fng_ce7_install.sh | sh -s -- --AI=wavtest.bat --AI=wavtest_md5sums.txt
    
  6. Wait to the install to the complete and execute:
    bootselect regular
    sync
    

Test 1 (first bootup):

  1. Turn the device off.
  2. Turn on the device and wait until device has been booted up.
  3. The initialization should execute the wavtest.bat and play a “Bing” sound.

Test 2 (second bootup):

  1. Turn the device off.
  2. Turn on the device and wait until device has been booted up.
  3. The initialization should not execute wavtest.bat and not play a “Bing” sound but only the “normal” windows bootup sound
  4. Connect via telenet to the device and execute:
    toolbox reg show HKLM\Software\Autojob\AutoInitList\
    

Verification:

  1. The bing sound is played on the first boot.
  2. The bing sound is not played the second boot.
  3. The toolbox command should output
     AutoinitDone = 1 (0x00000001)
    
Device

900-3367R: SANTARO x2 10.1 BX PCT IPS V1.2, S/N: 01800285

Status

OK

Languages

Features

  1. System Languages for English, German, French and Spanish
  2. Several locales.

Known Restrictions

  • No restrictions known.

CE7 7.0r246(01.06.2016)

Tests [Sum: 1, OK: 1]

Test Environment:

  • Start Windows with an explorer.
System language test (#16249)
Tested by Clemens Terasa on 30.05.2016

Test:

  1. Open the Regional Settings app in My Device -> ControlPanel -> Regional Settings
  2. In the User interface Language Tab open the Drop down menu.
  3. The menu should be selectable and show the supported languages.
  4. Select German (Germany).
  5. Confirm the Dialog and the popup dialog.
  6. Reboot the device
  7. verify the German UI: The My Device app should have become Mein Gerät.

Verification:

  1. The test fails if the drop down menu does not show multiple languages or is not selectable.
  2. The test fails if the UI is not shown in German after reboot.
Device

900-3128R SANTARO x2 7.0 BX (SN: 01746397)

Status

OK

Comment

Tested with revision r243.

Telnet Server

Features

  • Remote console/shell on the device

Known Restrictions

  • No restrictions known.

CE7 3.0r89(01.02.2016)

Tests [Sum: 1, OK: 1]
Perform Test

Test Environment:

  • An Ethern connected device.
  • A valid Ethernet configuration for the device and the test PC.

Used Tools:

  • Windows integrated telnet client via shell.
Connect to the device (#12533)
Tested by Bernd Mierzowski on 01.02.2016

Test:

  1. Boot up the device.
  2. Get from the Ethernet GUI dialog of the device the <ip address>.
  3. open the windows shell.
  4. Execute the following command on the windows shell:
    telnet <ip address>

Verification:

After the connection is established execute on the shell the command:

dir

The root folder content should be shown.

Device
  1. 900-3128R: SANTARO x2 7.0 BX, S/N: 01746459
Status

OK

Temperature

Features

  • Monitor the cpu temperature.
  • Resetting the system if a critical (configurable) temperature threshold is reached.
  • Displays the cpu temperature on boot and if the tool is executed manually without parameters

Known Restrictions

  • No restrictions known.

CE7 6.0r183(05.04.2016)

Tests [Sum: 0]
Perform Test

Test Environment:

  • Prepare a hot-air blower
  • Boot the device (The monitor tool willbe started automatically after boot)
  • Check the temperature and the alarm temperature displayed in the boot messages

Used Tools:

  • TempMonitor.exe
  • toolbox.exe
  • savereg.exe
  • reset.exe
  • No specific test cases executed in this version.


Change History

CE7 10.1r442(24.10.2017)

Fixed Error(s)

  • Capacitive Touch – EXC3000 I2C: Fix a detection bug for EXC3000 by increasing the reset-to-ready wait time. (#28229)

Added Feature(s)

  • Bootloader: Made Eboot XML-parsing more gracious (#28230)

CE7 10.0r416(10.03.2017)

Fixed Error(s)

  • Capacitive Touch – EXC3000 I2C: Fixed touch-up bug with EXC3000 I2C controllers. (#20145)

  • LVDS: Fixed cache flushing when calling OS in the Flash-N-Go Boot bootloader. Therefore the minimal required bootloader version is 9.0r3476. (#17274)

Added Feature(s)

  • Display: Added support for Display DataImage FG0700W0DSSWAGL1 (also in SCX0700C48GGU65) (#23044)

CE7 9.0r387(07.09.2016)

Fixed Error(s)

  • Bootloader: Fixed EBoot memory corruption by updating the Flash-N-Go Boot dependency to version 9.0. The cache issue was solved in Flash-N-Go Boot. (#17585)

  • Ethernet: Fixed TCPIP Exception error by updating Windows CE7 to Update 60 (June 2016). (#20054)

  • Flash-N-Go: Fix Image parameter of the install script. (#19274)

  • Image Config: Updated Windows Embedded Compact to Update 60 (June 2016) because of bug #20054. (#20062)

  • SDK: Added the GFVersionApi stub to SDK. (#20098)

Added Feature(s)

  • Bootloader: Autoinit: Propagate the force_autoinit setting form XML to the Windows Registry (#19686)

  • Capacitive Touch – SIS92xx I2C: Added support for SIS92xx touch controllers. (#17276)

  • Flash-N-Go: Autoinit: Added AI parameter type to the install script for Autoinit files. (#19681)

  • Source code management: Merged Fix-release 8.3 sources back to trunk. (#18028)

  • Tools: Added GFmd5 library to be used by GFmd5sum and autojob. (#19674)

  • Tools: AutoInit: Added one-time-initialization code to the Autojob tool. (#19676)

  • Tools: GFmd5sum: Added simple md5sum tool for testing purposes. (#19675)

CE7 8.0r275(04.07.2016)

Added Feature(s)

  • Bootloader: Added Windows image loading from FAT32 partition. Not used by default because of Bug #16200. (#15965)

  • Bootloader: Disabled the propagation of IP settings from EBoot to Windows. This enables the possibility to change the TCP/IP settings persistently. (#17159)

  • Bootlogo: Changed the befault background color for boot logos to black. (#16215)

  • Capacitive Touch – EXC7200 I2C: Added EDT-M06 touch variant support. (#17502)

  • Image Config: Added Fonts: Verdana, Arial and Courier New (#17457)

  • Image Config: Added the FTDI virtual COM port driver. (#17458)

  • Tools: Updated toolbox version to 1.7. It no supports Multi-String registry key. (#17459)

CE7 7.0r246(01.06.2016)

Fixed Error(s)

  • Bootloader: Fixed boot issue with older eMMC ICs and SANTARO board revisions by reducing the EBoot image size. (#16017)

  • Flash-N-Go: Fixed a typo in the install script. (#16237)

  • Video: Support for WMV videos. (#13101)

Added Feature(s)

  • Capacitive Touch – EXC7200 I2C: Added EETI EXC7200 USB touch support. (#15970)

  • Flash-N-Go: Mount the registry and FlashDisk partitions as TexFAT. (#16101)

  • Flash-N-Go: Updated the install script. (#16148)

  • Image Config: Added system languages English, German, French and Spanish (#13871)

  • Image Config: Added the DirectDraw XAML renderer. (#16199)

  • MDB: Added MDB-Master support including the MDB-Karl-test. (#16061)

  • Source code management: Updated the base sources coming from our BSP supplier to revision 954. (#16117)

  • Tools: Added the playwnd and ceplayit tools. (#16062)

  • USB-Internal: Added internal USB support. (#15968)

CE7 6.0r183(05.04.2016)

Fixed Error(s)

  • Display: Added special LDB clock change handling. (#13838)

  • Image Config: Removed the asynchronous drivers loading with the busenum2 driver loader. (#13493)

  • SDK: Added missing OpenGL headers to the SDK. (#13740)

  • USB-Host: Fixed USB Host issue with hot plugging. (#13742)

  • Video: Removed the legacy Windows Media Player OCX functionality.
    Using this corrupted the results of file read operations. (#13839)

Added Feature(s)

  • Bootloader: Get and parse ATAGS form the Flash-N-Go Boot bootloader. (#12781)

  • Bootloader: Publish Flash-N-Go Boot version to the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\FnGBoot\. (#12782)

  • Bootloader: Publish the EBoot version to the Registry to HKEY_LOCAL_MACHINE\software\eboot. (#12789)

  • Capacitive Touch – EXC7200 I2C: Added support for EETI EXC7200 touch. (#12684)

  • Capacitive Touch – EXC7200 I2C: Added the touchc touch calibration tool. (#13460)

  • Capacitive Touch – EXC7200 I2C: Added the touch test tools cetouchview.exe and etcha.exe to the image. (#13622)

  • Capacitive Touch – EXC7200 I2C: Added touch driver abstraction for per-touch configurations. (#13459)

  • Capacitive Touch – EXC7200 I2C: Code changes for EDT touch M06 variants. Still unsupported though. (#13451)

  • Display: Added support for the 7.” LG LB070WV8 Display. (#12683)

  • FTP Server: Added the ntlmadmin tool to manage users for services like FTP and TELNET. (#12688)

  • Flash-N-Go: Made the Flash-N-Go System version available in the Registry key HKEY_LOCAL_MACHINE\Software\FnGSystem\. (#12788)

  • Image Config: Added SQL Compact feature. (#13801)

  • Image Config: Added locales for English, German, Spanish, French and Turkish (#13800)

  • Image Config: Re-added the Media Player application. (#13814)

  • Tools: Add Flash-N-Go System, Flash-N-Go Boot, and Eboot version to the discovery service. (#13744)

  • Tools: Added a tool for temperature monitoring. (#13476)

  • Tools: Added the static library GFzlib to the source tree. (#12787)

CE7 5.0r138(26.02.2016)

Fixed Error(s)

  • Backlight: Added PWM frequency setting to the LVDS modes structure. (#12451)

  • Backlight: Added drive strength setting to backlight settings. (#12452)

  • Backlight: Fixed an issue with the PEM backlight in the 100% on case.
    The PWM was not constant but showed “ripples”. (#12450)

  • Bootloader: Added simulation of the early DCD execution. (#12562)

  • Display: Fixed Display power switching error. (#12287)

Added Feature(s)

  • Audio: Added audio recording support. (#12793)

  • Audio: Added wave playback support. (#12577)

  • Digital I/O: Added pingroup feature to the Digital IO driver. (#12732)

  • Display: Added display power sequence. (#12809)

  • Display: Added support for the Ampire AM800600K2TMQW display. (#12719)

  • Display: Added the disp.exe tool to rotate the display. (#12578)

  • Ethernet: Added Ethernet PHY reset at boot time. (#11978)

  • Matrix Keyboard: Added matrix keyboard support. (#12576)

  • OpenGL ES: Added the OpenGL based XAML renderer. (#13103)

  • Source code management: Removed the MfgTool capable project from the source tree. (#12811)

  • Tools: Added the Command Prompt dialog. (#12737)

  • Tools: Added the Windows Media Player App. (#13092)

  • USB-OTG: Added first USB-OTG support. (#12574)

  • USB-OTG: Added support for USB OTG port. (#12681)

CE7 4.0r107(05.02.2016)

Fixed Error(s)

  • Bootloader: Added version information to EBoot. (#12559)

  • RS232: Fixed muxing issue for RS232 RTS and CTS signals. (#12432)

  • Touch – resistive: Added filters to resitive STMPE610 touch driver to remove ghost samples. (#12599)

Added Feature(s)

  • RTC: Added GFRTCSync tool to synchronize the system time with the external PCF8563 RTC. Will be startet with init. (#12561)

  • RTC: Added NTP support. (#12589)

  • RTC: Set time zone to Western European Time. (#12585)

  • Tools: Added the “bootselect” tool to switch to Flash-N-Go System. (#12558)

  • Tools: Added the Internet Explorer Sample Browser. (#12590)

CE7 3.0r89(01.02.2016)

Fixed Error(s)

  • Backlight: Added PWM Backlight support. (#12394)

  • eMMC: Supporting boot from eMMC. (#12406)

Added Feature(s)

  • Backlight: Added the “Advanced Backlight” feature to the Display control panel app. (#12396)

  • Bootloader: Added Flash-N-Go boot support. FnGBoot starts EBoot bootloader. EBoot then configures the settings and starts Windows. (#12457)

  • CAN: Added Garz and Fricke FlexCAN driver. (#11987)

  • CAN: Added support for the the Garz and Fricke CAN API. (#11988)

  • Digital I/O: Add Garz & Fricke Digital IO driver.
    Currently the driver supports the external DIOs only. (#12433)

  • Digital I/O: Added Garz & Fricke Digital IO API support.
    The API has currently no pin reservation and pin group support. (#11984)

  • Display: Added support for the 8.4” NLT NL8060BC21-11C Display. (#12425)

  • RS485: Supporting RS485 Full Duplex Mode on COM4 (#12424)

  • Release issues: Added a version information file to the image. (#11991)

  • Tools: Added the Garz & Fricke SaveReg tool. (#12098)

  • Tools: Added the Garz & Fricke toolbox tool. (#11994)

  • Tools: Discovery service is running. The Device Control Center will be supported. (#12544)

  • eMMC: Add persistent Registry feature. Using the Flash-N-Go architecture to create the correct partitions. (#12407)

CE7 2.0(08.01.2016)

Added Feature(s)

  • Backlight: Added the Backlight PWM driver support. (#12395)

  • SDK: Added an SDK (#12186)

  • Tools: Added Autojob support. This includes autostart and autocopy (#12168)

  • Tools: Added reset tool using the hardware pin watchdog mechanism. (#12033)

CE7 1.0(18.12.2015)

Fixed Error(s)

  • SMP: Fixed an issue related to the idle time calculation. (#12240)

Added Feature(s)

  • Backlight: Activate display backlight without dimming. (#11968)

  • Bootloader: Added initial board support with catalog, project and board configuration files. (#12135)

  • Display: Added Ampire AM800480R3TMQW-TACH Display support. (#11963)

  • Ethernet: Added SMSC LAN8720A Ethernet Phy support. (#12153)

  • Touch – resistive: Added basic support for the on-board STMPE6100 resistive touch controller. (#11971)

  • USB-Host: Added external USB Host port support. (#12217)


© 2016 Garz & Fricke GmbH · All rights reserved · Release Notes built with version 294