Question

play 5 gen1 not work lost smbscand file, anyone can help

  • 26 November 2021
  • 2 replies
  • 23 views

I have a sonos play 5 gen1, recent days, it does not work. I use a uart connect the board,maybe can solve problems on the way:

1、anyone can help me with the smbscand file;

2、or tell me where can download the upd file, but I cannot spell the right url looks like http://update-firmware.sonos.com/firmware/Gold/28.1-83251-v5.2-pcyakr-RC4/28.1-83040-1-1.upd?

thanks a lot.

here are the logs:

 

U-Boot 1.1.1(1-16-4-zp5s-0.5), Build: zp5s-0.5

MPC8272 Reset Status: External Soft, External Hard

MPC8272 Clock Configuration

 - Bus-to-Core Mult 3x, VCO Div 4, 60x Bus Freq  16-50 , Core Freq  50-150

 - dfbrg 1, corecnf 0x10, busdf 3, cpmdf 1, plldf 0, pllmf 3

 - vco_out  400000000, scc_clk  100000000, brg_clk   25000000

 - cpu_clk  300000000, cpm_clk  200000000, bus_clk  100000000

 - pci_clk   33333333

CPU:   MPC8272 (HiP7 Rev 14, Mask unknown [immr=0x0d10,k=0x00e1]) at 300 MHz

Board: Sonos ZP5S

DRAM:  32 MB

IMMR: f0000000

DRAM tests running ... done

Using default environment

In:    serial

Out:   serial

Err:   serial

Net:   FCC1 ETHERNET, FCC2 ETHERNET

Hit any key to stop autoboot:  0 

NAND ID is 20:75

32M NAND flash (ST NAND256W3A)

Block 7 is bad

Block 26 is bad

Block 33 is bad

Block 128 is bad

Block 459 is bad

Block 795 is bad

Block 1124 is bad

Block 1543 is bad

S0 provisionally good, KP=1, G1

S1 provisionally good, KP=4, G1

Boot from partition 1

block 26 is bad, skipping

block 33 is bad, skipping

## Starting application at 0x00400000 ..�����������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������������..............................

(0)Memory BAT mapping: BAT2=16Mb, BAT3=8Mb, residual: 20Mb

(0)Linux version 2.4.22-rincon-11.3-16107-diag-dev-jpeters-200904111055 (jpeters@jpeters-vm2) (gcc version 3.4.4) #17 Sat Apr 11 10:56:23 EDT 2009

(0)On node 0 totalpages: 7168

(0)zone(0): 7168 pages.

(0)zone(1): 0 pages.

(0)zone(2): 0 pages.

(0)RPRINTF Virt: c01f1000:c01f2000 Phys: 1f1000:1f2000

(0)PCI: Probing PCI hardware

(0)PCI: moved device 00:10.0 resource 0 (200) to a0000000

(0)Did post-init PCI EMR/ESR reset

(0)Linux NET4.0 for Linux 2.4

(0)Based upon Swansea University Computer Society NET3.039

(0)Initializing RT netlink socket

(0)Starting kswapd

(0)devfs: v1.12c (20020818) Richard Gooch (rgooch@atnf.csiro.au)

(0)devfs: boot_options: 0x1

(0)JFFS2 version 2.2. (NAND) (C) 200�(0)ttyS0 at 0x0040 is a SMC

) 2001-2003 Red Hat, Inc.

(0)CPM UART driver version 0.01

(0)pty: 256 Unix98 ptys configured

(0)eth0: FCC ENET Version 0.2, 00:0e:58:af:ff:00

(0)eth0: PHY ID is 000e7237

(0)eth0: PHY control 3100 status 7849

(0)eth1: FCC ENET Version 0.2, 00:0e:58:6f:ff:00

(0)eth1: PHY ID is 000e7237

(0)eth1: PHY control 3100 status 7849

(0)RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize

(0)NAND device: Manufacturer ID: 0x20, Chip ID: 0x75 (ST Micro NAND 32MiB 3,3V 8-bit)

(0)Scanning device for bad blocks

(0)Bad eraseblock 7 at 0x0001c000

(0)Bad eraseblock 26 at 0x00068000

(0)Bad eraseblock 33 at 0x00084000

(0)Bad eraseblock 128 at 0x00200000

(0)Bad eraseblock 459 at 0x0072c000

(0)Bad eraseblock 795 at 0x00c6c000

(0)Bad eraseblock 1124 at 0x01190000

(1)Bad eraseblock 1543 at 0x0181c000

(1)Scanning NAND flash mtd c1b4a000 (2048 eraseblocks) for bad blocks

(1)block 7 is bad

