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

Re: serial log

Expand Messages
  • 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 1 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 2 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 3 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 4 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 5 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 6 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 7 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 8 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.