Question about FLIR One for Android

[newex]

Micron NAND Flash
This is NAND Flash and DDR in one chip.

[Uho]

In my case, after warming up Atmel, the thermal imager worked a week. Now it can only work a few minutes if you heat Atmel. It is glued with a compound and I can not remove it. The thermal imager does not respond to memory heating.

[newex]

Ok, try it. I have already passed this way.

[Uho]

Help is needed. I decoupled the AT91SAM26 and lost the resistor. Tell me please his resistance. It is connected to the pin F1 - TCLK4

[Fraser]

It is a 10K Ohm resistor

Just measured it on one of my units.

Fraser

[Uho]

Thank you very much!

[Fraser]

When applying heat in the area of that Atmel chip, do be conscious of the components on the other side of the PCB. Whilst an issue may appear to come from the large Atmel chip, heat is also warming the clock oscillator etc on the the other side. It is always worth checking these components before considering a reballing operation on the Atmel.

Clock oscillators do fail and sometimes respond to heat.

Fraser

[Fraser]

Uho,

No problem. I always have a FLIR One disassembled in case I need to check something on the PCB

Fraser

[Uho]

Clock oscillators do fail and sometimes respond to heat.

Fraser

I tried to heat Clock oscillators. There was no result.

[Fraser]

It would be great if someone with the available time would reverse engineer the FLIR One G2, at least to the point of a block diagram showing all major components. It may help others to identify helpful test points and likely causes of faults.

With a non responsive FLIR One G2, it is always the power supply circuit that should be checked first as I have little confidence in this area of the design. As for the battery.....

I owned two FLIR One G2 units from new. One was lightly used and the other sat in its sealed box, untouched. Both sat unused for several months. A fellow forum member wanted to buy my sealed unit and I was concerned whether the battery was OK. As soon as I connected the USB power supply, the camera began to charge normally. After testing, the cameras run time was a healthy 60 minutes. I tested my other FLIR One G2 that I have used. It also charged easily and ran for 60 minutes .

I carried out a test on three faulty units that await my attention (no boot) All of them took some coaxing to start their charge cycle. A coincidence or sign that those units have a duff battery or charge controller ? Those units were fully charged only a couple of months ago yet the charge circuit saw the battery as below normal charge initiation point. Hmmmm, something is not right there.

Fraser

[lambcutlet]

hello,
its my first post here so please go easy. I'd been reading this forum on and off for about a month now and thought i would have a punt at buying a faulty Flir one gen2 from Ebay.
To help others I thought i would share info i have found so far, see attachment.
In my case connector J7 the 4pin connector to the USB board had been wedged up breaking a solder joint. Once resoldered it now connected to my phone. However the punter on Ebay I bought the Flir from must also be trying to repair these as he has torn the ribbon cable to the visible camera. So the Flir will connect to the phone I can check the firmware but their is no display. Thinking i had purchased rubbish I then obtained a v1.4 breakout board from digikey in the hope the Lepton3 was as people have mentioned in the forum, bullet-proof. I hooked it up to a raspberry-pi using this, pylepton (branch lepton3) https://github.com/groupgets/pylepton/tree/lepton3 and thankfully it worked.
Questions:
Can anyone identify the visible camera? I need a replacement
Does anyone else use the raspberry-pi with a breakout board and Lepton3? and what software do you use? (off topic sorry)

'Charging the battery' to help Frasers previous query. The USB input feeds a BQ24295 which charges the battery and shares power to the system via multiple step-down convertors (markings C1xx, SM33G & SM28G). The BQ24295 can be and is controlled in part by the processor having found the username and password in these forums I poked around and found '/etc/battery.cfg' a file which specifies numerous controlling parameters, such as 'BATT_CHARGING_TIMEOUT_S=14400'.
here's the contents

Code: [Select]

$ cat /etc/battery.cfg
# max verbosity 3
DEBUG_LEVEL=0

# polling interval in msec
POLL_PERIOD_MS=100

# number of polling intervals before writing first status
STATUS_UPDATE_STARTUP_WAIT=100

# number of polling intervals between writing status
STATUS_UPDATE_TICKS=10

# number of polling intervals between logging statistics (if enabled)
LOG_UPDATE_TICKS=100

# number of consecutive polling intervals switch reads low to shut down
SHUTDOWN_TICKS=10

# time to try charging again after charger signals thermal fault
FAULT_RECOVERY_TICKS=600

# maximum time for trying to charge own battery:
# if battery is still not full after attempting to charge this long,
# assume there is a hardware problem and go into fault state
BATT_CHARGING_TIMEOUT_S=14400

# grace period for power-down: really turn off if switch stays 'off' this long
# special value of '0' disables switch checking (useful for bare boards)
POWEROFF_DEBOUNCE_MS=2000

# number of voltage readings to average when calculating battery level
NUM_VBATT_READINGS=5

# weight for filter used to smooth battery level estimate
CHARGE_FILTER_WEIGHT=0.9835

# voltage offset when USB5V is connected
# (subtracted from voltage reading)
USB5V_VOLTAGE_OFFSET=0.04

# minimum voltage (in mV) allowed from charger
MINIMUM_INPUT_VOLTAGE_MV=4520

# whether to allow iphone charging when own battery is full
ENABLE_PHONE_CHARGING=1

# timeout for staying phone charge mode if own battery is less than full
# (avoids leaving battery partially full after charger chip stole stole
# charge to boost current to phone)
PHONE_CHARGING_TOPOFF_TIMEOUT_S=1800

# whether to force statistics logging on startup
AUTO_ENABLE_LOGGING=0

# location of logfile (if logging is enabled, via autostart or socket command)
LOGFILE_PATH=/var/log/battery_statistics.log

## app management when 5V is plugged/unplugged

# command to run just usb app for charge-only mode
START_CHARGE_ONLY_COMMAND=/etc/init.d/userapps charge-only

# command to start streaming when switch turns "on"
START_STREAMING_COMMAND=/etc/init.d/userapps start

#command for system shutdown
SHUTDOWN_COMMAND=sync && echo o > /proc/sysrq-trigger

# how long after startup should we wait for activity before sleeping
DEEP_SLEEP_TIMEOUT_S=120

# how long after disconnect should we wait before sleeping
POWER_SAVE_TIMEOUT_S=120

# how many ticks between checking for deep sleep or power save states
POWER_SAVE_CHECK_TICKS=25So charging the battery is not a simple constant current constant voltage system it has smarts for added control and safety in the form of the BQ24295 in conjunction with the processor.

And to check 'battery voltage & status' issue this command 'cat /var/log/battery/status'

[Uho]

The lack of a video camera does not interfere with getting the battery charge status. Do you see the battery on the phone screen? Yes, without a camera there will not be a thermal image. I also did not find a camera with this kind of connector. I'm now looking for a memory chip.

[Fraser]

Lambcutlet,

Very sorry to hear that someone had been inside your F1G2 before you. That is always a worry as you do not know what further damage has been done. The classic 'heat it with a paint stripper' to reflow the chips comes to mind 

Thank you very much for the detail on the charge management. The FLIR i series use similar.

I am not a software tech but would like to take a look around inside my faulty F1G2 and DUO R cameras. Can you detail how you wentvabout accessing the file system in the F1G2. I know how to do it with i and E series cameras but not on the F1G2. Many Thanks.

Fraser

[misterno]

Hi all. Merry Christmas!

I have a flir one for android and after many attempts i end up with a damaged CPU. Is it possible though to check if the flir sensor is working even with other interface as well?
TIA

[lambcutlet]

Fraser, how much do you know about linux? below is some basic commands to help you navigate with examples
hardware setup. note: attach micro USB cable otherwise board powers down
solder 3 wires to Tx,Rx & Gnd (see my previous document for locations) using a TTL to USB convertor https://shop.clickandbuild.com/cnb/shop/ftdichip?productID=53&op=catalogue-product_info-null&prodCategoryID=296. then using putty http://www.putty.org to connect to the serial port of the TTL cable using settings 115200, 8n1.
so now when you power-up the Flir one you should see the boot sequence ending with a prompt
'Welcome to Rosebud (Operational)
(none) login:'

