use a K9F1G08U0C from Genuine Duo in a clone

Discussion in 'VuPlus Duo Hardware troubles and Repair support.' started by fingersd, Nov 19, 2016.

  1. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Hi JB, Your views please.

    I was wondering if it's possible to use a K9F1G08U0C from a fried genuine Duo to repair a Cloud Ibox 4 (Mini Duo Clone, Just using a diferent security chip) I have knocking about that requires a new Eprom, no doubt it will require jtagging but I have been unable to find a suitable BBS 3 XML file for the K9F1G08U0C (K9F1G08U0A and K9F2G08U0C are supported by Broadband Studio, but not this chip)

    It installed just fine and show's connected in BBS3, it's just finding an XML file I'm having problems with.

    The Cloud Ibox 4 uses a TC58NVGOS3ETA00 by default but the datasheet for it and the TC58NVGOS3ETA00 appear to be identical

    Any thought's on this, Thanks.
     
  2. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    You should be able to use the xml for the K9F1G08U0A for your K9F1G08U0C as the DevID is the same for both chips F1h and th layout is the same.
     
  3. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Thanks, didn't work for me under windows 7, I'll dig out an old XP machine and try with that.

    Also I use the 2 jumper Cypress board, and see from one of your images you were using yours with both jumpers attached, I've removed the one by the SDA, SCL header, should i replace it

    Thanks, Dave
     
    Last edited: Nov 19, 2016
  4. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    According to posts that i have seen with the clone (2 jumper) boards they have used both jumpers , I personally found it works better on win xp but have seen it working on win 7 x86.
     
  5. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    No change unfortunately using both jumpers and XP, still getting Maker Id from the flash: 0 does not match when using K9F1G08U0A
     
  6. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    Ok i took the K9F1G08U0A xml and basically changed the name to suit that flash tell me if you get the same issue .
     

    Attached Files:

    Johnny B. likes this.
  7. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,503
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Try this tricks..
    When you are in the flash mode, but has this Maker Id issue.
    Turn off the receiver, and turn it on, then try to recognize the nand chip again.
    Sometimes this also helps when you switch off the cypress board, and switch it on.

    However, if this also not helps and you are sure it has the K9F1G08U0C nand chip.
    Then it could be that there is some issue with the pins/solder of the nand chip thinking of the chip enable pin.
    If this is disabled, then the nand chip is not reachable.
    A good document about it, is this pdf Reverse Engineering Flash Memory for Fun And Benefit from recon.cx.

    Also be sure that your board has the K9F1G08U0C and not the Samsung K9F1G08R0C
    The K9F1G08R0C has another DevId, the 0xA1.

    But also, it is posable that the cpu doesn't support the Samsung chip, only what it has before, the TC58NVGOS3ETA00
     
  8. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    I give up! I've checked all soldering and it looks OK, but not perfect.
    I've tried cycling the power of both the mainboard and my Cypress board but no joy.
    Thanks Anyway.
    [​IMG][/URL][/IMG]
    [​IMG]
    [​IMG]
    [​IMG]
     
  9. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,503
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Pity to read...
    But I could help you with a used Toshiba chip if you like.
    I have here a X solo mini and cloud-ibox board who has one.
     
  10. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Great, I would love both assuming the bootloader is on. How much, I'm in the UK for shipping.
    Would you have a Solo 2 IC as well? (I have a laurison here in need of one)
     
  11. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,503
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    No I do not have the Solo 2 , as far as I think to know it has also the toshiba chip or else the samsung, but you should see it if you remove the sticker.
    I could sent you 3 TC58NVGOS3ETA00 chips, one from the x solo mini, other two from the cloud-ibox.
    all from boards with security chip issues.

    Just give a private message with your address which you want them receive it and I will sent them.
     
  12. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Thanks for your effort but no change, Still reporting Maker Id from the flash: 0 does not match
    I'm beginning to wonder if my Cypress board may be faulty.
    although I did have it connect on a different board and report bad block at sector 0 (unsurprisingly)
    So I've no idaea...
     
  13. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    Could maybe be that you have a dead chip or as Johnny says CE is disabled ...
    It could be the board as it is a clone , but hard to say unless you actually have had it working 100% on another chip.
    Test the continuity between your soldering and the cypress board and re-check SCL & SDA soldering specifically.
    Also out of curiosity what version of BBS 3 are you running ?
     
  14. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Hi again Koevoet, BBS is ver 3.1.60125.8
    When I 1st soldered in my SDA, SCL and Ground to this particular mobo I did get a connection immediately and the chip was selectable and identified as a Toshiba TC58NVG0S3ETA00 but with bad block @ ..... etc unsurprisingly as the box had suffered from anti-clone measures, so it's probably safe to assume my Jtag connections are fine. As i had a K9F1G08U0C knocking about from a Genuine Duo I figured why not give it a go as from the specs they do appear compatible (all be it without a XML file readily available) JB even expected the K9F1G08U0A file to work without modification.

    I think the only conclusion to make here is as you say CE is disabled by VU+ probably as an anticlone measure.
    I did enjoy the "fiddling" though and hate getting beaten!

    I'll wait for a genuine TC58NVG0S3ETA00 and retry with that (i'll keep Jtag connected to see if i can access that when fitted)

    Cheers, Dave.
     
  15. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    So you have lifted the NAND from a genuine duo and resoldered onto this box correct ? Did you by any chance test BBS out when this chip was on the duo ? also if you did move the chip is it resoldered /reflowed correctly ? And lastly any chance you may of dmaged the chip whilst removing/replacing ?
     
  16. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    I have just tested a genuine vu + duo with the exact same chip and it identifies correctly using the old K9F1G08U0A xml , so doubt CE is disabled ,, so leads me to believe either the chip itself is borked , or not soldered onto the new board correctly , or there is issues with your cypress board .

    I tested this on Win XP using BBS version 3.1.50215.13
     
    Johnny B. likes this.
  17. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    Interesting... No i didn't test the chip in the duo before removing it (would have made sense to have done so though)
    my soldering looks pretty fine although I do say so myself (did you see my pictures earlier) not that that they do it justice, Maybe a naff IC (could have been the original Duo fault) it was given to me with extensive man made track damage around the buck regulator area from a bodged cap and IC repair, or as you say, maybe a dodgy programmer (think I'll order another programmer to compare with anyway)

    I did assume as I was getting "Connected" handshake was successful and the error was with the XML, but obviously this is not true.
     
  18. Koevoet

    Koevoet New Member

    Messages:
    15
    Likes Received:
    5
    Trophy Points:
    3
    Gender:
    Male
    Location:
    England
    I would personally say it is a faulty NAND , but hard to say without trying the chip elsewhere .
     
  19. Johnny B.

    Johnny B. Technical Support Staff Member Moderator

    Messages:
    2,822
    Likes Received:
    1,503
    Trophy Points:
    113
    Gender:
    Male
    Location:
    Netherlands
    Home Page:
    Everything is possible,
    A: Cpu does not support another type nand chip than the one it already has.
    B: One of the I/O data lines are bad ( this can be measured by ohms, all the I/O pins should have the same Mohms range between the ground and the I/O pin).
    C: Issue with the pins 7/8/9/16 etc..
    D: Bad nand chip.
    E: Unexpected other causes as a cpu pin issue to the I/O data lines.

    In any case, if I have this issue then I measure with ohms first the pins, if they have logic measurements.
    If so, and I know for sure that my cypress board is function well, then I remove it again and check it in my programmer.
    If that is fine..
    I check all the I/O print lines if they have a logic ohms value.

    And if i'm in a hurry, I just remove the nand chip and replace it for another.
     
  20. fingersd

    fingersd Member

    Messages:
    64
    Likes Received:
    9
    Trophy Points:
    8
    Gender:
    Male
    LOL, I like your final solution, I'm in no hurry though and am happy to wait till next week when the postman will hopefully bring me a new chip to try ;-)

    I have ordered another 13A-56 EZ-USB FX2LP USB2.0 board for comparison though, if both appear to work I'll be taking one to Spain where I spend half my time anyway.
     
    Johnny B. likes this.