OpenWrt Forum Archive

Topic: OpenWRT reboots in a loop on Siemens SE505

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

I think we are pretty close to a solution since there are just two things remaining:

1. make diag.o module compatible to SE505 version 2 or remove it from preinit boot on this platform (I don't really miss the wlan LED ;-)

2. deal with the odd Siemens NVRAM settings (eth not working after flashing) maybe automatically erase on firstboot....

....still need some developers to promote the changes to the experimental build and some guys to test with SE505 hardware not afraid to end up with a silver brick...

BratMaxxe wrote:

....still need some developers to promote the changes to the experimental build and some guys to test with SE505 hardware not afraid to end up with a silver brick...

Well, I'm new to this business. But I just got my SE505 to play around with OpenWRT.
If I can provide something usefull, don't hesitate to ask!

/regards
netsurfer

Hi,
I also would like to test OpenWRT on my SE505. So, if you got it working in the experimental build, it would be great!!!

Best regards,
Whoopie

OK, give me something to load on my SE505 MK2 and I will try, until now I never received a .trx or other stuff. Holli

Unfortunatelly it turns out that posting attachments is not allowed in this forum anymore. But I can send the image I'm using to you guys via PM.... just drop me a PM with your email, okay?

The new Siemens se505 pcb looks *very* like a Belkin F5D7230-4 Version 1444:
http://www.efn.org/~rick/work/f5d7230/imag0014.jpg

You can extract kernel and cromfs from the firmware
http://communications.siemens.com/repos … nglish.exe
like this:

#!/bin/sh
KOFFSET=56
KSIZE=608928
dd if=siemens_en_3.01.05 of=piggy.gz count=$KSIZE bs=1 skip=$KOFFSET
FSYS="$(expr $KOFFSET + $KSIZE)"
dd if=siemens_en_3.01.05 of=filesystem.dump bs=$FSYS skip=1

Read http://www.seattlewireless.net/index.cg … 5D7230_2d4 !

Hi all!

Kaloz wrote:

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

Would you still try to help us "simple SE505 v2" owners?? :-)
If yes, I would like to send you my "virgin-ish" nvram.siemens file (fresh after a complete reflash/factory settings)

@BratMaxe: Is your v2 now running stable? If yes, on what? ;-)
(See also: http://forum.openwrt.org/viewtopic.php?id=1846)

Salut, Jörg

the problem is we have no hardware to fix it.

if anyone have a se505 on spare, donate it to the openwrt project.

Hi wbx!

What needs to be done with the h/w? I've some tools here and my device is open all the time as I suspect(ed) the surronding heat to be a major xx for the stability problems...

So if I could help with my h/w *from here, where it is* I would be glad...

Salut, Jörg

[edit01]
Tools mean *hard*ware, Scope, "electrical mind", wires, beer
the essentials, you see? ;-)

(Last edited by jsl123 on 16 Jul 2005, 17:16)

if you have a serial connection to your se505 you could help by providing the output on boot. i think it is still the diag kernel modul problem, but without real access to hardware it is not possible to fix.

you can build a firmware without loading the module... target/default/... preinit

Hello wbx (and all)!

Perhaps you are right regarding your suspicion against the diag module.