Code: [Select]

RomBOOT
Start AT91Bootstrap version svn-r5344 ...
Init HALF drive strength DDR... BOARD_ConfigureDdram()
DDRSDRC->DDRSDRC_LPR: 0x12101
Done!
Downloading image...
Trying to load uboot...
nandflash_hw_init()
reset_nandflash()
AT91F_NandReadID()
ManufacturerID: 0x2c DeviceID: 0xa1
chip id: 0x2ca1
Copy 0x50000 bytes from 0x40000 to 0x23f00000
nandflash_cfg_8bits_dbw_init()
switch(sNandInfo.uDataNbBytes) 2048:
read_nandflash: while (1)
read_nandflash: while (1)
read_nandflash: while (1)
read_nandflash(): return 0;
Done!
Returning jump to 0x0x23f00000


U-Boot 2010.06-svn5344 (Aug 03 2015 - 13:27:27)

DRAM:  64 MiB
NAND:  nand->ecc.bytes 28
nand->ecc.steps 1
nand->ecc.layout = pmecc_oobinfo_2048
host->mm 13
host->nn 8191
host->tt 4
host->sector_size 512
host->sector_number 4
host->ecc_bytes_per_sector 7
host->alpha_to 0x10C000
host->index_of 0x108000
128 MiB
*** Warning - bad CRC or NAND, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   macb0, macb1
eth_enable not set, skipping macb init.
eth_enable not set, skipping macb init.
Watchdog enabled.
Hit CTRL-C to stop autoboot:  0
Data (writethrough) Cache is ON
boot operational

Loading from nand0, offset 0xe00000
   Image Name:   Linux-2.6.39+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3358884 Bytes = 3.2 MiB
   Load Address: 20008000
   Entry Point:  20008000
Bit flip in data area, byte_pos: 772, bit_pos: 5, 0xbc -> 0x9c
Bit flip in data area, byte_pos: 192, bit_pos: 4, 0x72 -> 0x62
Bit flip in data area, byte_pos: 1503, bit_pos: 4, 0x72 -> 0x62
Bit flip in data area, byte_pos: 826, bit_pos: 0, 0x27 -> 0x26
Bit flip in data area, byte_pos: 937, bit_pos: 2, 0xbe -> 0xba
Bit flip in data area, byte_pos: 104, bit_pos: 3, 0xfc -> 0xf4
Bit flip in data area, byte_pos: 1636, bit_pos: 7, 0xc3 -> 0x43
Automatic boot of image at addr 0x22000000 ...
## Booting kernel from Legacy Image at 22000000 ...
   Image Name:   Linux-2.6.39+
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3358884 Bytes = 3.2 MiB
   Load Address: 20008000
   Entry Point:  20008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.025000] AT91: CM rev B and higher
[    0.037000] AT91: EK rev B and higher
Starting watchdog...done
mounting jffs2 READ-ONLY...done
start battery charge control
Starting battery_charge: OK
done
Formatting /tmp/versions: OK
[    1.666000] lepton_init
[    1.672000] lepton_probe: using 16-bit SPI width

Welcome to Rosebud (Operational)
(none) login:now enter the username and password to gain access

Code: [Select]

Welcome to Rosebud (Operational)
(none) login: root
Password:
login[313]: root login on ‘ttyS0‘
-sh: id: not found
sh: bad number
-sh: id: not found
-sh: /bin/hostname: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
-sh: alias: not found
$ you now have a root prompt.
type 'ls' to show what's in your directory
type 'pwd' to show where you are

Code: [Select]

$ ls
RBTest.sh     shared_files
$
$ pwd
/root
$ you are in directory '/root'
now 'cd' to change directory, example 'cd shared_files/'
then 'ls' to show contents

Code: [Select]

$ cd shared_files/
$ ls
CameraFiles.zip         lepton_info.txt         version_dv.txt
batteryvoltages.txt     manufacturing_data.txt  version_op.txt
connector_type          version.txt             version_up.txt
$to view the contents of regular files use 'cat' for example 'cat batteryvoltages.txt'