(1)block 26 is bad

(1)block 33 is bad

(1)block 128 is bad

(1)block 459 is bad

(1)block 795 is bad

(1)block 1124 is bad

(1)block 1543 is bad

(1)After accounting for bad blocks, mtd c1b4a000 size (in 512 byte blocks) is 65280

(1)NAND badmap entry 0: lbase 0 pbase 0 nblocks 7

(1)NAND badmap entry 1: lbase 7 pbase 8 nblocks 18

(1)NAND badmap entry 2: lbase 25 pbase 27 nblocks 6

(1)NAND badmap entry 3: lbase 31 pbase 34 nblocks 94

(1)NAND badmap entry 4: lbase 125 pbase 129 nblocks 330

(1)NAND badmap entry 5: lbase 455 pbase 460 nblocks 335

(1)NAND badmap entry 6: lbase 790 pbase 796 nblocks 328

(1)NAND badmap entry 7: lbase 1118 pbase 1125 nblocks 418

(1)NAND badmap entry 8: lbase 1536 pbase 1544 nblocks 504

(1)Partition 0: offset 0 size 278528

(1)Partition 1: offset 278528 size 819200

(1)Partition 2: offset 1097728 size 4210688

(1)Partition 3: offset 5308416 size 22822912

(1)Partition 4: offset 28131328 size 786432

(1)Partition 5: offset 28917760 size 4194304

(1)nand_rincon_check_partition: success (generation 1)

(1)nand_rincon_check_partition: success (generation 1)

(1)nand_rincon_check_partition: success (generation 1)

(1)nand_rincon_check_partition: success (generation 1)

(1)Selected boot section 0 (generation 1)

(1)link: /dev/nandroot -> /dev/mtdblock_autobadmap/3

(1)link: /dev/nandjffs -> /dev/mtdblock/4

(1)Creating 10 MTD partitions on "NAND 32MiB 3,3V 8-bit":

(1)0x00000000-0x00044000 : "P1"

(1)Scanning NAND flash mtd c1b45000 (17 eraseblocks) for bad blocks

(1)block 7 is bad

(1)After accounting for bad blocks, mtd c1b45000 size (in 512 byte blocks) is 512

(1)0x00044000-0x0010c000 : "P2"

(1)Scanning NAND flash mtd c1b45200 (50 eraseblocks) for bad blocks

(1)block 9 is bad

(1)block 16 is bad

(1)After accounting for bad blocks, mtd c1b45200 size (in 512 byte blocks) is 1536

(1)0x0010c000-0x00510000 : "P3"

(1)Scanning NAND flash mtd c1b45400 (257 eraseblocks) for bad blocks

(1)block 61 is bad

(1)After accounting for bad blocks, mtd c1b45400 size (in 512 byte blocks) is 8192

(1)0x00510000-0x01ad4000 : "P4"

(1)Scanning NAND flash mtd c1b45600 (1393 eraseblocks) for bad blocks

(1)block 135 is bad

(1)block 471 is bad

(1)block 800 is bad

(1)block 1219 is bad

(1)After accounting for bad blocks, mtd c1b45600 size (in 512 byte blocks) is 44448

(1)0x01ad4000-0x01b94000 : "P5"

(1)Scanning NAND flash mtd c1b45800 (48 eraseblocks) for bad blocks

(1)After accounting for bad blocks, mtd c1b45800 size (in 512 byte blocks) is 1536

(1)0x01b94000-0x01f94000 : "P6"

(1)Scanning NAND flash mtd c1b45a00 (256 eraseblocks) for bad blocks

(1)After accounting for bad blocks, mtd c1b45a00 size (in 512 byte blocks) is 8192

(1)0x00000000-0x02000000 : "P7"

(1)Scanning NAND flash mtd c1b45c00 (2048 eraseblocks) for bad blocks

(2)block 7 is bad

(2)block 26 is bad

(2)block 33 is bad

(2)block 128 is bad

(2)block 459 is bad

(2)block 795 is bad

(2)block 1124 is bad

(2)block 1543 is bad

(2)After accounting for bad blocks, mtd c1b45c00 size (in 512 byte blocks) is 65280

(2)0x00000000-0x02000000 : "P8"

(2)Scanning NAND flash mtd c1b45e00 (2048 eraseblocks) for bad blocks

(2)block 7 is bad

(2)block 26 is bad

(2)block 33 is bad

(2)block 128 is bad

(2)block 459 is bad

(2)block 795 is bad

(2)block 1124 is bad

(2)block 1543 is bad

(2)After accounting for bad blocks, mtd c1b45e00 size (in 512 byte blocks) is 65280

