Difference between revisions of "Compulab Technical Support"
| Line 4: | Line 4: | ||
Please use the following template when you open an issue: | Please use the following template when you open an issue: | ||
# State the hardware product revision | # State the hardware product revision | ||
| − | # State the software release date you are using<br/> | + | # State the software release date you are using<br/>In Android this information is provided under ''Settings->About phone->Kernel version'' |
# Does the problem occur on CompuLab evaluation platform? | # Does the problem occur on CompuLab evaluation platform? | ||
# What is the symptom (upload a log file) | # What is the symptom (upload a log file) | ||
| Line 35: | Line 35: | ||
[[Category:Windows CE]] | [[Category:Windows CE]] | ||
| + | [[Category:WEC7]] | ||
[[Category:Linux]] | [[Category:Linux]] | ||
| + | [[Category:Android]] | ||
Revision as of 12:14, 14 February 2013
Compulab provides support for its products through the online support system. Please refer to the SupportDB help page for information about the system and its use.
Please use the following template when you open an issue:
- State the hardware product revision
- State the software release date you are using
In Android this information is provided under Settings->About phone->Kernel version - Does the problem occur on CompuLab evaluation platform?
- What is the symptom (upload a log file)
- What are you expecting
- Steps to reproduce
- Additional relevant information
Providing all the above information will enable us to provide faster and more accurate support.
Issue report example
I am using the Windows CE package for CM-X300 released on 13/4/2014, and downloaded from www.anotherinvalidplace.nul.
The following happens on Compulab's eval board (CM+SB):
RTC fails to save the time.
I expect the date and time to persist when doing a software reboot.
To reproduce:
- turn the module on
- Set the time and date
- Reboot the module using Software reboot
- Check the time
Additional info:
- Doing the same experiment with a GPIO reset succeeds.
- The device is powered by the battery when doing this.
- Plugging the device to the power supply resolves this.
The log file is attached
Thanks,
Someone
