Hello,

i just bought an Siemens SE505 and want to try OpenWRT.
After tftp'ing the latest snapshot to the SE505
it enters a loop. I think it is constantly rebooting.
A ping is possible for 5 secs, then LEDs flicker and ping hangs for some seconds.

What can i try. The unit is working fine with the original firmware. OpenWRT would be much cooler and powerful.

What could i try?

  Ciao
        Dietmar

Service Set Identifier (SSID)   ConnectionPoint 
Internet Connection:   Static - Connected 
     
System Time:   2005/02/15 , 01:29:02 
Firmware Version :    en_3.01.05

You are probably doing something wrong. Mine is very stable.

Try it again to tftp to 192.168.2.1 and don'r interrupt. let it reboot after the upload.

I've just rename the firmware to .trx since it'S already started with the HEX 48. (hdr0)

Well, well I got the same on my unit. Which is a relativly new one with a BCM4712 running at 200MHz an not like in the OpenWRT documentation points out a 125MHz CPU based board.

Reflashing the original firmware by Siemens via TFTP fixes the problem of rebooting in a loop and prevents the one from starting a carrer as a brick but OpenWRT is not supposed to run on SE505 anymore.

Would be interesting in getting access to the serial console of the board to watch and analyse the boot messages....

Does anyone have any ideas?
Regards

Did you try the "old" openwrt or the new one (TheRoDents V2.2 build or the "new experiamental Version" of openwrt)?

I just used the snapshoot from the 2th of february and the snapshoot from the 31th january loaded from 
http://openwrt.org/downloads/snapshots/. Both times the file openwrt-linux.trx because the README points out that this is the right one for non-linksys brands and the others would'nt flash on my unit anyhow, since the boadloader is rejecting them.

What do yo mean with old and new one? What is the TheRoDents V2.2 build? Where can I get them? I'd be glad to try...

The new Siemens SE505 is a very interessting unit, since it is distributed by a couple of DSL providers in germany as goody with a contract and you can get them for cheap on ebay. But the original linux firmware by Siemens is crap 8)

It seems that there are at least to hardware revisions out there. The old one with a BCM4710 and hardwired reset button and a new one with a BCM4712 (200Mhz), more Flash and RAM, 3.3V serial Port, real reset button.

I have'nt got a converter cable for the onboard serial port yet, otherwise I'd be glad to provide you a snapshoot of the bootscreen.

Thanks for any advice!

Hello,

I didn't know, that there are more revisions of the 505, too. Is there any clue on the outside of it (revision number or so). On the old one, OpenWrt works flawlessly, but I update the page about the new one later.

I doubt that there is any usefull revision number on the box, at least I have'nt seen any. Siemens is just putting a sticker with the brand name and company at the bottom.

But I've got a real reset button on my unit on the back and the OpenWRT documentation record says that the SE505 (old) does just have a hardwired (what ever this is suppose to mean). Maybe this button is a hint?   

Did you have a look at the attached image of the board? What revision of the Linksys router is matching this Broadcom board most?

Would be very nice and looking forward to get OpenWRT running

It is likely a v2.0 wrt. How much ram/flash does it have? The button is a clue, just wondering, if we can find some easier-to-find thing for the users. How does the serial number start on Your unit? A friend asked me to get the old one work (zhis is the reason I said it works), I will ask him for his serial as well.

I actually don't know how to detect the amount of Flash/RAM on the board. How can I check this? How does the Flash/RAM chips look like?

Probably the bootscreen might tell me... but I'm still waiting for my datalink cable to get access to the serial console

Just write here the letters/numbers from the chips.

Okay, here we go:

1x BCM4712KPB
1x ADM6996L
1x M29W320DB-70N6
1x VG36641641DT

The sticker on the back states:

Gigaset SE505 dsl/cable
S30853-S1006-R107-3
CE 0682 S8
Serial: 4248J023867

Hope this helps identify...

