Horstbox DVA-G3342SB with FreeBSD

What happened until now:

- look what the original Linux is doing
- replace Redboot with a version with working network
- configure nvram
- build Kernel and world for FreeBSD as written in the FreeBSD-Wiki
- boot FreeBSD

Todo: get Network running 1) Replace Redboot:

Looks like Maxina mixed up the Interfaces and redboot is not able to boot from the network.
Someone in the Ip-Phone-Forum already built a working one. Upload redboot_ram via xmodem, execute, load new Redboot-Binary, write to flash


RedBoot> load -m xmodem
CEntry point: 0x00100040, address range: 0x00100000-0x0012a784
xyzModem - CRC mode, 1901(SOH)/0(STX)/0(CAN) packets, 8 retries
RedBoot> go
+**Warning** FLASH configuration checksum error or invalid key
Use 'fconfig -i' to [re]initialize database
No network interfaces found


RedBoot(tm) bootstrap and debug environment [RAM]
Red Hat certified release, version 2.02 - built 20:49:36, Apr 24 2005

Platform: IXDP425 Development Platform (IXP42X 533MHz) BE
Copyright (C) 2000, 2001, 2002, 2003, 2004 Red Hat, Inc.

RAM: 0x00000000-0x04000000, [0x0013a3a8-0x03fd1000] available
FLASH: 0x50000000 - 0x51000000, 128 blocks of 0x00020000 bytes each.
RedBoot> load -r -b %{FREEMEMLO} redboot.bin
Using default protocol (TFTP)
Can't load 'redboot.bin': invalid parameter
RedBoot> load -r -b %{FREEMEMLO} -m xmodem redboot.bin
CRaw file loaded 0x0013a400-0x001839fb, assumed entry at 0x0013a400
xyzModem - CRC mode, 2348(SOH)/0(STX)/0(CAN) packets, 3 retries
RedBoot> cksum
Computing cksum for area 0x0013a400-0x001839fc
POSIX cksum = 4208155669 300540 (0xfad35c15 0x000495fc)
RedBoot> fis unlock RedBoot
... Unlock from 0x50000000-0x50080000: ....
RedBoot> fis create RedBoot
An image named 'RedBoot' exists - continue (y/n)? y
... Erase from 0x50000000-0x50080000: ....
... Program from 0x0013a400-0x001839fc at 0x50000000: ...
... Unlock from 0x50fe0000-0x51000000: .
... Erase from 0x50fe0000-0x51000000: .
... Program from 0x03fe0000-0x04000000 at 0x50fe0000: .
... Lock from 0x50fe0000-0x51000000: .
RedBoot> fis lock RedBoot
... Lock from 0x50000000-0x50080000: ....
RedBoot>



2) Configure Nvram to configure network in Redboot permanentely


RedBoot> fconfig
Run script at boot: true
Boot script:
Enter script, terminate with empty line
>> fis load zImage
>> exec
>>
Boot script timeout (1000ms resolution): 3
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address: 192.168.2.45
Local IP address mask: 255.255.255.0
Default server IP address: 192.168.2.64
Console baud rate: 115200
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Default network device: npe_eth0
Network hardware address [MAC] for NPE eth0: 0x00:0x03:0x47:0xDF:0x32:0xA8
Network hardware address [MAC] for NPE eth1: 0x00:0x03:0x47:0xDF:0x32:0xAA
serial_nr: 00179A131A8F
Update RedBoot non-volatile configuration - continue (y/n)? y
... Unlock from 0x50fc0000-0x50fc1000: .
... Erase from 0x50fc0000-0x50fc1000: .
... Program from 0x03fd3000-0x03fd4000 at 0x50fc0000: .
... Lock from 0x50fc0000-0x50fc1000: .



4) Boot FreeBSD

RedBoot> load -b 0x200000 kernel-horst.nfs
Using default protocol (TFTP)
Address offset = 0x40000000
Entry point: 0x00200100, address range: 0x00200000-0x0054e330
RedBoot> go
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2008 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #1: Wed May 14 07:24:11 CEST 2008
root@g33.rebootking.de:/usr/obj/arm/samba/freebsd7-arm/src/sys/HORST
CPU: IXP425 533MHz rev 1 (ARMv5TE) (XScale core)
DC enabled IC enabled WB enabled LABT branch prediction enabled
32KB/32B 32-way Instruction cache
32KB/32B 32-way write-back-locking Data cache
real memory = 67108864 (64 MB)
avail memory = 58355712 (55 MB)
ixp0: on motherboard
pcib0: on ixp0
pci0: on pcib0
ixppcib: no mapping for 0/12/0
ixppcib: no mapping for 0/13/0
ixppcib: no mapping for 0/14/0
ixppcib: no mapping for 0/14/1
ixppcib: no mapping for 0/14/2
pci0: at device 12.0 (no driver attached)
pci0: at device 13.0 (no driver attached)
ohci0: irq -1 at device 14.0 on pci0
ixppcib: no mapping for 0/14/0
ohci0: Could not allocate irq
pcib0: ohci0 called release_resource
device_attach: ohci0 attach returned 6
ohci1: irq -1 at device 14.1 on pci0
ixppcib: no mapping for 0/14/1
ohci1: Could not allocate irq
pcib0: ohci1 called release_resource
device_attach: ohci1 attach returned 6
ehci0: mem 0x48002200-0x480022ff irq -1 at device 14.2 on pci0
pcib0: ehci0 called activate_resource
ehci0: Could not map memory
device_attach: ehci0 attach returned 6
ixpclk0: on ixp0
ixpiic0: on ixp0
iicbb0: on ixpiic0
iicbus0: on iicbb0 master-only
iicbus0: at addr 0
iic0: on iicbus0
ad74180: at addr 0x50 on iicbus0
ds16720: at addr 0xd0 on iicbus0
ixpwdog0: on ixp0
uart0: on ixp0
uart0: [FILTER]
uart0: console (115200,n,8,1)
uart1: on ixp0
uart1: [FILTER]

This entry was posted by molli123 on Wednesday, May 14. 2008 at 08:40. and is filed under Hardwarezoo. You can leave a response, or trackback from your own blog.

Trackbacks

Trackback specific URI for this entry

    No Trackbacks

Comments

Display comments as (Linear | Threaded)

    No comments


Add Comment


Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.
CAPTCHA