wiki2773: Nto640FreescaleI.mx27AdsTrunkReleasenotes (Version 5) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Notes of the QNX 6.4.0 BSP for Freescale i.MX27 ADS Trunk#System requirements#Target system#
Host development system#
System layout#The tables below depict the memory layout for the image and for the flash. Memory layout
The interrupt vector table can be found in the buildfile located at src/hardware/startup/boards/mx27ads/build
Getting Started#Step 1: Connect your hardware#1. Set up the board. Refer to the manual for the correct default jumper settings to use.
Step 2: Build the BSP#You can build a BSP OS image from the source code or the binary components contained in a BSP package. For instructions about building a BSP OS image, please refer to the chapter Working with a BSP in the Building Embedded Systems manual.Step 3: Transfer the OS image to the target using the ROM monitor#On your host machine, start your favorite terminal program with these settings:
1. Make sure the host machine is capable of handling TFTP requests (see the inetd documentation for details). You should see output similar to the following: RedBoot(tm) bootstrap and debug environment [ROMRAM] Non-certified release, version FSL 200749 - built 17:00:12, Dec 13 2007 Platform: MX27 ADS/EVB (Freescale i.MX27 based) PASS 2.1 [x32 SDR] Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc. RAM: 0x00000000-0x07f00000, [0x00025260-0x07ed1000] available FLASH: 0xc0000000 - 0xc2000000, 256 blocks of 0x00020000 bytes each. RedBoot> Step 4: Setting up the environment#1. At the RedBoot prompt, issue the following command to change the current environment:fconfig The current configurations will be displayed; change the configuration if you want. Run script at boot: false Use BOOTP for network configuration: false Gateway IP address: 10.42.96.1 Local IP address: 10.42.103.53 Local IP address mask: 255.255.240.0 Default server IP address: 10.42.98.230 Board specifics: 0 Console baud rate: 115200 Set eth0 network hardware address [MAC]: true eth0 network hardware address [MAC]: 0x40:0x00:0x00:0xEA:0x18:0xF0 Set FEC network hardware address [MAC]: false GDB connection port: 9000 Force console for special debug messages: false Network debug at boot time: false Default network device: cs8900a_eth0 alias/bsp_tag: BSP_VER=rel3 Update RedBoot non-volatile configuration - continue (y/n)? Typey to accept the new configuration; RedBoot will write the new configuration to the flash. 2. Once the above setup is complete, you can run the load command at the RedBoot prompt to download the image: load -r -b 0x00100000 /images/ifs-mx27.raw RedBoot will display the following message and start downloading the boot image: Using default protocol (TFTP) If the image is successfully loaded, you will see the following message from the RedBoot prompt: Raw file loaded 0x00100000-0x002cbef7, assumed entry at 0x00100000 3. Type: run 0x00100000 You should now see the QNX Neutrino welcome message on your terminal screen: Welcome to Neutrino on the MX27ADS (ARM 926 core) Board Creating a flash partition#1. Enter the following command to start the NOR flash filesystem driver:devf-mx31ads -s0xc0000000,32M 2. Erase the flash:
Because the ROM monitor and the QNX boot image are in the flash, you may not want to erase them. Use the -l (length) and -o (offset) options to avoid these areas. flashctl -p/dev/fs0 -o4M -l16M -ve 3. Format the partition: flashctl -p/dev/fs0p0 -o4M -l16M -vf 4. Slay, then restart the driver: slay devf-mx31ads You should now have a /fs0p0 directory which you can copy files to.
Driver Command Summary #The following table summarizes the commands to launch the various drivers.
Some of the following drivers are commented out in the default buildfile. To use the drivers in the target hardware, you'll need to uncomment them in your buildfile, rebuild the image, and load the image into the board. Startup#Command: startup-mx21ads [startup-options] Some modules are not enabled by default on power up, so you need to use command-line options to startup to enable them. These options must be passed before any other startup options.
ETFS flash (NAND):#Command to run the ETFS NAND flash driver (64 MB): You need to use the -e option the first time you start NAND flash driver. To erase and format the NAND flash partition: etfsctl -d /dev/etfs2 -S -e You should slay and restart the driver, after which you should have the mountpoint /fs/etfs/, which you can use to copy files to. USB host :#USB can be run either on the USB HOST Serial Interface (FS/LS) or the USB HOST ULPI Interface (HS), which are referred to as Host 1 and Host 2 respectively. To use Host 1 FS:
The USB host port is J8. To use Host 2 HS:
The USB host port is J7. You will want to include class drivers, such as devb-umass in order to make use of attached USB devices.
Fixed Issues for this BSP #The following issues have been addresseed with the NTO 6.4.0 1.0.0 release:
Known Issues for this BSP#
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||