About Voipac i.mx25 Development kit. Packing List Connector Locations Connecting the components and cables. First Step

Transcription

1

2 Release Date: January 15, 2013

3 About Voipac i.mx25 Development kit Packing List Connector Locations Connecting the components and cables First Step Controlling the Development Kit over serial line Using external monitor (or supplied TFT panel) and USB Keyboard Controlling the Development Kit Over Ethernet (telnet, ssh, ftp, sftp) Open On-Chip Debugger with Voipac`s JTAG Cable under WinXP JTAG Cable Installation How to run Open On-Chip Debugger How to connect to Open On-Chip Debugger using Telnet How to connect to Open On-Chip Debugger using terminal (TeraTerm) How to load bootloader into i.mx25 SODIMM Module (barebox.bin) How to flash zimage and rootfs through the TeraTerm Advanced ToolKit (ATK) with Voipac`s JTAG Cable under WinXP 16 How to load files into i.mx25 SODIMM Module using ATK Configuring the Hardware Using the Flash Tool Flashing Windows CE into i.mx25 SODIMM Module Flashing Linux into i.mx25 SODIMM Module Erasing i.mx25 SODIMM Module using ATK Important and Practical Information E-Fuses Changing MAC Address Mounting Fasteners Products` Life Cycle Phase CE compliance of Voipac products Technical Support

4 About Voipac i.mx25 Development kit Voipac i.mx25 SODIMM Baseboard is designed to be used as development platform for the Voipac cross-compatible i.mx53/i.mx51/i.mx25 SODIMM Modules. Together they create a low power system with excellent MIPS/mW performance allowing deployment in situation where power source is limited. Besides the standard PC peripheral interfaces, the system provides numerous communication channels as well as universal expansion slots and connectors. This QuickGuide shows, how to install JTAG Cable, load Linux using TeraTerm, install Advaced ToolKit (ATK) and load Windows CE or Linux using ATK. All programs run under Windows XP. Packing List COMPONENTS QUANTITY SODIMM Base Board 1 SODIMM Module 1 JTAG cable with serial line 1 Support CD 1 Aluminium case set 1 Serial port cable 1 Crossover Ethernet cable 1 SODIMM socket 1 JTAG pitch compression connector 1 SODIMM Module Printed Schematics 1 Mounting Fastener 2 Quickguide Brochure 1 DATAIMAGE TFT display with touchscreen set (Optional) 1 OPTREX TFT display with touchscreen set (Optional) 1 EDT TFT multitouch capacitive display with mounting ears set (Optional) 1-4-

5 Connector Locations Connecting the components and cables Prepare Basebord and plug in JTAG Cable with Serial line, Ethernet cable and other devices or interfaces you need. IMPORTANT! Be careful when connecting JTAG`s 20 conductor flat cable to the board. Check if the conductor 1 is connected to Pin 1 (Header connector J901) on the board before you turn on the board. -5-

6 First Step The development kit is supplied with pre-installed bootloader, linux kernel and demo file system. The development kit can be controlled over: Controlling the Development Kit over serial line Recommended HW: a) PC with serial port or USB to serial adapter b) Voipac i.mx25 development kit c) Voipac serial cable ( Recommended SW: Serial line terminal (PUTTY, Minicom, Ckermit, Hyperterminal, TeraTerm,...) Default serial port settings: Speed (baud): Data bits: Stop bits: Parity: Flow control: None None Controlling the development kit using TeraTerm -6-

7 Using external monitor (or supplied TFT panel) and USB Keyboard Recommended HW: a) External monitor with DVI or VGA connector (for VGA monitor is required to use DVI to VGA adapter) DATAIMAGE TFT Display (optional, OPTREX TFT Display (optional, EDT TFT Display (optional, b) Voipac i.mx25 development kit Recommended SW: IMPORTANT! External monitor must support one of following resolutions 640x480px, 800x480px or 800x600px. Controlling the development kit using external monitor and USB Keyboard Illustration Photo Controlling the Development Kit over Ethernet (telnet, ssh, ftp, sftp) Recommended HW: a) PC with Ethernet b) Voipac i.mx25 development kit c) Ethernet cable ( Recommended SW: - Telnet client (Telnet, PUTTY, ) - SSH client (SSH,PUTTY, ) - FTP client (FTP, Filezilla, BareFTP,...) - SFTP client (Filezilla, PUTTY, WinSCP,...) -7-

8 IMPORTANT! Demo modules are shipped with empty root password. The default IP address is dynamic and setup by your dhcp server upon boot. SSH, SFTP require root password to be set up. ( passwd command) FTP, SFTP are recommended only for data transfers. (binary mode is recommended) Controlling the development kit using PUTTY Controlling the development kit using WinSCP (Explorer Interface) -8-

9 Open On-Chip Debugger with Voipac`s JTAG Cable under WinXP JTAG Cable Installation 1. Connect JTAG Cable to USB port on your computer. JTAG Cable will be installed automatically and prepared for usage. 2. Download OpenOCD v ( 4. Unzip the file and place to the folder you want to. How to run Open On-Chip Debugger 5. Run OpenOCD using, for examle, Total Commander. Open the folder where is placed the unzipped file. Type in command line: openocd -f vmx25w.cfg. Press [Enter]. 6. Open On-Chip Debugger is running. -9-

10 How to connect to Open On-Chip Debugger using Telnet 7. Clik on Start/Run, type telnet localhost 4444 and click on OK button. Open On-Chip Debugger is running. How to connect to Open On-Chip Debugger using terminal (TeraTerm) 8. Open TeraTerm program, click on File/New Connection, check TCP/IP and type 4444 into TCP port# field. Press OK

11 Open On-Chip Debugger over TeraTerm program is running. 9. Open TeraTerm program, click on File/New Connection, check Serial and choose the port where the JTAG cable is connected to a PC. 10. Click on Setup, choose Serial port and set Baud rate. (115200, 8n1)

12 How to load bootloader into i.mx25 SODIMM Module (barebox.bin) Type commands below using TCP/IP console in two steps (Open On-Chip Debugger connection): Type: reset halt Type: vmx25_init Type: boot (Barebox is loaded into the i.mx25 module SRAM.) (Note) After loading, the barebox is being executed

13 The previously loaded bootloader (barebox.bin) is running in Serial console. (Note) When the module is swithed off, barebox is erased. To flash barebox again, use the same procedure as shown in Step 10. (Note) When the module is swithed off, the MAC address is not erased. It is not required to set MAC address again

14 How to flash zimage and rootfs through the TeraTerm Run TFTP server. Type or paste commands in Serial console to set Ethernet: eth0.ipaddr= eth0.netmask= eth0.gateway= eth0.serverip= Type or paste commands in Serial console to erase Flash: erase /dev/nand0-14 -

15 Type or paste commands separately in Serial console to load files: update barebox tftp folder/barebox vmx25-vpac3.bin update kernel tftp folder/zimage-2_6_35-vmx25-vpac8.bin update rootfs tftp folder/rootfs-ubifs-bb-1-18-vmx-vpac1.bin Final step is to press reset button on baseboard or run 'reset' command Type MAC address (if required) from the module in standard form (00:0d:15:00:XX:XX) and press [Enter]. Type vmx25 login root and press [Enter]

16 Advanced ToolKit (ATK) with Voipac`s JTAG Cable under WinXP How to load files into i.mx25 SODIMM Module using ATK Download and install Advanced ToolKit. Installation requires extracting the files to a temporary folder, and then executing a setup file. The ATK Package can be downloaded from: To install the standard ATK tool: 1. Extract the ATK package and place it in a temporary folder you created. 2. From the folder, execute FSL_ATK_TOOL_WINS_STD_INSTALL_1_70.exe. Rebooting the PC is not required. 3. From the Start Menu, point to Programs, then to Advanced ToolKit, and then click Advanced ToolKit. The Advanced ToolKit configuration screen is displayed. At this point the USB drivers are installed. Installation and uninstallation of USB drivers. (optional) During the install procedure, the USB drivers are installed automatically. If not, you can go to <TOOL_INSTALL_PATH>/windriver/ and run wd_install_4nt.bat to install it manually. To uninstall the USB driver, you can uninstall ATK or go to <TOOL_INSTALL_PATH>/windriver/ and run wd_uninstall_4nt.bat manually. Older version of USB drivers can also be uninstalled with this program. To verify that the USB driver is ready to use, navigate to the Device Manager. An item labeled Jungo should appear in the devices list, similar to the one shown in Figure

17 Configuring the Hardware Hardware configuration requires setting the board switches and then connecting the board to the host computer. Change the H902 jumper (BOOTMODE) on the baseboard to select Serial Boot. By default, jumper pins 1 and 2 are connected together for Direct Boot Direct Boot Serial Boot (Internal Boot) Connecting the Host to the Board using USB follow theese steps: 1. Connect the USB cable to the mini USB port of the board. 2. From the Start Menu, point to Programs, then to Advanced ToolKit, and then click Advanced ToolKit if the program is not running. 3. Select the i.mx CPU that you will use. Version supporting USB is i.mx25_to For Device memory initial (DDR or SDRAM, DDR2 or MDDR), select the memory initialization script to use for the device program. For the i.mx25 TO1.1: Custom Initial File: Click the button to select a custom memory initialization script (the script is in a folder you created when extracting the ATK package). You can also use your own memory initialization file if it has the correct format. 5. In the Host Setting section, select a physical communication channel between PC host and device: Serial Port: Selects the UART as the communication channel. USB: Selects the USB as the communication channel

18 6. To Bypass the settings, use the following information: If selected, the settings on this configuration screen are ignored. Note that the ATK supports the tools independent of the configuration. If cleared, the tool will check the configuration settings, including opening the USB/COM port, and others. 7. Click Next. The Select Advanced Toolkits dialog is displayed. (Note) The Select Advanced Toolkits dialog will not be displayed if the board is not connected successfully. Using the Flash Tool You can use the Flash tool to download, program, dump, and erase images in Flash memory to the i.mx boards. To use the Flash tool, click Flash Tool in the Select Advanced Toolkits screen and then click Go

19 The Flash Tool screen is displayed: In the Operation Type field you can select the Type of Operation to use. Generally, you should check the BBT for Linux images with a Flash Model type of NAND, and check BI Swap for Windows Embedded CE images with a Flash Model type of NAND and a size exceeding 2k per page

20 In the Flash Model field, select the type (this option is unavailable if you selected Download as the Operation Type). Supported Flash memories are: NAND Address from: 0x MMC/SD Address from: 0x Enter the address, where the operation should start, and the size (which is entered only for dumping and erasing operations). In the Image Field, click on Browse button to choose a file to be programmed, downloaded, dumped, or erased. In the Operation Type, Select program/download/dump/erase to start the operation. All options are described in the table: Section Option Description Operation type Download Downloads the image to the address specified, and then executes directly at the downloaded address. Dump Dumps a selected area of Flash device to a file. Program Programs a selected area of Flash from a file. Erase Erases a selected area of Flash. BI Swap Swaps Bad block identifier data, which is one solution for Bad block identifier data in the case that Nand Flash is incompatible with Nand Flash Controller. BBT Bad block Table, which is the table recording all bad block information. Interleave The are two kind of access mode when they are multiple nand flash chips on board, for example, 4 chips on board. LBA Logic Block Address, which indicates that the input address is a logic block address if it is checked. This option is only used on wince platform, for Linux, it should be ignored. Read Back Check Comparing the programmed data with original data in programming process will not be done to speed up the programming speed if this option is un-checked. The option will be visible only when programming option is selected. By default, this option is checked. Flash Device Flash Model Click the down arrow to select the Flash type for the associated board when the Program, Dump, or Erase Flash operations are selected. Flash Lib Device program running on the board that handles the communication with the PC host through the protocol to program/dump/erase the flash. Operation Settings Address The address in the physical memory of the target board where the operation will start. Size Size in bytes for erase and dump operations. Image Image file For downloading operations, indicates the image to be downloaded to RAM. For Flash operations, indicates the image to be downloaded to Flash. For dumping operations, indicates the file that is used to store the dumped content. Process Progress bar Displays the completed percent of the selected operation. Information Log Displays the execution log

21 Flashing procedure consist of erasing and flashing procedure. The Windows CE based system have following partitioning and are using BI Swap to handle bad blocks. Address Size File Note 0x x Directb.nb0 First stage bootloader 0x x Eboot.nb0 Second stage bootloader 0x x NK.nb0 Windows CE 0x Bootloader environment + Persistant storage The Linux based system (including android) have following partitioning and are using BBT to handle bad memory blocks. Address Size File Note 0x x Barebox.bin Kernel bootloader 0x x Bootloader Environment 0x x002A 0000 zimage.bin Linux kernel 0x rootfs.bin Root filesystem Flashing Windows CE into i.mx25 SODIMM Module Flashing first stage bootloader on address 0x :

22 Flashing second stage bootloader on address 0x : Flashing Windows CE image on address 0x :

23 Turn off the board and change the H902 jumper (BOOTMODE) on the baseboard to select Direct Boot bootmode. (Change back the jumper state to connect pins 1 and 2 together.) Open a terminal (Hyperterminal, TerTerm,...) and set serial port: Speed (baud): Data bits: Stop bits: Parity: Flow control: None None Turn on the board and press [SPACE] to stop Windows CE booting. (Bootdelay is defaultly set on 3 seconds.) Boot device is defaultly set on Disabled. Press [5] to set NK from NAND and [S] to save Settings. Press [L] to launch existing Image or Reset the board. Windows CE (eboot - recommended configuration): Initiating image launch in 3 seconds Freescale imx SOC Menu Item [0] IP Address : [1] Set IP Mask : [2] Boot Delay : 3 [3] DHCP : Enabled [4] Reset to Factory Default Configuration [5] Select Boot Device : NK from NAND [6] Set MAC Address : 0-D [7] Format OS NAND Region [8] Format All NAND Regions [9] Bootloader Shell [I] KITL Work Mode : Interrupt [K] KITL Enable Mode : Enable [P] KITL Passive Mode : Disable [S] Save Settings [D] Download Image Now [L] Launch Existing Flash Resident Image Now [E] Select Ether Device : FEC [M] MMC and SD Utilities Selection:

24 Flashing Linux into i.mx25 SODIMM Module Flashing bootloader on address 0x : Flashing Kernel on address 0x :

25 Flashing Root Filesystem on address 0x : Turn off the board and change the H902 jumper (BOOTMODE) on the baseboard to select Direct Boot bootmode. (Change back the jumper state to connect pins 1 and 2 together.) Open a terminal (Hyperterminal, TerTerm,...) and set serial port: Speed (baud): Data bits: Stop bits: Parity: Flow control: None Nonexs Turn on the board and set MAC Address shown on the Module label. (MAC Address must be set in a form including colons: 00:0d:15:00:XX:XX). Press [ENTER]. Linux will start to boot. To stop booting press [SPACE]. (Bootdelay is defaultly set on 3 seconds.) vmx25 login is root

26 Linux (barebox - recommended configuration): barebox (Jan :59:13) Board: Voipac VMX25 SDRAM at 0x : 64MB (512Mb, 13 ROWs, 10 COLs) SDRAM at 0x : 64MB (512Mb, 13 ROWs, 10 COLs) NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 2046 at 0x0ffc0000 Bad eraseblock 2047 at 0x0ffe0000 Malloc space: 0x > 0x81f00000 (size 8 MB) Stack space : 0x816f8000 -> 0x (size 32 kb) envfs: wrong magic on /dev/env0 no valid environment found on /dev/env0. Using default environment running /env/bin/init... No MAC address set for eth0. Please enter the one found on your module: 00:0D:15:00:XX:XX Erasing i.mx25 SODIMM Module using ATK Erasing i.mx25 SODIMM Module with Windows CE: FLASH Erasing Size: MT29F1G08 Adress: 0x Size: 0x MT29F2G08 Adress: 0x Size: x

27 Erasing i.mx25 SODIMM Module with Linux: FLASH Erasing Size: MT29F1G08 Adress: 0x Size: 0x MT29F2G08 Adress: 0x Size: x

28 Important and Practical Information E-Fuses Due to multiple possible boot devices (NAND Flash, microsd/mmc, SPI Flash, I2C EEPROM) present on Voipac i.mx25 Module we deliver the module with e-fuses intact, contrary to KARO Modules with locked e-fuses to boot from NAND interface only. Boot configuration on Voipac i.mx25 modules is selected by pullup resistors R600-R609. (see attached schematics on sheet 6) To locate boot config resistors you can use board assembly file at: To be able to put pullups on boot configuration pins you have to lock e-fuses configuration by programming the e-fuses using barebox bootloader. To dump factory e-fuses configuration use barebox command barebox:/ md -b -s /dev/imx_iim_bank : b 2b d9 f4 b : To write e-fuses use barebox command (example writes MAC address 00:01:02:03:04:05) barebox:/ barebox:/ barebox:/ : : imx_iim_bank0.permanent_write_enable=1 mw -b -d /dev/imx_iim_bank0 0x1a md -b -s /dev/imx_iim_bank b 2b d9 f4 b BE AWARE THAT E-FUSES PROGRAMING IS NON REVERSAL PROCESS!!! WARRANTY CLAIM CAUSED BY IMPROPER E-FUSES PROGRAMMING WILL NOT BE ACCEPTED!!! More information about fuse banks layout you can find in AN3682.pdf document:

29 Changing MAC Address MAC address (indicated on the label of the module) is defaultly written in e-fuses for permanent identifying the module. Customer can change the MAC address using barebox: Stop autoboot and write: edit env/config Scroll down to a last line for changing the MAC address: 00:01:02:03:04:

30 Rewrite the MAC address and and press [CTRL+D] Type saveenv and press [Enter] Reset the board, stop autobooting and type: cat env/config. Newly specified MAC address is saved

31 Mounting Fasteners Fastener on the Baseboard Additional protection of the SODIMM Module fall out of he 200pin socket, ideal for mobile applications. Products` Life Cycle Phase Voipac products are divided into 4 phases: - INTRODUCTION PHASE, approximately the first 6-12 months. The last software issues are still being resolved. Product in this stage is the most suitable for new designs. - ACTIVE PHASE, the first 1-3 years following the product introduction. Product software packages are stable, additional functions, OS and GUI are being released. Product in this stage is suitable for new designs. - MATURITY PHASE, approximately the first 4-6 years after the introduction. Products are shipped in volumes, additional functions additions declines. Product in this stage is no longer recommended for new designs. - EOL PHASE, approximately 7-10 years after the introduction. Used components availability decreases, although product may still be purchased under specific circumstances. The Last Time Buy notification is send to all product users app. 6 months prior to product discontinuation. Components stocking service for discontinued products and manufacturing of further production batches is available. To find out the specific product life cycle phase, visit its product page and check the title color

32 CE compliance of Voipac products The CE label is a mandatory conformity mark for complex electronic devices placed on the market in the European Economic Area and each product sold within the EU needs a CE Certificate of Conformance that ensures that the product conforms to the essential requirements of the applicable EC directives. However, if such complex electronic devices are produced for further processing by the industry, skilled development teams or system integrators, they do not need to observe the above mentioned CE requirements and consequently do not need any identification either. This applies to the Voipac SODIMM sized Computers On Module, because these are not used as stand-alone devices by the general public. Anyway, to make sure that Voipac COMs can be used in CE marked devices, they are designed to obey the EC directives and the standard configuration SBCs manufactured by Voipac are tested for Electromagnetic Interference and operating temperature ranges plugged in corresponding Base Board and mounted in the standard Aluminium case provided to Voipac development kits. Please visit Downloads for the testing reports. TECHNICAL SUPPORT HW & SW support: support@voipac.com Warranty claims: warranty.claim@voipac.com Voipac I.MX53/51/25 development kits come with prepaid 1 month support packages. All of the relevant communication between the customer and Voipac should be executed via s preferably. Response time is up to 48 hours, except state holidays and weekends. Voipac working hours are: 8:00-17:00, Monday - Friday. Before contacting support, please read the following for the basic information about how to work with a development kit: Besides the free-of-charge support, we provide support for your new designs when it comes to the special drivers for the peripherals not included in the Voipac development kits, design of your own base boards, prototyping, or even new products development. Please contact: support@voipac.com for more info

33 Notes

34

35

36 Warranty: VOIPAC TECHNOLOGIES s.r.o. Does Not Bear Responsibility for the Following: Failure of a product resulting from misuse, accident, modification, unsuitable operating environment, or improper maintenance by user Unless otherwise agreed in written, a product does not include technical support and the customer may be able to purchase technical support under separate agreement Any technical or other support provided under warranty by VOIPAC TECHNOLOGIES s.r.o. such as assistance, set-up and installation is provided WITHOUT WARRANTY OF ANY KIND. Disclaimer: VOIPAC TECHNOLOGIES s.r.o. reserves the right to make changes, without notice, to any product, including circuits and/or software described or contained in this datasheet. VOIPAC TECHNOLOGIES s.r.o. assumes no responsibility or liability for the use of the described product(s), conveys no license or title under any patent, copyright, or mask work rights to these products, and makes no representations or warranties that these products are free from patent, copyright, or mask work right infringement, unless otherwise specified. Trademark Acknowledgment: Brand and product names are trademarks or registered trademarks of their respective owners. VOIPAC TECHNOLOGIES s.r.o., M.R. Stefanika 6670/19, Trencin, Slovak Republic