Ts-7370 manual

Technologic Systems provides complete documentation for our mature products, including manuals, schematics, mechanical drawings, etc. The most recent documentation files are always made available through our website. If you don't find the documentation you are looking for, contact support for more information. Also, please make sure to visit our Embedded Systems Support webpage, our official documentation , and join our official Developers Forum.

We use cookies to ensure you get the best experience. Opt out. Schematic Manual. SD card pre-installed with standard Debian Linux distribution.

Linux "bootload" program allows booting of Linux kernels and other OS' from within Linux itself. Quantity 10 female-to-female 6-inch red jumper wires for use with 0. To save your changes permanently, type "save" at the fastboot prompt. Technologic Systems offers a null modem cable with both 25 pin and 9 pin connectors at each end as part number CB Use a null modem cable to connect the ARM system to your workstation.

There are many serial clients for Linux, but 3 simple ones would be picocom, screen, and minicom. Linux has a few applications capable of connecting to the board over serial. You can use any of these clients that may be installed or available in your workstation's package manager:. Putty is a small simple client available for download here. Open up Device Manager to determine your console port.

See the putty configuration image for more details. Connect a regulated VDC, 1A minimum power source on the power input connector. Please note the polarity printed on the board. The boot messages, by default, are all displayed on COM1 at baud. The board will also answer telnet connections to IP address Upon bootup, The board will boot within 1.

The default fastboot shell has available several standard Linux commands through the "busybox" program. Technologic Systems has made several modifications to the busybox source code to keep bootup as fast and simple as possible.

The modified source code is available to Technologic Systems customers. Upon bootup, you should see out of your serial port when booting from a properly formatted SD card:. This is a busybox shell which presents you with a very minimalistic system.

This filesystem is loaded into memory, so none of the changes will be saved unless you type 'save', or mount a filesystem as read write. This can also provide a simple mechanism for running your application in an entirely read only environment.

The linuxrc script will be the first thing executed as soon as the kernel is loaded. It will also add common paths and load libraries from the Debian system. Many of the Debian applications will work by default.

If an application relies on certain paths being in certain places, or running services, you should instead boot to Debian to run them. This shell when started on the COM port is what is blocking a Debian boot. If you close it by typing 'exit', the boot process will continue.

If you are connected through telnet, this will instead open up its own instance of the shell so typing 'exit' will only end that session. Through any connection method you can relink the linuxrc script to always boot into Debian.

To use any of the other boot scripts, you can simply replace 'linuxrc-sdroot' with the script name mentioned above. It reads the first bytes of the SD card, and jumps execution to the binary there. The code in the MBR looks at the partition table for the first partition of type 0xda, and loads this to memory 0x The second partition of type 0xda is loaded into memory at 0x This also sets up the ATAGS which are used by the kernel to identify the hardware, and so it knows where to load the initrd.

After that it jumps into execution at 0x to the kernel. This is so that it executes the 'linuxrc' script as soon as it mounts the initrd. If backing up on a separate workstation, keep in mind Windows does not have direct block device support needed to write these images. You will also need to determine the SD card device. If you are backing up directly on the board you will likely need to use some kind of offboard storage like a thumbdrive or external hard drive.

You can find the latest SD card image here. Make sure you decompress the image first before writing. If you botch a modification during development on the TS it is easy to recover it to a previous or factory state.

In order to mount the fourth partition which contains the Debian root filesystem, the host Linux machine will need the "jfsutils" package which can be installed using. Alternatively, you may also restore the SD card to the state in which you received it. Power on the TS which will then boot from SD. Within a few seconds the board will have booted to a fastboot prompt from the SD card. Type "exit" to boot to the SD card version of Linux. After booting in about 1.

Standard Linux utilities are provided by the busybox program. Type 'help' for a list of provided utilities. A shell subroutine file, ts This file is executed at startup and defines several convenient functions. Type 'tshelp' for a list of these features. This can be used from within the Debian environment as well by exporting it with the command ". Full descriptions of each are detailed below. Other programs that use serial ports to transfer should work as well.

You can login as root or any valid user previously created from the useradd utility. With the SD card, a user named "eclipse" is present with password "eclipse". USB memory devices need no extra accessory to connect to the host PC.

