sirius
sirius copied to clipboard
Bridge dead?
Our bridge's network LED won't light up anymore, nor does it show up in Bonjour Browser. I triple-checked the cable/connection and that's all working perfectly.
Does the bridge ping an external service to check if it's connected, could that be down? Did it just brick itself? Anything I can try on the hardware side of things? I already opened it up (nice and clean little board btw) and noticed 2 switches, RESET & SW1.
Now that I got I just got it working again on the software side of things, it would be sad that the hardware just failed on me :disappointed:
Any help/pointers would be appreciated!
Colleague of @bskrt here! I hooked up our bridge to a serial console and it seems the flash / image got corrupted.
mtd->read(0x3b4 bytes from 0x878c4c) returned ECC error JFFS2 notice: (383) check_node_data: wrong data CRC in data node at 0x00878c4c: read 0x3d37dfa4, calculated 0xc9f19407.
Is a re-flash necessary? Or does this point more towards a hardware problem?
Full output :
?@ macb0: link down (status: 0x7849)
Hit any key to stop autoboot: 0
U-Boot> RomBOOT
Start AT91Bootstrap...
U-Boot 2012.04.01 (Sep 18 2012 - 14:24:35)
CPU: AT91SAM9G20
Crystal frequency: 18.432 MHz
CPU clock : 396.288 MHz
Master clock : 132.096 MHz
DRAM: 32 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: macb0
macb0: Starting autonegotiation...
macb0: Autonegotiation timed out (status=0x7849)
macb0: link down (status: 0x7849)
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0xa0000, size 0x200000
2097152 bytes read: OK
## Booting kernel from Legacy Image at 20800000 ...
Image Name: Linux-2.6.36.4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1734152 Bytes = 1.7 MiB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 2.6.36.4 (nick@buildbot) (gcc version 4.6.3 (Buildroot 2013.02-dir
ty) ) #1 Wed Apr 24 18:01:13 BST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: Atmel AT91SAM9G20-EK
Memory policy: ECC disabled, Data cache writeback
Clocks: CPU 396 MHz, master 132 MHz, main 18.432 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: console=ttyS0,115200 root=/dev/mtdblock6 mtdparts=atmel_nan
d:128k(bootstrap)ro,256k(uboot)ro,128k(env1),128k(env2),2M(linux),16M(config),-(
root) rw rootfstype=jffs2 runmode=standard
PID hash table entries: 128 (order: -3, 512 bytes)
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: 28968k/28968k available, 3800k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xc2800000 - 0xfee00000 ( 966 MB)
lowmem : 0xc0000000 - 0xc2000000 ( 32 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.init : 0xc0008000 - 0xc0025000 ( 116 kB)
.text : 0xc0025000 - 0xc0318000 (3020 kB)
.data : 0xc0330000 - 0xc034e200 ( 121 kB)
NR_IRQS:192
AT91: 96 gpio irqs in 3 banks
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 197.83 BogoMIPS (lpj=989184)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource pit
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 56
io scheduler noop registered (default)
atmel_usart.0: ttyS0 at MMIO 0xfefff200 (irq = 1) is a ATMEL_SERIAL
brd: module loaded
ssc ssc.0: Atmel SSC device at 0xc2868000 (irq 14)
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xda (Micron NAND 256MiB 3,3V 8-bit
)
AT91 NAND: 8-bit, Software ECC
Scanning device for bad blocks
7 cmdlinepart partitions found on MTD device atmel_nand
Creating 7 MTD partitions on "atmel_nand":
0x000000000000-0x000000020000 : "bootstrap"
0x000000020000-0x000000060000 : "uboot"
0x000000060000-0x000000080000 : "env1"
0x000000080000-0x0000000a0000 : "env2"
0x0000000a0000-0x0000002a0000 : "linux"
0x0000002a0000-0x0000012a0000 : "config"
0x0000012a0000-0x000010000000 : "root"
atmel_spi atmel_spi.1: Atmel SPI Controller at 0xfffcc000 (irq 13)
MACB_mii_bus: probed
eth0: Atmel MACB at 0xfffc4000 irq 21 (40:d8:55:01:ce:22)
eth0: attached PHY driver [Micrel KS8041] (mii_bus:phy_addr=ffffffff:00, irq=-1)
usbmon: debugfs is not available
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
at91_ohci at91_ohci: AT91 OHCI
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: irq 20, io mem 0x00500000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (now
ayout= 0)
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
Registering the dns_resolver key type
VFP support v0.3: not present
Empty flash at 0x011b6734 ends at 0x011b6800
VFS: Mounted root (jffs2 filesystem) on device 31:6.
Freeing init memory: 116K
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Starting logging: OK
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Starting BERG Cloud linkd...
Socket mode enabled
Initializing random number generator... read-only file system detected...done
Starting network...
udhcpc (v1.21.0) started
Failed to kill daemon: No such file or directory
Sending discover...
Sending discover...
Sending discover...
No lease, failing
Sat Sep 1 12:00:00 UTC 2012
Getting initial time via default ntp serversNTP failed, falling back to tlsdate
getaddrinfo(bridge.bergcloud.com): Name or service not known
connection failed
child process failed in SSL handshake
.
Starting network time protocol daemon: ntpd.
Remounting RW
Welcome to Linux (BERG Cloud Bridge)
(none) login: uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Remounting RO
Finished updates
Loading override URL
Running compiled BERG Cloud daemon
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Unclean exit. Remaining daemon restart count is now 4
Remounting RW
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Remounting RO
Finished updates
Loading override URL
Running compiled BERG Cloud daemon
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Unclean exit. Remaining daemon restart count is now 3
Remounting RW
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Remounting RO
Finished updates
Loading override URL
Running compiled BERG Cloud daemon
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Unclean exit. Remaining daemon restart count is now 2
Remounting RW
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Remounting RO
Finished updates
Loading override URL
Running compiled BERG Cloud daemon
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Unclean exit. Remaining daemon restart count is now 1
Remounting RW
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Remounting RO
Finished updates
eth0: link up (100/Full)
Loading override URL
Running compiled BERG Cloud daemon
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
Data CRC 3d37dfa4 != calculated CRC c9f19407 for node at 00878c4c
Bus error
Unclean exit. Remaining daemon restart count is now 0
Rebooting!
Restarting system.
RomBOOT
Start AT91Bootstrap...
I don't know if this ever got answered/sorted, but I had my LP working for about two hours and then the upstream and downstream lights just stopped being lit and it all went offline. Now, nothing. I'm assuming it's bricked, but unsure.
I'm not technically-minded but I can follow instructions. Any way to reset the bridge or is it dead and gone for good?
Any help appreciated, or even a "nope, can't help!" would be cool :-)
@purplesime Our bridge is still dead too. I guess @genmon is the only one who could enlighten us on this one.
@purplesime Just to be sure, did you update your bridge as described here? Also, does the Ethernet LED light up?
@anneris I actually had it working on my Pi for about two hours and then suddenly the bridge became unresponsive. I unplugged the ethernet (which still lights up when plugged in) and powered it off. Once powered back on, ethernet led and power led come on, downstream flashes and then nothing.
I don't know why it might have stopped, but having determined it's not a software issue I'm left with the suggestion that it's a hardware fail.
Hi there -- the nature of the Bridge hardware is pretty much beyond me. But from what's being said above, this does sound like hardware failure.
I'm half-remembering old conversations here, but I think there's an intrinsic risk in corrupting the internal Flash storage whenever it is unlocked (??) to change what's stored? Like updating the software or changing where the Bridge points. This is an old memory, but maybe this is what's happened here. If it's corrupted, I don't know if there's anything that can be done... the kit to make new Bridges or put new software onto them is no longer around.
@genmon Thanks for the update. It does sound like like that's the case. Shame. I might see if I can find someone who has a bridge they don't want and try again.
What I will say is, as someone who isn't technical, getting it working, even for a short period of time, was really good fun.
@purplesime @genmon After applying the update about 9 months ago, my bridge has bitten the dust and got bricked :( I'll shelve the printer for now until I find another bridge online somewhere.
Any news here? I got the firmware update by genmon and everything worked fine some years ago. Now i tried to bring my printer back to life (because new application & stuff). But now the Ethernet light won't turn on anymore. Did anybody had the same issues (and knows how to fix it)?
Sadly, mine just died too, same thing, I was using it quite a lote lately with the ios app Nord made, but now it just wont light any other light than the power one, I'll try to test the hardware, but its probably the flash unit. I would love to buy a bridge if anyone is interested on sell one.
Yeah, I just connected got the USB adaptor and the message its basically the same
uncorrectable error :
mtd->read(0x4e5 bytes from 0x878c90) returned ECC error
So, I'll try to reflash it, I'll post some updates.
Hey everyone. I am also seeing the same with the Kernel being corrupt:
Skipping bad block 0x00140000
NAND read from offset 240000 failed -74
1572864 bytes read: ERROR
## Booting kernel from Legacy Image at 20800000 ...
Image Name: Linux-2.6.36.4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1734152 Bytes = 1.7 MiB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
So I have two questions:
- can we reflash the corrupt images? I did wonder whether it was possible to contact 'telegesis' who see to have developed the SoC originally and ask whether we can reflash... Am I sniffing in the right direction?
- Are we not at a point where we can bypass the bridge altogether? If I read around correctly it looks like the it might be possible to communicate directly to the printer itself using ZigBee? https://github.com/pipt/little-printer-payload-inspector
I been trying to use the bridge as it is, but Ive got random responses, sometimes it loads the uboot and sometimes it doesn't.
So, I opened the actual printer and found out the thermal printer is a generic APS ELM205-HS mechanism, so I'm planing to connect it to a raspberry zero and go from there.
As to bypass the bridge, I would love to see that happens, I'll try to connect a TTL to the printer board, and see what I get. Maybe it needs some sort of hardware key? Anyone knows about that?
@royletron were you able to solve this at all? I have the exact same issue with ERROR: can't get kernel image!
I flashed my bridge a couple of years ago and it was working fine up until a few months ago. Only the power light comes on, no Upstream or Downstream at all.
The serial console prints out the following when powered up but then nothing else:
RomBOOT
Start AT91Bootstrap...
U-Boot 2012.04.01 (Sep 18 2012 - 14:24:35)
CPU: AT91SAM9G20
Crystal frequency: 18.432 MHz
CPU clock : 396.288 MHz
Master clock : 132.096 MHz
DRAM: 543.1 MiB
Adding here in case anyone comes up with any solutions. I'm currently wondering if it'd be possible to access the processor another way to read the contents of the flash storage. 🤷
In reply to https://github.com/genmon/sirius/issues/14#issuecomment-613015374 I was able to get a little further
U-Boot> setenv verify n
U-Boot> boot
NAND read: device 0 offset 0xa0000, size 0x200000
Skipping bad block 0x00140000
NAND read from offset 240000 failed -74
1572864 bytes read: ERROR
## Booting kernel from Legacy Image at 20800000 ...
Image Name: Linux-2.6.36.4
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1734152 Bytes = 1.7 MiB
Load Address: 20008000
Entry Point: 20008000
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux...
But it just hangs forever. My only guess is the kernel is corrupt, and I haven't got the skills insane enough to reflash it...