Compulab Mediawiki - User contributions [en]

CM-iTC: Hardware: Revision Notes

2014-05-04T11:26:45Z

Dimitry: New page: ==Rev 1.1 [15-Dec-2010]== * Initial public release.

==Rev 1.1 [15-Dec-2010]==
* Initial public release.

CM-X270: Hardware: Revision Notes

2014-05-01T13:29:34Z

Dimitry: /* Rev 1.7 [1-Dec-2012] */

=CM-X270L=
==Rev 1.7 [1-Dec-2012]==

* Marvell 88AP270 PCMCIA access issue fixed, pull-up added to PCM_PWAIT for preventing system hang-up

==Rev 1.6 [1-May-2009]==

* DM9000 reset bug fixed, RC circuit added for proper reset
* MMDAT3_GPIO111 disconnected from W2SW interface

==Rev 1.5 [27-Jun-2008]==

* W2SW2001 reset and boot-strap fixed

==Rev 1.4 [30-May-2008]==

* BGW2xx replaced with the W2SW2001 module
* NAND flash ALE and CLE signals are gated with NAND_CS
* NAND_CS is routed out of CPLD. Added U56, U57, U58

==Rev 1.3a [5-Feb-2008]==

* Routed CPU GPIO[0] directly to CAMI PME#
* Fixed BGW211 boot option to support SPI interface
* Altered SDCLK routing
* Added more powerful PU/PD to CPU GPIO[0] and GPIO[1]
* Added a test point for RST_IN signal
* Connected UCB1400 VADCN to AGND
* Added a pull-up to MMCLK_WIFI
* Routed REG/GNT pair 3 to CAMI instead of pair 0
* Added revision setting RN
* Added SDCS always active for D128
* Added PCM_PWE# option for NOR flash

 

=CM-X270W=
==Rev 1.4i [1-Jul-2013]==
* Marvell 88AP270 PCMCIA access issue fixed, pull-up added to PCM_PWAIT for preventing system hang-up

==Rev 1.4 [20-Feb-2009]==
* RTC crystal changed to the new small foot-print type
* CPLD clock bug detected in 1.3 fixed
* Separate audio codec crystal added
* DM9000 reset bug fixed, RC circuit added for proper reset
* Pull-down added to the Bluetooth enable signal

==Rev 1.3 [30-Aug-2008]==
* Wi2Wi WLAN controller added
* CSR Bluetooth controller added
* NAND flash control lines buffered with logic gates

==Rev 1.23 [12-Aug-2008]==
* Missing nets IDEINT_KP_MKIN0_GPIO100, GPIRQ1_KP_MKIN1_GPIO101 corrected

CM-X270: Hardware: Revision Notes

2014-05-01T13:29:22Z

Dimitry: /* CM-X270W */

=CM-X270L=
==Rev 1.7 [1-Dec-2012]==

* Marvell 88AP270 PCMCIA access bug fixed, pull-up added to PCM_PWAIT for preventing system hang-up

==Rev 1.6 [1-May-2009]==

* DM9000 reset bug fixed, RC circuit added for proper reset
* MMDAT3_GPIO111 disconnected from W2SW interface

==Rev 1.5 [27-Jun-2008]==

* W2SW2001 reset and boot-strap fixed

==Rev 1.4 [30-May-2008]==

* BGW2xx replaced with the W2SW2001 module
* NAND flash ALE and CLE signals are gated with NAND_CS
* NAND_CS is routed out of CPLD. Added U56, U57, U58

==Rev 1.3a [5-Feb-2008]==

* Routed CPU GPIO[0] directly to CAMI PME#
* Fixed BGW211 boot option to support SPI interface
* Altered SDCLK routing
* Added more powerful PU/PD to CPU GPIO[0] and GPIO[1]
* Added a test point for RST_IN signal
* Connected UCB1400 VADCN to AGND
* Added a pull-up to MMCLK_WIFI
* Routed REG/GNT pair 3 to CAMI instead of pair 0
* Added revision setting RN
* Added SDCS always active for D128
* Added PCM_PWE# option for NOR flash

 

=CM-X270W=
==Rev 1.4i [1-Jul-2013]==
* Marvell 88AP270 PCMCIA access issue fixed, pull-up added to PCM_PWAIT for preventing system hang-up

==Rev 1.4 [20-Feb-2009]==
* RTC crystal changed to the new small foot-print type
* CPLD clock bug detected in 1.3 fixed
* Separate audio codec crystal added
* DM9000 reset bug fixed, RC circuit added for proper reset
* Pull-down added to the Bluetooth enable signal

==Rev 1.3 [30-Aug-2008]==
* Wi2Wi WLAN controller added
* CSR Bluetooth controller added
* NAND flash control lines buffered with logic gates

==Rev 1.23 [12-Aug-2008]==
* Missing nets IDEINT_KP_MKIN0_GPIO100, GPIRQ1_KP_MKIN1_GPIO101 corrected

CM-X270: Hardware: Revision Notes

2014-05-01T13:27:23Z

Dimitry: /* CM-X270L */

=CM-X270L=
==Rev 1.7 [1-Dec-2012]==

* Marvell 88AP270 PCMCIA access bug fixed, pull-up added to PCM_PWAIT for preventing system hang-up

==Rev 1.6 [1-May-2009]==

* DM9000 reset bug fixed, RC circuit added for proper reset
* MMDAT3_GPIO111 disconnected from W2SW interface

==Rev 1.5 [27-Jun-2008]==

* W2SW2001 reset and boot-strap fixed

==Rev 1.4 [30-May-2008]==

* BGW2xx replaced with the W2SW2001 module
* NAND flash ALE and CLE signals are gated with NAND_CS
* NAND_CS is routed out of CPLD. Added U56, U57, U58

==Rev 1.3a [5-Feb-2008]==

* Routed CPU GPIO[0] directly to CAMI PME#
* Fixed BGW211 boot option to support SPI interface
* Altered SDCLK routing
* Added more powerful PU/PD to CPU GPIO[0] and GPIO[1]
* Added a test point for RST_IN signal
* Connected UCB1400 VADCN to AGND
* Added a pull-up to MMCLK_WIFI
* Routed REG/GNT pair 3 to CAMI instead of pair 0
* Added revision setting RN
* Added SDCS always active for D128
* Added PCM_PWE# option for NOR flash

 

