DM8000 - can't flash - too much data (or bad sectors)

Discussion in 'Hardware troubles and Repair support.' started by jumperger, May 5, 2019.

Tags:
Page 1 of 4
  1. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    Hi,
    My dm8000 original brings the following error when I attempt to flash:
    Code:
    too much data (or bad sectors) in partition 3 (end: 10000000, pos: 10000000)
    after I gave DreamUp a try with "recovery of bad sectors" Enabled I got this error:
    Code:
    Flashing failed (!!! 005 too much data (or bad sectors) in partition 2 (end: 00800000, pos: 00800000)), box will be unusable now!!
    Will I have to replace the flash-chip? is this possible?
    Prior to trying to flash I had issues with the tuners, tuners were not always recognized, when unpluging one of the 2 DVB-T tuners , the 3 remaining where recognized.
    After this the box became problems to power up from standby, I had to switch on and off several times to boot.
    Some days or weeks later the box did not boot anymore .
    And now I try to flash, but it does not work.

    I have access to the box by telnet into the BIOS
    I have access to the box by browser using the IP of the Box
    I have access to the box by DreamUp with IP and RS232

    When I enable "recovery of bad sectors" in DreamUp and flash or in BIOS and flash using old portable firefox, I get the same error:
    Code:
    00:30:51 box type: DM8000
