Hi, I have a starview 4 with the corrupt boot-loader file problem (ie. when box is switched on it appears it has no power but there is red light coming from the s/pdif port). I bought a jtag cable from a reputable box-seller and it appears to be ok (all wires and connections seem good). I have connected the jtag's 4-pin push-on connector to the board and the null modem cable to the PC and opened the loader program. I then select the bin file, click download and turn the box on but nothing seems to happen. Can anyone tell me what I'm doing wrong? I have com1 port baud rate set to 115200. Loader program I'm using is 'GTROM_V40 MFC Application' and bin file is 'USB V1.02_FTA' Any help would be greatly appreciated.
im having exactly the same problem on the the box usb receiver, anyone can help us both out please? thanks
Short answer, there is no fix available for the bootloader prob, first off there is no jtag for it, and second there is no tsop for it, this is a supplier only fix, which means the box must be replaced.
thanks for the reply e45. There are a couple of very reputable box sellers selling jtag cables for the sv4. What is the intended use for these cables if they cannot fix the bootloader issue?
Hi All woke up this morning and all channels gone on Starview usb, screen showing no signal. just wondering if anyone can help I am not very up to date on these boxes
tried the signal cable directly into the tv and its ok.don't know what else to do. Any more suggestions please ?
your supplier could have disconnected it from the mains.if your not paying for your viewing within the house.it has happened to a couple of friends of mine.whear are you based.
I live in dublin, cable paid up to date ,i have the box working on tv upstairs, but can't get it working in the main room. Sorry for the interruption Captclint
There is no fix for this only for the supplier to replace it see my previous posts above for details http://forums.afterdawn.com/t.cfm/f-59/help_needed_jtagging_starview_4-800578/#4844486
That 'fix' has nothing to do with jtag, it's just bad terminology used to describe a fix for boxes that have got screwed while re-programming. In this case, the boxes still have the bootloader code intact which allows the processor to run and therefore enables serial comms between the PC & the SV4. The 'fix' that you were sold was to recover from that situation, also referred to as 8882 due to the message displayed on the front panel LEDs. The bootloader problem is a whole different ball game. The bootloader area of the flash memory on-board has either been erased or has become corrupt, so the processor will not run and therefore no comms etc. The SV4 does have proper jtag points on-board so a fix could be created, however nobody has yet released one. If the SV4 didn't have theses jtag points then they couldn't configure them when manufactured (unless they pre-programmed the flash before soldering it to the board). The SV4 uses a completely different processor to the earlier models and therefore needs a very different jtag solution.
8882 will show on led for the jtag fix.normally because of a bad flash and not following tuts to the letter,inserting or removing usb while powered on. a dead box is blank=dead
And prob the reason your box is dead is because you loaded a firmware not suitable for a clone box also your box should be under warranty if you only got it and its a genuine box
first turn ur cable connection of at the wall,or youl get a shock lol when its off tighten the screw on ur connection as tight as you can get it, then put in back in,turn it on at the wall again and see if that helps,worked for me like.
@thebish - Thanks for the excellent reply, that has really clarified it for me. correct me if I'm wrong, but if the box has the bootloader problem (not 8882) I presume that there is no way of telling what firmware was on it? The reason why I ask is that I intend to contact the box supplier for a replacement as the box is still under warranty. Is it possible for him to say that I had an unofficial firmware on the box that voids the warranty? @E45 - its defo not a clone box. It was running fine with 1.10 but died just days before 1.12 was released. Guess I'm one of the unlucky ones with a fried genuine box. As you said, it is still under warranty so I'll contact the supplier. Thanks for your reply.