=CM-X270W=
==Rev 1.4 [20-Feb-2009]==
* RTC crystal changed to the new small foot-print type
* CPLD clock bug detected in 1.3 fixed
* Separate audio codec crystal added
* DM9000 reset bug fixed, RC circuit added for proper reset
* Pull-down added to the Bluetooth enable signal

==Rev 1.3 [30-Aug-2008]==
* Wi2Wi WLAN controller added
* CSR Bluetooth controller added
* NAND flash control lines buffered with logic gates

==Rev 1.23 [12-Aug-2008]==
* Missing nets IDEINT_KP_MKIN0_GPIO100, GPIRQ1_KP_MKIN1_GPIO101 corrected

CM-FX6: Linux: Known Issues

2014-01-26T14:52:41Z

Dimitry:

{{IssueCategory|Enlightenment Window Manager|
* If the '''Touchscreen''' profile is selected the '''Settings Panel''' doesn't have '''Profiles''' setting menu. It is not possible to switch the profile.
:'''Workaround :''' Launch the {{cmd|xterm}} from '''Applications->Accessories''' and change the default profile from the command line:
<pre>
enlightenment_remote -default-profile-set Standard-copy
</pre>
}}

[[Category:Linux|Known issues]]
[[Category:CM-FX6|Linux: Known issues]]

CM-FX6: Linux: Known Issues

2014-01-26T14:52:30Z

Dimitry:

{{IssueCategory|Enlightenment Window Manager|
* If the '''Touchscreen''' profile is selected the '''Settings Panel''' doesn't have '''Profiles''' setting menu. It is not possible to switch the profile.
:'''Workaround :''' Launch the {{cmd|xterm}} from '''Applications->Accessories''' and change the default profile from the command line:
<pre>
enlightenment_remote -default-profile-set Standard-copy
</pre>
}}
---
[[Category:Linux|Known issues]]
[[Category:CM-FX6|Linux: Known issues]]

CM-T3730: Hardware: Revision Notes

2014-01-26T14:51:41Z

Dimitry: /* Rev 1.1 [1-Aug-2010] */

==Rev 1.2 [1-Aug-2012]==

* Older CM-T3730 board revisions supported only a micro-SD based onboard storage options. Revision 1.2 of the board supports additional onboard storage options:
*# Onboard 128MB or 512MB NAND flash drive (Precludes onboard micro-SD socket option).
*# Onboard micro-SD slot (Precludes onboard NAND storage option), same as with older board revisions.
* WIFI and Bluetooth circuitry has been changed to support a different WIFI/BT combo SiP (Texas Instruments WiLink6.0 based SiP).
* Placement of several board components has been changed to allow integration of the above changes.

For detailed revision information please see the attached document: [[Media:CM-T3730_PCN-AM20022012.zip|CM-T3730_PCN-AM20022012.zip]]

==Rev 1.1 [1-Aug-2010]==
* Initial release

[[Category:CM-T3730]]

CM-T3730: Hardware: Revision Notes

2014-01-26T14:51:31Z

Dimitry:

CM-A510: Linux: Debian

2010-11-03T11:35:49Z

Dimitry: 1 revision(s)

== Overview ==
The example run-time Linux filesystem image for CM-A510 is based on Debian GNU/Linux Sid. The CompuLab Linux package for CM-A510 includes ready to run NAND flash image, archive of the root filesystem used to create the image and Linux kernel configuration and source code patches.

The default Debian Sid Linux image takes approximately 170 megabytes of flash space, and includes more than 400 software packages. Among them:

* Core system
* Debian package management system
* X11 Windowing System
* Enlightment E17 desktop manager
* Netsurf web browser
* Samba connectivity suite
* SSH and FTP server and client

The [[CM-A510: Linux: Getting started|Getting started with Linux on CM-A510]] page provides a brief introduction on how to install the run-time Linux image. This article describes package structure and peripheral device options specific to the CM-A510.

== CM-A510 specific settings ==

=== Connection and Logging In ===
Use the following usernames and passwords to login:

Account with administrative privileges:
<pre>
User: root
Password: 111111
</pre>

Regular user account:

<pre>
User: user
Password: 111111
</pre>

In addition to these accounts CM-A510 allows anonymous FTP access.
To login into the Linux system, you may use a serial console (ttyS0) at 115200 bps, or connect through the network, or use a keyboard and LCD display (tty1, tty2, tty3).

=== Networking ===
To configure networking, edit ''/etc/network/interfaces'', ''/etc/resolv.conf'', and ''/etc/hostname''. For more information about Debian Linux network configuration, refer to [http://www.debian.org/doc/manuals/reference/ch-gateway.en.html Network configuration] chapter in the [http://www.debian.org/doc/manuals/reference/index.en.html Debian Reference].

=== Consoles ===
Linux file system image is designed to suit different kernel versions and configurations. Therefore, during the operating system startup, consoles at several serial ports and VGA display are enabled. Some of these devices may not be supported either because of kernel versions incompatibilities or because the kernel was not configured to support these devices. When the console is enabled at such device the following or similar message will appear on active console:
INIT: Id "T0" respawning too fast: disabled for 5 minutes
This is not an error message, it is just a warning that can be eliminated by editing ''/etc/inittab'' file.

=== X Windows system ===
CompuLab distribution contains full featured X Windows system with Enlightment window manager.
Before starting X Windows, connect USB mouse and keyboard to the system.
You can run X Windows by typing '''''startx'''''.

== Software Management ==

Debian Linux for CM-A510 image includes all the information required to use Debian package management utilities. You can use [http://linux.die.net/man/8/apt-get apt-get] and [http://www.wlug.org.nz/dpkg(8) dpkg] out of the box.

== See also ==

* [[CM-A510: Linux: Getting started]]
* [[CM-A510: Linux: Kernel]]
* [[Linux: Development for ARM modules]]
* [[Linux: Debian: Minimal ARM filesystem]]

[[Category:Linux|Debian]]
[[Category:CM-A510|Linux: Debian]]

CM-A510: U-Boot: Firmware Update

2010-11-03T11:35:49Z

Dimitry: 1 revision(s)

== CM-A510 Firmware Update process ==

=== Preliminary ===
Some basic steps are needed to be taken in order to update the CM-A510 firmware successfully:
* Make sure to power off the CM-A510 board
* Connect the host PC to the CM-A510 via the serial cable supplied with the CM-A510 evaluation kit.
* Start terminal console application on your host system and configure the following:
** Set the serial port to the COM port to which the serial cable is connected.
** Set baud rate to 115200 bps
** 8 bit per frame
** 1 stop bit
** no parity
** no flow control
* Turn on the CM-A510 system
* The U-Boot boot-loader will start and you will get a command prompt
{{Note| If you have an operating system installed or U-Boot environment configured for auto boot, you will have to stop the auto boot sequence by pressing any key in your terminal application during the start of the boot process!}}
U-Boot firmware can be updated from a [[CM-A510:_U-Boot:_Firmware_Update#Network_TFTP_download|Network TFTP download]], from a [[CM-A510:_U-Boot:_Firmware_Update#USB_flash_drive|USB flash drive]] (with FAT filesystem), or from a [[CM-A510:_U-Boot:_Firmware_Update#Hard Disk|Hard disk]] (with FAT/EXT2 filesystem).
Either method is done from U-Boot command line.

=== Preferred U-Boot Update Option ===
{{Warning| DO NOT RESET OR POWER OFF THE MODULE DURING THE UPDATE PROCESS! DOING SO MAY RESULT IN DISABLED MODULE!}}
In order to use this update method, you need:
* TFTP service/server installed on your host system
* Firmware file should reside in the root directory of TFTP service

To update the U-Boot firmware via tftp download, follow the instructions precisely!
* You can use U-boot {{cmd|dhcp}} command to obtain IP address or manually set {{parameter|ipaddr}} environment variable:
<pre>
> setenv ipaddr <CM-A510 ip address>
</pre>
* Set {{parameter|serverip}} environment variable and save the new environment to SPI flash:
<pre>
> setenv serverip <host ip address>
> saveenv
</pre>
* Download the firmware using the {{cmd|bubt}} command.
** Type: ''bubt <firmware filename>''
** Type: ''y'' to override U-Boot environment with default one
<pre>
CM-A510>> bubt cm-a510-firmware
Using egiga0 device
TFTP from server 10.1.1.209; our IP address is 10.1.1.175
Filename 'cm-a510-firmware'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
######
done
Bytes transferred = 693248 (a9400 hex)
Checking file size: [Done]
Override Env parameters to default? [y/N] y
Unprotecting flash: [Done]
Erasing 0xc0000 - 0xd0000: [Done]
Erasing 0x0 - 0xc0000: [Done]
Writing image to flash: [Done]
Protecting flash: [Done]
</pre>

=== Other U-Boot Update Options ===
==== USB flash drive ====
{{Note| Please, connect your flash drive directly to the base board of the module! Do not use any USB hubs or other separating equipment!}}
To update the U-Boot firmware via USB flash drive, follow the instructions precisely!
* Start the U-Boot USB subsystem and check that your storage device is ready and contains the firmware
** Type: ''usb start''
** Type: ''fatls usb 0'' to ensure you have the firmware in place
<pre>
CM-A510>> usb start
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
CM-A510>> fatls usb 0
693248 cm-a510-firmware

1 file(s), 0 dir(s)
</pre>

* Load the firmware to memory
** Type: ''fatload usb 0 200000 <firmware filename>''

<pre>
CM-A510>> fatload usb 0 200000 cm-a510-firmware
reading cm-a510-firmware

693248 bytes read
</pre>
* Proceed to [[CM-A510: U-Boot: Firmware Update#Update process|Update process]] section

==== Hard Disk ====
To update the U-Boot firmware via Hard Disk, follow the instructions precisely!
* Start the U-Boot SATA subsystem and check that your storage device is ready and contains the firmware
** Type: ''ide reset''
** Type: ''fatls/ext2ls ide 0:1'' to ensure you have the firmware in place
<pre>
CM-A510>> ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
[0 0 0]: Enable DMA mode (6)
Device 0 @ 0 0:
Model: Hitachi HTS543216L9A300 Firm: FB2OC40C Ser#: 090902FB22005CFBBP0A
Type: Hard Disk
Supports 48-bit addressing
Capacity: 152627.8 MB = 149.0 GB (312581808 x 512)

CM-A510>> ext2ls ide 0:1
693248 cm-a510-firmware

1 file(s), 0 dir(s)
</pre>

* Load the firmware to memory
** Type: ''fatload/ext2load ide 0:1 200000 <firmware filename>''

<pre>
CM-A510>> ext2load ide 0:1 200000 cm-a510-firmware
reading cm-a510-firmware

693248 bytes read
</pre>
* Proceed to [[CM-A510: U-Boot: Firmware Update#Update process|Update process]] section

==== Network TFTP download ====
In order to use this update method, you need:
* TFTP service/server installed on your host system
* Firmware file should reside in the root directory of TFTP service
To update the U-Boot firmware via tftp download, follow the instructions precisely!
* Download the firmware to module's memory
** Type: ''tftp 200000 <firmware filename>''
<pre>
CM-A510>> tftp 200000 cm-a510-firmware
Using egiga0 device
TFTP from server 10.1.1.209; our IP address is 10.1.1.175
Filename 'cm-a510-firmware'.
Load address: 0x200000
Loading: #################################################################
#################################################################
######
done
Bytes transferred = 693248 (a9400 hex)
</pre>
* Proceed to [[CM-A510: U-Boot: Firmware Update#Update process|Update process]] section
{{Note| If you get the "''could not establish link''" message, check that your ethernet plugs are in place and try again.}}

==== Update process ====
{{Warning| DO NOT RESET OR POWER OFF THE MODULE DURING THE UPDATE PROCESS! DOING SO MAY RESULT IN DISABLED MODULE!}}

* Flash the firmware to onboard NAND storage
** Type: ''sf probe 0''
** Type: ''sf protect off''
** Type: ''sf erase 0 c0000''
** Type: ''sf write 200000 0 c0000''
<pre>
CM-A510>> sf probe 0
SF: Got idcode ef 40 14 00 00
SF: Detected W25Q32BV with page size 256, total 1048576 bytes
1024 KiB W25Q32BV at 0:0 is now current device
CM-A510>> sf protect off
CM-A510>> sf erase 0 c0000
CM-A510>> sf write 200000 0 c0000
</pre>
* Now you may reset the board

== See also ==

* [[U-Boot quick reference]]
* [[U-Boot images]]
* [http://www.denx.de/wiki/U-Boot/Documentation U-Boot documentation]
* [[CM-A510: Linux: Getting started]]

[[Category:U-Boot]]
[[Category:CM-A510]]

CM-A510: Linux: Kernel

2010-11-03T11:35:49Z

Dimitry: 1 revision(s)

== Overview ==
The CM-A510 Linux kernel provides support for on-board peripherals and abstracts the functionality provided by the hardware. Current support coverage is specified at [http://www.compulab.co.il/a510/html/a510-os-support.htm O/S support coverage map] page. CompuLab provides ready-to-run binary kernel images, and source code of the modifications and additions made to the Linux kernel to work properly with CM-A510 modules.

== Kernel command line ==
The CM-A510 Linux kernel is shipped with built-in command line parameters:
ubi.mtd=1,2048 root=ubi0_0 rootfstype=ubifs useNandHal=4bitecc pm_disable console=ttyS0,115200

The default kernel command line defines primary console, default display settings, root device and root filesystem type.

Setting U-Boot {{parameter|bootargs}} environment variable overrides default kernel command line and can be used to set desired kernel parameters.

== Building kernel for CM-A510 ==
=== Cross-Compiler ===
There are several options for cross-compilation toolchain setup. You can either compile your cross-compiler or use an already built cross-compiler. The cross-compiler should support the ARM embedded-application binary interface ("[http://en.wikipedia.org/wiki/Application_binary_interface#EABI EABI]")
* Pre-built toolchain:
** [http://www.codesourcery.com/sgpp/lite/arm/portal/release324 CodeSourcery]
* Tools for creating cross-compilers:
** [http://ymorin.is-a-geek.org/dokuwiki/projects/crosstool Crosstool-ng]: Builds a cross-compiler from source. Non-distribution specific.
** [http://www.gentoo.org/proj/en/base/embedded/handbook/index.xml?part=1&chap=4 Crossdev]: Gentoo's cross-compiler builder. Needs Gentoo.

=== U-Boot mkimage tool ===
U-Boot {{cmd|mkimage}} utility is required in order to create kernel images that can be loaded by the CM-A510 boot-loader.
You can download pre-built [[media:mkimage.tar.gz|{{cmd|mkimage}} binary]] or build it yourself:
<pre>
mkdir ~/tmp
cd tmp
wget ftp://ftp.denx.de/pub/u-boot/u-boot-latest.tar.bz2
tar -xjvf u-boot-latest.tar.bz2
cd u-boot-2009.08
touch include/config.{h,mk}
make tools
sudo install tools/mkimage /usr/local/bin
</pre>

=== Getting kernel sources ===
There are two ways to get Linux kernel sources that can be used as a baseline for CM-A510 kernel. You can create a copy of linux-2.6.32.y git tree or download a snapshot and extract it. We assume that you have created {{filename|/home/development/cm-a510/kernel}} directory for CM-A510 kernel development.
==== Snapshot download ====
* Download [http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.32.9.tar.bz2 linux-v2.6.32.9] snapshot with your web browser.
* Extract the downloaded archive {{filename|linux-2.6.32.9.tar.bz2}}
<pre>
cd /home/development/cm-a510/kernel
tar xzvf /path/to/downloaded/linux-2.6.32.9.tar.bz2
</pre>
: This will create {{filename|/home/development/cm-a510/kernel/linux-2.6.32.9}} directory containing linux-2.6.32.9 kernel tree.
* Apply the CM-A510 patch
<pre>
cd /home/development/cm-a510/kernel/linux-2.6.32.9
patch -p1 < /path/to/cm-a510-linux/kernel/linux-2.6.32.9-cm-a510.patch
</pre>

==== Git clone ====
* Install [http://git-scm.com/ git] version control system.
* Create a clone of linux-2.6.32.y kernel tree
<pre>
cd /home/development/cm-a510/kernel
git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.32.y.git linux-2.6.32.9
</pre>
* Create a branch for CM-A510 development. The CM-A510 patches are generated vs. tag v2.6.32.9 in the linux-2.6.32.y tree. It is recommended to use exactly the same baseline to avoid merge conflicts.
<pre>
git checkout -b cm-a510-dev v2.6.32.9
</pre>
* Apply the CM-A510 patch
<pre>
cd /home/development/cm_a510/kernel/linux-2.6.32.9
git apply /path/to/cma510-linux/kernel/linux-2.6.32.9-cm-a510.patch
</pre>

=== Building the kernel ===
<pre>
export ARCH=arm
export CROSS_COMPILE=arm-none-linux-eabi-
make cm_a510_defconfig
make menuconfig
make && make uImage && \
INSTALL_MOD_PATH=/home/development/cm-a510/rootfs make modules_install
</pre>

In the example above, the Linux kernel image ({{filename|uImage}}) will be created in {{filename|/home/development/cm-a510/kernel/linux-2.6.32.9/arch/arm/boot}}, and the loadable kernel modules will be installed into the {{filename|/home/development/cm-a510/rootfs/lib/modules}} directory.

Now, if you boot CM-A510 with newly created kernel image and with networked root filesysem at {{filename|/home/development/cm-a510/rootfs/}} the system will be able to properly load kernel modules and you avoid modules versioning problems.

== See also ==
* [[CM-A510: Linux: Getting started]]

[[Category:Linux]]
[[Category:CM-A510]]

CM-A510 Linux

2010-11-03T11:35:48Z

Dimitry: 1 revision(s)

{{summary|
This page contains links to information about Linux kernels, packages and software development for CM-A510 modules.

CompuLab Linux support for CM-A510 includes modifications of [[CM-A510: Linux: Kernel|Linux kernel]] and [[CM-A510: Linux: Debian|'''example''' file system image]] based on Debian Linux. It is possible to use other embedded Linux distributions and environments.

|A510_CM_top_hq.JPG|thumb}}
{{Resources Linux
|* [[CM-A510: Linux: Getting started|Getting started with Linux on CM-A510]]
* [[CM-A510: U-Boot: Firmware Update|U-Boot update for CM-A510]]
|* [[CM-A510: Linux: Kernel|Linux Kernel for CM-A510]]
* [[CM-A510: Linux: Debian|Debian Linux for CM-A510]]
* [[Linux Development for ARM modules]]
* [[Linux: Debian: Minimal ARM filesystem | Minimal Debian ARM filesystem]]
|*[[Support]]
* [[CM-A510: Linux: Known Issues|Known Issues]]
}}

{{ChangelogRss| content=

===== 28-Oct-2010: =====
: Initial release of Debian Linux for CM-A510
}}

[[Category:Linux]]
[[Category:CM-A510]]

CM-A510: Linux: Getting started

2010-11-03T11:35:48Z

Dimitry: 1 revision(s)

== Preparation steps ==
{{Note|It is possible to install Linux on CM-A510 using either an NFS share, USB flash drive or a SATA hard drive. The NFS method is recommended because NFS setup will ease further Linux evaluation and development.}}
* Obtain a PC workstation with serial communication port.
* For installation using NFS install TFTP server on host PC. For Windows machines we recommend [http://tftpd32.jounin.net/ TFTPD32] included in this distribution package.
* Download the [http://www.compulab.co.il/x300/download/x300-linux.zip Linux distribution package for CM-A510] from CompuLab's website . Unzip the package to a directory on your host workstation.
* All image files mentioned below can be found in {{filename|images}} subdirectory
* Copy {{filename|debian-image.ubi}} and {{filename|kernel.img}} from [http://www.compulab.co.il/x300/download/x300-linux.zip Linux distribution package for CM-A510] either to a directory exported through NFS or to a USB flash drive.

== Image installation ==
* Connect the host PC to the CM-A510 via the serial cable supplied with the CM-A510 evaluation kit.
* Start terminal emulation software on your PC using the COM port to which the serial cable is connected. Set baud rate to 115200 bps, 8 bit per frame, 1 stop bit, no parity, no flow control.
* Turn on the CM-A510. The U-Boot boot-loader will start and you will get a command prompt.
*: {{Note|If the boot settings of your CM-A510 are different than default, you may need to press and hold ^C while turning on the CM-A510, in order to get command prompt.}}

=== Installation using NFS ===
* Connect CM-A510 LAN0 Ethernet port (connector P11 on SB-A510) to your local Ethernet
* Make sure that Linux kernel binary image {{filename|kernel.img}}, ramdisk image {{filename|ramdisk.img}} and bootloader script image {{filename|bootscr.img}} are accessible by the TFTP server.
*: - On Windows machine: copy {{filename|kernel.img}}, {{filename|ramdisk.img}} and {{filename|bootscr.img}} to the same folder and point the TFTP server to that folder
*: - On Linux machine: copy {{filename|kernel.img}}, {{filename|ramdisk.img}} and {{filename|bootscr.img}} to TFTP sevrver root directory, usually {{filename|/tftpboot}} or {{filename|/tftproot}}.
* You can use U-boot {{cmd|dhcp}} command to obtain IP address or manually set the {{parameter|ipaddr}} environment variable:
<pre>
> setenv ipaddr <CM-A510 ip address>
</pre>
* Set the {{parameter|serverip}} environment variable and save the new environment to NAND flash:
<pre>
> setenv serverip <host ip address>
> saveenv
</pre>

* Use the following U-boot command to boot Linux on CM-A510:
<pre>
> tftp 100000 bootscr.img && autoscr 100000
</pre>
* During boot the CM-A510 tries to obtain an IP address using DHCP. If you do not have DHCP server you can set the CM-A510 IP address statically using {{cmd|ifconfig}}:
<pre>
$ ifconfig eth0 <ip address>
</pre>
* After the ramdisk image is loaded you will get Linux login prompt. Login as {{parameter|root}} into the system.
* Mount the NFS share containing {{filename|kernel.img}} and {{filename|debian-image.ubi}} image:
<pre>
$ mount <host ip>:/path/to/nfs/share /mnt/net
</pre>
* Format the NAND flash kernel partition and write the kernel image onto it:
<pre>
$ flash_eraseall /dev/mtd0
$ nandwrite -p /dev/mtd0 /mnt/net/kernel.img
</pre>
* Format the NAND flash root filesystem partition and write Debian filesystem image onto it:
<pre>
$ ubiformat /dev/mtd1 -f /mnt/net/debian-image.ubi
</pre>

=== Installation using USB flash drive ===
* Make sure that CM-A510 LAN0 Ethernet port (connector P11 on SB-A510) is '''disconnected'''
* Make sure that Linux kernel binary image {{filename|kernel.img}}, ramdisk image {{filename|ramdisk.img}}, Debian filesystem UBI image {{filename|debian-image.ubi}} and bootloader script image {{filename|bootscr.img}} are present at the root directory of the USB flash drive.
* Connect USB flash drive to SB-A510. Use USB1 port (the lower USB connector of P11 on SB-A510).
* Use the following U-boot command to boot Linux on CM-A510:
<pre>
> usb start
> fatload usb 0:1 100000 bootscr.img
> autoscr 100000
</pre>
* After the ramdisk image is loaded you will get Linux login prompt. Login as {{parameter|root}} into the system.
* The USB flash drive will be automatically mounted under {{filename|/media/sda1}}
* Format the NAND flash kernel partition and write the kernel image onto it:
<pre>
$ flash_eraseall /dev/mtd0
$ nandwrite -p /dev/mtd0 /media/sda1/kernel.img
</pre>
* Format the NAND flash root filesystem partition and write Debian filesystem image onto it:
<pre>
$ ubiformat /dev/mtd1 -f /media/sda1/debian-image.ubi
</pre>

== After Installation ==

<ol>
<li> Reset the CM-A510.</li>
{{Note|If the boot settings of your CM-A510 are different than default, you may need to press and hold ^C while turning the CM-A510 on, in order to get command prompt.}}
<li> To boot Linux, type:
<pre>> setenv bootargs
> nboot 200000 nand0 0; bootm</pre>
{{Caution|The Linux kernel for CM-A510 is shipped with built-in command line parameters that define primary console, default display settings, root device and root filesystem type. Setting U-Boot {{parameter|bootargs}} environment variable overrides default kernel command line!}}
</li>
<li> For Linux automatic boot, type:
<pre>
> setenv bootdelay 3
> setenv bootcmd "nboot 200000 nand0 0; bootm"
> saveenv
> boot
</pre>
{{Note|If you want to get back to U-Boot prompt, hold '''Ctrl-C''' during reset.}}
</li>
</ol>

=== Connection and Logging In ===

Use the following usernames and passwords to login:

Account with administrative privileges:
<pre>
User: root
Password: 111111
</pre>
Regular user account:
<pre>
User: user
Password: 111111
</pre>
In addition to these accounts CM-A510 allows anonymous FTP access.

== See also ==

* [[Linux Development for XScale modules]]
* [[CM-A510: Linux: Kernel | Linux Kernel for CM-A510]]
* [[CM-A510: Linux: Debian | Debian Linux for CM-A510]]
* [[CM-A510: U-Boot: Firmware Update| U-Boot for CM-A510]]

[[Category:Linux]]
[[Category:CM-A510]]

CM-iAM: Hardware: Revision Notes

2010-08-04T14:43:30Z

Dimitry: New page: ==Rev 1.1 [01-Nov-2009]== * Initial public release. ==Rev 1.2 [08-May-2010]== * Audio codec changed to ALC662. * SuperIO changed to Fintek F71808. SuperIO-related GPIOs definition change...

==Rev 1.1 [01-Nov-2009]==
* Initial public release.

==Rev 1.2 [08-May-2010]==
* Audio codec changed to ALC662.
* SuperIO changed to Fintek F71808. SuperIO-related GPIOs definition changed. Refer to reference manual for more information.
* SPARE4(P2-42) is connected to ADC in SuperIO chip (SIO_VIN4).

SBC-FITPC2: Hardware: Revision Notes

2010-05-31T11:28:09Z

Dimitry: 1 revision(s)

=Rev 1.4 [10-Jan-2010]=
* Audio codec is changed to Realtek ALC662 for providing better audio quality and S/PDIF support. 5.1 audio output supported via S/PDIF.
* New audio connectors with sense support and S/PDIF support (with adapter).
* Serial-ATA implementation moved to the main board. HDD interface is now SATA only.
* PATA connector was changed to SATA 12-pin
* WiFI aperture was increased
* Instant power ON support.
* Ethernet controller changed (8111B->8111D) for improving Ethernet performance and design optimization.
* Mechanical support for half mini PCIExpress modules.
* Power supply efficiency improvements.
* USB +5V off in S5 support.
* Provisional FPC connector for LVDS interface support.

=Rev 1.21 [2-Apr-2009]=
* 1st mass-production revision

SBC-FITPC2: Hardware: Revision Notes

2010-03-03T13:33:49Z

Dimitry: /* Rev 1.4 [10-Jan-2010] */

CM-T3530: Hardware: Revision Notes

2010-02-24T11:12:28Z

Dimitry: 1 revision(s)

==Rev 1.0 [1-Nov-2009]==
* Initial release

CM-T3530: Hardware: Revision Notes

2010-02-23T17:37:28Z

Dimitry: New page: ==Rev 1.0 [1-Nov-2009]== * Initial release

==Rev 1.0 [1-Nov-2009]==
* Initial release

BIOS for CM-iAM

2009-12-28T07:43:56Z

Dimitry:

= BIOS Revision Notes =
== 27-Dec-2009 ==
* Added [[#Saving_default_setup|User CMOS defaults (Save CMOS as defaults)]] support
* Added [[#Atom_Pre-boot_Chipset_Configuration_.28APCC.29|APCC (Atom preboot chipset configuration)]] support
* Added [[#Etherlink|Etherlink]] support
* Updated microcode to version 26_18

== 15-Oct-2009 ==
* Initial Release
 

= BIOS Update =
== Updating using external USB ==
=== Preparation ===
# Insert removable disk-on-key into USB slot (ensure that you don't have any other USB mass storage devices connected).
# Run the ImUpdate.exe utility and select as "Target" the desired disk (by letter/size).
# Choose 128MBDOS.img as the "Source image".
# Press the "Start Restore" key to proceed and wait for completion.
# Reinsert a bootable USB device with the preinstalled image
# Copy to the root directory files SFlash16.exe and the BIOS image (biosx.rom-1045k image)

=== Writing the BIOS ===
# Insert a USB disk and power on the system
# Boot to DOS
# Type SFlash16.exe devel34x.rom /Force
# Wait for completion
# Restart

== Updating Using Ethernet Link ==
'''This method of BIOS update is available only if the BIOS version currently installed on the module is dated 27-Dec-2009 or later.'''
* Connect the ethernet port (P4 on SB-iAM baseboard) to the LAN.
* Ensure that no SATA disk is connected to the module.
* The Host PC requires a TFTP server supporting TFTP options and large files (>32Mb). Read the [[#Installation|Etherlink installation]] section for details.
* Set {{Filename|c:\bios_upd\}} as the TFTP server base directory. For Windows TFTPD32 choose "Settings" and browse for "Base directory". Choose standard TFTP security.
* On the host Enter BIOS[F2] , go to the "Advanced" submenu and select "Start EtherLink" .
* Configure EtherLink by pressing 1 (Configure) in the main menu. Carefully read the [[#Etherlink|Etherlink]] section of this document to accomplish the configuration.
* Ensure that the BIOS image name (specified in the 5th line of Etherlink menu or the 6th line of Config menu) is the same as in the {{Filename|c:\bios_upd\}} folder (i.e., "bios.bin" – 1MB image). If not, change the BIOS image name by pressing '6' in the Config menu.
* Return to the Etherlink main menu by pressing 0. Review the TFTP server parameters at the end of the 5th line.
* Start a secure BIOS update by pressing 5 (Download bios image) and then press "Y". Wait for process completion. It takes about 30-40 sec. {{Warning|Do not interrupt the host PC and CM-iAM until the process has been completed!}}
* Return to the main menu by pressing any key.

== After Update ==

Reboot the CM-iAM by pressing the RESET button. Verify that the BIOS revision date has been updated, according to the revision date of the BIOS you installed. The BIOS date is specified in the bottom left-hand corner of the BIOS configuration box displayed upon startup. If the BIOS date has not been changed - you probably missed something during the installation process and are still using the previous version of BIOS. In such a case, please repeat the installation steps correctly.
 

= CompuLab-specific features =
== Saving default setup ==
== Etherlink ==
===Introduction===
EtherLink enables fast binary transfers between a host computer and a target Computer-on-Module, through an Ethernet link. The network communication is based on the TFTP protocol. 
EtherLink can write or read back contents of the NAND flash for the purpose of an o/s package’s installation/duplication, as well as write/read BIOS and Configuration Block. 
Host system: any computer with an Ethernet port and a TFTP server supporting large files (>32MB). 
Target System: CM-iAM 

===Installation===
The EtherLink utility is an integrated part of BIOS and resides in the boot flash device. 
The Host side requires the installation of a TFTP server supporting TFTP options and large files (>32MB). 
Recommended TFTP servers:
* “tftpd32 by Ph.Jounin” TFTP server for a Windows-based host (http://tftpd32.jounin.net/).
* tftpd package for your distribution on a Linux-based host. For example, tftp-server-0.34-1mdk on Mandrake.
{{Note|TFTPD file names are case-sensitive, therefore the file name typed in EtherLink must be in the same case as the file name of the NAND or BIOS image.}}

===Activation===
Interactive activation through BIOS [F2] >>Advanced>> Start EtherLink menu.

===Usage===
The EtherLink menus are self-explanatory. The full menu tree of EtherLink is presented below. The value in brackets specifies the meaning of the parameter which should be provided and its default value.
─┐─1 Configure
├─1.1 Use DHCP to obtain ip address for the device (Yes)
├─1.2 Set static ip address for the device (0.0.0.0)
├─1.3 Set subnet mask for the device (0.0.0.0)
├─1.4 Set ip address of the tftp server (server-ip-address)
├─1.5 Set NAND image file name (NAND-image-filename)
├─1.6 Set BIOS image file name (bios-image-filename)
├─1.7 Set configblock file name (configblock-image-filename)
├─1.8 Set NAND image start sector (00000000h)
├─1.9 Set NAND image end sector (ffffffffh)
└─1.A Enable split (for nand size >2Gb)
──3 Download NAND image (from tftp://server-ip-address/NAND-image-filename - full image)
──4 Upload NAND image (to tftp://server-ip-address/NAND-image-filename - full image)
──5 Download BIOS image (from tftp://server-ip-address/bios-image-filename)
──6 Download configblock (from tftp://server-ip-address/bios-image-filename)
──7 Upload configblock (to tftp://server-ip-address/configblock-image-filename)
──8 Upload BIOS image (to tftp://server-ip-address/configblock-image-filename)
──9 Save configurations
──10 Quit EtherLink and reboot

The operation of the EtherLink includes the following steps:
====Setup network and remote host (Configure menu)====
* The user is asked to use DHCP (automatic) settings or to specify network parameters manually. The relevant parameters are: target system IP address and subnet mask.
{{Note|The utility is not intended to work with different subnets or to make any sort of name resolution; therefore, parameters such as default gateway and DNS server IP are not relevant.}}
* The user has to provide the TFTP server’s IP address and for an image, a filename for each supported image type (menus 1.4 - 1.7).
* The partial NAND Flash image can be specified by the start and end sector parameters. For the download, the remote file image will be updated on the NAND Flash starting from the start sector until the end sector or the end of the remote file. For the upload, the remote file image will be updated with NAND Flash data read from the start sector until the end sector or until the NAND Flash’s last sector (if the end sector is not specified - 0xffffffff) (Menus 1.8 - 1.9).
====Accepting commands====
* Download NAND image - The contents of the remote image file from the TFTP server are written into the NAND Flash.
* Upload NAND image - The contents of the NAND Flash are read back into the remote image file on the TFTP server. For files >2Gb, the “Enable split“ option should be enabled(default) – it will automatically split an image into 2 files adding *_01,*_02 extensions to the file name. The ”Enable split“ option is mutually exclusive with the NAND image start/end custom sector. Disable this option for a 1Gb NAND flash or for files less than 2Gb.
* Download BIOS image (with confirmation) – The BIOS is updated with the contents of the remote BIOS image file from the TFTP server. The remote BIOS image is downloaded twice and only if the images are identical, will the actual update take place. An additional check for image size and contents is performed in order to ensure that the BIOS image is valid for the module (expected image size is about 1MB). The configuration block isn’t changed during this operation.
* Download configblock - The configblock is updated with the contents of the remote configblock image file on the TFTP server. The configblock contains BIOS factory defaults and EtherLink settings and APCC code. The update is performed in two phases like in the BIOS’ case (expected image size is 64 KB).
* Upload configblock - The contents of configblock are read back into the remote configblock image file on the TFTP server.
* Upload BIOS image - The BIOS is read back (including config block) into the remote BIOS image file on the TFTP server.

====Loading/Saving EtherLink configuration====
The EtherLink configurations can be saved into the BIOS configblock for later use.
 At each activalion, the EtherLink performs an automatic load of stored configurations. If the configurations are not found or are corrupted, the following default configurations are used:
Use DHCP for automatic IP address assignment.
Remote TFTP server IP address – 00.00.00.00
Remote NAND image filename – disk.dat
Remote BIOS filename – bios.raw
Remote configblock filename – config.raw
NAND partial image start sector – 00h
NAND partial image end sector – ffffffffh
Enable split - Yes

== Atom Pre-boot Chipset Configuration (APCC) ==
APCC allows the user to configure CM-iAM hardware or to perform any other action before booting the operating system. The user can load his own code into the FWH flash and the BIOS will execute it right before calling the O/S bootstrap routine. When user code is placed in the flash, the module startup sequence is: [Powerup] >> [BIOS] >> ['''APCC code'''] >> [Operating System]
APCC provides an alternative method to run user code prior to O/S launch.
===User Code Definitions===
User code must be in the following format:
{| class="wikitable" border="1"
|-
! Property
! Description
|-
| Mode
| 16-bit real mode. If high memory or flash access is required - use BIOS interrupt calls to access the required locations.
|-
| Stack
| Initialized, 4000 bytes only. If you need a larger stack - define your own.
|-
| Memory organization
| Code is loaded starting from address 9000:0002 (segment:offset, in Hex).
|-
| Available BIOS services
| All:INT13h – disk services, INT10h – console outputetc.
|-
| Code size
| Less than 16383 bytes
|-
| Registers that can be used
| All
|-
| Return from code to BIOS
| Far return (retf)
|}
An example satisfying all the above requirements is provided and can be used as a template for your program.

===Coding Guidelines===
* The standard library functions are not available, since no operating system is running.
* All hardware access code must be written in assembler.
* See the APCC.c file for an example of chipset configuration.
===Building Instructions===
{{Caution|User code must be written in file APCC.c. Do not make changes in gskel.asm unless you are proficient in assembler code.}}
# Insert your source code into APCC.c.
# Open the file MK_BL.BAT and provide the relevant path to the Borland C compiler binaries.
# Run MK_BL.BAT from the command prompt. Ensure that the build process is finished without errors or warnings.
As a result of the build process, you will have two files:
* APCC.bin – compiled executable (<16k)
* userbl.bin – 16kB block patched with the code (used for upload) and padded with FF
===Loading the Binary Image to the CM-iAM===
# Preparin a bootable DOS USB image:
#* Insert a removable disk-on-key into the USB slot (ensure that you don't have any other USB mass storage devices connected)
#* Run the ImUpdate.exe utility and select as the "Target" the desired disk (by letter/size)
#* Choose 128MBDOS.img as the "Source image"
#* Press the "Start Restore" key to proceed and wait for completion
#* Reinsert a bootable USB device with the pre-installed image
# Copy the executable file apcc_up.exe and the prepared userbl.bin into the USB root directory
# For upload, run apcc_up.exe /A userbl.bin and wait for completion
# Reboot the CM-iAM
# Enter bios->”Advanced” and choose “On” for the “Load and run APCC code” and then “Exit Saving Changes”
# Reboot and enjoy
===Removing APCC from the CM-iAM===
You can simply enter bios ->”Exit” and choose “Off” for the “Load and run APCC code” and then “Exit Saving Changes”.
 To remove the APCC code completely, run “apcc_up.exe /R” after booting to DOS.

== Watchdog ==
Enabling the watchdog feature in BIOS allows the monitoring of an O/S boot process and allows rebooting the system in case the boot process hangs.
To enable the watchdog, go to BIOS Setup [F2] >> [Advanced] and you will find a "Watchdog" menu. The timeout should be long enough to ensure that the O/S is booted before the watchdog reboots the system.
{{Caution|The watchdog should be enabled in BIOS only after the watchdog driver is installed in the main O/S running on the module. If the driver is not installed, the system will be rebooted after the timeout expires.}}

== Overclocking ==

CM-X270: Hardware: Revision Notes

2009-12-27T09:33:32Z

Dimitry: CM-X270 Revision Notes moved to CM-X270: Hardware: Revision Notes: Naming convention changed

=CM-X270L=
==Rev 1.6 [1-May-2009]==

* DM9000 reset bug fixed, RC circuit added for proper reset
* MMDAT3_GPIO111 disconnected from W2SW interface

==Rev 1.5 [27-Jun-2008]==

* W2SW2001 reset and boot-strap fixed

==Rev 1.4 [30-May-2008]==

* BGW2xx replaced with the W2SW2001 module
* NAND flash ALE and CLE signals are gated with NAND_CS
* NAND_CS is routed out of CPLD. Added U56, U57, U58

==Rev 1.3a [5-Feb-2008]==

* Routed CPU GPIO[0] directly to CAMI PME#
* Fixed BGW211 boot option to support SPI interface
* Altered SDCLK routing
* Added more powerful PU/PD to CPU GPIO[0] and GPIO[1]
* Added a test point for RST_IN signal
* Connected UCB1400 VADCN to AGND
* Added a pull-up to MMCLK_WIFI
* Routed REG/GNT pair 3 to CAMI instead of pair 0
* Added revision setting RN
* Added SDCS always active for D128
* Added PCM_PWE# option for NOR flash

 

=CM-X270W=
==Rev 1.4 [20-Feb-2009]==
* RTC crystal changed to the new small foot-print type
* CPLD clock bug detected in 1.3 fixed
* Separate audio codec crystal added
* DM9000 reset bug fixed, RC circuit added for proper reset
* Pull-down added to the Bluetooth enable signal

==Rev 1.3 [30-Aug-2008]==
* Wi2Wi WLAN controller added
* CSR Bluetooth controller added
* NAND flash control lines buffered with logic gates

==Rev 1.23 [12-Aug-2008]==
* Missing nets IDEINT_KP_MKIN0_GPIO100, GPIRQ1_KP_MKIN1_GPIO101 corrected

CM-X270 Revision Notes

2009-12-27T09:33:32Z

Dimitry: CM-X270 Revision Notes moved to CM-X270: Hardware: Revision Notes: Naming convention changed

#REDIRECT [[CM-X270: Hardware: Revision Notes]]

CM-iGLX: Hardware: Revision Notes

2009-12-25T09:24:53Z

Dimitry: /* Rev 1.x */

=Rev 2.x=
This revision contains WiFi functionality. The DRAM size is limited to 256MB.

==Rev 2.1 [10-Dec-2008]==
*NAND flash controller changed for more robust and stable storage

==Rev 2.01 [31-Nov-2007]==
*Layout improvement of rev. 2.0 for better manufacturability

==Rev 2.0 [22-Jun-2007]==
*On-board WiFi functionality added
*DISP_EN pin is connected to the P3-9 (SPARE0)
 

=Rev 1.x=
Modules of revision 1.x do not contain WiFi.
 The DRAM size can be up to 512MB in rev. 1.4 only.

==Rev 1.4 [23-Jul-2008]==
* DDR extension up to 512MB (using BGA DDRs)
==Rev 1.31 [15-May-2008]==
* Layout improvement of rev. 1.3

==Rev 1.22 [22-Dec-2007]==
* Layout improvement of rev. 1.21 for better production yield

==Rev 1.3 [19-Dec-2007]==
* NAND flash controller change from IT8907 to SM321
* Memory power supply was redesigned
* AC97_BITCLK was disconnected from the CAMI interface when internal AUDIO assembled
* DISP_EN pin was connected to the P3-9 (SPARE0)
==Rev 1.21 [14-Jun-2007]==
* Power up stability fix

==Rev 1.2 [28-Jan-2007]==
* Audio codec change from USB1400 to WM9715
* P3-105 and P3-101 pins are NC from this revision
* Minor improvements
==Rev 1.1 [16-Jun-2006]==
* Initial release

CM-X270: Hardware: Revision Notes

2009-12-14T14:50:25Z

Dimitry: /* CM-X270W */

Test

2008-07-10T06:31:39Z

Dimitry:

Bacup & restore 1

Why tell me why ?

Because Because Because.

Test

2008-07-09T14:54:01Z

Dimitry:

Bacup & restore 1

Why tell me why ?

Test

2008-07-09T07:54:05Z

Dimitry:

Bacup & restore 1