Yep - just tested and it works. Just trying again from a clean boot with no pre-existing hack file
Yep - just tested and it works. Just trying again from a clean boot with no pre-existing hack file
..and of course you should be able to use the same method to install a custom boot screen
Yep - just tested and it works. Just trying again from a clean boot with no pre-existing hack file
addfile flashfs/system/appcore.d/config.d/e8.cfg
Only needs the camera.cmd in the zipQuoteaddfile flashfs/system/appcore.d/config.d/e8.cfg
Edit: forgot to ask, how much space is left on the flash device?
So when FLIR is uploading new firmware, we should basically be keeping our fingers off?
Or there's no way they can block this?
Only needs the camera.cmd in the zipQuoteaddfile flashfs/system/appcore.d/config.d/e8.cfg
Edit: forgot to ask, how much space is left on the flash device?
173 MB...
FLASH:
Toshiba AX1682
TAIWAN 13159AE 3
TC58NVG1S3ETA00
SLC NAND FLASH, 256 MBytes
Used 83/256 Mb, that's pretty low usage. Which is a good thing. Plenty room for some extra experimentation. Not strange now that I think about it, since that flash will also have to store all the images. Right? I recall Mike mentioning only 1 flash chippie, and two seperate LPDDR's (fpga + cpu).There is _plenty_ of ways they could block this ... too many to enumerate and I wouldn't want to give them ideas ...
There is _plenty_ of ways they could block this ... too many to enumerate and I wouldn't want to give them ideas ...
rm -rf https://www.eevblog.com/forum/testgear/flir-e4-thermal-imaging-camera-teardown
Didn't work...and of course you should be able to use the same method to install a custom boot screen
But I'd be more interested to find out how that .exe gets a shell in the first place and if we can make a software that does it.
Yeah, because it's soooo hard now.. - I suppose it would be nice to avoid needing the FLIR software. Nice of them to include all the tools you need ready in the box though!
Mike (and anyone else with an E4):
How useful would you estimate this particular camera is for taking images of PCBs, in enough detail to identify which components are getting warm (with or without the benefit of your recent work)?Yes -
See pics on this post
The only issue at the moment is adjusting the lens for close-up focus -the lens can be adjusted without opening as it's only locked by the friction of the surrounding rubber, but it's a bit hard to grab hold of.
I am working on a tool to do this, as well as looking at using cheap laser cutter lenses
Looking at the moulding on the lens surround could you make a tool out of polymorph? Just soften it and push it against the lens surround.Maybe - problem is it needs to be rigid enough to push against the outer ring, but hollow enough to not block too much field of view - currently looking at a PCB ring with pins.
I'm fairly sure you can do it by putting the rndis.rsc file in \flashfs\system\appcore.d\factory.d
This file is in one of the early hack zips.
with rndis the only thing you can't do is webcam mode - you can pull your saved images via the Flir toolbar thing, or FTP
zlast_RNDIS.rsc
in the firmware file for the FLIR iX series firmware. Could you just rename that file, or is the real RNDIS.rsc different?
I'm fairly sure you can do it by putting the rndis.rsc file in \flashfs\system\appcore.d\factory.d
This file is in one of the early hack zips.
with rndis the only thing you can't do is webcam mode - you can pull your saved images via the Flir toolbar thing, or FTP
There is aCode: [Select]zlast_RNDIS.rsc
in the firmware file for the FLIR iX series firmware. Could you just rename that file, or is the real RNDIS.rsc different?
Attatched are .rsc files for normal and rndis.
I'm not sure what happens if you have both - my best guess is they are read alphabetically, so to do rndis without touching the existing usb.rsc you may need to rename it to something later alphabetically.
The files are CR32'd, so can't just be edited without re-CRCing (method a few pages earlier here)
I did try making one that did all 3 protocols but it went a bit nuts..
BTW a reminder that the first thing you should probably to if playing is run RNDIS and use filezilla to ftp off a backup copy of the whole \flashfs structure, as this is all the data specific to your camera.
#
# USB mode MSD
#
.system entry
.system.usbmode text "RNDIS"
# CRC32 d51f0c78
#
# Generated at 2000-01-08 21:43:17
# ID
#
.system entry
.system.usbmode text "UVC_MSD"
# CRC32 c37005c3
#
# USB mode MSD
#
.system entry
.system.usbmode text "RNDIS"
# CRC32 d51f0c78
(This may explain the zlast name above)
So does the CRC checks the filename, or is removing "zlast_" via camera.cmd a possibility