Loading ...
Sorry, an error occurred while loading the content.

Re: bad flash or dead?

Expand Messages
  • pietpukje80
    I have tried another psu (5volt- 3,5A) and that did not help. I also replaced the capacitors C13 and C28. But I still get the same error message with the old
    Message 1 of 14 , Apr 7, 2009
    • 0 Attachment
      I have tried another psu (5volt- 3,5A) and that did not help.
      I also replaced the capacitors C13 and C28.
      But I still get the same error message with the old and new psu.
      I don't have a usb powered hub, so i can't try that, but there is a 5v output on the nslu2 usb.
    • pietpukje80
      i got connected the nslu2 with a serial port and this is the log when booted: +Ethernet eth0: MAC address 00:14:bf:70:e2:cc IP: 192.168.0.1/255.255.255.0,
      Message 2 of 14 , Apr 10, 2009
      • 0 Attachment
        i got connected the nslu2 with a serial port and this is the log when booted:
        +Ethernet eth0: MAC address 00:14:bf:70:e2:cc
        IP: 192.168.0.1/255.255.255.0, Gateway: 192.168.0.1
        Default server: 0.0.0.0, DNS server IP: 0.0.0.0

        RedBoot(tm) bootstrap and debug environment [ROMRAM]
        Red Hat certified release, version 1.92 - built 15:16:07, Feb 3 2004

        Platform: IXDP425 Development Platform (XScale)
        Copyright (C) 2000, 2001, 2002, Red Hat, Inc.

        RAM: 0x00000000-0x02000000, 0x000723a0-0x01ff3000 available
        FLASH: 0x50000000 - 0x50800000, 64 blocks of 0x00020000 bytes each.
        == Executing boot script in 2.000 seconds - enter ^C to abort
        RedBoot> boot;exec 0x01d00000
        have eRcOmM
        copy kernel code from flash to RAM
        copy ramdisk file from flash to RAM
        run kernel
        Using base address 0x01d00000 and length 0x000f0f4c
        Uncompressing Linux.............................................................
        ... done, booting the kernel.
        Linux version 2.4.22-xfs (shearer@sure_linux) (gcc version 3.2.1) #430 Sat Jul 2
        15:01:45 CST 2005
        CPU: XScale-IXP425/IXC1100 revision 1
        Machine: Intel IXDP425 Developm
        Warning: bad configuration page, trying to continue
        Security risk: creating user accessible mapping for 0x60000000 at 0xff00f000
        Security risk: creating user accessible mapping for 0x51000000 at 0xf1000000
        On node 0 totalpages: 8192
        zone(0): 8192 pages.
        zone(1): 0 pages.
        zone(2): 0 pages.
        Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x01000000,10M m
        em=32M@0x00000000
        Calibrating delay loop... 263.78 BogoMIPS
        Memory: 32MB = 32MB total
        Memory: 20040KB available (1306K code, 554K data, 236K init)
        Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
        Inode cache hash table entries: 2048 (order: 2, 16384 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: 8192 (order: 3, 32768 bytes)
        POSIX conformance testing by UNIFIX
        PCI Autoconfig: Found Bus 0, Device 1, Function 0
        PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000
        PCI Autoconfig: Found Bus 0, Device 1, Function 1
        PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bffe000
        PCI Autoconfig: Found Bus 0, Device 1, Function 2
        PCI Autoconfig: BAR 0, Mem, size=0x100, address=0x4bffdf00
        PCI: bus0: Fast back to back transfers disabled
        Linux NET4.0 for Linux 2.4
        Based upon Swansea University Computer Society NET3.039
        Initializing RT netlink socket
        Starting kswapd
        VFS: Disk quotas vdquot_6.5.1
        Journalled Block Device driver loaded
        i2c-core.o: i2c core module
        i2c-dev.o: i2c /dev entries driver module
        i2c-core.o: driver i2c-dev dummy
        i2c-algo-bit.o: i2c bit algorithm module version 2.6.1 (20010830)
        pty: 256 Unix98 ptys configured
        Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
        abled
        ttyS00 at 0xff000003 (irq = 15) is a XScale UART
        ttyS01 at 0xff001003 (irq = 13) is a XScale UART
        RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
        SCSI subsystem driver Revision: 1.00
        * host:<NULL>
        cfi_cmdset_0001: Erase suspend on write enabled
        Using buffer write method
        Using static MTD partitions.
        Creating 4 MTD partitions on "IXP425 Flash":
        0x00000000-0x00040000 : "RedBoot "
        0x00040000-0x00060000 : "System Configuration"
        0x00060000-0x00160000 : "Kernel"
        0x00160000-0x00800000 : "Ramdisk"
        usb.c: registered new driver hub
        pci probe begin
        ehci_hcd 00:01.2: NEC Corporation USB 2.0
        ehci_hcd 00:01.2: irq 26, pci mem c3801f00
        usb.c: new USB bus registered, assigned bus number 1
        PCI: 00:01.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
        PCI: 00:01.2 PCI cache line size corrected to 32.
        ehci_hcd 00:01.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
        Device descriptor:8 bytes received.
        Device descriptor:18 bytes received.
        hub.c: USB hub found
        hub.c: 5 ports detected
        pci probe ok
        host/usb-uhci.c: $Revision: 1.3 $ time 15:02:12 Jul 2 2005
        host/usb-uhci.c: High bandwidth mode enabled
        host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
        host/usb-ohci.c: USB OHCI at membase 0xc3809000, IRQ 28
        host/usb-ohci.c: usb-00:01.0, NEC Corporation USB
        usb.c: new USB bus registered, assig
        Device descriptor:8 bytes received.
        Device descriptor:18 bytes received.
        hub.c: USB hub found
        hub.c: 3 ports detected
        host/usb-ohci.c: USB OHCI at membase 0xc380f000, IRQ 27
        host/usb-ohci.c: usb-00:01.1, NEC Corporation USB (#2)
        usb.c: new USB bus registered, assigned bus number 3
        Device descriptor:8 bytes received.
        Device descriptor:18 bytes received.
        hub.c: USB hub found
        hub.c: 2 ports detected
        Initializing USB Mass Storage driver...
        usb.c: registered new driver usb-storage
        USB Mass Storage support registered.
        i2c-dev.o: Registered 'IXP425 I2C Adapter' as minor 0
        i2c-core.o: adapter IXP425 I2C Adapter registered as adapter 0.
        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 2048 bind 4096)
        IP-Config: No network devices available.
        NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
        NetWinder Floating Point Emulator V0.97 (double precision)
        RAMDISK: Compressed image found at block 0
        invalid compressed format (err=1)<6>Freeing initrd memory: 10240K
        VFS: Mounted root (ext2 filesystem) readonly.
        Freeing init memory: 236K
        Kernel panic: No init found. Try passing init= option to kernel.

        I find 2 errors:
        Warning: bad configuration page, trying to continue
        And Kernel panic: No init found. Try passing init= option to kernel.
        could it be that my sysconf area is corrupted???
      • Rod Whitby
        Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing. -- Rod ... From: pietpukje80
        Message 3 of 14 , Apr 10, 2009
        • 0 Attachment
          Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
          -- Rod

          -----Original Message-----
          From: "pietpukje80" <pietpukje80@...>
          Date: Friday, Apr 10, 2009 10:50 pm
          Subject: [nslu2-linux] serial log
          To: nslu2-linux@yahoogroups.comReply-To: nslu2-linux@yahoogroups.com

          i got connected the nslu2 with a serial port and this is the log when booted:
          >+Ethernet eth0: MAC address 00:14:bf:70:e2:cc
          >IP: 192.168.0.1/255.255.255.0, Gateway: 192.168.0.1
          >Default server: 0.0.0.0, DNS server IP: 0.0.0.0
          >
          >RedBoot(tm) bootstrap and debug environment [ROMRAM]
          >Red Hat certified release, version 1.92 - built 15:16:07, Feb 3 2004
          >
          >Platform: IXDP425 Development Platform (XScale)
          >Copyright (C) 2000, 2001, 2002, Red Hat, Inc.
          >
          >RAM: 0x00000000-0x02000000, 0x000723a0-0x01ff3000 available
          >FLASH: 0x50000000 - 0x50800000, 64 blocks of 0x00020000 bytes each.
          >== Executing boot script in 2.000 seconds - enter ^C to abort
          >RedBoot> boot;exec 0x01d00000
          >have eRcOmM
          >copy kernel code from flash to RAM
          >copy ramdisk file from flash to RAM
          >run kernel
          >Using base address 0x01d00000 and length 0x000f0f4c
          >Uncompressing Linux.............................................................
          >... done, booting the kernel.
          >Linux version 2.4.22-xfs (shearer@sure_linux) (gcc version 3.2.1) #430 Sat Jul 2
          > 15:01:45 CST 2005
          >CPU: XScale-IXP425/IXC1100 revision 1
          >Machine: Intel IXDP425 Developm
          >Warning: bad configuration page, trying to continue
          >Security risk: creating user accessible mapping for 0x60000000 at 0xff00f000
          >Security risk: creating user accessible mapping for 0x51000000 at 0xf1000000
          >On node 0 totalpages: 8192
          >zone(0): 8192 pages.
          >zone(1): 0 pages.
          >zone(2): 0 pages.
          >Kernel command line: console=ttyS0,115200 root=/dev/ram0 initrd=0x01000000,10M m
          >em=32M@0x00000000
          >Calibrating delay loop... 263.78 BogoMIPS
          >Memory: 32MB = 32MB total
          >Memory: 20040KB available (1306K code, 554K data, 236K init)
          >Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)
          >Inode cache hash table entries: 2048 (order: 2, 16384 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: 8192 (order: 3, 32768 bytes)
          >POSIX conformance testing by UNIFIX
          >PCI Autoconfig: Found Bus 0, Device 1, Function 0
          >PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bfff000
          >PCI Autoconfig: Found Bus 0, Device 1, Function 1
          >PCI Autoconfig: BAR 0, Mem, size=0x1000, address=0x4bffe000
          >PCI Autoconfig: Found Bus 0, Device 1, Function 2
          >PCI Autoconfig: BAR 0, Mem, size=0x100, address=0x4bffdf00
          >PCI: bus0: Fast back to back transfers disabled
          >Linux NET4.0 for Linux 2.4
          >Based upon Swansea University Computer Society NET3.039
          >Initializing RT netlink socket
          >Starting kswapd
          >VFS: Disk quotas vdquot_6.5.1
          >Journalled Block Device driver loaded
          >i2c-core.o: i2c core module
          >i2c-dev.o: i2c /dev entries driver module
          >i2c-core.o: driver i2c-dev dummy
          >i2c-algo-bit.o: i2c bit algorithm module version 2.6.1 (20010830)
          >pty: 256 Unix98 ptys configured
          >Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI en
          >abled
          >ttyS00 at 0xff000003 (irq = 15) is a XScale UART
          >ttyS01 at 0xff001003 (irq = 13) is a XScale UART
          >RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
          >SCSI subsystem driver Revision: 1.00
          >* host:<NULL>
          >cfi_cmdset_0001: Erase suspend on write enabled
          >Using buffer write method
          >Using static MTD partitions.
          >Creating 4 MTD partitions on "IXP425 Flash":
          >0x00000000-0x00040000 : "RedBoot "
          >0x00040000-0x00060000 : "System Configuration"
          >0x00060000-0x00160000 : "Kernel"
          >0x00160000-0x00800000 : "Ramdisk"
          >usb.c: registered new driver hub
          >pci probe begin
          >ehci_hcd 00:01.2: NEC Corporation USB 2.0
          >ehci_hcd 00:01.2: irq 26, pci mem c3801f00
          >usb.c: new USB bus registered, assigned bus number 1
          >PCI: 00:01.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW.
          >PCI: 00:01.2 PCI cache line size corrected to 32.
          >ehci_hcd 00:01.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Jun-19/2.4
          >Device descriptor:8 bytes received.
          >Device descriptor:18 bytes received.
          >hub.c: USB hub found
          >hub.c: 5 ports detected
          >pci probe ok
          >host/usb-uhci.c: $Revision: 1.3 $ time 15:02:12 Jul 2 2005
          >host/usb-uhci.c: High bandwidth mode enabled
          >host/usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
          >host/usb-ohci.c: USB OHCI at membase 0xc3809000, IRQ 28
          >host/usb-ohci.c: usb-00:01.0, NEC Corporation USB
          >usb.c: new USB bus registered, assig
          >Device descriptor:8 bytes received.
          >Device descriptor:18 bytes received.
          >hub.c: USB hub found
          >hub.c: 3 ports detected
          >host/usb-ohci.c: USB OHCI at membase 0xc380f000, IRQ 27
          >host/usb-ohci.c: usb-00:01.1, NEC Corporation USB (#2)
          >usb.c: new USB bus registered, assigned bus number 3
          >Device descriptor:8 bytes received.
          >Device descriptor:18 bytes received.
          >hub.c: USB hub found
          >hub.c: 2 ports detected
          >Initializing USB Mass Storage driver...
          >usb.c: registered new driver usb-storage
          >USB Mass Storage support registered.
          >i2c-dev.o: Registered 'IXP425 I2C Adapter' as minor 0
          >i2c-core.o: adapter IXP425 I2C Adapter registered as adapter 0.
          >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 2048 bind 4096)
          >IP-Config: No network devices available.
          >NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
          >NetWinder Floating Point Emulator V0.97 (double precision)
          >RAMDISK: Compressed image found at block 0
          >invalid compressed format (err=1)<6>Freeing initrd memory: 10240K
          >VFS: Mounted root (ext2 filesystem) readonly.
          >Freeing init memory: 236K
          >Kernel panic: No init found. Try passing init= option to kernel.
          >
          >I find 2 errors:
          >Warning: bad configuration page, trying to continue
          >And Kernel panic: No init found. Try passing init= option to kernel. could it be that my sysconf area is corrupted???
          >
          >
          >
          >------------------------------------
          >
          >Yahoo! Groups Links
          >
          >
          >
          >
        • pietpukje80
          ... the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress: 3bfeff+0005c0
          Message 4 of 14 , Apr 11, 2009
          • 0 Attachment
            --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
            >
            > Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
            > -- Rod
            >
            the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
            3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu---------------------------------
            broadcast: flash programming error [std::exception]
            The NSLU2 reported an error reprogramming the flash, this is
            potentially a serious hardware problem, however it is probably
            worth while retrying the upgrade to see if the problem is
            temporary.

            is there a memcheck so i can check the flash memory for errors?
          • bullfrog528
            ... I suspect others may give better suggestions, not sure if you ve tried linking to the serial port. If you have, then this may work or at least give a
            Message 5 of 14 , Apr 11, 2009
            • 0 Attachment
              --- In nslu2-linux@yahoogroups.com, "pietpukje80" <pietpukje80@...> wrote:
              >
              > --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@> wrote:
              > >
              > > Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
              > > -- Rod
              > >
              > the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
              > 3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu---------------------------------
              > broadcast: flash programming error [std::exception]
              > The NSLU2 reported an error reprogramming the flash, this is
              > potentially a serious hardware problem, however it is probably
              > worth while retrying the upgrade to see if the problem is
              > temporary.
              >
              > is there a memcheck so i can check the flash memory for errors?
              >

              I suspect others may give better suggestions, not sure if you've tried linking to the serial port. If you have, then this may work or at least give a clearer understanding of the problem.

              http://www.nslu2-linux.org/wiki/HowTo/RecoverFromABadFlashUsingOnlyTheSerialPort

              Bullfrog
            • Rod Whitby
              Try loading an image with RedBoot (be *very* careful that you do not overwrite RedBoot when doing this). It looks to me like you actually do have a bad flash
              Message 6 of 14 , Apr 11, 2009
              • 0 Attachment
                Try loading an image with RedBoot (be *very* careful that you do not overwrite RedBoot when doing this).
                It looks to me like you actually do have a bad flash sector in your hardware. You may be able to get around this by using a distro that has jffs2 (which may skip over the bad block) at that location - perhaps Openwrt.
                -- Rod

                -----Original Message-----
                From: "pietpukje80" <pietpukje80@...>
                Date: Saturday, Apr 11, 2009 7:46 pm
                Subject: [nslu2-linux] Re: serial log
                To: nslu2-linux@yahoogroups.comReply-To: nslu2-linux@yahoogroups.com

                --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
                >
                >> Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
                > -- Rod
                >
                >the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
                >3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu--------------------------------- broadcast: flash programming error [std::exception]
                >The NSLU2 reported an error reprogramming the flash, this is
                >potentially a serious hardware problem, however it is probably
                >worth while retrying the upgrade to see if the problem is
                >temporary.
                >
                >is there a memcheck so i can check the flash memory for errors?
                >
                >
                >
                >
                >
                >------------------------------------
                >
                >Yahoo! Groups Links
                >
                >
                >
                >
              • Kirk Wallace
                ... It looks like Digikey has these flash chips available: http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=te28f640 ... Kirk
                Message 7 of 14 , Apr 11, 2009
                • 0 Attachment
                  On Sat, 2009-04-11 at 13:40 -0700, Rod Whitby wrote:
                  >
                  >
                  > Try loading an image with RedBoot (be *very* careful that you do not
                  > overwrite RedBoot when doing this).
                  > It looks to me like you actually do have a bad flash sector in your
                  > hardware. You may be able to get around this by using a distro that
                  > has jffs2 (which may skip over the bad block) at that location -
                  > perhaps Openwrt.
                  > -- Rod

                  It looks like Digikey has these flash chips available:

                  http://search.digikey.com/scripts/DkSearch/dksus.dll?keywords=te28f640

                  -------------
                  Kirk
                  http://www.wallacecompany.com/machine_shop/
                • pietpukje80
                  Can i load it from a usb stick because serial uploading works but i can not write it to the flash. i got this error with serial uploading in RedBoot: RedBoot
                  Message 8 of 14 , Apr 13, 2009
                  • 0 Attachment
                    Can i load it from a usb stick because serial uploading works but i can not write it to the flash.
                    i got this error with serial uploading in RedBoot:

                    RedBoot> load -r -v -b 0x01000000 -m xm
                    CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                    xyzModem - CRC mode, 65537(SOH)/0(STX)/0(CAN) packets, 3 retries
                    RedBoot> cksum
                    Computing cksum for area 0x01000000-0x01800000
                    POSIX cksum = 4056400472 8388608 (0xf1c7c258 0x00800000)
                    RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                    * CAUTION * about to program FLASH
                    at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                    ... Erase from 0x50060000-0x50800000: .............................Err = a0

                    Can't erase region at 0x50400000: Error trying to erase
                    RedBoot> load -r -v -b 0x01000000 -m ymodem
                    CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                    xyzModem - CRC mode, 2(SOH)/8192(STX)/0(CAN) packets, 4 retries
                    RedBoot> cksum
                    Computing cksum for area 0x01000000-0x01800000
                    POSIX cksum = 451052206 8388608 (0x1ae282ae 0x00800000)
                    RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                    * CAUTION * about to program FLASH
                    at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                    ... Erase from 0x50060000-0x50800000: .............................Err = a0

                    Can't erase region at 0x50400000: Error trying to erase
                    RedBoot>

                    --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
                    >
                    > Try loading an image with RedBoot (be *very* careful that you do not overwrite RedBoot when doing this).
                    > It looks to me like you actually do have a bad flash sector in your hardware. You may be able to get around this by using a distro that has jffs2 (which may skip over the bad block) at that location - perhaps Openwrt.
                    > -- Rod
                    >
                    > -----Original Message-----
                    > From: "pietpukje80" <pietpukje80@...>
                    > Date: Saturday, Apr 11, 2009 7:46 pm
                    > Subject: [nslu2-linux] Re: serial log
                    > To: nslu2-linux@...: nslu2-linux@yahoogroups.com
                    >
                    > --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@> wrote:
                    > >
                    > >> Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
                    > > -- Rod
                    > >
                    > >the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
                    > >3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu--------------------------------- broadcast: flash programming error [std::exception]
                    > >The NSLU2 reported an error reprogramming the flash, this is
                    > >potentially a serious hardware problem, however it is probably
                    > >worth while retrying the upgrade to see if the problem is
                    > >temporary.
                    > >
                    > >is there a memcheck so i can check the flash memory for errors?
                    > >
                    > >
                    > >
                    > >
                    > >
                    > >------------------------------------
                    > >
                    > >Yahoo! Groups Links
                    > >
                    > >
                    > >
                    > >
                    >
                  • Rod Whitby
                    That s clearly a hardware flash chip problem. If RedBoot can t erase it, then that 256kB block is dead forever. You will never be able to use upslug2 or write
                    Message 9 of 14 , Apr 13, 2009
                    • 0 Attachment
                      That's clearly a hardware flash chip problem. If RedBoot can't erase it, then that 256kB block is dead forever.
                      You will never be able to use upslug2 or write a whole image with redboot unless you replace the flash chip (very difficult).
                      The only other option will be to create a custom image which skips the bad block, and then use RedBoot to write the two parts of that image before and after the bad block.
                      You will need to read the wiki carefully regarding the flash layout, and you will need to understand how to use slugimage, including reading the Perl source code to understand the -r option advanced syntax to include a dummy block in the right place.
                      Then you would split the resulting image using dd into three pieces (before the bad block, dummy for the bad block, after the bad block), and flash the two good pieces using RedBoot.
                      -- Rod

                      -----Original Message-----
                      From: "pietpukje80" <pietpukje80@...>
                      Date: Monday, Apr 13, 2009 11:42 pm
                      Subject: [nslu2-linux] Re: serial log
                      To: nslu2-linux@yahoogroups.comReply-To: nslu2-linux@yahoogroups.com

                      Can i load it from a usb stick because serial uploading works but i can not write it to the flash. i got this error with serial uploading in RedBoot:
                      >
                      >RedBoot> load -r -v -b 0x01000000 -m xm
                      >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                      >xyzModem - CRC mode, 65537(SOH)/0(STX)/0(CAN) packets, 3 retries
                      >RedBoot> cksum
                      >Computing cksum for area 0x01000000-0x01800000
                      >POSIX cksum = 4056400472 8388608 (0xf1c7c258 0x00800000)
                      >RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                      >* CAUTION * about to program FLASH
                      > at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                      >... Erase from 0x50060000-0x50800000: .............................Err = a0
                      >
                      >Can't erase region at 0x50400000: Error trying to erase
                      >RedBoot> load -r -v -b 0x01000000 -m ymodem
                      >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                      >xyzModem - CRC mode, 2(SOH)/8192(STX)/0(CAN) packets, 4 retries
                      >RedBoot> cksum
                      >Computing cksum for area 0x01000000-0x01800000
                      >POSIX cksum = 451052206 8388608 (0x1ae282ae 0x00800000)
                      >RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                      >* CAUTION * about to program FLASH
                      > at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                      >... Erase from 0x50060000-0x50800000: .............................Err = a0
                      >
                      >Can't erase region at 0x50400000: Error trying to erase
                      >RedBoot>
                      >
                      >--- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
                      >
                      >> Try loading an image with RedBoot (be *very* careful that you do not overwrite RedBoot when doing this).
                      > It looks to me like you actually do have a bad flash sector in your hardware. You may be able to get around this by using a distro that has jffs2 (which may skip over the bad block) at that location - perhaps Openwrt.
                      > -- Rod
                      >
                      > -----Original Message-----
                      > From: "pietpukje80" <pietpukje80@...>
                      > Date: Saturday, Apr 11, 2009 7:46 pm
                      > Subject: [nslu2-linux] Re: serial log
                      > To: nslu2-linux@...: nslu2-linux@yahoogroups.com
                      >
                      > --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@> wrote:
                      > >
                      > >> Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
                      > > -- Rod
                      > >
                      > >the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
                      > >3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu--------------------------------- broadcast: flash programming
                    • pietpukje80
                      Maybe a stupid question but, you mean with the flash chip, the 2 memory chips with the text U10 between then? Because a friend of my has a smd rework station,
                      Message 10 of 14 , Apr 14, 2009
                      • 0 Attachment
                        Maybe a stupid question but, you mean with the flash chip, the 2 memory chips with the text U10 between then?
                        Because a friend of my has a smd rework station, so if i find the right sdram modules i can change this 2 chips and do i need then a j-tag to restore the bootloader or is that another chip?


                        --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
                        >
                        > That's clearly a hardware flash chip problem. If RedBoot can't erase it, then that 256kB block is dead forever.
                        > You will never be able to use upslug2 or write a whole image with redboot unless you replace the flash chip (very difficult).
                        > The only other option will be to create a custom image which skips the bad block, and then use RedBoot to write the two parts of that image before and after the bad block.
                        > You will need to read the wiki carefully regarding the flash layout, and you will need to understand how to use slugimage, including reading the Perl source code to understand the -r option advanced syntax to include a dummy block in the right place.
                        > Then you would split the resulting image using dd into three pieces (before the bad block, dummy for the bad block, after the bad block), and flash the two good pieces using RedBoot.
                        > -- Rod
                        >
                        > -----Original Message-----
                        > From: "pietpukje80" <pietpukje80@...>
                        > Date: Monday, Apr 13, 2009 11:42 pm
                        > Subject: [nslu2-linux] Re: serial log
                        > To: nslu2-linux@...: nslu2-linux@yahoogroups.com
                        >
                        > Can i load it from a usb stick because serial uploading works but i can not write it to the flash. i got this error with serial uploading in RedBoot:
                        > >
                        > >RedBoot> load -r -v -b 0x01000000 -m xm
                        > >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                        > >xyzModem - CRC mode, 65537(SOH)/0(STX)/0(CAN) packets, 3 retries
                        > >RedBoot> cksum
                        > >Computing cksum for area 0x01000000-0x01800000
                        > >POSIX cksum = 4056400472 8388608 (0xf1c7c258 0x00800000)
                        > >RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                        > >* CAUTION * about to program FLASH
                        > > at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                        > >... Erase from 0x50060000-0x50800000: .............................Err = a0
                        > >
                        > >Can't erase region at 0x50400000: Error trying to erase
                        > >RedBoot> load -r -v -b 0x01000000 -m ymodem
                        > >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                        > >xyzModem - CRC mode, 2(SOH)/8192(STX)/0(CAN) packets, 4 retries
                        > >RedBoot> cksum
                        > >Computing cksum for area 0x01000000-0x01800000
                        > >POSIX cksum = 451052206 8388608 (0x1ae282ae 0x00800000)
                        > >RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                        > >* CAUTION * about to program FLASH
                        > > at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                        > >... Erase from 0x50060000-0x50800000: .............................Err = a0
                        > >
                        > >Can't erase region at 0x50400000: Error trying to erase
                        > >RedBoot>
                        > >
                        > >--- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@> wrote:
                        > >
                        > >> Try loading an image with RedBoot (be *very* careful that you do not overwrite RedBoot when doing this).
                        > > It looks to me like you actually do have a bad flash sector in your hardware. You may be able to get around this by using a distro that has jffs2 (which may skip over the bad block) at that location - perhaps Openwrt.
                        > > -- Rod
                        > >
                        > > -----Original Message-----
                        > > From: "pietpukje80" <pietpukje80@>
                        > > Date: Saturday, Apr 11, 2009 7:46 pm
                        > > Subject: [nslu2-linux] Re: serial log
                        > > To: nslu2-linux@: nslu2-linux@yahoogroups.com
                        > >
                        > > --- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@> wrote:
                        > > >
                        > > >> Your initrd is corrupted. A reflash is required. Make sure you check the md5sum of the image you downloaded before flashing.
                        > > > -- Rod
                        > > >
                        > > >the md5sum is good, but i can not reflash the nslu2, see my first post, every image i try i get the error at the same adress:
                        > > >3bfeff+0005c0 ...UUUUUUUUUUUUUUUUUUUUUUUUUUuu--------------------------------- broadcast: flash programming
                        >
                      • Rod Whitby
                        The wiki has details of which chips are which. The bootloader is in the flash chip before everything else, and yes you would need jtag access to put it back
                        Message 11 of 14 , Apr 14, 2009
                        • 0 Attachment
                          The wiki has details of which chips are which.
                          The bootloader is in the flash chip before everything else, and yes you would need jtag access to put it back into a new flash chip.
                          -- Rod

                          -----Original Message-----
                          From: "pietpukje80" <pietpukje80@...>
                          Date: Tuesday, Apr 14, 2009 6:54 pm
                          Subject: [nslu2-linux] Re: serial log
                          To: nslu2-linux@yahoogroups.comReply-To: nslu2-linux@yahoogroups.com

                          Maybe a stupid question but, you mean with the flash chip, the 2 memory chips with the text U10 between then? Because a friend of my has a smd rework station, so if i find the right sdram modules i can change this 2 chips and do i need then a j-tag to restore the bootloader or is that another chip?
                          >
                          >
                          >--- In nslu2-linux@yahoogroups.com, "Rod Whitby" <rod@...> wrote:
                          >
                          >> That's clearly a hardware flash chip problem. If RedBoot can't erase it, then that 256kB block is dead forever.
                          > You will never be able to use upslug2 or write a whole image with redboot unless you replace the flash chip (very difficult).
                          > The only other option will be to create a custom image which skips the bad block, and then use RedBoot to write the two parts of that image before and after the bad block.
                          > You will need to read the wiki carefully regarding the flash layout, and you will need to understand how to use slugimage, including reading the Perl source code to understand the -r option advanced syntax to include a dummy block in the right place.
                          > Then you would split the resulting image using dd into three pieces (before the bad block, dummy for the bad block, after the bad block), and flash the two good pieces using RedBoot.
                          > -- Rod
                          >
                          > -----Original Message-----
                          > From: "pietpukje80" <pietpukje80@...>
                          > Date: Monday, Apr 13, 2009 11:42 pm
                          > Subject: [nslu2-linux] Re: serial log
                          > To: nslu2-linux@...: nslu2-linux@yahoogroups.com
                          >
                          > Can i load it from a usb stick because serial uploading works but i can not write it to the flash. i got this error with serial uploading in RedBoot:
                          > >
                          > >RedBoot> load -r -v -b 0x01000000 -m xm
                          > >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                          > >xyzModem - CRC mode, 65537(SOH)/0(STX)/0(CAN) packets, 3 retries
                          > >RedBoot> cksum
                          > >Computing cksum for area 0x01000000-0x01800000
                          > >POSIX cksum = 4056400472 8388608 (0xf1c7c258 0x00800000)
                          > >RedBoot> fis write -f 0x50060000 -b 0x01060000 -l 0x7a0000
                          > >* CAUTION * about to program FLASH
                          > > at 0x50060000..0x507fffff from 0x01060000 - continue (y/n)? y
                          > >... Erase from 0x50060000-0x50800000: .............................Err = a0
                          > >
                          > >Can't erase region at 0x50400000: Error trying to erase
                          > >RedBoot> load -r -v -b 0x01000000 -m ymodem
                          > >CRaw file loaded 0x01000000-0x017fffff, assumed entry at 0x01000000
                          > >xyzModem - CRC mode, 2(SOH)/8192(STX)/0(CAN) packets, 4 retries
                          > >RedBoot> cksum
                        Your message has been successfully submitted and would be delivered to recipients shortly.