200MHz CPU, 4MB Flash, 8MB ram (this can be a reason for rebooting.. Just to make sure, isn't there another chip on the bottom of the PCB?)

Unfortunatelly :-( there is no additional chip on the back of the board, but a spare spot on the right, so I suppose siemens decided 8MB Ram is enough and is going to sell crap...

Do you think that OpenWRT will run and perform on it?

I don't have any unit, which has only 2Mb flash or 8Mb ram, but i will check, hat I can do. However, I won't be able to test it, unsell someone donates/volunteers to test it.

I can try to run for testing if you want. just give me an image....

PM.

Finally I got some more maybe interesting information about the boot loop. I got access to the serial console and here is a dump:

Decompressing..........done
Here we try to capture the default reset button: None.

CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Fri May 14 09:44:24 CST 2004 (denny@dnylinux)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.60.9.0
CPU type 0x29007: 200MHz
Total memory: 0x800000 bytes (8MB)

Total memory used by CFE:  0x80300000 - 0x80434F90 (1265552)
Initialized Data:          0x8032F0A0 - 0x803313D0 (9008)
BSS Area:                  0x803313D0 - 0x80332F90 (7104)
Local Heap:                0x80332F90 - 0x80432F90 (1048576)
Stack Area:                0x80432F90 - 0x80434F90 (8192)
Text (code) segment:       0x80300000 - 0x8032F0A0 (192672)
Boot area (physical):      0x00435000 - 0x00475000
Relocation Factor:         I:00000000 - D:00000000

Device eth0:  hwaddr 00-01-E3-0E-ED-E6, ipaddr 192.168.2.1, mask 255.255.255.0
        gateway not set, nameserver not set
Reading :: Failed.: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: ...... 1634304 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
CPU revision is: 00029007
Primary instruction cache 8kb, linesize 16 bytes (2 ways)
Primary data cache 4kb, linesize 16 bytes (2 ways)
Linux version 2.4.20 (mbm@reboot2.lan) (gcc version 3.3.3) #1 Wed Feb 2 04:14:00
EST 2005
Determined physical RAM map:
memory: 00800000 @ 00000000 (usable)
On node 0 totalpages: 2048
zone(0): 2048 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/mtdblock2 rootfstype=squashfs init=/etc/preinit n
oinitrd console=ttyS0,115200
CPU: BCM4712 rev 1 at 200 MHz
Calibrating delay loop... 199.47 BogoMIPS
Memory: 6084k/8192k available (1411k kernel code, 2108k reserved, 100k data, 68k
init, 0k highmem)
Dentry cache hash table entries: 1024 (order: 1, 8192 bytes)
Inode cache hash table entries: 512 (order: 0, 4096 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 2048 (order: 1, 8192 bytes)
Checking for 'wait' instruction...  unavailable.
POSIX conformance testing by UNIFIX
PCI: Disabled
PCI: Fixing up bus 0
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
Starting kswapd
devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis Communications AB.
pty: 256 Unix98 ptys configured
Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
abled
ttyS00 at 0xb8000300 (irq = 3) is a 16550A
ttyS01 at 0xb8000400 (irq = 0) is a 16550A
Software Watchdog Timer: 0.05, timer margin: 60 sec
loop: loaded (max 8 devices)
PPP generic driver version 2.4.2
Amd/Fujitsu Extended Query Table v1.0 at 0x0040
Physically mapped flash: JEDEC Device ID is 0xCB. Assuming broken CFI table.
Physically mapped flash: Swapping erase regions for broken CFI table.
number of CFI chips: 1
Flash device: 0x400000 at 0x1c000000
Physically mapped flash: squashfs filesystem found at block 914
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "pmon"
0x00040000-0x003f0000 : "linux"
0x000e49b0-0x001b71a1 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-o
nly
0x003f0000-0x00400000 : "nvram"
0x001c0000-0x003f0000 : "OpenWrt"
sflash: found no supported devices
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 512 bind 1024)
ip_conntrack version 2.1 (5953 buckets, 5953 max) - 352 bytes per conntrack
ip_conntrack_pptp version 1.9 loaded
ip_nat_pptp version 1.5 loaded
ip_tables: (C) 2000-2002 Netfilter core team
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
NET4: Ethernet Bridge 008 for NET4.0
Bridge firewalling registered
802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 68k freed
Algorithmics/MIPS FPU Emulator v1.5
Using /lib/modules/2.4.20/diag.o
diag boardtype: 00000101
using v2 hardware
Decompressing..........done
Here we try to capture the default reset button: None.

CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Fri May 14 09:44:24 CST 2004 (denny@dnylinux)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.60.9.0
CPU type 0x29007: 200MHz
Total memory: 0x800000 bytes (8MB)

Total memory used by CFE:  0x80300000 - 0x80434F90 (1265552)
Initialized Data:          0x8032F0A0 - 0x803313D0 (9008)
BSS Area:                  0x803313D0 - 0x80332F90 (7104)
Local Heap:                0x80332F90 - 0x80432F90 (1048576)
Stack Area:                0x80432F90 - 0x80434F90 (8192)
Text (code) segment:       0x80300000 - 0x8032F0A0 (192672)
Boot area (physical):      0x00435000 - 0x00475000
Relocation Factor:         I:00000000 - D:00000000

The funny thing is that is starts re-booting right after it says: 'using v2 hardware'.

Since the SE505 hardware is not the same as WRT54 v2.0 hardware, it comes with much less memory.

Hope this helps.
Regards!

Ok, I see what's going on here - the Siemens doesn't have leds configured the same and the diag module is crashing the machine trying to control the leds. Edit /etc/preinit and comment out the diag module.

I'd be glad to try. How can I uncomment/modify this in the preinit script. I've just got a .trx image. Does this mean I have to install and get a complete build environment running in order to modify or is there another way to get access to files in the trx image?

Thanks for any advice!

Uncommenting out the diag module in preinit solves the problem of re-booting in a loop. So far this works now. By the way, the new experimental build system is very nice

Still got some trouble accessing the router via eth...

Okay, I aksed my friend, his serial is 12453002432. Anyone between 1* and 4* can tell us, which hardware does he/she have?

How is it working now? I think I bought the same type of SE505 because it enters in a loop and it has a real reset button too.

Can I try the experimental build or do I need the image from Kaloz?

BratMaxxe: Please post here the full output of "nvram show".

garrett: we need tu figure out the gpios. I will send instruction to BratMaxxe later today. Stay tuned.

Okay I will send a dump of the NVRAM as soon as I can, but might take some time... The firmware I got running is an experimental version build by myself.

You can get the build root from:

http://openwrt.org/downloads/experimental/

You might need a linux box with wget support (like gentoo does in order to load, compile and link the image. Then apply the minor fix: uncomment out the diag.o module in the preinit script. It crashes due to an incorrect hardware detection. Kaloz: Who could probably fix this module?

Without the diag module the router will boot fine, but is still not accessable via telnet/eth (serial console is the only option then) since some legacy Siemens NVRAM network settings screw the OpenWRTG network configuration and I have'nt have enough time in the last days to investigate and configure the unit properly...

Regards,
BratMaxxe

I could fix it But the first is to get the ethernet working. For this, i need the full output of "nvram show".