P5040-RDB Using Bootline NULL

Cole_B — Tue, 13 May 2025 14:37:23 GMT

I am trying to boot a P5040-RDB with VxWorks 7. However, I think there is something wrong with my U-Boot environment variables. After loading the VxWorks image and dtb, it hangs. The entire serial output including environment variables is below:

U-Boot 2013.01-dirty (Jul 09 2013 - 13:14:36)
CPU0: P5040E, Version: 2.0, (0x820c0020)
Core: E5500, Version: 1.2, (0x80240012)
Clock Configuration:
CPU0:2200 MHz, CPU1:2200 MHz, CPU2:2200 MHz, CPU3:2200 MHz,
CCB:800 MHz,
DDR:800 MHz (1600 MT/s data rate) (Asynchronous), LBC:100 MHz
FMAN1: 600 MHz
FMAN2: 600 MHz
QMAN: 400 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: P5040RDB, Sys ID: 0x27, Sys Ver: 0x01, FPGA Ver: 0x04, vBank: 0
Reset Configuration Word (RCW):
00000000: 10600000 00000000 2c181800 00000000
00000010: 089e4400 00283000 de800000 61000000
00000020: 00000000 00000000 00000000 10070000
00000030: 00000000 00000000 00000000 00000000
SERDES Reference Clocks: Bank1=100Mhz Bank2=125Mhz Bank3=125Mhz Bank4=125Mhz
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
DDR: failed to read SPD from address 81
Detected UDIMM 18KSF1G72HZ-1G6E2
6 GiB left unmapped
8 GiB (DDR3, 64-bit, CL=11, ECC on)
Testing 0x00000000 - 0x7fffffff
Testing 0x80000000 - 0xffffffff
Testing 0x100000000 - 0x17fffffff
Testing 0x180000000 - 0x1ffffffff
Remap DDR 6 GiB left unmapped
POST memory PASSED
Flash: 128 MiB
L2: 512 KB enabled
Corenet Platform Cache: 2048 KB enabled
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
PCIe1: Root Complex, no link, regs @ 0xfe200000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe201000
PCIe2: Bus 01 - 01
PCIe3: disabled
In: serial
Out: serial
Err: serial
Warning: SERDES bank 3 expects reference clock 312.5MHz, but actual is 125MHz
Net: Initializing Fman
Fman1: Uploading microcode version 106.1.7
Fman2: Uploading microcode version 106.1.7
FM1@DTSEC3 [PRIME], FM1@DTSEC4, FM1@DTSEC5, FM1@TGEC1, FM2@DTSEC3, FM2@DTSEC4, FM2@DTSEC5, FM2@TGEC1
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
bdev=sda1
bootargs_vx=dtsec(3,0)host:vxWorks h=${serverip} e=${ipaddr}:${netmask} g=${gatewayip} u=target pw=vxTarget f=0x00
bootcmd=run bootcmd_vx
bootcmd_linux=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000
bootcmd_vx=setenv bootargs "${bootargs_vx}"; tftp ${loadaddr} ${bootfile}; tftp ${fdtaddr} ${fdtfile}; bootm ${loadaddr} - ${fdtaddr}
bootdelay=5
bootfile=P5040/uVxWorks
bootfile_linux=uImage
c=ffe
consoledev=ttyS0
eth1addr=00:04:9F:02:AB:D2
eth2addr=00:04:9F:02:AB:D3
eth3addr=00:04:9F:02:AB:D4
eth4addr=00:04:9F:02:AB:D5
eth5addr=00:04:9F:02:AB:D6
eth6addr=00:04:9F:02:AB:D7
eth7addr=00:04:9F:02:AB:D8
eth8addr=00:15:17:12:b6:b4
eth9addr=00:15:17:12:b6:b5
ethact=FM1@DTSEC3
ethaddr=00:04:9f:02:ab:d1
ethprime=FM1@DTSEC3
fdtaddr=f000000
fdtaddr_linux=c00000
fdtfile=P5040/p5040ds.dtb
fdtfile_linux=uImage-p5040rdb-serdes02.dtb
fileaddr=13F8000
filesize=80000
fman_ucode=0xef000000
gatewayip=192.168.1.0
hwconfig=fsl_fm1_xaui_phy:xaui;fsl_fm2_xaui_phy:xaui
ipaddr=192.168.1.1
loadaddr=2000000
loadaddr_linux=1000000
netdev=eth0
netmask=255.255.255.0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr
ping1=setenv ethact FM1@TGEC1;setenv ipaddr 192.168.1.1;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.5;ping $serverip
ping2=setenv ethact FM2@TGEC1;setenv ipaddr 192.168.2.1;setenv gatewayip 192.168.2.1;setenv serverip 192.168.2.5;ping $serverip
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskar
ramdiskaddr=2000000
ramdiskfile=fsl-image-core-p5040rdb.ext2.gz.u-boot
rootpath=/opt/nfsroot
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b e
uboot=u-bootP5040.bin
ubootaddr=0xeff80000
Environment size: 2366/8188 bytes
=> boot
Using FM1@DTSEC3 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'P5040/uVxWorks'.
Load address: 0x2000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
FM1@DTSEC4 Waiting for PHY auto negotiation to complete......... TIMEOUT !
FM1@DTSEC4: No link.
FM1@DTSEC5 Waiting for PHY auto negotiation to complete....
U-Boot 2013.01-dirty (Jul 09 2013 - 13:14:36)
CPU0: P5040E, Version: 2.0, (0x820c0020)
Core: E5500, Version: 1.2, (0x80240012)
Clock Configuration:
CPU0:2200 MHz, CPU1:2200 MHz, CPU2:2200 MHz, CPU3:2200 MHz,
CCB:800 MHz,
DDR:800 MHz (1600 MT/s data rate) (Asynchronous), LBC:100 MHz
FMAN1: 600 MHz
FMAN2: 600 MHz
QMAN: 400 MHz
L1: D-cache 32 kB enabled
I-cache 32 kB enabled
Board: P5040RDB, Sys ID: 0x27, Sys Ver: 0x01, FPGA Ver: 0x04, vBank: 0
Reset Configuration Word (RCW):
00000000: 10600000 00000000 2c181800 00000000
00000010: 089e4400 00283000 de800000 61000000
00000020: 00000000 00000000 00000000 10070000
00000030: 00000000 00000000 00000000 00000000
SERDES Reference Clocks: Bank1=100Mhz Bank2=125Mhz Bank3=125Mhz Bank4=125Mhz
I2C: ready
SPI: ready
DRAM: Initializing....using SPD
DDR: failed to read SPD from address 81
Detected UDIMM 18KSF1G72HZ-1G6E2
6 GiB left unmapped
8 GiB (DDR3, 64-bit, CL=11, ECC on)
Testing 0x00000000 - 0x7fffffff
Testing 0x80000000 - 0xffffffff
Testing 0x100000000 - 0x17fffffff
Testing 0x180000000 - 0x1ffffffff
Remap DDR 6 GiB left unmapped
POST memory PASSED
Flash: 128 MiB
L2: 512 KB enabled
Corenet Platform Cache: 2048 KB enabled
NAND: 512 MiB
MMC: FSL_SDHC: 0
EEPROM: NXID v1
PCIe1: Root Complex, no link, regs @ 0xfe200000
PCIe1: Bus 00 - 00
PCIe2: Root Complex, no link, regs @ 0xfe201000
PCIe2: Bus 01 - 01
PCIe3: disabled
In: serial
Out: serial
Err: serial
Warning: SERDES bank 3 expects reference clock 312.5MHz, but actual is 125MHz
Net: Initializing Fman
Fman1: Uploading microcode version 106.1.7
Fman2: Uploading microcode version 106.1.7
FM1@DTSEC3 [PRIME], FM1@DTSEC4, FM1@DTSEC5, FM1@TGEC1, FM2@DTSEC3, FM2@DTSEC4, FM2@DTSEC5, FM2@TGEC1
Hit any key to stop autoboot: 0
=> printenv
baudrate=115200
bdev=sda1
bootargs_vx=dtsec(3,0)host:vxWorks h=${serverip} e=${ipaddr}:${netmask} g=${gatewayip} u=target pw=vxTarget f=0x00
bootcmd=run bootcmd_vx
bootcmd_linux=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;bootm e8020000 e9300000 e8800000
bootcmd_vx=setenv bootargs "${bootargs_vx}"; tftp ${loadaddr} ${bootfile}; tftp ${fdtaddr} ${fdtfile}; bootm ${loadaddr} - ${fdtaddr}
bootdelay=5
bootfile=P5040/uVxWorks
bootfile_linux=uImage
c=ffe
consoledev=ttyS0
eth1addr=00:04:9F:02:AB:D2
eth2addr=00:04:9F:02:AB:D3
eth3addr=00:04:9F:02:AB:D4
eth4addr=00:04:9F:02:AB:D5
eth5addr=00:04:9F:02:AB:D6
eth6addr=00:04:9F:02:AB:D7
eth7addr=00:04:9F:02:AB:D8
eth8addr=00:15:17:12:b6:b4
eth9addr=00:15:17:12:b6:b5
ethact=FM1@DTSEC3
ethaddr=00:04:9f:02:ab:d1
ethprime=FM1@DTSEC3
fdtaddr=f000000
fdtaddr_linux=c00000
fdtfile=P5040/p5040ds.dtb
fdtfile_linux=uImage-p5040rdb-serdes02.dtb
fileaddr=13F8000
filesize=80000
fman_ucode=0xef000000
gatewayip=192.168.1.0
hwconfig=fsl_fm1_xaui_phy:xaui;fsl_fm2_xaui_phy:xaui
ipaddr=192.168.1.1
loadaddr=2000000
loadaddr_linux=1000000
netdev=eth0
netmask=255.255.255.0
nfsboot=setenv bootargs root=/dev/nfs rw nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip:$gatewayip:$netmask:$hostname:$netdev:off console=$consoledev,$baudrate $othbootargs;tftp $loadaddr
ping1=setenv ethact FM1@TGEC1;setenv ipaddr 192.168.1.1;setenv gatewayip 192.168.1.1;setenv serverip 192.168.1.5;ping $serverip
ping2=setenv ethact FM2@TGEC1;setenv ipaddr 192.168.2.1;setenv gatewayip 192.168.2.1;setenv serverip 192.168.2.5;ping $serverip
ramboot=setenv bootargs root=/dev/ram rw console=$consoledev,$baudrate $othbootargs;tftp $ramdiskaddr $ramdiskfile;tftp $loadaddr $bootfile;tftp $fdtaddr $fdtfile;bootm $loadaddr $ramdiskar
ramdiskaddr=2000000
ramdiskfile=fsl-image-core-p5040rdb.ext2.gz.u-boot
rootpath=/opt/nfsroot
serverip=192.168.1.2
stderr=serial
stdin=serial
stdout=serial
tftpflash=tftpboot $loadaddr $uboot && protect off $ubootaddr +$filesize && erase $ubootaddr +$filesize && cp.b $loadaddr $ubootaddr $filesize && protect on $ubootaddr +$filesize && cmp.b e
uboot=u-bootP5040.bin
ubootaddr=0xeff80000
Environment size: 2366/8188 bytes
=> boot
Using FM1@DTSEC3 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'P5040/uVxWorks'.
Load address: 0x2000000
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
################################
867.2 KiB/s
done
Bytes transferred = 1825064 (1bd928 hex)
Using FM1@DTSEC3 device
TFTP from server 192.168.1.2; our IP address is 192.168.1.1
Filename 'P5040/p5040ds.dtb'.
Load address: 0xf000000
Loading: ####
708 KiB/s
done
Bytes transferred = 15956 (3e54 hex)
WARNING: adjusting available memory to 30000000
## Booting kernel from Legacy Image at 02000000 ...
Image Name: vxworks
Image Type: PowerPC VxWorks Kernel Image (uncompressed)
Data Size: 1825000 Bytes = 1.7 MiB
Load Address: 00200000
Entry Point: 00200000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
## Ethernet MAC address not copied to NV RAM
## No elf image at address 0x00200000
## Not an ELF image, assuming binary
## Using bootline (@ 0x0): <NULL>
## Starting vxWorks at 0x00200000 ...

Re: P5040-RDB Using Bootline NULL

Bio_TICFSL — Wed, 14 May 2025 16:43:56 GMT

Hello,

Try to use the current bootloader for P5040, if the problem persist contact VxWorks.

Regards

Re: P5040-RDB Using Bootline NULL

Cole_B — Wed, 14 May 2025 17:55:39 GMT

Thanks for the reply!

Where can I find the current bootloader for the P5040?

topic Re: P5040-RDB Using Bootline NULL in P-Series

P5040-RDB Using Bootline NULL

Re: P5040-RDB Using Bootline NULL

Re: P5040-RDB Using Bootline NULL