00:30:51 Enabled recovery of bad sectors
00:32:00 Calculating checksum...
00:32:02 Uploading file to box...
00:32:52 box is flashing from its memory...
00:32:57 Log: +++ 015 bad sector recovery enabled
00:32:57 Log: +++ 006 verify failed, at 00180000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 001a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 001c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 001e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00200000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00220000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00240000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00260000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00280000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 002a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 002c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 002e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00300000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00320000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00340000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00360000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00380000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 003a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 003c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 003e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00400000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00420000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00440000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00460000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00480000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 004a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 004c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 004e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00500000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00520000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00540000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00560000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00580000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 005a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 005c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 005e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00600000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00620000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00640000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00660000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00680000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 006a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 006c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 006e0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00700000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00720000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00740000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00760000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 00780000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 007a0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 007c0000: 60. Block will be marked as bad.
00:32:57 Log: +++ 006 verify failed, at 007e0000: 60. Block will be marked as bad.
00:32:57 Flashing failed (!!! 005 too much data (or bad sectors) in partition 2 (end: 00800000, pos: 00800000)), box will be unusable now!!
    BIOS-Info looks like this:
    [​IMG]

    I hope you may help me to get my beloved dm8000 to life again.
    Thank you for your help
     
    jumperger, May 5, 2019
    #1
  2. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Yeah, sorry to say but it has to much bad sectors, thus the nand flash chip needs to be replaced for a new one, and yes, when you have the right skills and tools to remove the old nand flash chip, and to solder the new one, then it's not so difficult to do.

    Tuners issue may also be related to the bad nand flash chip, however it may also be cause due other hardware issues.
    But this you can only known after replacing the nand flash chip.
     
    Johnny B., May 5, 2019
    #2
  3. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    Thank you for replying to my question.
    Do you know where I could order this nand flash chip and what are the references?

    I'm not a solder hero, but I do have a soler/desolderstation with hot air, never used it for chips, but as the DM8000 is dead, it could not come worse.
     
    jumperger, May 5, 2019
    #3
  4. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    It depends a bit which one you have, brand may differ but further the same specs.
    In any case, mine boards has the MT29F2G08AAD 2GBit Flash Memory from MICRON
    Search for example at Ebay to MT29F2G08AAD and you will find some sellers.
     
    Johnny B., May 5, 2019
    #4
  5. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    so it should be this chip (picture from my dm8000 rev.6)
    [​IMG]

    As their are 2 places, is it possible to put 2 chips in and get 4GB Flash this way?
     
    jumperger, May 5, 2019
    #5
  6. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Yes it's the U904, and yeah good question of what happens when you add two of them.
    To be honest, no clue, I've never tried this.

    dm8000hd-u904Snap.jpg

    By the way, better is to protect the surrounding area with kapton tape due the heat.
     
    Johnny B., May 5, 2019
    #6
  7. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    jumperger, May 5, 2019
    #7
  8. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Just see this,

    MT29F2G08AAD.jpg
    With other words, keep it to the MT29F2G08AAD WP-D
     
    Johnny B., May 5, 2019
    #8
  9. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    ET-D should be good too , as it seems to accept more temperature.
    Which temperature would you use on your solderstation?
     
    jumperger, May 5, 2019
    #9
  10. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    I normally use a piece of kapton tape for protecting the surrounding area, and use a Soldeer Picker for pulling on the nand chip, first one side until it's lift up, not to high otherwise you may damage the tracks on the other side of the chip, but enough to release it from the solder, then the other side.
    Temp, I use the highest setting to do it very fast or a lower temp and using solder flux paste.
    One rule, never stay on one place with a hot air gun, see youtube for instruction movies or search with google to,
    youtube, removing nand chip by hot air gun

    For example, this youtube one is a good example how it can be done, Hot air SMD MEMORY CHIP removal.
     
    Johnny B., May 5, 2019
    #10
  11. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    445
    Likes Received:
    554
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    Did you tried to change the CAPS on the PSU first ? As if you had a general problem of power (Tuners, reboots not finishing, and now Flash chip not writting)... it looks like to me more a PSU problem that doesn't give enough power... so checking the small CAP as on the clones could perhaps help ?

    On clone V1/V2 the caps are (same as on original as for v1 clone) :

    22uF/50V (C109) Model V1 or 47uF/50V Model V2

    Some people are using a 63V instead of 50V... perhaps it can help, and I would take a Rubycon instead. Then if this doesn't solve the problem, try to replace the 4 caps (if there is hills on them), that are 1000uF/35V (Again here you can use higher Voltage).

    Let us know... before touching the Flash chip, that could just have not enough Power from the PSU to write into it !

    TS
     
    toysoft, May 7, 2019
    #11
  12. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    Thanks for your advice,
    I changed all the Caps some time ago, I have also a working 7020HD, I think it has the same PSU, I will try to swap them and see what will happen.
    regards
    Jack
     
    jumperger, May 7, 2019
    #12
  13. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    445
    Likes Received:
    554
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    Yes, the PSU is exactly the same for DM7020HD and DM8000HD, test BOTH boxes when you swap the PSU as the symptoms you have with the DM8000HD could be different on the DM7020HD, and vice versa you are not sure the PSU of the DM7020HD is fully functionnal for the DM8000HD.

    TS
     
    toysoft, May 7, 2019
    #13
  14. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    Thanks for the hint.
    Does a special testing procedure exist for the PSU? Are the should-be voltages/Ohms known?
     
    jumperger, May 7, 2019
    #14
  15. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    445
    Likes Received:
    554
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    Swap them and let's see how it goes,

    TS
     
    toysoft, May 7, 2019
    #15
  16. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    I did the swap:
    UPS8000 in DM7020hd -> normal boot
    UPS7020 in DM8000pvr -> boots into ***STOP***

    Swapping the UPS did not change anything
     
    jumperger, May 8, 2019
    #16
  17. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    445
    Likes Received:
    554
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    Check the frontpanel button, to be sure it's not stuck.

    boots into ***STOP***

    If it's not stuck, then it means the Flash has no "vmlinux" (Kernel) file, so it will go back to Flashing mode.

    TS
     
    toysoft, May 8, 2019
    #17
  18. jumperger

    jumperger Member

    Messages:
    34
    Likes Received:
    1
    Trophy Points:
    8
    Gender:
    Male
    I have dismounted the front panel to be sure the button is not stuck.

    I have red that it's possible to boot from a USB-stick, tried it, but can't get it to run.
    I'm not sure that my Img file for the stick is right.

    Jack
     
    jumperger, May 8, 2019
    #18
  19. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    445
    Likes Received:
    554
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    I would still check the PSU with Johnny, to be sure it is fully OK,

    TS
     
    toysoft, May 8, 2019
    #19
  20. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,957
    Likes Received:
    1,576
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    I assume you use the dm7025+ psu because the dm7020 psu is a different power supply.
     
    Johnny B., May 9, 2019
    #20
Page 1 of 4