Release Notes for the QNX Neutrino 6.4.1 BSP for Freescale P1020RDB#

1.System Requirements#

Target Requirements
  1. QNX Neutrino RTOS 6.4.1
  2. Board version: P1020RDB
  3. P1020 processor
  4. 512 MB DDR SDRAM
  5. 16 MB NOR flash
  6. 32 MB NAND flash

Host Requirements

  1. QNX Momentics 6.4.1
  2. Terminal emulation program (Qtalk, Momentics IDE Terminal, tip, HyperTerminal, etc.)
  3. RS-232 serial port and serial cable, or a USB-to-serial cable
  4. Ethernet link

2.System Layout#

0x00100000OS Image Loaded
0xC00000000xDFFFFFFFPCIe1 Memory
0xA00000000xBFFFFFFFPCIe2 Memory
0x800000000x9FFFFFFFPCIe3 Memory
0xEF0000000xEFFFFFFFNor Flash (on eLBC)
0xF00200000xF002FFFFPCIe1 IO
0xF00100000xF001FFFFPCIe2 IO
0xF00000000xF000FFFFPCIe3 IO
0xF00300000xF012FFFFNAND Flash Bank 1 (eLBC Chip Select 1)

3.Getting Started#

3.1 Building 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.

3.2 Connect your Hardware#

Connect the serial cable to the serial port of the P1020RDB board to the first serial port of your host machine. There is 1 serial port on P1020RDB. Use the one which is near the boundary of the board. Usually you should see some Uboot output on the console when you connect cable to the correct port. If you have a Neutrino host with a serial mouse, you may have to move the mouse to the second serial port on your host, because some terminal programs require the first serial port.

The correct terminal settings of the program handling serial connection should be:

data8 bit
flow controlnone

3.3 Setup your environment#

1. Power on your target. You should see the u-boot output on your console. 2. Conenct an ethernet cable to any of the 3 PHY port available on the back side of the board.

4. Boot the IFS image#

You can use TFTP download (the default) or serial download to transfer an OS image to the board, as described below.

4.1 Boot via tftp#

This method requires that you put the raw image generated by BSP (by default at $BSP_ROOT/images/ifs-p1020rdb.raw) to a TFTP server. This server must be reachable via board and preferably should be on the same LAN. As soon as u-boot starts, press any key so that u-boot stops and doesnt boot the prebuild linux kernel. Configure u-boot parameters as follows:
=> setenv ipaddr
=> setenv serverip
=> setenv bootfile ifs-p1020rdb.raw
=> setenv loadaddr 0x100000
=> setenv bootcmd 'tftpboot $loadaddr $bootfile; go $loadaddr'
=> setenv bootdelay 2
=> saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
flash erase done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
=> boot

4.1 Boot via serial#

This method requires an SREC image. You have to modify the buildfile to create this format. Change this:

[virtual=ppcbe-spe,raw] to this:

[virtual=ppcbe-spe,srec] Rebuild the image. On your target, type:

=>: setenv loads_echo 0
=>: saveenv
=>: loads

On your host, copy the image to the serial port that's connected to the board. For example, on a Neutrino host: cp ifs-p1020rdb.srec /dev/ser1 On a Windows host, you can use Hyperterminal's transfer feature to copy the image as a text file.

## First Load Addr = 0x00100000
## Last  Load Addr = 0x0023955B
## Total Size      = 0x0013955C = 1283420 Bytes
## Start Addr      = 0x00101E38

Type go start_addr

At this point, you should see output similar to this when it finishes downloading:

## Starting application at 0x00100000 ...
Welcome to QNX Neutrino 6.4.1 on the PowerPC P1020RDB board

Congratulations! QNX 6.4.1 kernel is running on your system. 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 " Driver Command Summary" section.

6. Creating a flash partition#

Follow the description mentioned below for NAND flash and NOR flash

7. Driver Command Summary#

ComponentBuildfile CommandRequired BinariesRequired LibrariesSource Location
Startupstartup-p10xxrdb -v -c0xFFE00000 -t66660000 -D0xffe04500startup-p10xxrdblibstartup.asrc/hardware/startup/boards/p10xxrdb
Serialdevc-ser8250 -e -c400000000 -b115200 0xffe04500,16
waitfor /dev/ser1
reopen /dev/ser1
USBio-usb -d ehci-p2020 ioport=0xFFE22100,irq=5 -d ehci-p2020 ioport=0xFFE23100,irq=6 & waitfor /dev/io-usb/io-usb 10
I2Ci2c-mpc8572 -i17 -p0xffe03000 (for controller 1)
i2c-mpc8572 -i17 -p0xffe03100 --u1 (for controller 2)
SMPPATH=:/proc/boot:/bin:/usr/bin LD_LIBRARY_PATH=:/proc/boot:/lib:/usr/lib:/lib/dll procnto-booke-smp -vprocnto-booke-smpnoneprebuilt
Networkio-pkt-v4-hc -dmpcsec -p tcpip-v6 ipsec -dmpc85xx mac=00112233AABB,emu_phy=0io-pkt-v4-hc
NOR Flashdevf-generic -s 0xEF000000,16M,,,128k,2,1 -rdevf-generic
NAND Flashfs-etfs-p2020rdb512 -e
fs-etfs-p2020rdb512 -m /fs/etfs
RTCrtc -v ds3232 /dev/i2c0
rtc -s -v ds3232 /dev/i2c0
MMCSDdevb-mmcsd-p10xx mmcsd bs="ccbclock=400000000"
Watchdogwdtkick -k2000 -t10000wdtkick/src/hardware/support/p1020/wdtkick


devb-umass& (This will exit if it doesn't find any mass storage device, so start this only after plugging in a device)

The second USB Controller pins are shared with eLBC module pins ( which is interfaced with NOR/NAND Flash ), so by default USB 2 is disabled for NOR/NAND Flash functionality.

To Start USB controller 2 add -u option in startup command as below:

startup-p10xxrdb -v -c0xFFE00000 -t66660000 -D0xffe04500 -u


To start network driver without encryption, run:

io-pkt-v4-hc -dmpcsec -p tcpip-v6 ipsec -dmpc85xx mac=00112233AABB,emu_phy=0

you should see following output when you run ifconfig

# ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
        inet netmask 0xff000000
tsec0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bb
        media: Ethernet none
tsec1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bc
        media: Ethernet none
tsec2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
        capabilities tx=0
        address: 00:11:22:33:aa:bd
        media: Ethernet none

To bring a network interface up, type following command

ifconfig tsec0 up

Here is the IP address assign to your target and 24 is the netmask bits (i.e. The LEDs of the RJ45 ports corresponding to an enabled interface shall glow periodically. This can be used to identify the correct port corresponding to each tsec.


The RTC used in P1020RDB board is DS3232. Make sure the i2c driver is up and running before running the RTC utility, as the RTC DS3232 is connected to the first i2c bus.

If the i2c driver is not running, issue the following command

i2c-mpc8572 -i17 -p0xffe03000 --u0

To run the RTC utility, use the following command:

rtc -v ds3232 /dev/i2c0

This command updates the current time and date from the hardware clock in the board.

To set the hardware clock in the board with the current date and time, use the following command:

rtc -s -v ds3232 /dev/i2c0

NAND Flash#


fs-etfs-p2020rdb512 -e

to erase the NAND device and to create an empty file system that is ready to use. The factory marked bad blocks are not erased. Blocks that become bad during normal use are also skipped during the erasing.

After the erase of the NAND device, run the following command

fs-etfs-p2020rdb512 -m /fs/etfs

This command sets the directory /fs/etfs as the mount point.

NOR Flash#


devf-generic -s 0xEF000000,16M,,,128k,2,1 -r

to run the generic Flash filesystem driver on your board. After running this command, two partitions will get created. Normally the file names are as below: /dev/fs0 which is the default mountpoint for socket 0 and /dev/fs0p0 which has the raw access for socket 0, partition 0.

After these partitions get created, we should erase and format the flash using the flashctl utility.

The commands are as follows:

flashctl -p /dev/fs0 -o 0 -l 15M -ev

This command erases the nor flash starting from an offset of 0 to 15MB.

Though the nor flash is 16MB, we erase only 15MB as the last 1MB of flash contains the u-boot image.

After giving the above command, slay the driver using the slay devf-generic command and then restart it again.

The Nor flash is erased now and we can mount the given flash filesystem partition as the filesystem mountpoint /flash using the command below:

flashctl -p /dev/fs0p0 -o 0 -l 15M -f -n /flash

After this command is successfully run, slay the driver and restart it again. This formats the nor flash and mounts it over the filesystem mountpoint /flash.

We can create multiple filesystem partitions based on our requirement.


devb-mmcsd-p10xx mmcsd bs="ccbclock=400000000"

Command given above will start the mmcsd driver.

Driver can be started at any time, irrespective of when sdmmc card is plugged.

After plugging a sdmmc card, a /dev/hdX is created.

SDMMC card can be mounted by

mount -t <filesystem> /dev/hdXtX /mnt


wdtkick -k2000 -t10000

The above command starts the watchdog timer with a timeout value of 10000 milliseconds (option -t) and it also kicks (or resets) the timer every time after an interval of 2000 milliseconds (-k option).

These time-out and kick time periods used here is an example but any value can be chosen between 0 to ((2^64) - 1) depending on requirement.

Watchdog will reset the board if this utility is unable to kick before the watchdog times out.

Other options are:

-p : Define priority of the Watchdog Timer Module event. (default: 10)

-f : Input Clock Frequency in Hz to the Timebase (board specific, default: 400MHz)

8. Known Issues#

  1. eTSEC2-SGMII is not supported
  2. errors while loading the BSP into the IDE (Ref# 73518,71146 - SPE issues with the IDE have been resolved in IDE 4.7 included in SDP 6.5.0). Workaround:
  3. Enable the kprintf trace which gives the clock values, in the startup/boards/p10xxrdb/main.c. Whatever the CCB clock reported by startup, please use it as the clock input for the devc-ser8250 driver. This issue will be fixed in the next release of the BSP (Ref# 75148).
  4. While testing the NOR flash driver, please do not erase the first sector (128KB) of the NOR flash (0xEF000000 to 0xEF01FFFF) , as it contains the Firmware for the Vitesse Switch VSC7385 in the first 8KB. As you can erase the NOR flash, only sector wise, do not erase the first sector of the NOR flash. In case you erase it, the ethernet will not work on the eTSEC1 (Remember there are 3 eTSECs (1, 2, 3))
  5. if you are using 6.4.1 SDP with 4.6 IDE then for successful debugging using gdb download gdb update 5 from