wiki3923: Nto641BspFreescaleP2020rdbReleaseNotes (Version 2) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Release Notes for the QNX Neutrino 6.4.1 BSP for Freescale P2020RDB (Experimental)#1.System Requirements#Target Requirements
Host Requirements
2.System Layout#
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 first serial port of the P2020RDB board to the first serial port of your host machine. There are 2 serial ports on P2020RDB. 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:
3.3 Setup you 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-p2020rdb.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 10.42.175.189 => setenv serverip 10.42.175.188 => setenv bootfile ifs-p2020rdb.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-p2020rdb.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 P2020RDB 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. 5. Writing the IFS image to flash using the boot loader#6. Creating a flash partition#7. Driver Command Summary#
USB#devb-umass& (This will exit if it doesn't find any mass storage device, so start this only after plugging in a device)Network#To start network driver without encryption, run: io-pkt-v4-hc -dmpc85xx you should see following output when you run ifconfig # ifconfig lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192 inet 127.0.0.1 netmask 0xff000000 tsec0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM> capabilities tx=0 enabled=0 address: 00:04:9f:00:d8:fe media: Ethernet none tsec1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM> capabilities tx=0 enabled=0 address: 00:04:9f:00:d8:ff media: Ethernet none tsec2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 capabilities rx=7<IP4CSUM,TCP4CSUM,UDP4CSUM> capabilities tx=0 enabled=0 address: 00:11:8c:84:00:11 media: Ethernet none To bring a network interface up, type following command ifconfig tsec2 10.42.175.186/24 up Here 10.42.175.186 is the IP address assign to your target and 24 is the netmask bits (i.e. 255.255.255.0) 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. On the P2020RDB, eTSEC2 is connected to the Vitesse SGMII PHY (VSC8641). This interface is not yet tested. This is tsec2 in the ifconfig output.
PCI#PCI is not yet tested on the P2020RDBpci -v This shall output all PCI devices currently detected on your system. RTC#RTC is not yet supported on the P2020RDBNOR Flash#NOR is not yet supported on the P2020RDB 8. Known Issues#
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||