Vu+ Solo2 - HW ERROR

Discussion in 'VuPlus Solo2 Hardware troubles and Repair support.' started by Piotrekop, Nov 15, 2020.

  1. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    Solo2 works once and fails. (I got it for free). Sometimes it works after a hard power reset.
    Goes into a loop:

    Starting
    FPGA Update
    Checkin
    Erasing
    Writing
    Verifying
    Finished
    - HW ERROR

    I am attaching the logs with the SAT cable connected. and LAN (a), and without LAN and satellite cables (b). Solo2 without HDD.

    I did flashing on the original software vuplus-image-vusolo2-20191218151100_usb.zip and then OpenPLi _7.3

    I can see that there are also bad sectors, but does this amount exaggerate? Up to 10 sectors should not be disturbing. What can cause this error?

     

    Attached Files:

  2. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Nothing to find with google search to end trace 17cf52829e77ab1c
    But try it without the tuner(s) to see if the box become stable by starting up.

    Bad section question, max 10 bad sections may, a higher number may give issues and when that happens than it's better to replace the nand chip for a new one.

    Also, if you could find a image file which is less mb's than you now use, it may sufficient to still use the nand chip but that depends on which addresses the bad sectors are.
     
    raza05 likes this.
  3. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    I uploaded the original factory soft and also does not start. It recognizes USB does flashing and loops again and HW Error
     
    Last edited: Nov 16, 2020
  4. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Try it without the front panel connected, in any case I always remove everything of what is removable from the motherboard to see if it's caused only due the motherboard or not.

    You can flash the box without the front panel when you add a empty text file on the usb stick and call it force.update
    Thus only call it force.update and not force.update.txt

    Monitor with your putty in serial mode when the flash process are done, you will see a reboot counter on the end.
    remove the usb stick before it reboots, otherwise it repeat the flash process.
     
    raza05 likes this.
  5. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    I uploaded the factory image and cfe from this post https://jb8a8f8.com/support/index.php?threads/vu-solo2-original-not-starting.516/#post-4478 although I believe that cfe updates with every flash new image. Did not help.

    I used the image OpenPLi_4, which is a small flash volume and it did not help either.
    =============================================================================

    i did but it doesn't work. Solo2 is not working. Solo2 does not start when observing putts. Solo2 does not work when the front panel is detached. It is impossible to flash as you wrote. And there is no this counter in the logs?
    I am attaching logs while flashing. Still unchanged.
    I did some tests with different images and no changes either.
     

    Attached Files:

    Last edited: Nov 16, 2020
  6. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Ah yes sorry, i was still with you into the Vu+Duo2 mode, instead of this topic the Vu+Solo2 and by this box it needs the front panel to powering the motherboard.

    In any case, as first with these solo2 boxes it's important to know if your box is a original, or a clone version.
    Best is to give a picture from it to see what you have because there were several clone versions released, and when you dealing with a clone box, it may needs his own cfe file and software to operate fully.
     
    raza05 likes this.
  7. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Just a question about... Solo2 works once and fails.

    When it did, did the tuners than also worked, or gave it no reception screen.
     
  8. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    Well, I have duo2 and solo2. Yes, I know about the clones. No, no - it's original. I know what the clone of Vu + and Lonrinsun looks like. They differ significantly from the original made in korea.
    =============================================================================
    I got it for free as damaged. HW Error. I uploaded the original image and then OpenPLi_7.3 and it didn't work. He gets in a loop and again. It will restart itself every 180 seconds. After several self-reset and wake cycles, it worked. It was working for a week. HW Error again after a week. I manually reset it with the power supply 2-3 times and it worked again for several days. Now it resets itself again and restarts every 180 seconds but no longer loads the image. That's all.
     
  9. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Hmm okay, than it may be the nand flash chip, but be aware that you need to jtag the cfe file to a empty nand chip because I do not think that a empty nand flash chip will check the usb ports.

    But still, it may also be a issue with the tuners which can not be removed, or even the cpu or memory.
    Based on your log file that it oops after the tuners, it could be the tuners.
    I would check the tuner area, caps replacement etc.
     
    raza05 likes this.
  10. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8

    Attached Files:

    Last edited: Nov 16, 2020
  11. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Okay, so you have the HW Error which is often related to the FPGA chip, and often due a corrupt upgrade.
    Normally you should/could/maybe fix the "HW Error" /FPGA Security chip by upgraded it back to the oldie's FPGA upgrade, probally one from 2014 may sufficient.

    In any case, it is most likely related to the FPGA chip, probably due a corrupt or wrong upgrade.
     
    raza05 and Piotrekop like this.
  12. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    So upload the old original image from the Vu + website?
    I noticed that while starting Solo2, the CPU gets very hot. This is normal or is it a result of a failure?
    I have already tried with various images but to no avail.

    where to get such an old solo2 image?
     
  13. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    I think, read here the post from brunito with these error, the post from brunito, at Jan 25, 2019

    As for the stressed cpu, this may happen due the fact it is not starting up, the cpu must work harder than normal.
    It's another story when the box runs, and the cpu becomes very hot, then it could be a bad heatsink or cpu etc.
     
    raza05 and Piotrekop like this.
  14. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    Solo2 works on the BlackHole-2.0.7-vusolo2_usb.zip (2013) image and on BlackHole-2.0.7.1-vusolo2_usb.zip (2013)
    Online software update locks and freezes for Solo2 at "Starting".

    Until BlackHole-2.1.3-vusolo2_usb.zip (2014) to versions 2.1.7; 3.0.8 does not work. I didn't check further. This kind of doesn't do the trick, because I have an OpenPLi 7.3 (2020) image set up, which also doesn't work on but did work before.

    It also doesn't work on versions:

    BlackHole-3.0.9-vusolo2_usb_relea (2020); BlackHole-3.1.0-vusolo2_usb_release_20201005_b5f1952.zip (2020)
    http://www.vuplus-community.net/board/forums/openbh-vu-solo2-images.180/
    What to do to make it work on the latest images?
    I've read that some clone images work in the original solos2. Maybe it will help with updating to newer images?

    +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
    The image was also loaded but it didn't work with the clone. Solo2 started up but this image was not working.
    openpli-7.1-vusolo2-drgsolo2-20190624_usb.zip 2019-06-24 20:17 95M (https://e2.chickenkiller.com/images/)
    After flashing this image from clone, Solo2 started but the image does not work. Instead, he cleaned up all the rubbish - that's my theory. Factory painting

    Image Vu + Solo2 - OI 3.0 vuplus-image-vusolo2-20191218151100_usb.zip could not cope with the problem and it should. I flashed the image of Vu + Solo2 again - OI 3.0 vuplus-image-vusolo2-20191218151100_usb.zip
    and Solo2 started. Now you can upload any image, i.e. your preferred backup image.

    Solo2 works.

    Thanks for the help. Now I will be fixing the duo2.
     

    Attached Files:

    Last edited: Nov 17, 2020
    Johnny B. likes this.
  15. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    That was quite a undertake before you managed to fix it, but the result is that you now have a working Vu + Solo2, so congrats with repairing it.

    And thank you for explaining how you did it, always useful to someone else who may needs it.
     
    raza05 and toysoft like this.
  16. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    443
    Likes Received:
    551
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    HW-Error means the driver didn't upgrade the FPGA, so probably the use of a specific image, with the correct driver inside, updated the box FPGA chip, and then all worked from that moment.

    TS
     
    Piotrekop and raza05 like this.
  17. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    Maybe so, but why didn't that right image where Solo2 was working didn't update the driver? Could not update any version of the image. It was only done by an image on a clon that didn't work properly in solo2. It didn't really work, but it did cause Solo2 to unlock. Only after that it was possible to install the original factory image vu + OI 3.0. Rather, it was about more than just updating the driver. Especially since OpenPLi 7.3 worked earlier and then nothing wanted to work.
     
  18. toysoft

    toysoft Well-Known Member Staff Member

    Messages:
    443
    Likes Received:
    551
    Trophy Points:
    93
    Gender:
    Male
    Location:
    Switzerland
    Home Page:
    Simple, because the FPGA upgrade is not present on all drivers... so you by change used the right image with it on the driver, and so it fixed the FPGA. Then from that moment any image with any driver will work.

    TS
     
    raza05 and Johnny B. like this.
  19. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,504
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    @Ts,

    Yeah you are probably correct however to my experiences it can not jump from a old version to the newest, it must be build up, thinking something as in the sequence that they were released.
    When not it may ends up to the HW error.

    But luckily that the fpga chip accept backwards upgrades, thus you can always go back to the oldest one, otherwise it would be final.
    In any case, when I had replaced the fpga chip from a original board to a clone board I had a same situation, and eventually mannish to find the correct order to bring the clone board to the latest original image files.
    And this clone board is still working flawless with latest original image files.
     
    raza05 likes this.
  20. Piotrekop

    Piotrekop Member

    Messages:
    93
    Likes Received:
    16
    Trophy Points:
    8
    Solo2 has the same crash again. I ran it 10 times from deep standby and same HW Error
     
    Last edited: Nov 19, 2020
    Johnny B. likes this.