Embedded Linux for module

New images for firmware modules based on TI SDK

Modifications and MB moduleMLOu-boot.imgu-boot-spl.bin.zImagerootfs.tar.gzubi.imgDeviceTree

Module: v4, MB: v2

MLO u-boot.img u-boot-spl.bin zImage rootfs_full.tar.gz ubi.img am335x-mtax.dtb

Firmware documentation


Script to create uploading SD card


The patch for audit to r586 version TISDK


Built-in PHY module

To use the network through a built-in module PHY (TLK106) in Linux it is necessary to replace the configuration file of the device board-support / linux-3.12.10-ti2013.12.01 / arch / arm / boot / dts / am335x-mtax.dts in lined below am335x- mtax_phyinternal.dts:


New images for modules firmware

Module modification MBMLOu-boot.imgu-boot-spl.bin.uImagerootfs.tar.gzubi.imgАрхив с прошивками

Module: v4, MB:V2

Network work for module with PHY is corrected

MLO u-boot.img u-boot-spl.bin uImage rootfs_full.tar.gz ubi_full.img am335xv4_MBv2_r564.tar.gz

SDK installation script version (1.9GB)


The patch for the audit to the r564 version TISDK


Script to create loading SD card


Images for firmware modules (SDK v.

Module modification and MB

MLOu-boot.imgu-boot-spl.bin.uImagerootfs.tar.gzubi.imgFiles with firmware
Module::v4, MB:v2, ОЗУ:512MB MLO u-boot.img u-boot-spl.bin uImage rootfs.tar.gz ubi.img am335xv4_512M_MBv2.tar.gz
Module: v4, MB:v2, ОЗУ:256MB MLO u-boot.img u-boot-spl.bin uImage rootfs.tar.gz ubi.img am335xv4_256M_MBv2.tar.gz
Module: v1, MB:v1, ОЗУ:256MB MLO u-boot.img u-boot-spl.bin uImage rootfs.tar.gz ubi.img am335xv1_MBv1.tar.gz
Module: v4, MB:v1, ОЗУ:512MB MLO u-boot.img u-boot-spl.bin uImage rootfs.tar.gz ubi.img  
Module: v4, MB:v2, ОЗУ:256MB(300MHz) MLO u-boot.img u-boot-spl.bin        

u-Boot download via UART

1. Make sure that the "CCCCCC" symbols are displayed in the terminal program (minicom will be only considered in Linux) after power on. If this does not happen, you should set the loading priority to from UART0 mode (eg jumper XBOOT1 (2-3) or the compound through a resistor X3: 29 and X3: 80 - 00011 - UART0, SPI0, XIP, MMC0) before turning on the power.

2. Turn off the power of the module.

3. In mini com adjust the buffer size (1K) for transmission over XMODEM / YMODEM: Ctrl-a o, File transfer protocols, and to register the team and sx -vv -k sb -vv -k.

4. Pass on the loader starter Xmodem: Ctrl-a, s, xmodem choose u-boot-spl.bin file (double-spaced selected and goes through catalogs) and hit enter.

5. Turning on the power, and expect to see a running percentage download

6. After a successful uploadROM code runs the startup boot loader, which expects u-Boot loader on Ymodem protocol.

7. After the second "CCCC" send on Ymodem: Ctrl-a, s, ymodem choose u-boot.img file and press enter.

8. After successful up load you see a prompt U-Boot #

Downloading images via UART and NAND firmware

NAND flash erasure:
nand erase 0 0x780000

Loading MLO on UART and firmware in NAND:
loady 0x81000000

Ctrl+a, s, y modem, choose MLO:
nand write 0x81000000 0x0 0x020000;
nand write 0x81000000 0x20000 0x020000;
nand write 0x81000000 0x40000 0x020000;
nand write 0x81000000 0x60000 0x020000;

Download u-boot.img on UART and firmware in NAND:
loady 0x81000000

Ctrl+a, s, y modem, choose file u-boot.img
nand write 0x81000000 0x80000 0x200000;

Loading uImage for UART and firmware in NAND:
loady 0x81000000 Ctrl+a, s, y modem, choose file uImage
nand write 0x81000000 0x280000 0x500000;

After reset and NAND uploading order selection Linux root file ubi / ubifs system in NAND must be loaded.

Loading images from SD card and NAND firmware
loady 0x81000000 Ctrl+a, s, y modem, delect a file ubi.img
nand write 0x81000000 0x780000 ${filesize};

Firmware recording for AM335x on SD card (for Linux users).

1. Insert micro SD card into your computer. 2. Run dmesg utility to make sure that the card is defined and available in the system. Console output (last line) should be similar to:

	[438112.009168] sd 25:0:0:0: Attached scsi generic sg4 type 0
  [438112.012077] sd 25:0:0:0: [sde] 7716864 512-byte logical blocks: (3.95 GB/3.67 GiB)
  [438112.012624] sd 25:0:0:0: [sde] Write Protect is off
  [438112.012628] sd 25:0:0:0: [sde] Mode Sense: 03 00 00 00
  [438112.013168] sd 25:0:0:0: [sde] No Caching mode page present
  [438112.013171] sd 25:0:0:0: [sde] Assuming drive cache: write through
  [438112.016163] sd 25:0:0:0: [sde] No Caching mode page present
  [438112.016167] sd 25:0:0:0: [sde] Assuming drive cache: write through

This finding means that the card is available in the system through the device file / dev / sde.

3. To format the SD card, create 2 partitions and copy the files can run the script:

sudo ./mksd-ti335x.sh /dev/sde MLO u-boot.imguImage rootfs.tar.gz

Options to run the script:

  • SD card device file, eg / dev / sde;
  • Binary image of MLO loader;
  • Binary image of the bootloader u-bool.img;
  • Image of the Linux core - u-Image;
  • Archive of the root file system rootfs.tar.gz

In addition to the given file parameters the follow in gare required files to prepare the SD card:

  • pointercal - to skip the touch screen calibration utility;
  • ubi.img - ubi image for flashing into the NAND

As a result of the script work 2 partitions are created in the memory card with FAT and ext3 file systems. The first file should contain:

  • MLO
  • ubi.img
  • u-boot.img
  • uImage
  • pointercal

On the second section root file system is created from a firmware backup rootfs.tar.gz.To complete firmware image of the root file system can be used rootfs_full.tar.gz

Created SD card can be removed from the computer, insert into the connector on the motherboard MTAX-MB. If you specify uploading method from SD card (for example a jumper XBOOT3 (1-2) or the compound through a resistor X3: 31 and X5: 38) and supply power, Linux OS should be uploaded from memory card.

Firmware images.
All imsges: https://drive.google.com/open?id=0B1nl8q4_-tA-UWJDNk9jVVAtNm8

Firmware images in NAND flash while uploading from SD card.

1. Connect the USB cable into the connector XUSBFT1, insert the SD card and apply power. Run a terminal program (TerraTerm, PUTTY, minicom) and configured to work with the appropriate computer serial port. For Linux, run:

minicom -D /dev/ttyUSB1.

The serial port settings: 115200n8 (press Ctrl + a, s, and choose the appropriate settings).

2. Press ENTER to stop the automatic download of Linux and log in u-Bootcommand mode.

3. Inthe console u-Boot execute a command to erase NAND flash.

nand erase.chip

4. Run the command for the firmware binary image in NAND:
mmc rescan;
fatload mmc 0 0x81000000 MLO;
nand write 0x81000000 0x0 ${filesize};
nand write 0x81000000 0x20000 ${filesize};
nand write 0x81000000 0x40000 ${filesize};
nand write 0x81000000 0x60000 ${filesize};
fatload mmc 0 0x81000000 u-boot.img;
nand write 0x81000000 0x80000 ${filesize};
fatload mmc 0 0x81000000 uImage;
nand write 0x81000000 0x280000 ${filesize};

for v7.0:

mmc rescan
load mmc 0:2 0x81000000 /boot/MLO
nand write 0x81000000 NAND.SPL ${filesize}
nand write 0x81000000 NAND.SPL.backup1 ${filesize}
nand write 0x81000000 NAND.SPL.backup2 ${filesize}
nand write 0x81000000 NAND.SPL.backup3 ${filesize}
load mmc 0:2 0x81000000 /boot/u-boot.img
nand write 0x81000000 NAND.u-boot ${filesize}
load mmc 0:2 0x81000000 /boot/am335x-mtax.dtb
nand write 0x81000000 NAND.u-boot-spl-os ${filesize}
load mmc 0:2 0x81000000 /boot/zImage
nand write 0x81000000 NAND.kernel ${filesize}

5. Firmware UBI root file system:
load mmc 0:2 0x81000000 ubi.img
nand write 0x81000000 NAND.file-system ${filesize}

Note: When downloading files over the network using tftpboot is necessary to specify the size of files without explicitly ${filesize}.

6. After reloading Linux should upload from NAND, if the appropriate loading modeis chosen.

Uploading log from NAND

Upload images over the network and firmware in NAND (flash recovery on a network)

1. Set the boot from EMAC1 (if connected to EMAC1 PHY controller MII mode, such as TLK106 module MTAX-SOM-AM335x or debug board MTAX-MB-AM335x-v2, but not both simultaneously). To do this, you can choose the loading order SYSBOOT = b01011 (USB0-NAND-SPI0-MMC0).

2. Configure eth1 interface on the Linux PC, eg - Static IP:

3. Install and configure the tftp server / tftpboot directory as the default directory, such as file /etc/xinetd.d/tftp:

	service tftp
  protocol = udp
  port = 69
  socket_type = dgram
  wait = yes
  user = nobody
  server = /usr/sbin/in.tftpd
  server_args = /tftpboot
  disable = no

When using the TI SDK and run the setup.sh script tftp server above settings are automatically set.

4. Set the dhcp-server (isc-dhcp-server package) and set up:

  • In the file / etc / default / isc-dhcp-server prescribe interfaces for DHCP:
	INTERFACES="usb0 usb1 eth1"
  • In /etc/dhcp/dhcpd.conf register DHCPfileconfiguration for eth1 and download files on the tftp.
	subnet netmask {
  interface eth1;
  range dynamic-bootp;
  option subnet-mask;
  option broadcast-address;
  option routers;
  option root-path "/tftpboot";
  if substring (option vendor-class-identifier, 0, 10) = "DM814x ROM" {
  filename "u-boot-spl.bin";
  # Check for PG2.0, CPSW or USB RNDIS
  } elsif substring (option vendor-class-identifier, 0, 10) = "AM335x ROM" {
    filename "u-boot-spl.bin.restore";
  } elsif substring (option vendor-class-identifier, 0, 17) = "AM335x U-Boot SPL" {
    filename "u-boot.img.restore";
  } else {
    filename "uImage";

5. Run dhcp server:

	sudo service isc-dhcp-server start

6. Copy files to directory /tftpboot:

  • u-boot-spl.bin.restore (u-boot-spl image, compiled with support for uploading EMAC1)
  • u-boot.img.restore (image u-boot.img, compiled with support for uploading and EMAC1 debrick.scr)
  • debrick.scr (script to download images of MLO, u-boot.img, uImage, ubi.img and firmware in NAND)
  • MLO, u-boot.img, uImage, ubi.img - images for recording in NAND.

7. Turn on the power and wait for the boot firmware and all the images.

8. The following steps can be done to prepare the script restore its image over the network:

  • Create a file debrick.txt with u-boot commands, for example:
	# erase NAND
nand erase.chip
# get MLO
tftp 0x81000000 MLO
nand write 0x81000000 0x0 0x20000
nand write 0x81000000 0x20000 0x20000
nand write 0x81000000 0x40000 0x20000
nand write 0x81000000 0x60000 0x20000
# get u-boot.img
tftp 0x81000000 u-boot.img
# write the whole block (4*MLO + u-boot.img) to NAND
nand write 0x81000000 0x80000 ${filesize}
# get uImage
tftp 0x81000000 uImage
nand write 0x81000000 0x280000 ${filesize}
# get ubi.img
tftp 0x81000000 ubi.img
nand write 0x81000000 0x780000 ${filesize}  

create an image of it, clear for u-boot:

mkimage -A arm -O U-Boot -C none -T script -d debrick.txt debrick.scr

Perhaps before mkimagethere will be a need to specify the full path, eg/home/user/ti-sdk-am335x-evm-

WIFI Setting rezhimet AP (access point)

1. Download the configuration file ( ap.cfg.gz). Unpack it and burn on the support available from the Linux on board.

2. Run the command to apply the configuration:

unifi_config –dev /dev/unifiudi1 –setap_cfg /home/root/ap.cfg

3. Generate KEY, such as "88888888" password and the access point "the testpoint" run:

wpa_passphrase testpoint 88888888

The result is


4. Enter the command to WIFI transfer to AP mode:

iwpriv wlan0 AP_SET_CFG ASCII_CMD=AP_CFG,SSID=«testpoint»,SEC=«wpa2-psk»,KEY=fa9c7090ea11704cec8e01fd5a06148c21f6c7dd0aff38ab2082155884af2651,


5. Run:iwpriv wlan0 AP_BSS_START

(to stop:iwpriv wlan0 AP_BSS_STOP)

6. On your computer find network"the testpoint" and enter the password "88888888".

Development and debugging Linux applications modules MTAX-SOM-AM335x

Copyright © 2011–2018 AXONIM Devices
Order products

Fill in the form to order

Your name: