Fluke TI200 not working

[Klommy]

Hi

I bought a TI200 a few years ago, only for private purposes. I have been using it since once every month or so. It basically still looks as new.
It has been sitting in the drawer now for at least 8 month without using it. Yesterday I wanted to turn it on but it wouldnt boot up completely. It always boots until a screen where it says:

RE Serial: RE not attached
RE FPGA: RE not attached
RE NIOS: RE not attached
...


The camera is eveentually recognized by Fluke Connect. But it shows up without firmware version.
Is it possible that due the long time being turned off an internal battery has been depleated and some important data has been deleted? Is there any emergengy firmware recovery or something like that?

[Fraser]

You need to open the camera and connect to the engineering serial port. This will produce a boot log that should suggest the point at which the boot sequence stops or has issues. Use a USB to 3.3V UART adapter and PC Serial terminal program to access the engineering port. If the camera still remembers the correct date and time after the main battery has been removed, the internal memory battery is still working.

Fraser

[Klommy]

I checked the battery, it has 3,2V

can you help me make out the serial port? is it the top of the picture labeled "510"?

[Fraser]

I have not worked on that particular model so cannot help much on the location of the engineering port . I normally track the ports down using an oscilloscope and looking for the serial data coming out of the port whilst the camera is booting. Then I use the USB to UART bridge cable to monitor the data and try different baud rates.

All that said……. Yes, the unpopulated connector marked “510” looks promising.
I have to wonder ….”510” = SIO = Serial Input Output ?

Fraser

[Fraser]

Can you upload a picture of the other side of the PCB in case there is a connector I recognise as the engineering port.

Fraser

[Fraser]

Having thought about your fault symptoms a little, I would suggest that you check the various power supply voltages on the PCB. If you are lucky they will be marked with their voltages at test points. If not, you will need to check the output of each DC-DC converter (there will be several of these) and determine whether the output voltage is present and correct by using the Switching IC’s datasheet. The supply to the FPGA is an obvious place to start as that is reported as not present by the system. You may find a mix of DC-DC buck converters and LDO’s on the PCB and some may only be active when switched on by the processor. This is why you need to check the IC data sheets for any enable pin.

Loss of relatively random subsystems on the camera can be due to loss of a sub system power supply rail. Failure of the cameras firmware is not my first thought or that common in my experience. More likely a failed MLC capacitor or DC-DC converter.

Fraser

[Fraser]

It may be nothing but I do not like the look of the MLC capacitor that I have highlighted in the attached picture. The upper of the two MLCC’s (C54) has a suspicious mark adjacent to the solder cap and this can indicate a failure in the capacitors layers and so failure of the capacitor, sometimes short circuit, or low resistance. It could just be an innocent mark on the surface of the capacitor though.

Fraser

[Klommy]

Ok thx. I will check at night.
Meanwhile a pic of the backside of the PCB

[Klommy]

hi.

I was quite busy and couldnt really work on the fluke. the only thing I found out so far is that the PCB battery might be damaged after all. One day without the big Fluke battery, the battery on the PCB drops from 3,3V to below 2,7V

[Fraser]

Those RTC/memory retention cells are often rechargeable types so it could just be that your cell needs a decent period of charging. Do not get too focussed on the RTC battery for the moment.

Fraser

[Klommy]

hey

didnt have much (any) time to dedicate me on the Fluke...
today I tried my luck again using DS-Logic and with like 30 minutes I found a UART TX Pad. It is TP17 on the bottom side of the OCB, just below the Cyclone IV. Baud rate is 115200
booting up only the PCB itself results in this:

Code: [Select]

U-Boot SPL 2012.04.01 (Apr 17 2014 - 08:37:13)
OMAP SD/MMC: 0


U-Boot 2012.04.01 (Jul 27 2021 - 16:19:23)

I2C:   ready
Reserving 543k for U-Boot at: 83f68000
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

++++++++++timed out waiting for frame done
          going on with dss initialization anyway
In:    serial
Out:   serial
Err:   serial
Die ID #4df800229e380000015a8b920300902a
Power Button Pressed: 0
Line Power Present: 0
▒▒▒▒▒▒▒▒▒60
U-Boot SPL 2012.04.01 (Apr 17 2014 - 08:37:13)
OMAP SD/MMC: 0


U-Boot 2012.04.01 (Jul 27 2021 - 16:19:23)

I2C:   ready
Reserving 543k for U-Boot at: 83f68000
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

++++++++++timed out waiting for frame done
          going on with dss initialization anyway
In:    serial
Out:   serial
Err:   serial
Die ID #4df800229e380000015a8b920300902a
Power Button Pressed: 1
Line Power Present: 0
DEBUG-DEBUG-DEBUG INFO: DSS L3 agent status = 0x0000000000002030
Net:   (Re)start USB...
USB:   Register 1313 NbrPorts 3
USB EHCI 1.00
scanning bus for devices... The request port(2) is not configured
The request port(2) is not configured
2 USB Device(s) found
       scanning bus for ethernet devices... 0 Ethernet Device(s) found
Board Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc0(part 0) is current device
MMC: block number 0x1 exceeds max(0x0)

** Unable to use mmc 0:1 for fatload **
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.4.79+
   Created:      2021-07-27  21:21:13 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2724264 Bytes = 2.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Initializing cgroup subsys cpuset
Linux version 3.4.79+ (fluke@GeminiPlatformBuildMachine) (gcc version 4.7.1 20120402 (prerelease) (crosstool-NG linaro-1.13.1-2012.04-20120426 - Linaro GCC 2012.04) ) #3 PREEMPT Tue Jul 27 16:21:05 CDT 2021
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3(Fluke)
bootconsole [earlycon0] enabled
/dev/emmc0p3: recovering journal
/dev/emmc0p3: Superblock last mount time is in the future.
        (by less than a day, probably due to the hardware clock being incorrectly set)  FIXED.

          34 inodes used (0.01%, out of 408000)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 26
       49424 blocks used (3.03%, out of 1628736)
           0 bad blocks
           1 large file

          16 regular files
           9 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
          25 files

Welcome to Buildroot 2015.02-git!

[  OK  ] Created slice Root Slice.
[  OK  ] Listening on udev Kernel Socket.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on Journal Socket.
[  OK  ] Reached target Swap.
[  OK  ] Listening on Journal Socket (/dev/log).
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
         Expecting device dev-ttyO2.device...
[  OK  ] Created slice System Slice.
         Starting Create Static Device Nodes in /dev...
[  OK  ] Created slice system-serial\x2dgetty.slice.
         Starting Load/Save Random Seed...
         Mounting POSIX Message Queue File System...
         Starting Journal Service...
         Mounting Debug File System...
[  OK  ] Reached target Local File Systems.
         Starting TI DVSDK Linux Utils Drivers...
[  OK  ] Reached target Slices.
[  OK  ] Reached target Paths.
[  OK  ] Listening on udev Control Socket.
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Listening on FLUKE On-Demand Service Socket.
[  OK  ] Started TI DVSDK Linux Utils Drivers.
[  OK  ] Listening on FLUKE Root Service Socket.
[  OK  ] Started Journal Service.
         Starting TI DVSDK DSPLink...
         Starting Keypad Input...
         Starting FLUKE FPGA Initialization Service...
[  OK  ] Reached target Sockets.
         Starting udev Kernel Device Manager...
[  OK  ] Started TI DVSDK DSPLink.
[  OK  ] Started Keypad Input.
[  OK  ] Started udev Kernel Device Manager.
         Starting Apply Kernel Variables...
         Mounting FUSE Control File System...
         Starting TI DSP Codecs Hosting Service...
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Apply Kernel Variables.
[  OK  ] Started TI DSP Codecs Hosting Service.
fluke-fpga[175]: #!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#
fluke-fpga[175]: GPMCMemImpl::initGPMCMem(): Fluke GPMC Initializing Memory!
fluke-fpga[175]: #!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#
fluke-fpga[175]: ERROR: RE is not responding => Assumed status: 'not attached'.
[  OK  ] Started FLUKE FPGA Initialization Service.
         Starting FLUKE Root Service...
[  OK  ] Started FLUKE Root Service.
         Starting udev Coldplug all Devices...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Found device /dev/ttyO2.
[  OK  ] Reached target Sound Card.
[  OK  ] Reached target System Initialization.
         Starting Restore Sound Card State...
         Starting FLUKE TI Frame Server Service...
[  OK  ] Reached target Basic System.
         Starting USB Ethernet Gadget Service...
         Starting System DBus Service...
[  OK  ] Started System DBus Service.
         Starting The Initialize WiFi Service...