The flash memory devices can then be hot swapped inserted or removed without rebooting the host PC. Using the Zmodem protocol not installed by default to send files to and from the TS SBC is simple and straightforward. The only requirement is a terminal emulation program that supports Zmodem, and virtually all do. If you are using Windows 95 or later for your development work, the HyperTerminal accessory works well. To download a file to the TS from your host PC, execute lrz at the Linux command line on the TS while using console-redirection from within your terminal emulator and begin the transfer with your terminal emulator.

In HyperTerminal, this is 'Send File Many emulators, HyperTerminal among them, will automatically begin the transfer themselves. Occasionally there may be errors in transmission due to background operations.

This is not a problem -- Zmodem uses very accurate CRC checks to detect errors and simply resends bad data. Once the file transfer is complete the file is completely error free. For best results when using HyperTerminal, the hardware handshaking must be enabled in HyperTerminal. Although this method can be a bit more involved, it's the fastest and easiest way to transfer files to and from a development PC.

Basically, setup a development PC running Linux and set it up as an NFS server to share a directory see online documentation for accomplishing this such as this one on sourceforge. You can even work directly in the folder. The command to mount an NFS server would look similar to this:. Linux applications run in a protected and separate environment where they can do no damage to either the kernel or other applications running simultaneously.

This protected environment does not allow arbitrary manipulation of hardware registers by default. When programming Linux applications that handle hardware devices on the TSXX, it is important to understand the Memory Map of the EP processor and additional hardware features. Each hardware device or functional component has its reserved memory address space, where the specific management registers are located. Device drivers implementation is mostly reading and writing operations to specific memory registers.

This is accomplished from the Kernel space through straight access to the physical memory. The resulting device driver provides high level procedures to the user so that one is able to talk to the hardware without knowing memory map, bits and such. It is also possible to talk to hardware devices from user space. In doing so, one does not have to be aware of the Linux Kernel development process.

For instance, to set up access to the GPIO registers at 0x12c on the TS, the following snippet of C code is provided as an example:. An example program has been made available which demonstrates this principle by gathering data from the buffered inputs of the TS here: getbufin. Although working with the TS Linux is identical in most ways to working with a PC version Linux, one does need to be aware of some driver differences.

The SD card has a slightly different partition scheme to facilitate usage on a host PC. Note that the MBR installed by default on the TS contains a byte bootloader program that loads the initial power-on kernel and initrd from the first and second partitions. Our supported OS is Debian 4. You can find our provided distributions here. The typical way of doing Linux development on the TS is actually on the board itself.

By running the full version of Linux and not scaled-down microcontroller project OS's such as ucLinux , the TS can run the entire suite of applications contained in the Debian Linux distribution including the compilers.

All too often, open-source projects do not anticipate the possibility of cross-compilation in their build systems, leaving issues for the system integrator to resolve. One can still use cross-compilers hosted on just about any platform if there is a specific need. When using the Debian Linux file system, adding new packages and removing undesired ones is done all through Debian's package management.

With Debian, one can easily install and remove software packages. For a quick demonstration of how easy it is to remove and install programs with Debian, try the following commands:. Visit the Debian home page for further information, since a full in-depth discussion on Debian is outside the scope of this document. After the desired Linux Kernel is loaded and executed, the file system loads and networking, logging, Apache web server, etc.

When the login prompt is displayed, type "root" to login, with no password. A Bash login prompt will then appear. If you are new to Linux, www. If you need more control over the driver configuration, you can skip the plug and play feature and use the module parameters. Get more information about the Lincan driver using the modinfo tool. By using more than one TS-CAN1 card on a single system, you can set up a CAN network for testing and development with a single target embedded hardware.

The Lincan device driver supports up to 8 CAN boards. You can load a single driver to give support to all cards by setting the appropriate parameters on driver loading. The parameters of the driver can be extended by using index commas.

For example, to set up the Lincan driver to support 3 different CAN boards and use plug and play functionality:. If you want to set specific values to the other parameters, it is possible to skip the plug and play functionality by assigning values others than Notice that the -1 value tells the driver to use plug and play or default values to the specific parameter. The same methodology can be applied for IRQ and baudrate configuration.

More More. Page actions Read View source History.