The postal Gods were kind to me and the "back-up" GC-0308 camera module arrived this morning I thought Customs clearance would delay things, but not this time.
I have spent much of today working on the UTi-690B in a determined effort to repair it. I installed the new GC-0308 camera core, booted the UTi-690 and........ no change The camera still halted at the 100% boot point. A check on the boot log showed no change from when the original GC-0308 was installed. I tested all of the replacement GC-0308 cameras on my ESP32-CAM module and all worked as expected. The original GC-0308 module is known to be faulty but I tested it again to make sure, and it is non responsive.
Whilst the UTi-690B complains about the lack of response from its GC-0308 camera core, I have now tried 3 different GC-0308 camera cores in it and none change the symptoms. As all are proven working, it would suggest that the problem is not the camera core. The original GC-0308 core did have a failed MLCC across is power rails that was drawing excess current, but the core was found to also be faulty after investigation. I have investigated possible causes of failure, such as a fault in its dedicated power supply IC and went so far as to stress test that IC to eliminate it from enquiries. It appears to be operating correctly with no transients or noise at its output to harm the GC-0308. The cause of the original GC-0308 failure is not known but it is possible that the MLCC failure has nothing to do with the camera failure and it is just coincidence.
With the GC-0308 camera module hardware eliminated from the investigation I have had to look at the data side of things. Could UNI-T have used a custom GC-0308 camera core in their product that the firmware needs to identify ? I very much doubt that as this is a building block component with no reason to make it unique in any way. All power and data lines associated with the core have been tested yet the GC-0308 is not working in the UTi-690B chassis.
I have done my best to identify any issues with the Linux firmware but found nothing unusual that could be causing this fault. I came to the conclusion that I am likely dealing with either some exotic firmware corruption or a failure in the SoC hardware. File substitution in the Firmware from a known good copy did not remove the fault so that leaves the SoC as a prime suspect and there is nothing I can do to repair that.
After spending a fair few hours on this camera I think it is time to declare this patient deceased. I shall advise the owner accordingly
Sady you cannot win them all and these budget cameras are virtually "disposable" technology now.
I learnt a lot about the UTi260B/Uti690B during this investigation and I may create a separate repair thread dedicated to the various stages of the investigation and findings. If you own one of these and it stops working, do check the GC-0308 camera module current draw, in case the MLCC has failed, but be warned that there may be a deeper failure that is uneconomic to repair by a tech.
Fraser
I have a UTi690B that I (stupidly?) attempted to update the firmware, just to have the latest. Yeah, I'm one of those that defy the common sense to only update firmware when you have an issue. My argument has always been that fw updates are made to fix bugs and improve features/performance, so even if I haven't run into those yet, I want to stay ahead of it. In nearly 40 years of updating fw (and also writing fw) on various devices, I've had very few bricked outcomes that I couldn't recover from fairly easily (like, maybe 2 or 3 at most).
Well, I got the latest firmware from a YouTuber along with detailed instructions on applying the firmware that he received from Banggood. I followed the directions, update went ok per the device UI, which then prompted me to restart. Now I'm stuck at 100% on the Loading screen (which replaced the UNI-T logo splash screen).
I'm having a support email conversation back and forth with Banggood, asking for (but not expecting) a recovery procedure that doesn't require getting fully booted. They first sent me the exact same fw package and instructions I got from the YTer (which at least validated his source, as first thing I did was do a binary compare of the two packages). After that they asked for a video demonstrating the problem. Now they've given me something else to try this morning that I'll attempt when I get home, but I'm not optimistic. Side note: I'm pleasantly surprised at how Banggood is trying to help here. I've purchased a lot from them over the years, but never attempted to get any kind of technical support out of them. I just don't know how much they can help with this, despite their efforts. They're very apologetic and seem keen to help, but as I've had this camera for almost 2 years now, I don't expect any sort of warranty repair/return from them even if it is a Banggood-exclusive model.
My next step is to open it up and try to hook up the UART to check logs, copy files, or whatever might be helpful. My issue seems to be entirely fw related and not a hardware issue, as it was working prior to the update attempt.
Anything more specific or targeted other than just flailing around in the OS assuming I get the UART connected and talking?
I asked banggood if there was a firmware to solve a blocking problem (which I don't encounter...) on my UTi-690b camera, they gave me the files that I put as an attachment, maybe you can try these on the blocked camera?
Note, I will not be testing these files on my working camera !
https://www.cjoint.com/c/MGtr3PmtYaj
After see there is nothing that I can do I open the device and use uart communication to copy my old UTi260B_Thermal 1.2.28 to root and voila device come back to life again.
What firmware device had before upgrade attempt?
But at least don’t worry device is ok and nothing burnt down …
Thanks, that's a relief then. Unfortunately I looked at but didn't write down the exact version or backup my firmware first (I wasn't aware of the fw backup process until I came here looking for solutions AFTER I bricked it). I want to say mine might have been something like 1.2.32 but I can't swear to it. I did download someone's stock fw backup that was posted in the backup thread though, so if I can get the UART to work then I'll try that.
The upgrade process did, thankfully, save my calibration data to a file on the SD Card, which I have since backed up. I assume if I apply someone else's firmware image, I'll have to restore this calibration file. I'll cross that bridge when I get to it.
Quote from: Veteran68Thanks, that's a relief then. Unfortunately I looked at but didn't write down the exact version or backup my firmware first (I wasn't aware of the fw backup process until I came here looking for solutions AFTER I bricked it). I want to say mine might have been something like 1.2.32 but I can't swear to it. I did download someone's stock fw backup that was posted in the backup thread though, so if I can get the UART to work then I'll try that.
The upgrade process did, thankfully, save my calibration data to a file on the SD Card, which I have since backed up. I assume if I apply someone else's firmware image, I'll have to restore this calibration file. I'll cross that bridge when I get to it.
My firmware is 1.2.28 and I can’t find any newer of series “1.” Anything from series “2.” It will not work, at least two of them that I try 2.0.20 and 2.0.22 that’s why I create that simple script in the backup thread you mention, to collect some firmwares here so we make a database since we cannot find nothing on the net.
Any way if you want my firmware I will pass it to you.
I changed only UTi260B_Thermal and device is normal again no any calibration data since I get the same as old, every time you run upgrade menu that .ini file is written to your as card.
SMD marking 01AH most likely means IRLML6402TRPbF MOSFET P-Ch -3.7A 65mOhm 8nC Log Lvl.
Quote from: Veteran68Thanks, that's a relief then. Unfortunately I looked at but didn't write down the exact version or backup my firmware first (I wasn't aware of the fw backup process until I came here looking for solutions AFTER I bricked it). I want to say mine might have been something like 1.2.32 but I can't swear to it. I did download someone's stock fw backup that was posted in the backup thread though, so if I can get the UART to work then I'll try that.
The upgrade process did, thankfully, save my calibration data to a file on the SD Card, which I have since backed up. I assume if I apply someone else's firmware image, I'll have to restore this calibration file. I'll cross that bridge when I get to it.
My firmware is 1.2.28 and I can’t find any newer of series “1.” Anything from series “2.” It will not work, at least two of them that I try 2.0.20 and 2.0.22 that’s why I create that simple script in the backup thread you mention, to collect some firmwares here so we make a database since we cannot find nothing on the net.
Any way if you want my firmware I will pass it to you.
I changed only UTi260B_Thermal and device is normal again no any calibration data since I get the same as old, every time you run upgrade menu that .ini file is written to your as card.Are we sure the 690B and 260B have the same firmware version numbers? Why would Banggood be providing people this version for 690B devices without asking what version you have to start with? There would typically be a warning in the instructions they provide to check current firmware version. I will reply back to them that I'm hearing that v1 firmware cannot be upgraded with v2 firmware and see what they say.
Let me go through the backup thread and check the versions that I've downloaded, then try to get the UART connection going.
My camera is not from Banggood but from local supplier that is uni-t official reseller.
I try one firmware comes from Banggood for a user with 690b with version number 2.0.2.22 and got boot problem (100%) stuck.
Try second one after use uart to recover my device, from a user here that is comes from 260b that he bought from Banggood also with firmware 2.0.20 with the same result.
Thanks
My camera is not from Banggood but from local supplier that is uni-t official reseller.
I try one firmware comes from Banggood for a user with 690b with version number 2.0.2.22 and got boot problem (100%) stuck.
Try second one after use uart to recover my device, from a user here that is comes from 260b that he bought from Banggood also with firmware 2.0.20 with the same result.
Thanks
You have the UTi260B I take it? My understanding is the UTi690B, while identical, is an exclusive Banggood model and shouldn't be sold anywhere else (unless being re-sold). The firmware files for both are named the same (i.e. UTi260B_Thermal) but the UTi690B firmware actually contains its own model number rather than UTi260B for display on the Device Info screen. So while the firmware between the two may be functionally the same and work with each other, they do each have their own unique firmware image. So I'd prefer to restore a 690B firmware to my 690B, rather than a 260B's firmware.
Banggood got back to me after I let them know that I'm hearing that the V2.x firmware they're sending out may be bricking other users like this with devices shipped with V1.x firmware. They said they're reaching out to the manufacturer on this and will let me know. Again, kudos to Banggood for providing a level of technical support I did not expect, but I guess they have to if they're going to sell exclusive models not openly supported by Uni-T directly.
In the meantime, last night I got the device disassembled (could they make that any harder to figure out? If I hadn't watched a YT video of a teardown I don't know that I'd have ever figured out where the screws were hiding). Tonight I plan to solder in a header and use a USB to TTL converter to try and read it. Hopefully I don't break it any further. Which would suck if Banggood/Uni-T actually came back with a simple recovery process, but I'm not at all confident they will.
If it can be helpful, I have given my UTi-690B firmware backup here: https://www.eevblog.com/forum/thermal-imaging/uti260b-uti690b-firmware-backup-script/msg4967098/#msg4967098
SMD marking 01AH most likely means IRLML6402TRPbF MOSFET P-Ch -3.7A 65mOhm 8nC Log Lvl.
I have searched the internet to find (and buy) this mosfet, but i can find p-type and also n-type mosfets with the same name. I am confused...
Can you please share the link to the exact item you bought?
I have contacted Uni-T, but they did not offer any information, or schematics, or diagram at all.
Thank you very much!
The postal Gods were kind to me and the "back-up" GC-0308 camera module arrived this morning I thought Customs clearance would delay things, but not this time.
I have spent much of today working on the UTi-690B in a determined effort to repair it. I installed the new GC-0308 camera core, booted the UTi-690 and........ no change The camera still halted at the 100% boot point. A check on the boot log showed no change from when the original GC-0308 was installed. I tested all of the replacement GC-0308 cameras on my ESP32-CAM module and all worked as expected. The original GC-0308 module is known to be faulty but I tested it again to make sure, and it is non responsive.
Whilst the UTi-690B complains about the lack of response from its GC-0308 camera core, I have now tried 3 different GC-0308 camera cores in it and none change the symptoms. As all are proven working, it would suggest that the problem is not the camera core. The original GC-0308 core did have a failed MLCC across is power rails that was drawing excess current, but the core was found to also be faulty after investigation. I have investigated possible causes of failure, such as a fault in its dedicated power supply IC and went so far as to stress test that IC to eliminate it from enquiries. It appears to be operating correctly with no transients or noise at its output to harm the GC-0308. The cause of the original GC-0308 failure is not known but it is possible that the MLCC failure has nothing to do with the camera failure and it is just coincidence.
With the GC-0308 camera module hardware eliminated from the investigation I have had to look at the data side of things. Could UNI-T have used a custom GC-0308 camera core in their product that the firmware needs to identify ? I very much doubt that as this is a building block component with no reason to make it unique in any way. All power and data lines associated with the core have been tested yet the GC-0308 is not working in the UTi-690B chassis.
I have done my best to identify any issues with the Linux firmware but found nothing unusual that could be causing this fault. I came to the conclusion that I am likely dealing with either some exotic firmware corruption or a failure in the SoC hardware. File substitution in the Firmware from a known good copy did not remove the fault so that leaves the SoC as a prime suspect and there is nothing I can do to repair that.
After spending a fair few hours on this camera I think it is time to declare this patient deceased. I shall advise the owner accordingly
Sady you cannot win them all and these budget cameras are virtually "disposable" technology now.
I learnt a lot about the UTi260B/Uti690B during this investigation and I may create a separate repair thread dedicated to the various stages of the investigation and findings. If you own one of these and it stops working, do check the GC-0308 camera module current draw, in case the MLCC has failed, but be warned that there may be a deeper failure that is uneconomic to repair by a tech.
Fraser