got me a 16-core octeon donated.
Its made by Movidis, and it has some linux on it now which boots. Of course, getting openbsd-octeon on it was the next step, but it won't load the bsd.rd correctly: Movidis X16 U-Boot version 1.6.1 (Build time: Nov 23 2007 - 18:27:52) CUST_WSX16 board revision major:1, minor:1, serial #: F12032617 OCTEON CN38XX-NSP revision: 3, Core clock: 500 MHz, DDR clock: 333 MHz (666 Mhz data rate) DRAM: 4096 MB Flash: 2 MB IPD backpressure workaround verified, took 11 loops Clearing DRAM done BIST check passed. Starting PCI PCI Status: PCI-X 64-bit PCI BAR 0: 0x, PCI BAR 1: Memory 0x PCI 0xf800 Net: octeth0, octeth1, octeth2, octeth3, octeth4, octeth5, octeth6, octeth7 0 Movidis x16 INTERRUPT Movidis x16 Movidis x16 setenv ipaddr 192.168.1.199 Movidis x16 setenv serverip 192.168.1.70 Movidis x16 tftpboot 0 bsd.octeon octeth0:Up 1Gbs Full duplex, (port 0) Using octeth0 device TFTP from server 192.168.1.70; our IP address is 192.168.1.199 Filename 'bsd.octeon'. Load address: 0x10 Loading: ### done Bytes transferred = 7291501 (6f426d hex), 346 Kbytes/sec Movidis x16 bootoctlinux ELF file is 64 bit Allocated memory for ELF segment: addr: 0x100, size 0x72fb80 Error allocating memory for elf image! ## Loading Linux kernel with entry point: 0x0010 ... Bootloader: Done loading app on coremask: 0x1 and then it just hangs there. Other info from the U-boot: Movidis x16 printenv bootdelay=0 baudrate=115200 download_baudrate=115200 bootloader_flash_update=protect off 0xbf43 0xbf47;erase 0xbf43 0xbf47;cp.b 0x10 0xbf43 0x5 flash_update=protect off 0xbec3 0xbec7;erase 0xbec3 0xbec7;cp.b 0x10 0xbec3 0x5 gatewayip=192.168.1.1 netmask=255.255.255.0 dnsip=192.168.1.1 ipaddr=192.168.1.77 serverip=192.168.1.151 bootsas=tftpboot; bootoctlinux 3100 mem=0 numcores=16 root=/dev/sda1 autostart=yes ethact=octeth0 bootfile=vmlinux.64 bootpartsize=1e0 fsloadfile=vmlinux.64.ram.1.6 bootcmd=fsload; bootoctlinux 10 numcores=16 endbootargs mtdparts=ws16-nand:30m(kernel),20m(rootfs),10m(appl) loadaddr=0x10 coremask_override=0x numcores=16 stdin=serial stdout=serial stderr=serial Environment size: 767/65532 bytes Movidis x16 base Base Address64: 0x8000, Base Address: 0x Movidis x16 namedprint List of currently allocated named bootmem blocks: Name: __tmp_load, address: 0x0010, size: 0x00f0, index: 0 Name: __tmp_reserved_linux, address: 0x0100, size: 0x0800, index: 1 So it doesn't seem to like either bsd nor bsd.rd, and it doesn't print anything after bootoctlinux. Where to go from here? Is the 0x10 boot address completely off? -- May the most significant bit of your life be positive.
Re: got me a 16-core octeon donated.
After some insight from jasper, I stripped away the randomdata section and voila: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.5 (RAMDISK) #0: Fri Mar 14 12:10:56 CET 2014 r...@octeon.office.jasper.la:/usr/src/sys/arch/octeon/compile/RAMDISK real mem = 4002201600 (3816MB) avail mem = 3970760704 (3786MB) warning: no entropy supplied by boot loader mainbus0 at root cpu0 at mainbus0: Unknown CPU type (0x0) rev 0.3 500 MHz, Software FP emulation cpu0: cache L1-I 32KB D 16KB 4 way, L2 128KB direct clock0 at mainbus0: int 5 iobus0 at mainbus0 octcf at iobus0 base 0x1d000800 irq 0 not configured pcibus0 at iobus0 irq 0 pci0 at pcibus0 bus 0 0:0:0: mem address conflict 0xf800/0x800 0:2:0: bridge mem address conflict 0x1000/0x10 vendor Cavium, unknown product 0x0005 (class processor subclass MIPS, rev 0x03) at pci0 dev 0 function 0 not configured Pericom PI7C21P100 PCIX-PCIX rev 0x01 at pci0 dev 2 function 0 not configured cn30xxgmx0 at iobus0 base 0x118000800 irq 48 unsupported octeon model: 0xd0003 octrng at iobus0 base 0x14000 irq 0 not configured uar: ns16550, no working fifo com0: console com1 at uartbus0 base 0x118000c00 irq 35: ns16550, no working fifo root on rd0a swap on rd0b dump on rd0b WARNING: No TOD clock, believing file system. WARNING: CHECK AND RESET THE DATE! erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/octeon 5.5 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s The command was (assuming you have a mips64 or build cross-tools): /usr/cross/octeon/usr/bin/mips64-unknown-openbsd5.5-strip -R .openbsd.randomdata /tftpboot/bsd.rd.octeon and then it JustWorked(tm)! 2014-05-15 21:32 GMT+02:00 Jasper Lievisse Adriaanse jas...@openbsd.org: On Thu, May 15, 2014 at 09:04:14PM +0200, Janne Johansson wrote: Its made by Movidis, and it has some linux on it now which boots. Of course, getting openbsd-octeon on it was the next step, but it won't load the bsd.rd correctly: Movidis X16 U-Boot version 1.6.1 (Build time: Nov 23 2007 - 18:27:52) CUST_WSX16 board revision major:1, minor:1, serial #: F12032617 OCTEON CN38XX-NSP revision: 3, Core clock: 500 MHz, DDR clock: 333 MHz (666 Mhz data rate) DRAM: 4096 MB Flash: 2 MB IPD backpressure workaround verified, took 11 loops Clearing DRAM done BIST check passed. Starting PCI PCI Status: PCI-X 64-bit PCI BAR 0: 0x, PCI BAR 1: Memory 0x PCI 0xf800 Net: octeth0, octeth1, octeth2, octeth3, octeth4, octeth5, octeth6, octeth7 0 Movidis x16 INTERRUPT Movidis x16 Movidis x16 setenv ipaddr 192.168.1.199 Movidis x16 setenv serverip 192.168.1.70 Movidis x16 tftpboot 0 bsd.octeon octeth0:Up 1Gbs Full duplex, (port 0) Using octeth0 device TFTP from server 192.168.1.70; our IP address is 192.168.1.199 Filename 'bsd.octeon'. Load address: 0x10 Loading: ### done Bytes transferred = 7291501 (6f426d hex), 346 Kbytes/sec Movidis x16 bootoctlinux ELF file is 64 bit Allocated memory for ELF segment: addr: 0x100, size 0x72fb80 Error allocating memory for elf image! ## Loading Linux kernel with entry point: 0x0010 ... Bootloader: Done loading app on coremask: 0x1 and then it just hangs there. Other info from the U-boot: Movidis x16 printenv bootdelay=0 baudrate=115200 download_baudrate=115200 bootloader_flash_update=protect off 0xbf43 0xbf47;erase 0xbf43 0xbf47;cp.b 0x10 0xbf43 0x5 flash_update=protect off 0xbec3 0xbec7;erase 0xbec3 0xbec7;cp.b 0x10 0xbec3 0x5 gatewayip=192.168.1.1 netmask=255.255.255.0 dnsip=192.168.1.1 ipaddr=192.168.1.77 serverip=192.168.1.151 bootsas=tftpboot; bootoctlinux 3100 mem=0 numcores=16 root=/dev/sda1 autostart=yes ethact=octeth0 bootfile=vmlinux.64 bootpartsize=1e0 fsloadfile=vmlinux.64.ram.1.6 bootcmd=fsload; bootoctlinux 10 numcores=16 endbootargs mtdparts=ws16-nand:30m(kernel),20m(rootfs),10m(appl) loadaddr=0x10 coremask_override=0x numcores=16 stdin=serial stdout=serial stderr=serial Environment size: 767/65532 bytes Movidis x16 base Base Address64: 0x8000, Base Address: 0x Movidis x16 namedprint List of currently allocated named bootmem blocks: Name: __tmp_load, address: 0x0010, size: 0x00f0, index: 0 Name: __tmp_reserved_linux, address: 0x0100, size: 0x0800, index: 1 So it doesn't seem to like either bsd nor bsd.rd, and it doesn't print anything after bootoctlinux. Where to go from here? Is the 0x10 boot address completely off? The load address looks correct, as in, it's the same as
Re: got me a 16-core octeon donated.
Date: Thu, 15 May 2014 22:04:16 +0200 From: Janne Johansson icepic...@gmail.com After some insight from jasper, I stripped away the randomdata section and voila: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.5 (RAMDISK) #0: Fri Mar 14 12:10:56 CET 2014 r...@octeon.office.jasper.la:/usr/src/sys/arch/octeon/compile/RAMDISK real mem = 4002201600 (3816MB) avail mem = 3970760704 (3786MB) warning: no entropy supplied by boot loader mainbus0 at root cpu0 at mainbus0: Unknown CPU type (0x0) rev 0.3 500 MHz, Software FP emulation cpu0: cache L1-I 32KB D 16KB 4 way, L2 128KB direct clock0 at mainbus0: int 5 iobus0 at mainbus0 octcf at iobus0 base 0x1d000800 irq 0 not configured pcibus0 at iobus0 irq 0 pci0 at pcibus0 bus 0 0:0:0: mem address conflict 0xf800/0x800 0:2:0: bridge mem address conflict 0x1000/0x10 vendor Cavium, unknown product 0x0005 (class processor subclass MIPS, rev 0x03) at pci0 dev 0 function 0 not configured Pericom PI7C21P100 PCIX-PCIX rev 0x01 at pci0 dev 2 function 0 not configured Looks like ppb(4) is missing from the kernel config.
Re: got me a 16-core octeon donated.
On Thu, May 15, 2014 at 11:03:10PM +0200, Mark Kettenis wrote: Date: Thu, 15 May 2014 22:04:16 +0200 From: Janne Johansson icepic...@gmail.com After some insight from jasper, I stripped away the randomdata section and voila: Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2014 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 5.5 (RAMDISK) #0: Fri Mar 14 12:10:56 CET 2014 r...@octeon.office.jasper.la:/usr/src/sys/arch/octeon/compile/RAMDISK real mem = 4002201600 (3816MB) avail mem = 3970760704 (3786MB) warning: no entropy supplied by boot loader mainbus0 at root cpu0 at mainbus0: Unknown CPU type (0x0) rev 0.3 500 MHz, Software FP emulation cpu0: cache L1-I 32KB D 16KB 4 way, L2 128KB direct clock0 at mainbus0: int 5 iobus0 at mainbus0 octcf at iobus0 base 0x1d000800 irq 0 not configured pcibus0 at iobus0 irq 0 pci0 at pcibus0 bus 0 0:0:0: mem address conflict 0xf800/0x800 0:2:0: bridge mem address conflict 0x1000/0x10 vendor Cavium, unknown product 0x0005 (class processor subclass MIPS, rev 0x03) at pci0 dev 0 function 0 not configured Pericom PI7C21P100 PCIX-PCIX rev 0x01 at pci0 dev 2 function 0 not configured Looks like ppb(4) is missing from the kernel config. It is, I've got a diff to add it along with some devices when I get a chance to test them on my board.