Code: [Select]

$ cat batteryvoltages.txt
764
762
765
762
765
$ use 'cd ..' to move up a directory level

Code: [Select]

$ pwd
/root/shared_files
$ cd ..
$ pwd
/root
$using the above commands you can now navigate by changing directories, view the contents of that directory and view file contents.
so now on to more interesting locations the root of the linux system 'cd /' and perform 'ls'

Code: [Select]

$ cd /
$ ls
bin          home         linuxrc      proc         sys          var
dev          init         mnt          root         tmp          version.txt
etc          lib          opt          sbin         usr
$ this is the root of the system
this may help as a general guide to explain folder contents http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
location of log files '/var/log/'
location of config files '/etc/'

other helpful commands:
type 'reboot' to reboot the Flir one processor
type 'poweroff'' to powerdown and disconnect

[lambcutlet]

misterno, I used a lepton breakout board https://www.digikey.co.uk/products/en/development-boards-kits-programmers/evaluation-boards-sensors/795?k=lepton and a raspberry pi to check the thermal sensor, like this https://learn.sparkfun.com/tutorials/flir-lepton-hookup-guide

[Fraser]

@Lambcutlet,

Many thanks for the excellent guide to accessing the file system. That is really helpful to me. I am no Linux guru but I will study the Linux command set and work on gaining a better knowledge of it. My previous experience has only been with Knoppix !

I believe my FLIR PM series cameras also run Linux so I shall have to access their engineering serial port and do some digging around in them as well.

Many thank again 

Fraser

[misterno]

misterno, I used a lepton breakout board https://www.digikey.co.uk/products/en/development-boards-kits-programmers/evaluation-boards-sensors/795?k=lepton and a raspberry pi to check the thermal sensor, like this https://learn.sparkfun.com/tutorials/flir-lepton-hookup-guide

Thank you for immediate reply. I mention that my PCB is in good condition. Is it any chance to order a new empty CPU and do the programming later?
If that happens i would be very pleased. 

[tomas123]

@lambcutletF
thanks for sharing the information, how to debug the F1G2   

[mahony]

Hi lambcutlet,
very nice Infos!  Do you have pictures of your wiring setup?
Did you just connect the TTL to USB to the original USB pins?

Regards

[Fraser]

Mahoney,

The wiring points are shown on the open office text document that was provided but it needs to be viewed by an Open Office capable program. I converted it to PDF using an on line converter.

Fraser

[lambcutlet]

misterno,
I have never programmed an Atmel CPU but I suspect replacing a broken CPU with a blank version will not solve your problem. There has to be some embedded code programmed into the device to make it function.
Maybe others with more programming experience of these devices could help.

[Uho]

I got two not working thermal imager. The first one has problems with calibration. The second thermal imager does not turn on. 1.The shutter does not work. This problem arises from the poor quality of conductive paste. This paste is connected to the conductive paths in Lepton. Replace the paste with a good conductive coating. I make it from copper dust and nail polish. The main thing that a wife or daughter did not notice the loss of lacquer. 2. The thermal imager does not turn on. After connecting the dipstick of the oscillograph to quartz, it began to work. It works a few seconds or minutes well. Then the image freezes. The LED flashes. Shutter is working. The calibration button does not work. I checked the generation on quartz. Again there is no signal. There are three possible causes of failure. Quartz is defective. Defective capacitors next to it. Defective controller. I will look for quartz for replacement. maybe I'm lucky.  Photo signals and voltages that should be. Maybe for someone it's useful.
P.S. I changed the quartz. Nothing changed.

[Uho]

lambcutlet,
If you did not find the webcam, then you can try to connect an external one.
 1. Remove the SN9C270A.
 2. Connect the DM and DP of the external USB camera to the leads 29 and 30.
 3. Feed 5v and ground wire connect to the USB connector of the thermal imager.
If the webcam 640x480 then it should work.

[in.Vitro]

...

this will not work for the iOS Version, right?