Release Notes for the QNX Neutrino 6.4.0 BSP for Freescale Lite5200B and Media5200 1.0.0#

System requirements#

• QNX Neutrino RTOS 6.4.0
• Board version: Lite5200B or Media5200
• MPC5200B processor (based on MPC603e series)
• 32 MB flash on the Lite5200B / 64 MB flash on Media5200

Host development system

• QNX Momentics 6.4.0
• Terminal emulation program (Qtalk, Momentics IDE Terminal, tip, HyperTerminal, etc.)
• RS-232 serial port and serial cable, or a USB-to-serial cable
• Ethernet link
• For other system requirements (e.g. disk, RAM), see the installation notes for QNX Momentics.

System Layout#

Memory layout

Flash layout for Lite5200B (U-Boot view)

Flash layout for Lite5200B (IPL view)

Flash layout for Media5200 (U-Boot or IPL view)

The interrupt vector table can be found in the buildfile located at src/hardware/startup/boards/mgt5200B/build

Getting Started#

Starting Neutrino#

Step 1: 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.

Note: This BSP will build a default OS image for the Freescale Media5200 board. If you need to build an OS image for the Freescale Lite5200B, you need to change the buildfile. The buildfile has commented-out sections for the Lite5200B. Simply uncomment them and comment out the Media5200 sections.

Step 2: Connect your hardware

1. Setup the board. Refer to the manual for the correct default jumper settings to use.
2. Connect one end of the serial NULL-modem cable to the J3 serial port.
3. Connect the other end of the serial NULL-modem cable to the first available serial port of your host machine (e.g. ser1 on a Neutrino host).
4. Connect an RJ-45 Ethernet cable to J6 (100/10 Mbit Ethernet RJ-45 connector).
5. Connect the other end of the Ethernet cable to the Ethernet network where a TFTP server (which you'll use to transfer the boot image) exists.

On your host machine, start your favourite terminal program with these settings:

• Baud: 115200
• Bits: 8
• Stop bits: 1
• Parity: none

Then, apply power to the target board.

You should see output similar to the following if you are using the Lite5200B or Media5200:

U-Boot 1.1.3 (Jul 11 2005 - 16:46:38)

CPU:   MPC5200 v2.1 at 462 MHz
       Bus 132 MHz, IPB 132 MHz, PCI 33 MHz
Board: Freescale MPC5200 (Lite5200B)
I2C:   85 kHz, ready
DRAM:  256 MB
FLASH: 32 MB
PCI:   Bus Dev VenId DevId Class Int
        00  1a  1057  5809  0680  00
In:    serial
Out:   serial
Err:   serial
Net:   FEC ETHERNET
IDE:   Bus 0: OK
  Device 0: not available
  Device 1: not available

Type "run flash_nfs" to mount root filesystem over NFS

Hit any key to stop autoboot:  0
=>

Step 3: Setup the environment

1. At the U-boot prompt, issue the following command to view the current environment:
   printenv
2. Set the baud rate and follow the instructions:
   setenv baudrate 115200
3. Set the local IP address (replace x.x.x.x with the desired IP address):
   setenv ipaddr x.x.x.x
4. Set the IP address for your host TFTP server (replace x.x.x.x with the desired IP address):
   setenv serverip x.x.x.x
5. Set the gateway address (replace x.x.x.x with the desired IP address):
   setenv gatewayip x.x.x.x
6. Specify the image or fullpath to the OS image (on the host machine):
   setenv bootfile /full_path_to_image/image.raw
7. Once the above setup is complete, save the environment to the onboard EEPROM:
   saveenv
8. Copy the image from your host to the target:
   tftpboot loadaddr
   At this point you should see the ROM monitor download the boot image, indicated by a series of dots.
9. Type:
   go loadaddr

You should now see the QNX Neutrino welcome message on your terminal screen:

Welcome to QNX Neutrino 6.3 on the Freescale Lite5200B / Media5200

You can test the OS simply by executing any shell builtin command or any command residing within the OS image (e.g. ls).

Once the initial image is running, you can update the OS image using the network and flash drivers. For sample command lines, please see the "Summary of driver commands" section.