In the other thread (http://forum.openwrt.org/viewtopic.php?id=1846) I supposed that dnsmasq could be the root of major evil :-)
But to my dismay, my router would hang a few minutes later...

So I'll try and build my own binary w/o the diag module. But not today and at the beginning of the week since I am/will be very busy now... :-(

I will come back later when I have results regarding the diag module!

Thank you, though. Salut, Jörg
(Nice weather here in Germany, and I'm in front of some electrical "Mist", tss tss tss ;-)

Hi all ,
Here is the output on boot from the orginal siemens firmware on a SE505 v2 router , someone here wanted this stuff :

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-0F-B6-C4, 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: ..... 1433600 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 (root@localhost.localdomain) (gcc version 3.2.3 with Broadcom modifications) #17 Thu Jul 15 13:58:34 CST 2004

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 noinitrd console=ttyS0,115200

CPU: BCM4712 rev 1 at 200 MHz

Calibrating delay loop... 199.47 BogoMIPS

Memory: 6472k/8192k available (1206k kernel code, 1720k reserved, 108k data, 64k 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: Fixing up bus 0

PCI: Fixing up bridge

PCI: Fixing up bus 1

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

pty: 256 Unix98 ptys configured

Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled

ttyS00 at 0xb8000300 (irq = 3) is a 16550A

ttyS01 at 0xb8000400 (irq = 0) is a 16550A

Amd/Fujitsu Extended Query Table v1.1 at 0x0040

number of CFI chips: 1

Flash device: 0x400000 at 0x1c000000

Physically mapped flash: cramfs filesystem found at block 850

Creating 5 MTD partitions on "Physically mapped flash":

0x00000000-0x00040000 : "pmon"

0x00040000-0x003c0000 : "linux"

0x000d4b34-0x003c0000 : "rootfs"

0x003c0000-0x003e0000 : "profile"

0x003e0000-0x00400000 : "nvram"

sflash: found no supported devices

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP, IGMP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 512 bind 1024)

ip_conntrack version 2.1 (64 buckets, 512 max) - 344 bytes per conntrack

ip_tables: (C) 2000-2002 Netfilter core team

ipt_time loading

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

NET4: Ethernet Bridge 008 for NET4.0

802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>

All bugs added by David S. Miller <davem@redhat.com>

VFS: Mounted root (cramfs filesystem) readonly.

Mounted devfs on /dev

Freeing unused kernel memory: 64k freed

upgrade_wireless_nvram(): This firmware support WPA
setup_4712(): Enable VLAN
check_version_migration(): No need to process NVRAM migration
Using /lib/modules/2.4.20/kernel/drivers/net/et/et.o
Using /lib/modules/2.4.20/kernel/drivers/net/wl/wl.o
Using /lib/modules/2.4.20/kernel/drivers/net/slhc.o
Using /lib/modules/2.4.20/kernel/drivers/net/ppp_generic.o
Using /lib/modules/2.4.20/kernel/drivers/net/pppox.o
Using /lib/modules/2.4.20/kernel/drivers/net/pppoe.o
Using /lib/modules/2.4.20/kernel/drivers/net/ppp_async.o
Using /lib/modules/2.4.20/misc/mppe.o
Using /lib/modules/2.4.20/kernel/drivers/net/led/led.o
powerled_ctl(): WAN is  disconnected, turn power LED(GPIO 5) off!
led_ctl(): WAN is  disconnected, turn LED2(GPIO 0) off!
Hit enter to continue...rc: No need to start PPPoE
main_loop(): don't need to touch /tmp/pptp_man
CONSOLE connected!
Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
Added VLAN with VID == 0 to IF -:eth0:-
Added VLAN with VID == 1 to IF -:eth0:-
WARNING:  VLAN 1 does not work with many switches,
consider another number if you have problems.
TURN ON POWER LED!
powerled_ctl(): WAN is  connected, turn power LED(GPIO 5) on!
PRESTART
PRESTART for level 0
PRESTART for all services
killall: ntpclient: no process killed
killall: udhcpd: no process killed
killall: udhcpd: no process killed
killall: iapp: no process killed
ppp0 pppoe
cp: /tmp/fw_rules: No such file or directory
stop_firewall():create /tmp/fw_rules
stop_firewall():
killall: url_filter: no process killed
stop_wan():PRESTART for level 0
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
stop_firewall(): end
killall: ip-up: no process killed
killall: ip-down: no process killed
killall: pppoecd: no process killed
killall: pppd: no process killed
killall: udhcpc: no process killed
killall: stats: no process killed
killall: ntpclient: no process killed
killall: upnp: no process killed
killall: wan_test: no process killed
killall: route_check: no process killed
killall: set_dyndns: no process killed
killall: url_filter: no process killed
killall: auth: no process killed
ppp0: No such device
killall: httpd: no process killed
stop_lan():PRESTART for level 0
br0: No such device
wlconf: vlan0 failed (-1)
bridge br0 doesn't exist!
bridge br0 doesn't exist!
wlconf: wlanb0 failed (-1)
wlanb0: No such device
bridge br0 doesn't exist!
wlconf: wlana0 failed (-1)
wlana0: No such device
bridge br0 doesn't exist!
bridge br0 doesn't exist; can't delete it
killall: auth: no process killed
killall: netfilter_log: no process killed
eval_killall(nas): no process killedstart_lan():PRESTART for level 0
start_lan(): copy wan_ from m_wan
wlanb0: No such device
interface wlanb0 does not exist!
wlana0: No such device
interface wlana0 does not exist!
killall: udhcpd: no process killed
iapp: No such file or directory
start_dhcpd():  begin
start_dhcpd():  set_dhcp_static
info, Moreton Bay DHCP Server (v0.9.5) started
info, read_config(DHCPD_CONF_FILE(v0.9.5)
No interface specified. Quitting...
info, leases = malloc(v0.9.5)
info, static_removed(v0.9.5)
info, read_static_table(v0.9.5)
info, log_pid(v0.9.5)
info, write_leases(v0.9.5)
killall: upnp: no process killed
pre_firewall(): protocol(pppoe)
pre_firewall():pppoe/pptp
pre_firewall(): PPPoE in COD or manaul mode, drop NTP packets
iptables: No chain/target/match by that name
iptables: No chain/target/match by that name
pre_firewall(): end
start_wan(): don't execute in PPPoE manual mode after booting
ppp0: No such device
cannot use WAN interface "ppp0"
killall: dnsmasq: no process killed
start_dns():  fork process(0) to execute dnsmasq
forward_init(): /tmp/hosts not supported
killall: mac_2_ip: no process killed
Start virtual domain
start_virtual_domain():  fork process(86) to execute mac_2_ip
PRESTART level(0) end
Hit enter to continue...Hit enter to continue...Hit enter to continue...No interface specified. Quitting...
Hit enter to continue...no_same_process(): open /tmp/mac_2_ip.pid  successfully
no_same_process():Got non-killed mac_2_ip with pid(89)
mac_2_ip(): don't kill myself!
init_dnat_mac_list: start 1
init_dnat_mac_list: start 2
init_dnat_mac_list: start 3
DMZ: NULL dmz_macaddr()

Joachim wrote:

Device eth0:  hwaddr 00-01-E3-0F-B6-C4, ipaddr 192.168.2.1, mask 255.255.255.0

Beneath it's the boot of the original firmware and not OpenWRT I see your MAC starting with 00-01-E3 - is that maybe a v1 SE505? I have the same starting MAC on my SE515. My SE505 has 00-90-96 and is v2.

Cheers,
Heinz Peter

hph wrote:
Joachim wrote:

Device eth0:  hwaddr 00-01-E3-0F-B6-C4, ipaddr 192.168.2.1, mask 255.255.255.0

Beneath it's the boot of the original firmware and not OpenWRT I see your MAC starting with 00-01-E3 - is that maybe a v1 SE505? I have the same starting MAC on my SE515. My SE505 has 00-90-96 and is v2.

Cheers,
Heinz Peter

No , the boot was definitive from a Siemens SE505 v2 , orginal firmware from Siemens.
I think the MAC of the unit have nothing todo with the version ( v1 or v2 )
Maybe it is produced in the same week / month / year or so ....
I do not know in which order Siemens create the MAC¶ on the Devices , and i think you can not detect the
hardware -version of the router by reading only the MAC and then say ok the MAC is xxx then the router is version 1 or so

Just to get back to the objective of this thread: "OpenWRT reboots in a loop on Siemens SE505" ... I must admit that my v2 unit works pretty stable now with the whiterussian build rc2. smile

Anybody not scared should feel free to use this version by themselfs. Sorry to say but for me it did not work right out of the box and it was a long way to get there by trying many things.

But meanwhile this might have improved and to verify that previous problems are gone (such as the reboot loop and diag.o module problems), I would like to ask people with similar experiences for some feedback on the following issues:

1. Are you able to flash OpenWRT to your original (virgin) siemens box?
2. Is it still continously rebooting?
3. Are you able to successfully boot into OpenWRT without manually erasing the NVRAM?
4. Are you able to access the router via telnet after updating to OpenWRT?

If so we are pretty close to a perfect solution that works just out of the box and it's time to say thanks to all people involved!

Cheers,
BratMaxxe

Hi,

tried the whiterussian with the 505 but it seems not to install the firmware. After uploading the openwrt-wrt54g-jffs2/ or squashfs.bin the router just lights up the lan led's and then its there again with the standard firmware, rebouting is useless.

are there any hints to install correctly on the se505?

yours,
peter

callas wrote:

Hi,

tried the whiterussian with the 505 but it seems not to install the firmware. After uploading the openwrt-wrt54g-jffs2/ or squashfs.bin the router just lights up the lan led's and then its there again with the standard firmware, rebouting is useless.

are there any hints to install correctly on the se505?

yours,
peter

Hi ,
I think you have used the wrong firmware images  ,
openwrt-wrt54g-jffs2.bin  and wrt54g-squashfs.bin  are ONLY for the wrt54g and not for other routers .
I have successfully installed whiterussian rc2 on my brandnew se 505 v2 router and it worked perfect
"out of the box "
I have downloaded the file named openwrt-brcm-2.4-squashfs.trx and uploaded it via tftp to the router
after uploading the router reboots itself and ... ok it worked !
and YES of course ethernet and wifi and all worked perfect . ok , i know that at the moment there is no diag module
for the leds in the se 505 v2 is available , so i downloded the gpio program installed it on the se 505 and play around
with it
there are 3 leds who are controlled by gpio , the leds named www , power , wlan
I have found that the leds in the se 505 v2 are working in a totally other way as on the wrt54g .
Normally all leds off ( ok , ecept the wan and lan 1 -4 leds , they are controlled from the ethernet -switch )
if i do a
gpio disable 0 , the www - led turns on
and with
gpio enable 0  , the  www-led turns off

gpio disable 3 , the wlan - led turns on

gpio enable 3 the wlan - led turns off

gpio disable 5 , the power - led turns on

gpio enable 5 , the power - led turns off

all in all i can say ,
GPIO 0 = WWW-LED
GPIO 3 = WLAN-LED
GPIO 5 = POWER-LED

but for my opinion the logic of the leds on this router worked inversed

If someone can do the job , i see no problem to make a  led -controlling module for the se 505 ,
i'm not a very good programmer , but i think the guys here who can do this and worked at the openwrt -code have to do
other work with real problems , so i think this led -module is not really important ,
i can live without blinking leds at the router

oh , i think i have forgotten something , it must be written :

THANK YOU ALL FOR THIS GREAT SOFTWARE !

Hi Joachim,

the tip about the correct firmware did help me get the thing running. Many thanks for that.

You are absolutely right about that GREAT SOFTWARE. My thanks to the programmers and the community.

Thanks again,

Peter

Hi.

Was anything every resolved for the SE505 v1. I assume that is the one I have because I cant reboot from the web gui but I do have a reset button on the router.

I have tried flashing with the instructions on this site but keep getting errors.

is there a solution?


Thanks
eds2020

The discussion might have continued from here.