ah missed two little file called "Install" and "InsatllDesc" with content:
// ±æ…˝º∂∞¸ ∫œµƒ”≤º˛¡–±Ì£¨“‘º∞…˝º∂√¸¡Ó–Ú¡–°£
// …˝º∂∞¸µƒø…–≈»Œ–‘”¶∏√µ√µΩ±£÷§£¨∑ґڅ˱∏”–±ªhackµƒø…ƒ‹°£
// …˝º∂∞¸µƒø…–≈»Œ–‘”¶∏√µ√µΩ±£÷§£¨∑ґڅ˱∏”–±ªhackµƒø…ƒ‹°£
{//...
thats weired: got two of those yesterday evening - today its blocked!
anyway - they look like this:
General_HZXM_IPC_HI3516C_53H20L_S38_V4.02.R11.Nat.OnvifS.20160511_ALL.bin
General_HZXM__IPC_HI3516C_50H20L_RT3070_V4.02.R11.Nat.OnvifS.20160615_ALL.bin
and content is:
custom-x.cramfs.img 21kb...
thats the point - would be too easy: both ieGeeks died long time ago caused by firmware upgrade... :(
meanwhile I found this website
but also no flashable image, isnt it?!
yes and no: I've got a 3518 and an additional 3516 based one; both from ieGeek... and ready to go now: CH341A with inplace SOP8 testclip arrived a few days ago but I did not get a full bin-file to flash the 25Q128 spi chip yet... ideas?
me again - the tinkerer ;)
I'll give it a try: just ordered the CH341A programmer and the SOP8 clip at ALiExpress; will take some time to deliver
Question: does this eprom only contain the boot loader or the whole firmware?
got another working IPCAM with HI3516 and U-Boot running fine - flash...
oh my dear... lets say this is really "china crap" and I will invest time & money in a Hikvision IPCAM now...
Thank you very much again for your effort !!
BTW: and Yes -> it has a 24 / 25 series SPI flash in an 8-pin DIP package!
BUT: do I have to unsolder it? ist a SMD device and what...
okay... after a while I was so frustrated and decided to write "u-boot-200MHZ.bin" (from: Hi3518_SDK_V1.0.7.0) via "sf write 0x80008000 0 0x100000" to Flash - now the device is gone completly and not even booting anymore... :(
First of all: thank you to help me on this bricked stuff!!
short review: my ieGeek 1080p was flashed with most current firmware v11.x from official ieGeek site (!) because motion detection was not as good as needed and after a reboot there is NO webinterface, even NO configuration can be done...
bootup sequence looks like this:
16384 KiB hi_fmc at 0:0 is now current device
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1832528 Bytes = 1.7 MiB
Load Address: 80008000
Entry...
what I did meanwhile: tried to upload a renamed Firmware.bin via TFTP as uImage
sf probe0
sf erase 0x3e0000 0xa00000
tftp uImage
sf write 0x80008000 0x3e0000 0x36ff18
reset
no luck :(
so: is it possible to get the needed mtdblocks splitted from Firmware.bin file?