ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Just wondering whether any other service tool users have encountered the following issue and perhaps know of a solution?
I've added a new STB at home so decided to update the PUC table on my BV7-40mk3, but I'm consistently seeing the error below whilst trying to flash the new table.
21:38:08 - Reading Product Information...21:38:11 - Detecting if the TV is in STANDBY...21:38:13 - TV is in STANDBY. Continuing with software update...21:38:13 - Connecting...21:38:33 - Timeout occurred!21:38:33 - Software Update failed: device not entered flash state!
There's intermittent RX activity between the 'Connecting...' and the 'Timeout' stages, and I can hear the TVs fans start etc, so I'm not sure if this is a bug with the latest version of the service tool timing out too quickly or whether it is an issue with this particular BV.
I last updated the PUC table on this set around 18 months ago without issue and also updated it to Software build 0967 (sw 11.37a) at the same time, although I can't remember if I performed the PUC update before or after the software update and both would obviously have been carried out with whichever version of the ST was current at that time. I could try reverting the BV to a previous build but since 11.37a has been around for some time I think it is unlikely the problem lies there.
I can read product IDs & service counters etc so I know the port and cable set are okay.
Kind Regards,
Martin.
Hi Martin,
That is strange. As far as I can remember I never had this issue. I'm pretty sure that you already power cycled the TV?Maybe try the method for the older b-chassis? Unplug the power, start the PUC update and then replug?
BR,BeoMotion.
BeoMotion:That is strange. As far as I can remember I never had this issue.
No, me neither, although I don't have cause to use the service tool very often now.
BeoMotion:I'm pretty sure that you already power cycled the TV?
Yes, numerous times, and long enough for any charge to have dissipated to ensure a proper reset. I've also turned off pin code protection and performed a factory reset.
BeoMotion:Maybe try the method for the older b-chassis? Unplug the power, start the PUC update and then replug?
I tried this too, but the first or second stage of the process then complains about no connection to the TV, and if I power up the TV at this stage and choose to continue I ultimately end up with the same timeout error.
I've also tried starting the process with the TV on, and the ST then goes through the process of switching the TV into standby, waiting whilst this occurs, successfully detecting when the TV is in standby and continues from there, but again, the process still fails with the same timeout error.
I'm just installing windows on a spare laptop so that I can hopefully rule out any issues with the current laptop and if that makes no difference I'll try reflashing the current firmware build to the TV and then maybe even reverting to an older build. I do wonder whether the timeout duration in the software tool has been reduced at some stage as it does seem like there is stuff happening during that 'connecting' stage before the timeout.
Fingers crossed
Hi Sturrock,
Thanks for the suggestion. The Bv7-40mk3 is BS3 based / A chassis though so PUC update is via ML plug. Lead is definately fine though as I can read values from the BV and I've just reflashed the current build to rule out any firmware corruption (this made no difference unfortunately).
Kind regards
riverstyx:Hi Sturrock, Thanks for the suggestion. The Bv7-40mk3 is BS3 based / A chassis though so PUC update is via ML plug. Lead is definately fine though as I can read values from the BV and I've just reflashed the current build to rule out any firmware corruption (this made no difference unfortunately).Kind regardsMartin.
Sorry, the point I was trying to make before is that the mini jack cable is not used when updating the puc on BS3 based BVs. It's all done through the masterlink port so it's the same cable I've used without issue to flash the software on the same TV. I'm currently using it to flash the firmware back to current version after reverting this to an older build to see if it made any difference to the PUC update issue (it didnt).
It may be that my BV has developed a rather unusual fault, but given I have been able to successfully flash every module in the TV, I'm increasingly suspecting a bug or overly ambitious reduction in the timeout duration in the current version of ST. I just wish I had another BS3 based Beovision to hand that I could test with to confirm this theory.
Kind regards,
riverstyx:Sorry, the point I was trying to make before is that the mini jack cable is not used when updating the puc on BS3 based BVs. It's all done through the masterlink port so it's the same cable I've used without issue to flash the software on the same TV. I'm currently using it to flash the firmware back to current version after reverting this to an older build to see if it made any difference to the PUC update issue (it didnt). It may be that my BV has developed a rather unusual fault, but given I have been able to successfully flash every module in the TV, I'm increasingly suspecting a bug or overly ambitious reduction in the timeout duration in the current version of ST. I just wish I had another BS3 based Beovision to hand that I could test with to confirm this theory. Kind regards, Martin.
StUrrock:Any Hoy yet?
Hi StUrrock,
Nope, I sucesfully flashed the TV back to a build old enough that pretty much every module had a different software version, tried another PUC update (same issue), so flashed the TV back to current build (and still have the same issue with PUC flash) but haven't spent any time on this since.
Ideally I want try the process on with another laptop / USB adapter / cable set on my BV7 and/or try again with a different BV7 to confirm where the problem lies before raising this (possibly incorrectly) as an issue with the ST software.
Cheers,
I've had the situation once that a fuse was blown inside the BS3. Same behaviour. I was able to read a programm, but only some parts. Maybe there is a special PUC PCB with it's own fuse?
Beobuddy: I've had the situation once that a fuse was blown inside the BS3. Same behaviour. I was able to read a programm, but only some parts. Maybe there is a special PUC PCB with it's own fuse?
Thanks Beobuddy.
Are you talking about a replaceable glass fuse or a polyfuse on one of the PCBs?
It's certainly a strange fault - I believe the PUC table is stored in M2 module (which controls the PUC outputs) and the PW module (presumably for the on screen display aspects - for example when MENU is pressed and a list of PUC functions is shown). I can flash new firmware into both of these modules so they both appear able to communicate but it may be that there is a separate EEPROM within the chassis for the PUC table itself that is different from where the firmware for the module is stored - but I'm just speculating here and don't know for certain.
I'm probably going to avoid spending any more time on this right now until I've had a chance to try the current version of the service tool with another similar Beovision (or someone else is able to confirm it's working for them), as otherwise I may end up looking for faults that don't exist.