Join our email list
Foscam - Hoe camera resetten. Foscam cameras can update this and most modern router’s can also update your DDNS address. If you haven’t setup an update client, your IP address probably changed and your DDNS address is now pointed at an old IP address. Log in to your DDNS account and check if the IP is current. Then setup your router or camera to update the service. Hello to all you fine people! I;m hoping to get some help here. I've tried a number of forums with not a single answer to my question. I'm a total newbie when it comes to IT related stuff:( I purchased a genuine Foscam wireless IP cam FI8903W and set it up with little difficulties to run wireless. There is a firmware upgrade for R2 cameras (1.11.1.132.71.1.64) that can be upgraded via the Foscam phone app. Once this upgrade is installed, if you then try to log in to the camera with Safari, you will again see the “download plugins” message/link. If you don’t have a Foscam Cloud account, click “Tap HERE” to register one, then click “Get DDNS”. Page 43 After get DDNS, click “Finish” to go back to DDNS settings. Page 44 If the network error, you fail to get the DDNS, please try again. Once you success get Foscam DDNS, you can follow below step to use.
Receive exclusive offers, new product announcements and security news direct to your inbox. Plus, get up to 20% off your next order.
Firmware upgrade fail on FI9821W V2
Users can ask and answer questions regarding Foscam IP Cameras
Moderators:mycam, FOSCAM
Re: Firmware upgrade fail on FI9821W V2
Had the same problem. The following worked for me:
1. Make sure you have IP Camera Tool ver. 1.0.0.0
2. Repeat firmware upgrade 1.11.1.16 via the IP Camera tool, no matter what messages it sends
3. Repeat firmware upgrade 1.11.1.18 with IP Camera tool exactly as described in PDF document, no matter what messages it sends
4. After all upgrades, check image with web UI. If web UI gets stuck in Settings Tab, update Gateway and DNS with IP Camera Tool, and try port 8090.
Best of luck
1. Make sure you have IP Camera Tool ver. 1.0.0.0
2. Repeat firmware upgrade 1.11.1.16 via the IP Camera tool, no matter what messages it sends
3. Repeat firmware upgrade 1.11.1.18 with IP Camera tool exactly as described in PDF document, no matter what messages it sends
4. After all upgrades, check image with web UI. If web UI gets stuck in Settings Tab, update Gateway and DNS with IP Camera Tool, and try port 8090.
Best of luck
- elgeorgejmo
- Posts: 2
- Joined: Thu Jan 16, 2014 5:41 pm
Re: Firmware upgrade fail on FI9821W V2
elgeorgejmo wrote:Had the same problem. The following worked for me:
1. Make sure you have IP Camera Tool ver. 1.0.0.0
2. Repeat firmware upgrade 1.11.1.16 via the IP Camera tool, no matter what messages it sends
3. Repeat firmware upgrade 1.11.1.18 with IP Camera tool exactly as described in PDF document, no matter what messages it sends
4. After all upgrades, check image with web UI. If web UI gets stuck in Settings Tab, update Gateway and DNS with IP Camera Tool, and try port 8090.
Best of luck
1. Make sure you have IP Camera Tool ver. 1.0.0.0
2. Repeat firmware upgrade 1.11.1.16 via the IP Camera tool, no matter what messages it sends
3. Repeat firmware upgrade 1.11.1.18 with IP Camera tool exactly as described in PDF document, no matter what messages it sends
4. After all upgrades, check image with web UI. If web UI gets stuck in Settings Tab, update Gateway and DNS with IP Camera Tool, and try port 8090.
Best of luck
There should be NO reason to change ports, whatsoever, to upgrade firmware, or after a firmware upgrade. For this camera model or any camera model.
Ports 80, 8080 and 8090 are some of the worse ports you can choose for a camera. Because they can cause port conflicts with your local network equipment. When attempting to access your camera remotely. This is because MANY ISPs equipment can use these same ports for access to their equipment remotely as well as many Router/APs use these ports for same.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
Re: Firmware upgrade fail on FI9821W V2
I also have the same exact problem. I purchased my camera about two months ago from Amazon. Should I return it? Has anyone found a solution to this problem?
- sikemo
- Posts: 1
- Joined: Mon Jan 20, 2014 3:36 am
Re: Firmware upgrade fail on FI9821W V2
sikemo wrote:I also have the same exact problem. I purchased my camera about two months ago from Amazon. Should I return it? Has anyone found a solution to this problem?
You should contact your seller. If you have lost access to this camera. To see how they say to proceed.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
Re: Firmware upgrade fail on FI9821W V2
I am having this issue too. I have logged a case with my supplier about getting it fixed/replaced.
It would be nice if Foscam offered a more reliable method of upgrades. This forum seems flooded with posts about failed upgrades.
It would be nice if Foscam offered a more reliable method of upgrades. This forum seems flooded with posts about failed upgrades.
- stevenwells99
- Posts: 3
- Joined: Mon Feb 17, 2014 5:57 am
Re: Firmware upgrade fail on FI9821W V2
Foscam Upgrade Failed
Hey Don,
I'm having the same issue as the other two people. I have determined the cause to be flashing the .18 bin prior to flashing the sys_ver1.4.1.8 bin. I came from .16 but didn't flash sys_ver1.4.1.8 first instead I flashed .18. Now I can't upgrade nor downgrade the firmware. Is there a fix to this issue? I've contacted the seller but no response yet. I'd like to fix the problem myself if there is a solution. Please help
I'm having the same issue as the other two people. I have determined the cause to be flashing the .18 bin prior to flashing the sys_ver1.4.1.8 bin. I came from .16 but didn't flash sys_ver1.4.1.8 first instead I flashed .18. Now I can't upgrade nor downgrade the firmware. Is there a fix to this issue? I've contacted the seller but no response yet. I'd like to fix the problem myself if there is a solution. Please help
- 1foscam_newb
- Posts: 2
- Joined: Thu Apr 03, 2014 2:45 pm
Re: Firmware upgrade fail on FI9821W V2
1foscam_newb wrote:Hey Don,
I'm having the same issue as the other two people. I have determined the cause to be flashing the .18 bin prior to flashing the sys_ver1.4.1.8 bin. I came from .16 but didn't flash sys_ver1.4.1.8 first instead I flashed .18. Now I can't upgrade nor downgrade the firmware. Is there a fix to this issue? I've contacted the seller but no response yet. I'd like to fix the problem myself if there is a solution. Please help
I'm having the same issue as the other two people. I have determined the cause to be flashing the .18 bin prior to flashing the sys_ver1.4.1.8 bin. I came from .16 but didn't flash sys_ver1.4.1.8 first instead I flashed .18. Now I can't upgrade nor downgrade the firmware. Is there a fix to this issue? I've contacted the seller but no response yet. I'd like to fix the problem myself if there is a solution. Please help
Recovery instructions were Sent via PM ('Private Message') in the Forum.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
- 1foscam_newb
- Posts: 2
- Joined: Thu Apr 03, 2014 2:45 pm
Re: Firmware upgrade fail on FI9821W V2
You are very welcome.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
Re: Firmware upgrade fail on FI9821W V2
I'm having the exact same issue as 1foscam_newb wrote -- Firmware at 1.4.1.5 and the App Ware on 1.11.0.26 and I can't get the camera to continue it's updates properly. Please help!
- bleat22
- Posts: 3
- Joined: Tue Apr 08, 2014 5:45 am
Who is online
Users browsing this forum: No registered users and 7 guests
Foscam Digital Technologies LLC - A United States Limited Liability Corporation
Copyright © 2015, Foscam.us All rights reserved
Join our email list
Receive exclusive offers, new product announcements and security news direct to your inbox. Plus, get up to 20% off your next order.
Firmware upgrade fail on FI9821W V2
Users can ask and answer questions regarding Foscam IP Cameras
Moderators:mycam, FOSCAM
525 posts• Page 49 of 53 • 1 ... 46, 47, 48, 49, 50, 51, 52, 53
Re: Firmware upgrade fail on FI9821W V2
having issues upgrading 3/4 of my 9821w v2's
to
System firmware version: 1.5.3.13
App firmware version: 2.x.2.18
Plug-in version: 3.3.0.7
the one that was successful to firmware was not at System Firmware Version 1.4.1.10, so the 1.40.1.10 seems to be the issue,
This successful camera recently bought and was at another system firmware I believe somewhere at 1.5.
I tried everything, inculding different cables, different router and pc's fresh downloaded file and , factory reset, hard reset.
I am pretty sure i know what Im doing, i have jtaged many things. I think Foscam has to look at this upgrade progression.
Without that new firmware the cloud beta wont work with recording.
I think its very odd and inappropriate to ask people to 'ask there reseller'.
A friend who has 1 9821 v2 from a different seller , also said his upgrade failed and he also had alot of issues with firmware, So he is done trying.
Maybe a little carrot to foscam is that apparently the cloud beta wont work unless you have the new firmware.
to
System firmware version: 1.5.3.13
App firmware version: 2.x.2.18
Plug-in version: 3.3.0.7
the one that was successful to firmware was not at System Firmware Version 1.4.1.10, so the 1.40.1.10 seems to be the issue,
This successful camera recently bought and was at another system firmware I believe somewhere at 1.5.
I tried everything, inculding different cables, different router and pc's fresh downloaded file and , factory reset, hard reset.
I am pretty sure i know what Im doing, i have jtaged many things. I think Foscam has to look at this upgrade progression.
Without that new firmware the cloud beta wont work with recording.
I think its very odd and inappropriate to ask people to 'ask there reseller'.
A friend who has 1 9821 v2 from a different seller , also said his upgrade failed and he also had alot of issues with firmware, So he is done trying.
Maybe a little carrot to foscam is that apparently the cloud beta wont work unless you have the new firmware.
- tommyz1052
- Posts: 1
- Joined: Mon Nov 02, 2015 9:46 am
Re: Firmware upgrade fail on FI9821W
I have 2 Foscam F19821w not V2 one constantly rebooting and the other fail after upgrading.
I am using a usb serial converter 3.3v to access the camera but i do not know what to do after that with all the data.
Here is the Full Boot:
U-Boot 1.1.4 (Apr 8 2009 - 11:41:01)
U-Boot code: E0500000 -> E0517540 BSS: -> E051E2BC
HI_VERSION=U_BOOT_1_1_4-M08C0305B0301 @Hi3511v110_OSDrv_1_0_0_7 20
09-03-18 20:44:35
RAM Configuration:
Bank #0: e0000000 128 MB
Flash: 16 MB
In: serial
Out: serial
Err: serial
MAC: 00-25-07-00-00-3B
Hit any key to stop autoboot: 0
## Booting image at 34100000 ...
Image Name: hilinux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3711332 Bytes = 3.5 MB
Load Address: e0a00000
Entry Point: e0a00000
OK
initrd_start 0x 0,initrd_end 0x 0
Starting kernel ...
Uncompressing Linux...............................................
................. done, booting the kernel.
Kernel Early-Debug on Level 5
Linux version 2.6.14-hi3511v100dmeb-less-release (foscam@ubuntu) (
gcc version 3.4.3 (release) (CodeSourcery ARM Q3cvs 2004)) #8 Thu
Sep 20 15:22:18 CST 2012
CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
Machine: Hi3511v100
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 se
ts
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128
sets
Built 1 zonelists
Kernel command line: mem=64M console=ttyAMA0,115200 initrd=0xE1A
00000,0x400000 mtdparts=phys_mapped_flash:1M(boot),5M(kernel),10
M(jffs2)
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 58624KB available (1752K code, 211K data, 80K init)
Mount-cache hash table entries: 512
HI_VERSION=LINUX_2_6_14-M05C0303B0103 @Hi3511v110_OSDrv_1_0_0_1
2008-11-03 18:33:31
CPU: Testing write buffer coherency: ok
checking if image is initramfs... it is
Freeing initrd memory: 4096K
NET: Registered protocol family 16
Hisilicon clock system V0.01
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NetWinder Floating Point Emulator V0.97 (double precision)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
Serial: AMBA PL011 UART driver
ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011
ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011
ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011
io scheduler noop registered
RAMDISK driver initialized: 4 RAM disks of 20480K size 1024 bloc
ksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
PPP generic driver version 2.4.2
NET: Registered protocol family 24
physmap flash device: 4000000 at 34000000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: CFI does not contain boot bank location. Assu
ming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code bro
kenness.
3 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 3 MTD partitions on 'phys_mapped_flash':
0x00000000-0x00100000 : 'boot'
0x00100000-0x00600000 : 'kernel'
0x00600000-0x01000000 : 'jffs2'
i2c /dev entries driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing init memory: 80K
init started: BusyBox v1.1.2 (2008.11.03-10:24+0000) multi-call
binary
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ ___
/ /__/ |_/
/ __ / - _ ___
/ / / / / /
_ _ _ _/ / / _/ _ ______
________________________________
[RCS]: /etc/init.d/S00devs
[RCS]: /etc/init.d/S80network
[RCS]: /etc/init.d/S90init
Generic PHY: Registered new driver
HIETHV100-M03C0301 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:36:17
Hisilicon ETHv100 net controler.
Hisilicon ETHv100 MDIO Bus: probed
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: 22:C6:7A:A0:15:31
HIGPIO-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2012-07-04 19:35:42
------------------reg=9357897------------
GPIO_I2C-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:42
GPIO_I2C2-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:4
2
ptz_init start ptz_state[1],HorPos[0],VerPos[0]
setup ptz gpio success
ptz_init end ptz_state[1],HorPos[-1],VerPos[-1],flag[0]
pcf8563 driver init successful!
hm1375 [hm1375_device_init ,1046]: init hm1375 error
hm1375 [hm1375_init ,1085]: hm1375 device init fail,deregister i
t!
insmod: cannot insert `/mnt/mtd/app/modules/hm_1375.ko': Operati
on not permitted (-1): Operation not permitted
ov2643 [ov2643_device_init ,574]: init ov2643 error
ov2643 [ov2643_init ,614]: ov2643 device init fail,deregister it
!
insmod: cannot insert `/mnt/mtd/app/modules/ov_2643.ko': Operati
on not permitted (-1): Operation not permitted
sha204 [sha204_init ,300]: sha204 driver init successful!
HIDMAC-MDC030002 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:12
SDIO-M05C0302 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:18
SDIO-M05C0302 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:18
Card stack initializing, please wait ...........................
.....
No card connected.
Check card stack end,now you can do your job....................
..
usbcore: Unknown symbol pci_enable_device
usbcore: Unknown symbol pci_set_master
usbcore: Unknown symbol pci_disable_device
insmod: cannot insert `/lib/modules/2.6.14-hi3511v100dmeb-less-r
elease/kernel/drivers/usb/core/usbcore.ko': Unknown symbol in mo
dule (-1): No such file or directory
modprobe: failed to load module usbcore
usbcore: Unknown symbol pci_enable_device
usbcore: Unknown symbol pci_set_master
usbcore: Unknown symbol pci_disable_device
insmod: cannot insert `/lib/modules/2.6.14-hi3511v100dmeb-less-r
elease/kernel/drivers/usb/core/usbcore.ko': Unknown symbol in mo
dule (-1): No such file or directory
USB1_1-M0001C030002 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:1
5
Clock to USB host has been enabled
hisilicon-ohci hisilicon-ohci.0: hisilicon OHCI
hisilicon-ohci hisilicon-ohci.0: new USB bus registered, assigne
d bus number 1
hisilicon-ohci hisilicon-ohci.0: irq 20, io mem 0xa0000000
usb usb1: Product: hisilicon OHCI
usb usb1: Manufacturer: Linux 2.6.14-hi3511v100dmeb-less-release
ohci_hcd
usb usb1: SerialNumber: hisilicon
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Hisilicon Watchdog Timer: 0.01 initialized. default_margin=5 sec
(nowayout= 0, nodeamon= 0)
HISI_WDT-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:52
<6>HISI_WDT-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35
:52
usb 1-1: new full speed USB device using hisilicon-ohci and addr
ess 2
usb 1-1: Product: 802.11 n WLAN
usb 1-1: Manufacturer: Ralink
usb 1-1: SerialNumber: 1.0
tar: /mnt/mtd/app/z_bin.tar.gz: No such file or directory
cp: /bin/cgi-bin/*: No such file or directory
cp: /bin/lighttpd-1.4.30-hi: No such file or directory
insmod tlv_320aic31 OK!
insmod rtutil3070sta OK!
rt3070sta: module license 'unspecified' taints kernel.
insmod rt3070sta OK!
rtusb init rt3070STA --->
>rt2870_probe()!
--> RTMPAllocAdapterBlock
packet> data offset = 136
packet> len offset = 88
packet> cb offset = 48
pAd = cc901000, size = 530144
--> RTMPAllocTxRxRingMemory
<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
NumEndpoints=7
BULK IN MaxPacketSize = 64
EP address = 0x81
BULK OUT MaxPacketSize = 64
EP address = 0x 1
BULK OUT MaxPacketSize = 64
EP address = 0x 2
BULK OUT MaxPacketSize = 64
EP address = 0x 3
BULK OUT MaxPacketSize = 64
EP address = 0x 4
BULK OUT MaxPacketSize = 64
EP address = 0x 5
BULK OUT MaxPacketSize = 64
EP address = 0x 6
STA Driver version-2.5.0.3
NVM is EFUSE
Allocate a net device with private data size=0!
The name of the new ra interface is ra0...
RtmpOSNetDevAttach()--->
<---RtmpOSNetDevAttach(), ret=0
<rt2870_probe()!
usbcore: registered new driver rt3070STA
insmod rtnet3070sta OK!
TDE_MAIN_VERSION[v1.0.0.1] Build Time[Nov 4 2008, 09:15:32]
TDE_ADP_VERSION[hi3511 adp v1.0.0.3] Build Time[Nov 4 2008, 09:
15:32]
insmod tde OK!
load succcessed!
Hisilicon UMAP device driver interface: v1.00
insmod hi3511_base OK!
Chip Version: Hi35110110
insmod hi3511_sys OK!
insmod hi3511_viu OK!
insmod hi3511_dsu OK!
load vpp.ko ....OK!
insmod hi3511_vpp OK!
insmod hi3511_venc OK!
insmod hi3511_group OK!
load vdec.ko ....OK
insmod hi3511_vdec OK!
load md.ko....OK!
insmod hi3511_md OK!
insmod hi3511_sio OK!
insmod hi3511_ai OK!
insmod hi3511_ao OK!
insmod hi3511_chnl OK!
insmod hi3511_h264e OK!
insmod hi3511_jpege OK!
load succcessed!
Hisilicon Media Memory Zone Manager
/mnt/mtd/boot.sh: /mnt/mtd/boot.sh: 81: /bin/MsgServer: not foun
d
/mnt/mtd/boot.sh: /mnt/mtd/boot.sh: 82: /bin/watchdog: not found
Auto login as root ...
Nov 19 09:42:29 login[315]: root login on `<NULL>0'
BusyBox v1.1.2 (2008.11.03-10:24+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
[1;32mWelcome to HiLinux.[0;39m
None of nfsroot found in cmdline.
~ $
Is somebody have instruction to recover these camera ?
Normand
I am using a usb serial converter 3.3v to access the camera but i do not know what to do after that with all the data.
Here is the Full Boot:
U-Boot 1.1.4 (Apr 8 2009 - 11:41:01)
U-Boot code: E0500000 -> E0517540 BSS: -> E051E2BC
HI_VERSION=U_BOOT_1_1_4-M08C0305B0301 @Hi3511v110_OSDrv_1_0_0_7 20
09-03-18 20:44:35
RAM Configuration:
Bank #0: e0000000 128 MB
Flash: 16 MB
In: serial
Out: serial
Err: serial
MAC: 00-25-07-00-00-3B
Hit any key to stop autoboot: 0
## Booting image at 34100000 ...
Image Name: hilinux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3711332 Bytes = 3.5 MB
Load Address: e0a00000
Entry Point: e0a00000
OK
initrd_start 0x 0,initrd_end 0x 0
Starting kernel ...
Uncompressing Linux...............................................
................. done, booting the kernel.
Kernel Early-Debug on Level 5
Linux version 2.6.14-hi3511v100dmeb-less-release (foscam@ubuntu) (
gcc version 3.4.3 (release) (CodeSourcery ARM Q3cvs 2004)) #8 Thu
Sep 20 15:22:18 CST 2012
CPU: ARM926EJ-Sid(wb) [41069265] revision 5 (ARMv5TEJ)
Machine: Hi3511v100
Memory policy: ECC disabled, Data cache writeback
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 4, 32 byte lines, 128 se
ts
CPU0: D cache: 16384 bytes, associativity 4, 32 byte lines, 128
sets
Built 1 zonelists
Kernel command line: mem=64M console=ttyAMA0,115200 initrd=0xE1A
00000,0x400000 mtdparts=phys_mapped_flash:1M(boot),5M(kernel),10
M(jffs2)
PID hash table entries: 512 (order: 9, 8192 bytes)
Console: colour dummy device 80x30
Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
Memory: 64MB = 64MB total
Memory: 58624KB available (1752K code, 211K data, 80K init)
Mount-cache hash table entries: 512
HI_VERSION=LINUX_2_6_14-M05C0303B0103 @Hi3511v110_OSDrv_1_0_0_1
2008-11-03 18:33:31
CPU: Testing write buffer coherency: ok
checking if image is initramfs... it is
Freeing initrd memory: 4096K
NET: Registered protocol family 16
Hisilicon clock system V0.01
usbcore: registered new driver usbfs
usbcore: registered new driver hub
NetWinder Floating Point Emulator V0.97 (double precision)
devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
devfs: boot_options: 0x1
JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc.
Initializing Cryptographic API
Serial: AMBA PL011 UART driver
ttyAMA0 at MMIO 0x101f1000 (irq = 12) is a AMBA/PL011
ttyAMA1 at MMIO 0x101f2000 (irq = 13) is a AMBA/PL011
ttyAMA2 at MMIO 0x101f3000 (irq = 14) is a AMBA/PL011
io scheduler noop registered
RAMDISK driver initialized: 4 RAM disks of 20480K size 1024 bloc
ksize
loop: loaded (max 8 devices)
nbd: registered device at major 43
PPP generic driver version 2.4.2
NET: Registered protocol family 24
physmap flash device: 4000000 at 34000000
phys_mapped_flash: Found 1 x16 devices at 0x0 in 8-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
phys_mapped_flash: CFI does not contain boot bank location. Assu
ming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code bro
kenness.
3 cmdlinepart partitions found on MTD device phys_mapped_flash
Creating 3 MTD partitions on 'phys_mapped_flash':
0x00000000-0x00100000 : 'boot'
0x00100000-0x00600000 : 'kernel'
0x00600000-0x01000000 : 'jffs2'
i2c /dev entries driver
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing init memory: 80K
init started: BusyBox v1.1.2 (2008.11.03-10:24+0000) multi-call
binary
_ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ ___
/ /__/ |_/
/ __ / - _ ___
/ / / / / /
_ _ _ _/ / / _/ _ ______
________________________________
[RCS]: /etc/init.d/S00devs
[RCS]: /etc/init.d/S80network
[RCS]: /etc/init.d/S90init
Generic PHY: Registered new driver
HIETHV100-M03C0301 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:36:17
Hisilicon ETHv100 net controler.
Hisilicon ETHv100 MDIO Bus: probed
Invalid HW-MAC Address: 00:00:00:00:00:00
Set Random MAC address: 22:C6:7A:A0:15:31
HIGPIO-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2012-07-04 19:35:42
------------------reg=9357897------------
GPIO_I2C-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:42
GPIO_I2C2-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:4
2
ptz_init start ptz_state[1],HorPos[0],VerPos[0]
setup ptz gpio success
ptz_init end ptz_state[1],HorPos[-1],VerPos[-1],flag[0]
pcf8563 driver init successful!
hm1375 [hm1375_device_init ,1046]: init hm1375 error
hm1375 [hm1375_init ,1085]: hm1375 device init fail,deregister i
t!
insmod: cannot insert `/mnt/mtd/app/modules/hm_1375.ko': Operati
on not permitted (-1): Operation not permitted
ov2643 [ov2643_device_init ,574]: init ov2643 error
ov2643 [ov2643_init ,614]: ov2643 device init fail,deregister it
!
insmod: cannot insert `/mnt/mtd/app/modules/ov_2643.ko': Operati
on not permitted (-1): Operation not permitted
sha204 [sha204_init ,300]: sha204 driver init successful!
HIDMAC-MDC030002 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:12
SDIO-M05C0302 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:18
SDIO-M05C0302 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:18
Card stack initializing, please wait ...........................
.....
No card connected.
Check card stack end,now you can do your job....................
..
usbcore: Unknown symbol pci_enable_device
usbcore: Unknown symbol pci_set_master
usbcore: Unknown symbol pci_disable_device
insmod: cannot insert `/lib/modules/2.6.14-hi3511v100dmeb-less-r
elease/kernel/drivers/usb/core/usbcore.ko': Unknown symbol in mo
dule (-1): No such file or directory
modprobe: failed to load module usbcore
usbcore: Unknown symbol pci_enable_device
usbcore: Unknown symbol pci_set_master
usbcore: Unknown symbol pci_disable_device
insmod: cannot insert `/lib/modules/2.6.14-hi3511v100dmeb-less-r
elease/kernel/drivers/usb/core/usbcore.ko': Unknown symbol in mo
dule (-1): No such file or directory
USB1_1-M0001C030002 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:1
5
Clock to USB host has been enabled
hisilicon-ohci hisilicon-ohci.0: hisilicon OHCI
hisilicon-ohci hisilicon-ohci.0: new USB bus registered, assigne
d bus number 1
hisilicon-ohci hisilicon-ohci.0: irq 20, io mem 0xa0000000
usb usb1: Product: hisilicon OHCI
usb usb1: Manufacturer: Linux 2.6.14-hi3511v100dmeb-less-release
ohci_hcd
usb usb1: SerialNumber: hisilicon
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Hisilicon Watchdog Timer: 0.01 initialized. default_margin=5 sec
(nowayout= 0, nodeamon= 0)
HISI_WDT-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35:52
<6>HISI_WDT-MDC030001 @Hi3511v110_OSDrv_1_0_0_1 2008-11-03 18:35
:52
usb 1-1: new full speed USB device using hisilicon-ohci and addr
ess 2
usb 1-1: Product: 802.11 n WLAN
usb 1-1: Manufacturer: Ralink
usb 1-1: SerialNumber: 1.0
tar: /mnt/mtd/app/z_bin.tar.gz: No such file or directory
cp: /bin/cgi-bin/*: No such file or directory
cp: /bin/lighttpd-1.4.30-hi: No such file or directory
insmod tlv_320aic31 OK!
insmod rtutil3070sta OK!
rt3070sta: module license 'unspecified' taints kernel.
insmod rt3070sta OK!
rtusb init rt3070STA --->
>rt2870_probe()!
--> RTMPAllocAdapterBlock
packet> data offset = 136
packet> len offset = 88
packet> cb offset = 48
pAd = cc901000, size = 530144
--> RTMPAllocTxRxRingMemory
<-- RTMPAllocTxRxRingMemory, Status=0
<-- RTMPAllocAdapterBlock, Status=0
NumEndpoints=7
BULK IN MaxPacketSize = 64
EP address = 0x81
BULK OUT MaxPacketSize = 64
EP address = 0x 1
BULK OUT MaxPacketSize = 64
EP address = 0x 2
BULK OUT MaxPacketSize = 64
EP address = 0x 3
BULK OUT MaxPacketSize = 64
EP address = 0x 4
BULK OUT MaxPacketSize = 64
EP address = 0x 5
BULK OUT MaxPacketSize = 64
EP address = 0x 6
STA Driver version-2.5.0.3
NVM is EFUSE
Allocate a net device with private data size=0!
The name of the new ra interface is ra0...
RtmpOSNetDevAttach()--->
<---RtmpOSNetDevAttach(), ret=0
<rt2870_probe()!
usbcore: registered new driver rt3070STA
insmod rtnet3070sta OK!
TDE_MAIN_VERSION[v1.0.0.1] Build Time[Nov 4 2008, 09:15:32]
TDE_ADP_VERSION[hi3511 adp v1.0.0.3] Build Time[Nov 4 2008, 09:
15:32]
insmod tde OK!
load succcessed!
Hisilicon UMAP device driver interface: v1.00
insmod hi3511_base OK!
Chip Version: Hi35110110
insmod hi3511_sys OK!
insmod hi3511_viu OK!
insmod hi3511_dsu OK!
load vpp.ko ....OK!
insmod hi3511_vpp OK!
insmod hi3511_venc OK!
insmod hi3511_group OK!
load vdec.ko ....OK
insmod hi3511_vdec OK!
load md.ko....OK!
insmod hi3511_md OK!
insmod hi3511_sio OK!
insmod hi3511_ai OK!
insmod hi3511_ao OK!
insmod hi3511_chnl OK!
insmod hi3511_h264e OK!
insmod hi3511_jpege OK!
load succcessed!
Hisilicon Media Memory Zone Manager
/mnt/mtd/boot.sh: /mnt/mtd/boot.sh: 81: /bin/MsgServer: not foun
d
/mnt/mtd/boot.sh: /mnt/mtd/boot.sh: 82: /bin/watchdog: not found
Auto login as root ...
Nov 19 09:42:29 login[315]: root login on `<NULL>0'
BusyBox v1.1.2 (2008.11.03-10:24+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
[1;32mWelcome to HiLinux.[0;39m
None of nfsroot found in cmdline.
~ $
Is somebody have instruction to recover these camera ?
Normand
- normnicol
- Posts: 1
- Joined: Tue Nov 10, 2015 12:05 am
Re: Firmware upgrade fail on FI9821W V2
Okay Don, I tried hard. Called Groupon customer service from where I bought the camera but they couldn't help me instead recommended me to call FOSCAM,called FOSCAM multiple times and its waiting time on a regular day is average 20 to 30 mins to get someone to help me with the 'recovery instructions'. And when I did get hold of someone to help, they went through the same 'firmware download' instructions which didn't help me in the first place, and still I went ahead and did it, but I got the same 'upgrade fail' error. Finally, I still don't have the recovery instructions. If you can please send it to me via msg, it will be very helpful.
Thanks.
Hanuma.
Thanks.
Hanuma.
- hmhanuma
- Posts: 3
- Joined: Tue Oct 27, 2015 10:46 pm
Re: Firmware upgrade fail on FI9821W V2
hmhanuma wrote:Okay Don, I tried hard. Called Groupon customer service from where I bought the camera but they couldn't help me instead recommended me to call FOSCAM,called FOSCAM multiple times and its waiting time on a regular day is average 20 to 30 mins to get someone to help me with the 'recovery instructions'. And when I did get hold of someone to help, they went through the same 'firmware download' instructions which didn't help me in the first place, and still I went ahead and did it, but I got the same 'upgrade fail' error. Finally, I still don't have the recovery instructions. If you can please send it to me via msg, it will be very helpful.
Thanks.
Hanuma.
Thanks.
Hanuma.
I no longer am providing the recovery instructions and files. There are two major reasons for this:
1. The recovery files and instructions change often and using the wrong ones can cause issues.
2. Well over 70 percent of those who asked for recovery instructions and files did NOT even take the time to read my PM ('Private Message') to them which included current instructions and files required for recovery.
It should be noted that it takes considerable time on my part to locate the most current recovery files and instructions because for the H.264 based IP Cameras they are camera model specific.
Without the help of your seller you WILL lose your Foscam DDNS after using any recovery methods with Foscam H.264 based cameras. Because they need to re-create your Foscam DDNS which has also complicated recovery.
It would be best to contact your seller for these instructions. Please do NOT use any old recovery instructions for your Foscam camera that others claim could be used. Because those older recovery instructions could cause you to instantly and permanently ('As in forever') turn your camera into a paperweight vs. being able to recover your camera correctly with the help of your seller.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
FI9821W V2
I'm sorry for my English. and it is possible that I am not writing in the forum thread. I have a camera Foscam FI9826w v2 problem is that it does not include a web interface. I saw my dear TheUberOverLord sent instructions and firmware updates via the serial port. could you send me too? thank you in advance
- hecz
- Posts: 4
- Joined: Thu Dec 17, 2015 11:35 pm
Re: FI9821W V2
hecz wrote:I'm sorry for my English. and it is possible that I am not writing in the forum thread. I have a camera Foscam FI9826w v2 problem is that it does not include a web interface. I saw my dear TheUberOverLord sent instructions and firmware updates via the serial port. could you send me too? thank you in advance
I no longer am providing the recovery instructions and files. There are two major reasons for this:
1. The recovery files and instructions change often and using the wrong ones can cause issues.
2. Well over 70 percent of those who asked for recovery instructions and files did NOT even take the time to read my PM ('Private Message') to them which included current instructions and files required for recovery.
It should be noted that it takes considerable time on my part to locate the most current recovery files and instructions because for the H.264 based IP Cameras they are camera model specific.
Without the help of your seller you WILL lose your Foscam DDNS after using any recovery methods with Foscam H.264 based cameras. Because they need to re-create your Foscam DDNS which has also complicated recovery.
It would be best to contact your seller for these instructions. Please do NOT use any old recovery instructions for your Foscam camera that others claim could be used. Because those older recovery instructions could cause you to instantly and permanently ('As in forever') turn your camera into a paperweight vs. being able to recover your camera correctly with the help of your seller.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
Re: FI9821W V2
TheUberOverLord wrote:hecz wrote:I'm sorry for my English. and it is possible that I am not writing in the forum thread. I have a camera Foscam FI9826w v2 problem is that it does not include a web interface. I saw my dear TheUberOverLord sent instructions and firmware updates via the serial port. could you send me too? thank you in advance
I no longer am providing the recovery instructions and files. There are two major reasons for this:
1. The recovery files and instructions change often and using the wrong ones can cause issues.2. Well over 70 percent of those who asked for recovery instructions and files did NOT even take the time to read my PM ('Private Message') to them which included current instructions and files required for recovery.
It should be noted that it takes considerable time on my part to locate the most current recovery files and instructions because for the H.264 based IP Cameras they are camera model specific.
Without the help of your seller you WILL lose your Foscam DDNS after using any recovery methods with Foscam H.264 based cameras. Because they need to re-create your Foscam DDNS which has also complicated recovery.
It would be best to contact your seller for these instructions. Please do NOT use any old recovery instructions for your Foscam camera that others claim could be used. Because those older recovery instructions could cause you to instantly and permanently ('As in forever') turn your camera into a paperweight vs. being able to recover your camera correctly with the help of your seller.
Don
I live in Uzbekistan and do not have access to a seller. I understand the risk, but the camera still does not work anymore. I really need a firmware file. please help me.
- hecz
- Posts: 4
- Joined: Thu Dec 17, 2015 11:35 pm
Re: FI9821W V2
hecz wrote:TheUberOverLord wrote:hecz wrote:I'm sorry for my English. and it is possible that I am not writing in the forum thread. I have a camera Foscam FI9826w v2 problem is that it does not include a web interface. I saw my dear TheUberOverLord sent instructions and firmware updates via the serial port. could you send me too? thank you in advance
I no longer am providing the recovery instructions and files. There are two major reasons for this:
1. The recovery files and instructions change often and using the wrong ones can cause issues.
2. Well over 70 percent of those who asked for recovery instructions and files did NOT even take the time to read my PM ('Private Message') to them which included current instructions and files required for recovery.
It should be noted that it takes considerable time on my part to locate the most current recovery files and instructions because for the H.264 based IP Cameras they are camera model specific.
Without the help of your seller you WILL lose your Foscam DDNS after using any recovery methods with Foscam H.264 based cameras. Because they need to re-create your Foscam DDNS which has also complicated recovery.
It would be best to contact your seller for these instructions. Please do NOT use any old recovery instructions for your Foscam camera that others claim could be used. Because those older recovery instructions could cause you to instantly and permanently ('As in forever') turn your camera into a paperweight vs. being able to recover your camera correctly with the help of your seller.
Don
I live in Uzbekistan and do not have access to a seller. I understand the risk, but the camera still does not work anymore. I really need a firmware file. please help me.
I cannot.
Foscam has also recently had a change in their policy and no longer allow some of the new utilities required to recover cameras using serial connections to be distributed to end customers. Which means that the only authorized recovery via serial connections must be done by an authorized Foscam reseller or distributor.
Attempting to use older methods for serial recovery can permanently make your camera no longer recoverable afterwards. Even by authorized Foscam resellers or distributors.
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
Re: Firmware upgrade fail on FI9821W V2
I cannot.
Foscam has also recently had a change in their policy and no longer allow some of the new utilities required to recover cameras using serial connections to be distributed to end customers. Which means that the only authorized recovery via serial connections must be done by an authorized Foscam reseller or distributor.
Attempting to use older methods for serial recovery can permanently make your camera no longer recoverable afterwards. Even by authorized Foscam resellers or distributors.
Don
Foscam has also recently had a change in their policy and no longer allow some of the new utilities required to recover cameras using serial connections to be distributed to end customers. Which means that the only authorized recovery via serial connections must be done by an authorized Foscam reseller or distributor.
Attempting to use older methods for serial recovery can permanently make your camera no longer recoverable afterwards. Even by authorized Foscam resellers or distributors.
Don
You want to say that if you send me .bin File, and I ask it through TFTPD I do not get? or is it company policy that prohibits you help me? I'm willing to risk the camera, contact the Special and the service does not have the opportunity. I hope for your help and understanding.
- hecz
- Posts: 4
- Joined: Thu Dec 17, 2015 11:35 pm
Re: Firmware upgrade fail on FI9821W V2
hecz wrote:I cannot.
Foscam has also recently had a change in their policy and no longer allow some of the new utilities required to recover cameras using serial connections to be distributed to end customers. Which means that the only authorized recovery via serial connections must be done by an authorized Foscam reseller or distributor.
Attempting to use older methods for serial recovery can permanently make your camera no longer recoverable afterwards. Even by authorized Foscam resellers or distributors.
Don
Foscam has also recently had a change in their policy and no longer allow some of the new utilities required to recover cameras using serial connections to be distributed to end customers. Which means that the only authorized recovery via serial connections must be done by an authorized Foscam reseller or distributor.
Attempting to use older methods for serial recovery can permanently make your camera no longer recoverable afterwards. Even by authorized Foscam resellers or distributors.
Don
You want to say that if you send me .bin File, and I ask it through TFTPD I do not get? or is it company policy that prohibits you help me? I'm willing to risk the camera, contact the Special and the service does not have the opportunity. I hope for your help and understanding.
I am saying that there is more than simply a .bin file involved in the serial recovery of Foscam H.264 based IP Cameras. There are recovery utilities ('Programs') required as well. That are no longer allowed to be sent to end customers.
Because of that, serial recovery can now only be done by a authorized Foscam reseller or distributor.
You can contact Foscam about this here:
Here is the official 'Return and Repair' policy of Foscam.com ('The manufacturer') of all Foscam products. Please see the link below:
http://foscam.com/company/return-repair-policy.html
Don
- TheUberOverLord
- Posts: 13110
- Joined: Fri Jun 22, 2012 11:52 pm
525 posts• Page 49 of 53 • 1 ... 46, 47, 48, 49, 50, 51, 52, 53
Who is online
Users browsing this forum: No registered users and 7 guests
Foscam Upgrade Firmware
Foscam Camera Firmware
Foscam Digital Technologies LLC - A United States Limited Liability Corporation
Foscam System Firmware
Copyright © 2015, Foscam.us All rights reserved