OpenWrt Forum Archive

Topic: Axotec, Uboot, ARM (ARM920Tid, ARMv4T), Uboot-Parameter-Problem

The content of this topic has been archived on 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

We are experimenting with an Axotec Spider III, which uses an own (commercial) build system, which is very bad. We want to use Kamikaze, because of the very good menu-config-system. The compiling runs fine, but we need the uboot-parameters (are we?). How can we explain the bootloader were is kernel and rootfs. In the trunk/build-Dir is an file with uboot-parameters - is this the needed one? If I take these ones,
the kernel starts and then the box hangs. The second problem is: we want to use the Flash, the original system does use the ramfs. Does anyone have solved a problem like this? Thanks in advance...

bye,Bastian  / weimarnetz.de

Here the Original-Boots-Sequence:
----------------------------------------------
boot 1.0 (May 28 2004 - 14:44:06)

Uncompressing image...



U-Boot 1.1.2 SpiderIII
(c) Axotec Technologies GmbH, 2005

U-Boot code: 21F00000 -> 21F1560C  BSS: -> 21F218D4
DRAM Configuration:
Bank #0: 20000000 32 MB
Intel 28F128J3A (128Mbit) 16-Bit
Size: 16 MB in 128 Sectors
Flash: 16 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
Copy ramdisk to memory
## Booting image at 10040000 ...
   Image Name:
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2533296 Bytes =  2.4 MB
   Load Address: 20008000
   Entry Point:  20008000
OK
## Loading Ramdisk Image at 20800000 ...
   Image Name:
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    10485760 Bytes = 10 MB
   Load Address: 21000000
   Entry Point:  21000000
No Linux ARM Ramdisk Image

Starting kernel ...

Linux version 2.6.17.3axo-sp02 (root@linux) (gcc version 3.4.1) #321 Thu Aug
176
CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T)
Machine: Axotec Embedded Server
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists
Kernel command line: root=/dev/ram rw ramdisk_size=10280 console=ttyS0,115200
mM
AT91: 128 gpio irqs in 4 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 19608KB available (2053K code, 417K data, 92K init)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
checking if image is initramfs...it isn't (bad gzip magic numbers); looks like
d
Freeing initrd memory: 10240K
NET: Registered protocol family 16
Generic PHY: Registered new driver
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NET: Registered protocol family 2
IP route cache hash table entries: 256 (order: -2, 1024 bytes)
TCP established hash table entries: 1024 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 1024 bind 512)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (extended precision)
JFFS version 1.0, (C) 1999, 2000  Axis Communications AB
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
io scheduler noop registered (default)
at91_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a AT91_SERIAL
at91_usart.1: ttyS1 at MMIO 0xfffcc000 (irq = 9) is a AT91_SERIAL
at91_usart.2: ttyS2 at MMIO 0xfffc8000 (irq = 8) is a AT91_SERIAL
at91_usart.3: ttyS3 at MMIO 0xfffc4000 (irq = 7) is a AT91_SERIAL
at91_usart.4: ttyS4 at MMIO 0xfffc0000 (irq = 6) is a AT91_SERIAL
RAMDISK driver initialized: 1 RAM disks of 10280K size 1024 blocksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
Davicom DM9161E: Registered new driver
Davicom DM9131: Registered new driver
eth0: Link down.
eth0: AT91 ethernet at 0xfefbc000 int=24 10-HalfDuplex (00:50:c2:1a:92:34)
eth0: Broadcom BCM5221 PHY
SCSI Media Changer driver v0.25
Axotec Embedded Server MTD mappings:
  Flash 0x1000000 at 0x10000000
Axotec FLASH space reserved
Axotec FLASH space ioremaped
flash: Found 1 x16 devices at 0x0 in 16-bit bank
flash: Found 1 x16 devices at 0x800000 in 16-bit bank
Intel/Sharp Extended Query Table at 0x0031
Using buffer write method
cfi_cmdset_0001: Erase suspend on write enabled
Doing CFI-Probe
Axotec FLASH probe ok
Creating 1 MTD partitions on "flash":
0x00e00000-0x01000000 : "Axotec flash application partition"
FLASH device added
usbmon: debugfs is not available
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 23, io mem 0x00300000
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver libusual
mice: PS/2 mouse device common for all mice
MMC: 4 wire bus mode not supported by this driver - using 1 wire
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 10240KiB [1 disk] into ram disk... done.
VFS: Mounted root (ext2 filesystem).
Freeing init memory: 92K
init started:  BusyBox v1.00 (2006.01.24-15:42+0000) multi-call binary
mount: RPC: Unable to send; errno = Network is unreachable
mount: nfsmount failed: Bad file descriptor
mount: Mounting 192.168.100.100:/axoteclinux/nfs2target on /host failed:
Invalit
Starting ifconfigscript...
eth0: Link down.
Starting httpd...
Starting xinetd...
usb 1-2: new low speed USB device using at91_ohci and address 2
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
usb 1-2: new low speed USB device using at91_ohci and address 3
usb 1-2: device descriptor read/64, error -110
usb 1-2: device descriptor read/64, error -110
usb 1-2: new low speed USB device using at91_ohci and address 4
usb 1-2: device not accepting address 4, error -110
usb 1-2: new low speed USB device using at91_ohci and address 5
usb 1-2: device not accepting address 5, error -110
Axotec LED driver (Spider-III Rev.1.2) loaded
(C) Copyright 2006 by Axotec Technologies GmbH, all rights reserved
Axotec RTC driver (Rev 1.2.1) loaded
(C) Copyright 2006 by Axotec Technologies GmbH, all rights reserved


Axotec Embedded Linux is up!

Spider-III login: root
Password:
Jun 10 16:10:01 login[734]: root login  on `ttyS0'



BusyBox v1.00 (2006.01.24-15:42+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

~ # mount
/dev/ram0 on / type ext2 (rw)
none on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
~ #                                                       
----------------------------------------------------------------------

You don't have to rebuild/modify the bootloader. For both questions, following the way how we do it on Magicbox should work if you are creating the image the same way. Just make sure to erase/write the right locations to not brick the board. If you need more help, just let me know - and of course, patches are welcomed wink

The discussion might have continued from here.