[  OK  ] Started The Initialize WiFi Service.
         Starting FLUKE Session D-Bus Service...
         Starting Serial Getty on ttyO2...
[  OK  ] Started Serial Getty on ttyO2.
[  OK  ] Reached target Login Prompts.
         Starting FLUKE GPIO Export Service...
         Starting ALWAYS ON Dropbear SSH2 daemon...
[  OK  ] Started ALWAYS ON Dropbear SSH2 daemon.
[  OK  ] Reached target Timers.
[  OK  ] Started FLUKE GPIO Export Service.
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started FLUKE Session D-Bus Service.
         Starting The Gemini Qt Serial DBus Server...
[  OK  ] Started The Gemini Qt Serial DBus Server.
         Starting Avahi (Bonjour) Remote Device Discovery...
         Starting The FWCS Radio Startup Service...
[  OK  ] Started The FWCS Radio Startup Service.
         Starting The Gemini FWCS dbus server...
[  OK  ] Started The Gemini FWCS dbus server.
         Starting The Gemini BLECNX dbus server...
[  OK  ] Started The Gemini BLECNX dbus server.
[  OK  ] Started USB Ethernet Gadget Service.
[  OK  ] Started Avahi (Bonjour) Remote Device Discovery.

fluke-cam login:


with the camera head attached i get:

Code: [Select]

U-Boot SPL 2012.04.01 (Apr 17 2014 - 08:37:13)
OMAP SD/MMC: 0


U-Boot 2012.04.01 (Jul 27 2021 - 16:19:23)

I2C:   ready
Reserving 543k for U-Boot at: 83f68000
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

++++++++++timed out waiting for frame done
          going on with dss initialization anyway
In:    serial
Out:   serial
Err:   serial
Die ID #4df800229e380000015a8b920300902a
Power Button Pressed: 0
Line Power Present: 0
60
U-Boot SPL 2012.04.01 (Apr 17 2014 - 08:37:13)
OMAP SD/MMC: 0


U-Boot 2012.04.01 (Jul 27 2021 - 16:19:23)

I2C:   ready
Reserving 543k for U-Boot at: 83f68000
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment

++++++++++timed out waiting for frame done
          going on with dss initialization anyway
In:    serial
Out:   serial
Err:   serial
Die ID #4df800229e380000015a8b920300902a
Power Button Pressed: 1
Line Power Present: 0
DEBUG-DEBUG-DEBUG INFO: DSS L3 agent status = 0x0000000000002000
Net:   (Re)start USB...
USB:   Register 1313 NbrPorts 3
USB EHCI 1.00
scanning bus for devices... The request port(2) is not configured
The request port(2) is not configured
2 USB Device(s) found
       scanning bus for ethernet devices... 0 Ethernet Device(s) found
Board Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot:  0
Card did not respond to voltage select!
mmc0(part 0) is current device
MMC: block number 0x1 exceeds max(0x0)

** Unable to use mmc 0:1 for fatload **
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.4.79+
   Created:      2021-07-27  21:21:13 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2724264 Bytes = 2.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   XIP Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Booting Linux on physical CPU 0
Initializing cgroup subsys cpuset
Linux version 3.4.79+ (fluke@GeminiPlatformBuildMachine) (gcc version 4.7.1 20120402 (prerelease) (crosstool-NG linaro-1.13.1-2012.04-20120426 - Linaro GCC 2012.04) ) #3 PREEMPT Tue Jul 27 16:21:05 CDT 2021
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3(Fluke)
bootconsole [earlycon0] enabled
/dev/emmc0p3: recovering journal
/dev/emmc0p3: Superblock last mount time is in the future.
        (by less than a day, probably due to the hardware clock being incorrectly set)  FIXED.

          34 inodes used (0.01%, out of 408000)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 26
       49424 blocks used (3.03%, out of 1628736)
           0 bad blocks
           1 large file

          16 regular files
           9 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
          25 files

Welcome to Buildroot 2015.02-git!

[  OK  ] Reached target Paths.
[  OK  ] Created slice Root Slice.
[  OK  ] Created slice System Slice.
[  OK  ] Reached target Slices.
[  OK  ] Listening on /dev/initctl Compatibility Named Pipe.
[  OK  ] Listening on Journal Socket.
         Starting TI Wireless Module (wl1271) Calibration Service...
