I was wondering indeed if dropping the update files there could be a good move. Well, it won't hurt at that point, right ? Although I suppose I should probably put the latest firmware rather than the older...
Anyway, there is an eFLIRInstall.exe in the zip. Runing strings on it yields a bunch of interesting stuff, like
"About to destroy boot config to force TFTP download on next boot"
and all sorts of other fun things like
Usage: flash [cmd]
-e <eboot.nb0> Flash bootloader
-n <nk.bin> Flash OS Image file
-n <fs.bin> Flash file system image file(s)
-b <bitmap.bmp> Flash boot bitmap
-c bitmap Clear boot bitmap
-f [<part>] Create flash file system image file
-nomount Do not remount file system after file generation
-k Keep file system(s) mounted (caution)
This flag can be combined with any of the commands
-l No partition limit check when writing binary (caution)
-destroy Destroy boot config to force TFTP download on next boot
bit late to do anything, will wait until tomorrow morning !
Thanks for the hints
I have done the i2c again:
\FlashBFS\system>
\FlashBFS\system>i2c.exe r d1 07 00
Open I2C device
I2C read command 68 7 returned: 20 46 21 4 6 3 14
\FlashBFS\system>
20 - Hundredths of seconds
46 - Seconds
21 - Minutes
04 - Hour
06 - Day
03 - Month
14 - Year
etc...
no FTP/Telnet access?
So if you hold the 'load' button down during startup.....QuoteBootloader 16.3 for ASCO (May 6 2013 11:41:42)
PMIC wake up: R5=40h E_SEQ_RDY R6=1h E_nONKEY
PMIC status: R1=1h nONKEY R2=a0h COMP_DET GP_FB2
Fuel gauge check: res=1, voltage=3704
Reset reason (0x00000000): Power ON
Press [ENTER] to force OS/FS image update (MSD) or [SPACE] to cancel.
Initiating image update in 0 seconds.
Launching flash image ...
+InitSpecifiedEthDevice
INFO: Trying to initialize the built-in USB/MSD...
MSD:: initialization
MSD: USB initialization completed
..and if you then plug it into the PCQuoteUSB Attach: High speedAppears as a drive, but just a couple of uninteresting text files - probably looking for a firmware file to be saved
..and if you send a <space> to the UART during boot....
<quote>
SETTINGS:
0) IP address: 0.0.0.0
1) Subnet Mask: 0.0.0.0
2) Boot delay: 1 seconds
3) DHCP: Enabled
4) Reset to factory default configuration
5) Autoboot: NK from NOR
6) MAC address: 00:40:7F:0B:91:39
7) Host connection: (USB MSD)
ACTIONS:
S) Save configuration
D) Download image now
L) Launch existing flash image now
R) Launch existing flash image now in SAFE (restricted) mode
E) Erase flash file system area
B) Erase OS Image area
</quote>
Option 7 may be intersting - options are USB BSD, ETHERNET and USB RNDIS, which provides virtual ethernet over USB - fairly sure the latter is what enabled the i7 hack - unfortunately I've lost the email I had about that.
Safe mode doesn't do anything interesting
... with 2 files, ERROR.TXT which says "no error" (how ironic) and TYPEINFO.TXT which has
FLIR cam boot
MSDcmd 1.3
ASCO
and then 2 serial (including the one from the unit) and the ethernet MAC of the unit.
... with 2 files, ERROR.TXT which says "no error" (how ironic) and TYPEINFO.TXT which has
FLIR cam boot
MSDcmd 1.3
ASCO
and then 2 serial (including the one from the unit) and the ethernet MAC of the unit.
Just a short notice: I failed to quickly find "ERROR", "TYPEINFO" or "NK from NOR" anywhere in the firmware update files.
Btw - I'm wondering what MAC that might be - RNDIS "MAC", FPGA "MAC", SUID (maybe MAC with some static garbage to obfuscate it?
@FPGA experts: I'm guessing the FPGA has a factory deployed serial number - my guess is it's the new GUID code
I would at least try dropping that nk.bin on there and rebooting the camera to see if anything happens [...]
tsg, you can post the next(third) full-backup for analysis.
Just install the filezilla and the flir-network-driver on your pc,
then go in TIC in the hidden menue(Settings->device-settings->camera-information->10 seconds right and activate in the usb-menue the RNDIS-option)
(later you can do in the same way to reset to the UVC and MSD-option)
If RNDIS is on, connect with filezilla to 192.168.0.2, user: flir, pass: 3vlig and dowload and zip all files.
Then post the zip here und give some information about your cam (you find the data in the camera-information-menue)
all this operations don´t touch any warranty
here is the driver:
http://cdn.cloud.flir.se/swdownload/assets/other/flir_device_drivers.exe
...
FLIR have produced many models of TIC over the years and are experts in the field. For reasons not known to me, they decided to venture outside the industrial world in which they operated and into consumer products.
Their latest series, the Ex, offers consumers levels of image clarity and performance not previously seen at the price point.
Whilst it is true that the upgrades that I performed on my E4 completely transformed its performance (especially the resolution and manual range control upgrades) I would not say that the standard E4 was poor value for money or useless at the $1000 price point. Those who do not agree should study the history and prices of thermal imaging cameras before judging the E4 too harshly.
I'd hardly call the Ex a consumer model - it's clearly aimed at professionals in the HVAC, building and and electrical markets.
professional thermographers may scoff at it but I suspect at least some of that is fear that their clients will buy one and stop calling them.
FlirOne is of course clearly aimed at the consumer
So, copying the eFlirInstaller.exe and the fif on the FAT partition does not produce anything: actually, it does, files are erased upon restart. Any file (other than the ones that got their in the first place) is erased, for that matter, and nothing happens.
At that point, I cannot do more until I get it fixed/exchanged and then I will be more cautious.
Hopefully by the time I come back to the forum there will be progress
just dropped nk.bin there. Same result: gets erased on cold reboot.
Both updater scripts (1.18 and 1.21) have some failure handling at the end (past asking for reboot). So obviously what happened was beyond that. In retrospect I was careless, I should have stopped before rebooting and tried to play with telnet. Oh well.