(2)0x00000000-0x02000000 : "P9"

(2)Scanning NAND flash mtd c1b3d000 (2048 eraseblocks) for bad blocks

(2)block 7 is bad

(2)block 26 is bad

(2)block 33 is bad

(2)block 128 is bad

(2)block 459 is bad

(2)block 795 is bad

(2)block 1124 is bad

(2)block 1543 is bad

(2)After accounting for bad blocks, mtd c1b3d000 size (in 512 byte blocks) is 65280

(2)0x00000000-0x02000000 : "P10"

(2)Scanning NAND flash mtd c1b3d200 (2048 eraseblocks) for bad blocks

(2)block 7 is bad

(2)block 26 is bad

(2)block 33 is bad

(2)block 128 is bad

(2)block 459 is bad

(2)block 795 is bad

(2)block 1124 is bad

(2)block 1543 is bad

(2)After accounting for bad blocks, mtd c1b3d200 size (in 512 byte blocks) is 65280

(2)NET4: Linux TCP/IP 1.0 for NET4.0

(2)IP Protocols: ICMP, UDP, TCP, IGMP

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

(2)TCP: Hash tables configured (established 2048 bind 4096)

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

(2)VFS: Mounted root (cramfs filesystem) readonly.�(2)Mounted devfs on /dev

(2)Freeing unused kernel memory: 68k init

(3)Empty flash at 0x000c96cc ends at 0x000c9800

(3)Empty flash at 0x00221804 ends at 0x00221a00

(3)Empty flash at 0x008bd164 ends at 0x008bd200

(3)Empty flash at 0x00f02744 ends at 0x00f02800

(4)jffs2_get_inode_nodes(): Data CRC failed on node at 0x000c9488: Read 0x34eb3c21, calculated 0xa173e4a1

Initializing random number generator...

insmod: /lib/modules/2.4.22-rincon-11.3-16107-diag-dev-jpeters-200904111055: No such file or directory

insmod: /lib/modules: No such file or directory

insmod: cifs.o: no module by that name found

Using /wifi/N/ath_hal.o

Warning: loading ath_hal will taint the kernel: no license

  See http://www.tux.org/lkml/#export-tainted for information about tainted modules

(4)ath_hal: 0.9.14.25 (AR5416, DEBUG, REGOPS_FUNC)

Using /wifi/N/ath_driver.o

Warning: loading ath_driver will taint the kernel: no license

  See http://www.tux.org/lkml/#export-tainted for information about tainted modules

(5)ath0: registered with power management

(5)ath0: Atheros 5416 PCI: mem=0xa0000000, irq=19

Using MDP serial number 000E58580004A

Current wifi address: 00:1D:6A:56:AB:EE

Setting interface eth0 MAC address 00:0E:58:AF:FF:00 -> 00:0E:58:58:00:04

Setting interface eth1 MAC address 00:0E:58:6F:FF:00 -> 00:0E:58:58:00:04

Setting interface ath0 MAC address 00:1D:6A:56:AB:EE -> 00:0E:58:58:00:05

(5)ath0: set MAC address to 00:0E:58:58:00:05

Starting internet superserver: inetd.

PING 169.254.2.2 (169.254.2.2): 56 data bytes

Using /jffs/audiodev.o

Warning: loading audiodev will taint the kernel: no license

  See http://www.tux.org/lkml/#export-tainted for information about tainted modules

(5)dsp: Initializing DSP ... Allocated 80 bytes of DPRAM for 10 transmit buffer descriptors at c1695e10

(5)Complete

(5)dsp: registered.

/etc/Configure: 86: /opt/bin/smbscand: not found

Please press Enter to activate this console. (5)jffs2_get_inode_nodes(): Data CRC failed on node at 0x00f023cc: Read 0xa5d513c3, calculated 0xd8d023c0

(5)jffs2_get_inode_nodes(): Data CRC failed on node at 0x008bcde8: Read 0x87a73fbf, calculated 0xd47158f1

(5)jffs2_get_inode_nodes(): Data CRC failed on node at 0x002214bc: Read 0x0132f16e, calculated 0x1b3ef3b0

(7)CS44800 initialized


2 replies

Userlevel 7
Badge +22

My reading of this is that the flash has failed, but I am not an expert in this area. Even if you could find a clean version of the corrupted file, if the flash is toast I’m not sure what you could do with it.

My reading of this is that the flash has failed, but I am not an expert in this area. Even if you could find a clean version of the corrupted file, if the flash is toast I’m not sure what you could do with it.

nand flash has bad block is normal.But the filesystem can bypass the bad block after erase block. I think use the same smbscand file, maybe can fix the problem.

Reply