[  OK  ] Started TI Wireless Module (wl1271) Calibration Service.
[  OK  ] Listening on Journal Socket (/dev/log).
         Mounting POSIX Message Queue File System...
[  OK  ] Reached target Swap.
[  OK  ] Listening on udev Kernel Socket.
         Mounting Debug File System...
         Starting Journal Service...
[  OK  ] Reached target Local File Systems.
         Starting Load/Save Random Seed...
         Starting TI DVSDK Linux Utils Drivers...
[  OK  ] Created slice system-serial\x2dgetty.slice.
[  OK  ] Listening on Delayed Shutdown Socket.
[  OK  ] Listening on udev Control Socket.
         Expecting device dev-ttyO2.device...
         Starting Create Static Device Nodes in /dev...
[  OK  ] Mounted Debug File System.
[  OK  ] Mounted POSIX Message Queue File System.
[  OK  ] Started Journal Service.
[  OK  ] Started Load/Save Random Seed.
[  OK  ] Started TI DVSDK Linux Utils Drivers.
[  OK  ] Started Create Static Device Nodes in /dev.
[  OK  ] Listening on FLUKE Root Service Socket.
[  OK  ] Listening on FLUKE On-Demand Service Socket.
[  OK  ] Reached target Sockets.
         Starting udev Kernel Device Manager...
         Starting TI DVSDK DSPLink...
         Starting FLUKE FPGA Initialization Service...
         Starting Keypad Input...
[  OK  ] Started TI DVSDK DSPLink.
[  OK  ] Started udev Kernel Device Manager.
[  OK  ] Started Keypad Input.
         Starting TI DSP Codecs Hosting Service...
         Mounting FUSE Control File System...
         Starting Apply Kernel Variables...
[  OK  ] Started TI DSP Codecs Hosting Service.
[  OK  ] Mounted FUSE Control File System.
[  OK  ] Started Apply Kernel Variables.
fluke-fpga[183]: #!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#
fluke-fpga[183]: GPMCMemImpl::initGPMCMem(): Fluke GPMC Initializing Memory!
fluke-fpga[183]: #!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#!#
fluke-fpga[183]: ERROR: RE is not responding => Assumed status: 'not attached'.
[  OK  ] Started FLUKE FPGA Initialization Service.
         Starting FLUKE Root Service...
[  OK  ] Started FLUKE Root Service.
         Starting udev Coldplug all Devices...
[  OK  ] Started udev Coldplug all Devices.
[  OK  ] Reached target System Initialization.
[  OK  ] Reached target Timers.
         Starting FLUKE TI Frame Server Service...
[  OK  ] Reached target Basic System.
         Starting FLUKE GPIO Export Service...
         Starting USB Ethernet Gadget Service...
         Starting The Initialize WiFi Service...
[  OK  ] Started The Initialize WiFi Service.
         Starting System DBus Service...
[  OK  ] Started System DBus Service.
         Starting FLUKE Session D-Bus Service...
         Starting ALWAYS ON Dropbear SSH2 daemon...
[  OK  ] Started ALWAYS ON Dropbear SSH2 daemon.
         Starting Restore Sound Card State...
[  OK  ] Started FLUKE GPIO Export Service.
[  OK  ] Started FLUKE Session D-Bus Service.
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started USB Ethernet Gadget Service.
[  OK  ] Found device /dev/ttyO2.
[  OK  ] Reached target Sound Card.
         Starting Serial Getty on ttyO2...
[  OK  ] Started Serial Getty on ttyO2.
[  OK  ] Reached target Login Prompts.
         Starting The Gemini BLECNX dbus server...
[  OK  ] Started The Gemini BLECNX dbus server.
         Starting Avahi (Bonjour) Remote Device Discovery...
         Starting The FWCS Radio Startup Service...
[  OK  ] Started The FWCS Radio Startup Service.
         Starting The Gemini Qt Serial DBus Server...
[  OK  ] Started The Gemini Qt Serial DBus Server.
         Starting The Gemini FWCS dbus server...
[  OK  ] Started The Gemini FWCS dbus server.
[  OK  ] Started Avahi (Bonjour) Remote Device Discovery.

fluke-cam login:

I realized that the log is different with the camera head attached. But I didnt do any further analisis, will keep you updated...

[tcq1000]

I have dealt with similar malfunctions before, which are usually caused by communication abnormalities

[tcq1000]

Common fault cases