WiFi IP cameras on the Ingenic T10 processor (I21AG, HX-I2110T2, HW0036 and others)



Rep: (60)
WiFi IP cameras on the Ingenic T10 processor (I21AG, HX-I2110T2, HW0036, Digoo BB-M2 and others)
The camera has many clones from different "manufacturers": SANNCE I21AG; MixSight HX-I2110T2; Wan Scratch HW0036; Escam G02 and others.
In 2018, a new camera modification was released that works only through JoyLite. The happy owners of such cameras can not read the topic!
Joylite
1. The firmware can be merged, but there is no point in this - self-repair of the firmware from the memory card is provided.
2. The web interface is missing as a class.
3. No applications other than JoyLite work with the camera. JoyLite worksonlyvia the Internet, if the provider does not block the cloud.
4. The firmware is incompatible with old cameras - neither up nor down.
5. Discussion of all this is in the subject, if interested - the beginninghere, also see posts for fall 2018.
A photo
Attached Image


Important!
For the initial connection, you need an Android / iOS tablet. In the future, access is also possible from a computer / DVR.
Instructions for connecting in Russian
Access string in browser:http: // your_camera_ip: 81 /. In new firmware, the access port has been changed. Read the instructions or use Search-Production_Tools.
Full-size video 1280 * 1720 is available only in IE (after installing the plugin, link at the bottom of the page). In other browsers, the size is 640 * 360
You can watch the RTSP stream in the VLC player.
In my opinion, the most convenientOnvif device menager- he finds all the cameras in LAN, he can watch and record video in any available quality.

Some cameras can operate in access point mode, creating their own SSID. However, in those cameras that I visited, this functionality is cut.

Vulnerabilities are known in the camera software, therefore it is recommended to close the Internet for the camera on the router. If remote access is expected, open only the necessary ports.
In particular, there is a vulnerability that allows you to get a login / password in clear form, which gives full access to the camera.
And do not dismiss this under the pretext that anyone is interested in the view of mine .. insert the right one ..
Full access is used including for a botnet. In addition, it is believed that the scorching of cameras in some cases is connected with unauthorized access.

If your camera works, take ten minutes to createbackup firmware.This will save you a lot of time and nerves in the future.
And if you post (or send me) your backup, it will help other people. For my part, I promise to depersonalize the firmware (it will not have your data) and post it.

The firmware laid out below exactly works with such boards
Attached Image
Attached Image
Attached Image


Options
Specifications:
Processor: Ingenic T10
Image Sensor: 1/4 inch CMOS
Pixels: 1.0MP megapixels
Resolution: 1280 * 720
Frame Rate: 1-25fps
Record Mode: Scheduled / motion
Compression Format: H.264
Focus: 3.6mm fixed lens
LED: 6pcs IR LEDs, IR distance 10m
Low Lux: 0lux (IR LED on)
Digital Zoom: No; Remote Playback: Yes
Alarm Linkage: Snapshot, record, send email, APP message
Preset: 16 maximum; Online User: 4 maximum
Storage: support 64G TF Card
WiFi Protocol: 802.11b / g / n, one key set
Phone / pad APP: support Android / iOS OS
Browser: support IE, Firefox, Chrome, etc
APP Language: English, Chinese
Protocol: P2P, WiFi, HTTP, DHCP, SMTP, FTP, RTSP
Material: ABS plastic; Size: 9.6 * 9.1 * 12cm

MiniFAQ
Cameras do not know how to write video to the cloud / on ftp. Questions about this will be regarded as a flood.

Vlc player
rtsp: // your_camera_ip: 10554 / tcp / av0_0 first stream - HD
rtsp: // your_camera_ip: 10554 / tcp / av0_1 second stream (lower quality)
if it doesn’t start without a password, then this look:
rtsp: // your_camera_ip: 10554 / user = admin & password = & channel = 1 & stream = 0.sdp? real_stream

Ftp connection

Access via telnet.
1st method: install DIGMA, connect the camera in it, go to the settings, turn on telnet. DIGMA will tell us the username / password, by default it is root / hslwificam.

2nd method: reset telnet password.
1. Go Intenet Explorer (and only them) athttp: // your_camera_ip: 81 /
2. Select livestream mode (for Explorer) and go to the camera settings
3. Select Alarm Service Setting, then Ftp service settings.
4. In the field “FTP Server” enter: $ (killall telnetd)
5. In the field “FTP User” enter: $ (telnetd -l / bin / sh)
6. Click “set up”, then click “test”
7. A pop-up window will pop up with a test error message. This means that everything went fine and we have access to Telnet without a password.

Email alert settings:
As I understand it, the address for authorization should not exceed 7 characters + @ gmail.com, I could not configure the Yahoo address.
And forward 465 ports on the modem.
smtp gmail-a (SSL) works through port 465, and you need an open port for the camera to send a message
The name "User" must be complete, i.e. [email protected]
And secondly, SSL must be set to TLS

one more moment:
My account uses two-step authentication, and therefore there is no authorization.
Everything is solved quite easily,
1. go to the addresshttps: //security.googl...pppasswords&e=65716150
2. Log in
3. In the "Application" drop-down list, select "Other (enter a name)"
4. Name your application (I have wificam1)
5. Google will generate a password for this application, enter it in the camera settings !!!

if you are configuring not on gmail - read the instructions on the mail server.

Some mobile operators block Chinese clouds. You can get around setting up a VPN.
VPN setup example
If the camera is warming
In the normal state, the camera is a little warm, when you turn on the infrared light - it becomes noticeably warmer, this is normal.
Strong heating, and even more so - the appearance of a smell indicates a malfunction, you need to look for the cause.
One of the possible - increased supply voltage. There are several stabilizers on the board, their location and voltage are visible in the picture.
Attached Image


If you can’t find a reason, you can at least stick a radiator,how did itmih12345
Recovery
If the camera responds in the terminal and responds to keystrokes - there is hope to restore a little blood. Everything is quite simple (with straight hands)

1. disassemble the camera
2. Find on the main UART board. in our camera, these are three unsealed contacts near the flash drive slot. closest to the GND slot, then TX and RX. *
3. connect to the computer through the adapter. There are a lot of adapters on the network: home-made ones, from old phones, self-assembly kits, ready-made ones on the same Ali.
4. On the computer, run the terminal. On Windows "native" HyperTerminal, Linuxsoids usually recommend PuTTY. there is no difference - the whole thing is a habit. I personally liked Terminal by Bray ++ - all the settings in front of you are in the main window and you can change them on the fly
4.1 HyperTerminal from XP.Attached filehypertrm.rar(21.23 KB)

5. We expose for communication the port that our adapter has become, the speed is 115200, 8bit, none, 1, none. start a session
6. turn on the power to the camera and see what it writes to the terminal.
7. if at least the initial boot goes fine - we start working with it.

* For starters, we connect only to GND and TX. After making sure that the output is on, we also connect RX.
Explanation: With some adapters, the camera may not start with an RX connected. in this case, connect the RX through a 4.7k resistor.
Attached Image

about UART adapters
The simplest COM-TTL converter
example of probes for connection. the diameter of the sting should be no more than 0.5mm, otherwise they will not hold.
Attached Image


At the moment, at least three firmware options are known. Two of them are poorly compatible with each other, although they have the same U-boot. The third one (with kernel Jun 2 12:28:35 CST 2017) is not compatible with the U-boot from the previous ones and requires editing startup parameters. For this reason, the information previously published here has become irrelevant and may lead to a result opposite to what was expected.
Show the boot log and printenv in U-boot. Further actions depend on what you have and what you want to receive.
Outdated Information
Often the camera stops working due to a rally of settings.
we check, for this we enter env print in the terminal and check
The correct settings log
isvp # env print
baudrate = 115200
bootargs = console = ttyS1,115200n8 mem = 39M @ 0x0 ispmem = 5M @ 0x2700000 rmem = 20M @ 0x2C00000 init / linuxrc rootfstype = squashfs init = / linuxrc rootfstype = squashfs root = / dev / mtdblock2 rwztds boot) , 2176k (kernel), 3584k (rootfs), 2176k (system) quiet
bootcmd = sf probe; sf read 0x80600000 0x40000 0x280000; bootm 0x80600000
bootdelay = 1
ethact = Jz4775-9161
ethaddr = 00: 11: 22: 33: 44: 55
gatewayip = 193.169.4.1
ipaddr = 193.169.4.81
loads_echo = 1
netmask = 255.255.255.0
serverip = 193.169.4.2
stderr = serial
stdin = serial
stdout = serial

here we are interestedbootargs. the sizes of some areas may vary depending on the firmware. this is normal.ethaddr, gatewayip, ipaddr, serveripnot important.
If abootargsdifferent - restore:
setenv bootargs console = ttyS1,115200n8 mem = 39M @ 0x0 ispmem = 5M @ 0x2700000 rmem = 20M @ 0x2C00000 init / linuxrc rootfstype = squashfs init = / linuxrc rootfstype = squashfs root = / dev / mtdblocks rk mbbparts 256 = , 2176k (kernel), 3584k (rootfs), 2176k (system) quiet

you need to dial by hand and without errors: the camera does not understand the clipboard, it does not always respond adequately to backspace.
if you make a mistake, erase the entire line, press Enter and repeat the entry. after that we write printenv and make sure that the boot line is accepted and we haven’t messed up anywhere. if everything is OK -env saveandboot
must start.
Do not start? We enter such a line
setenv bootargs console = ttyS1,115200n8 mem = 39M @ 0x0 ispmem = 5M @ 0x2700000 rmem = 20M @ 0x2C00000 init / linuxrc rootfstype = squashfs init = / linuxrc rootfstype = squashfs root = / dev / mtdblocks rk mbbparts 256 = , 2176k (kernel), 3584k (rootfs), 2176k (system) init = / bin / sh

check, boot, wait a couple of minutes, distort the food. If it doesn’t help, go to the next spoiler.

If everything is OK - disconnect from the computer, collect the camera and enjoy life))

Recovery - 2. Firmware without evaporation
If restoring the settings did not help, lay out the download log in full, in each case, you can and should act differently.

Two firmware options are currently available: e10.7.1.17.59E and e10.9.1.17.5E Despite the large number of fill files, this is so. All blocks of these firmware are compatible with each other.
You can distinguish them by such a line
bootargs = console = ttyS1,115200n8 mem = 39M @ 0x0 ispmem = 5M @ 0x2700000 rmem = 20M @ 0x2C00000 init = / linuxrc rootfstype = squashfs root = / dev / mtdblock2 rw mtdparts = jz_sfc: 256k (boot), 2176 3584k (rootfs), 2176k (system) quiet

In June 2017, a new version of the firmware appeared - significantly redesigned. Only kernel is compatible with old firmware.
Initialization string
bootargs = console = ttyS1,115200n8 mem = 39M @ 0x0 ispmem = 5M @ 0x2700000 rmem = 20M @ 0x2C00000 init = / linuxrc rootfstype = squashfs root = / dev / mtdblock2 rw mtdparts = jz_sfc: 256k (boot), 2176 3328k (rootfs), 2304k (system), 64k (factory), 64k (param) quiet
features read above and below the post with firmware.

For those with a mustache:
Fill the camera with firmware. Download (old)Attached fileNOBOOT.rar(7.01 MB)
orfrom hereorfrom here
New from Sannce

unpack
We type in the terminal
isvp # sf probe
the manufacturer c2
SF: Detected MX25L64 ** E
isvp # sf erase 0x040000 0x7c0000
SF: 8126464 bytes @ 0x40000 Erased: OK
isvp # loadb
## Ready for binary (kermit) download to 0x82000000 at 115200 bps ...
and transfer the file using the terminal. If the transmission was successful, the camera answers
## Total Size = 0x007c0000 = 8126464 Bytes
## Start Addr = 0x82000000
pay attention to the file size - it must match. also see the parameterStart addrif it is different, then substitute the one that the camera issued (instead of 0x82000000)
isvp # sf write 0x82000000 0x040000 0x7c0000
SF: 8126464 bytes @ 0x40000 Written: OK
isvp # boot

after a reboot, the camera tries to connect to the "old" WiFi.
make an iron reset and initial connection setup.
If you got a cyclic SIGTERN - gohere

Recover DID and WiFi access
After the firmware, the camera receives "alien" parameters and is not visible through the cloud. Fix it.
We are connected by telnet
In the terminal, we enter in turn:
rm -rf /system/www/system.ini
rm -rf /system/param/factory.ini
rm -rf /system/www/network.ini

Making an iron reset.
After rebooting the camera, you should see your native camera ID everywhere and an invitation to connect.

Firmware
Firmware for the web interface Device Embeded Web UI Version - 12.9.7.5-savagemessiahzine.com
merged from the soldered flash drive of the new camera
Attached fileIPC.zip(7.1 MB)

it is also necessary to fill in the programmer. Some programmers allow you to record a USB flash drive without soldering. if you don’t have one, you will have to remove the USB flash drive and then solder it into place. however, one who has a programmer is unlikely to read this, he already knows))
ATTENTION! if you do not have a normal soldering station - do not pick your usual soldering iron. with a probability of 101% after that, the camera cannot be restored!
After flashing, be sure to restore the DID.
For fans to dig deeper))
Any actions with the camera files can lead to bricking. If you don’t know what you are doing, don’t do it better!
You do everything at your own peril and risk!
If you have not been stopped by warnings, let's get started.
1. Enter telnet.
1.1 You can use PuTTY: Enter the IP address of the camera, select telnet. Click Open.
1.2 Or native Windows. open cmd and enter telnet "IP_camera" (without quotes)
2. enter the username and password.
the camera answers: Processing / etc / profile ... Done
3. Run the ftp daemon with the command:
tcpsvd -vE 0.0.0.0 21 ftpd -w / &
(switch -w activates apload)
see the answer: ~ # tcpsvd: listening on 0.0.0.0:21, starting
this means that ftp access to the camera has been obtained.
4. We are connected by any ftp manager, for example Total Commander.
5. In cameras with Thx firmware, the ftp daemon is missing.adding busybox and enabling ftp.busybox is a sea of ​​opportunities, not just ftp
5.1 rootfs with integrated busybox for Thx firmware fromGosudar

Well, and then - you yourself know what to do. Another warning:If you do not know - do not do it better!

grade.sh - a script for rolling dumps from under Linux

some details

telnet enable bit

update structure

The camera log usually records:
videostream is run this is someone watching the web
p2p param opration camera data was requested through the cloud, the connection took place.
p2p livestream is run someone is looking through the cloud
p2p audiostream is run someone turned on the speaker through the cloud
These are the main statuses.

about audio and video streams - a continuation - and a little bit more)) - and in detail

Enhancing Security: Eliminating Vulnerabilities
If you opened the camera to the Internet - in addition to what is written in the "Important" section, you can do everything describedhere
Put your own password on telnet
improved web interface

Recommended software
For Android: DIGMA. Works with almost all cameras. It can work both locally and through Chinese P2P cloudsAttached fileDIGMA SmartCam_v1.13_apkpure.com.apk(7.61 MB)

Onvif device menagerfinds and shows all local cameras, displays useful information and shows the video stream (quality can be selected)
Chinese utility for searching and flashing cameras. It also finds all local cameras and displays basic information about them. The format of the firmware is unknown.Attached fileSearch - Production Tools 4.4.exe(1.85 MB)

A client with great functionality and capabilities. Connection:
Capture-Network - select Foscam (HTTP motion jpeg) - picture 640 * 360 FPS 3-4;
Capture-Network- rtsp: // IP: 10554 / tcp / av0_0 by checking the "For transport ..." checkbox - picture 1280 * 720 FPS 15
Attached fileContaCam-7.0.0-Setup-Rus.exe(16.41 MB)

A client that allows you to save video to your computer in avi format without removing the card from the camera.Attached fileDeviceClient.exe(12.5 MB)

Utility to reset cameras to factory settings. Application:
First, open Config.ini and change Type = 1 to Type = 0. we launch. check. if it doesn’t help, return Type = 1 and run it again, check. in the latter case, the camera fully returns to the factory settings, deeper than the Reset button.
There were no complaints about the bricking of the cameras after applying the program, but
You do everything at your own peril and risk!
Attached fileResetConfig.zip(291.32 KB)

Program for checking memory cards. Checks only free space, i.e. if you want to check the whole card, delete the files and format the card before checking.
Attached fileh2testw_1.4.zip(213.02 KB)
Official updates

Wanted camera firmwareEscam Elf QF200 . If you have such a camera - refer to Proshaaa or Gosudar
Wanted Wanscam HW0026-1 camera firmware

We are also looking for firmware for a camera that raises its own access point.


  • Before posting read the message Video section rules
  • Messages that are not related to the topic of discussion (offtopic) are deleted without warning.

K
There is no curator in the subject. For questions about filling the caps, please contact the section moderators via the buttonPictureunder the messages to which you want to add links.


Post has been editedmihadom - 16.09.19, 10:54
Reason for editing: new information added



Rep: (10)
vesli12 @ 17.04.19, 15:04*
but it does not issue infu terminal.

you have connected rx-tx?



Rep: (1)
* rabbi-t, tried rx-tx, tx-rx, tx-tx,
rx-rx cnd I took from the point where it was more convenient

Post has been editedvesli12 - 17.04.19, 12:31



Rep: (0)
Hello, I eat the camera (noname) with CPU cycles Ingenic T20 is similar to Sannce I21ag, stops working, cyclic rebuut.
I eat backup (merged when working).
boot.img, kernel.img, root.img, p2pcam.img, system.img

dev: size erasesize name
mtd0: 00040000 00008000 "boot"
mtd1: 00170000 00008000 "kernel"
mtd2: 00120000 00008000 "root"
mtd3: 00300000 00008000 "p2pcam"
mtd4: 00230000 00008000 "system"

Boot log terminal:


U-Boot SPL 2013.07 (Sep 26, 2017 - 10:51:34)
pll_init: 365
l2cache_clk = 375000000
pll_cfg.pdiv = 8, pll_cfg.h2div = 4, pll_cfg.h0div = 4, pll_cfg.cdiv = 1, pll_cfg.l2div = 3
nf = 36 nr = 1 od0 = 1 od1 = 1
cppcr is 02404900
CPM_CPAPCR 0470890d
nf = 42 nr = 1 od0 = 1 od1 = 1
cppcr is 02a04900
CPM_CPMPCR 07d0c90d
nf = 50 nr = 1 od0 = 1 od1 = 1
cppcr is 03204900
CPM_CPVPCR 0320490d
cppcr 0x9a794410
apll_freq 860160000
mpll_freq 1000000000
vpll_freq = 1200000000
ddr sel mpll, cpu sel apll
ddrfreq 500000000
cclk 860160000
l2clk 286 720 000
h0clk 250000000
h2clk 250000000
pclk 125000000
DDRC_DLP: 0000f003


U-Boot 2013.07 (Sep 26, 2017 - 10:51:34)

Board: ISVP (Ingenic XBurst T20 SoC)
DRAM: 64 MiB
Top of RAM usable for U-Boot at: 84000000
Reserving 435k for U-Boot at: 83f90000
Reserving 32784k for malloc () at: 81f8c000
Reserving 32 Bytes for Board Info at: 81f8bfe0
Reserving 124 Bytes for Global Data at: 81f8bf64
Reserving 128k for boot params () at: 81f6bf64
Stack Pointer at: 81f6bf48
Now running in RAM - U-Boot at: 83f90000
MMC: msc: 0
the manufacturer c2
SF: Detected MX25L64 ** E

In: serial
Out: serial
Err: serial
Net: Jz4775-9161
Hit any key to stop autoboot: 0
the manufacturer c2
SF: Detected MX25L64 ** E

--->probe spend 4 ms
SF: 1507328 bytes @ 0x40000 Read: OK
--->read spend 220 ms
## Booting kernel from Legacy Image at 80600000 ...
Image Name: Linux-3.10.14
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1446926 Bytes = 1.4 MiB
Load Address: 80010000
Entry Point: 80382800
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[0.000000] Linux version 3.10.14 (song @ fc12_song) (gcc version 4.7.2 (Ingenic r2.3.3 2016.12)) # 2 PREEMPT Thu Sep 28 14:49:47 CST 2017
[0.000000] bootconsole [early0] enabled
[0.000000] CPU0 RESET ERROR PC: 83F905DC
[0.000000] CPU0 revision is: 00d00101 (Ingenic Xburst)
[0.000000] FPU revision is: 00b70000
[0.000000] CCLK: 860MHz L2CLK: 430Mhz H0CLK: 200MHz H2CLK: 200Mhz PCLK: 100Mhz
[0.000000] Determined physical RAM map:
[0.000000] memory: 0041e000 @ 00010000 (usable)
[0.000000] memory: 00032000 @ 0042e000 (usable after init)
[0.000000] User-defined physical RAM map:
[0.000000] memory: 02600000 @ 00000000 (usable)
[0.000000] Zone ranges:
[0.000000] Normal [mem 0x00000000-0x025fffff]
[0.000000] Movable zone start for each node
[0.000000] Early memory node ranges
[0.000000] node 0: [mem 0x00000000-0x025fffff]
[0.000000] Primary instruction cache 32kB, 8-way, VIPT, linesize 32 bytes.
[0.000000] Primary data cache 32kB, 8-way, VIPT, no aliases, linesize 32 bytes
[0.000000] pls check processor_id [0x00d00101], sc_jz not support!
[0.000000] MIPS secondary cache 128kB, 8-way, linesize 32 bytes.
[0.000000] Built 1 zonelists in Zone order, mobility grouping off. Total pages: 9652
[0.000000] Kernel command line: console = ttyS1,115200n8 mem = 38M @ 0x0 ispmem = 8M @ 0x2600000 rmem = 18M @ 0x2E00000 init = / linuxrc rootfstype = squashfs root = / dev / mtdblock2 rw mtdparts = jz_sfc: 256k (boot), 1472k (kernel), 1152k (root), 3072k (p2pcam), - (system)
[0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
[0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
[0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
[0.000000] Memory: 33436k / 38912k available (3564k kernel code, 5476k reserved, 649k data, 200k init, 0k highmem)
[0.000000] SLUB: HWalign = 32, Order = 0-3, MinObjects = 0, CPUs = 1, Nodes = 1
[0.000000] Preemptible hierarchical RCU implementation.
[0.000000] NR_IRQS: 418
[0.000000] clockevents_config_and_register success.
[0.000024] Calibrating delay loop ... 858.52 BogoMIPS (lpj = 4,292,608)
[0.087752] pid_max: default: 32768 minimum: 301
[0.092721] Mount-cache hash table entries: 512
[0.100191] regulator-dummy: no parameters
[0.104440] NET: Registered protocol family 16
[0.113596] bio: create slab<bio-0>at 0
[0.119973] jz-dma jz-dma: JZ SoC DMA initialized
[0.125026] usbcore: registered new interface driver usbfs
[0.130639] usbcore: registered new interface driver hub
[0.136079] usbcore: registered new device driver usb
[0.141312] i2c-gpio i2c-gpio.0: using pins 12 (SDA) and 13 (SCL)
[0.147558] i2c-gpio i2c-gpio.1: using pins 57 (SDA) and 58 (SCL)
[0.153698] media: Linux media interface: v0.10
[0.158320] Linux video capture interface: v2.00
[0.165010] Switching to clocksource jz_clocksource
[0.169964] cfg80211: Calling CRDA to update world regulatory domain
[0.177063] jz-dwc2 jz-dwc2: cgu clk gate get error
[0.181947] jz-dwc2 jz-dwc2: regulator vbus get error
[0.187120] DWC IN OTG MODE
[0.340332] sft id ========================= off
[0.344923] dwc2 dwc2: Keep PHY ON
[0.348310] dwc2 dwc2: Using Buffer DMA mode
[0.552450] dwc2 dwc2: Core Release: 3.00a
[0.556571] dwc2 dwc2: DesignWare USB2.0 High-Speed ​​Host Controller
[0.562914] dwc2 dwc2: new USB bus registered, assigned bus number 1
[0.570266] hub 1-0: 1.0: USB hub found
[0.574006] hub 1-0: 1.0: 1 port detected
[0.578208] dwc2 dwc2: DWC2 Host Initialized
[0.582702] NET: Registered protocol family 2
[0.587696] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[0.594619] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[0.601099] TCP: Hash tables configured (established bind 512 512)
[0.607387] TCP: reno registered
[0.610587] UDP hash table entries: 256 (order: 0, 4096 bytes)
[0.616540] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[0.623158] NET: Registered protocol family 1
[0.627867] RPC: Registered named UNIX socket transport module.
[0.633800] RPC: Registered udp transport module.
[0.638635] RPC: Registered tcp transport module.
[0.643336] RPC: Registered tcp NFSv4.1 backchannel transport module.
[0.650319] freq_udelay_jiffys [0] .max_num = 10
[0.654746] cpufreq udelay loops_per_jiffy
[0.659208] dwc2 dwc2: ID PIN CHANGED!
[0.662988] init DWC as A_HOST
[ 0.666075] 12000 59885 59885
[ 0.669334] 24000 119771 119771
[ 0.672759] 60000 299428 299428
[ 0.676202] 120000 598857 598857
[ 0.679830] 200000 998095 998095
[ 0.683286] 300000 1497142 1497142
[ 0.687095] 600000 2994285 2994285
[ 0.690728] 792000 3952457 3952457
[ 0.694435] 1008000 5030400 5030400
[ 0.698255] 1200000 5988571 5988571
[0.707533] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[0.714392] jffs2: version 2.2. В© 2001-2006 Red Hat, Inc.
[0.720367] msgmni has been set to 65
[0.725309] io scheduler noop registered
[0.729345] io scheduler cfq registered (default)
[0.735761] jz-uart.1: ttyS1 at MMIO 0x10031000 (irq = 58) is a uart1
[0.744044] console [ttyS1] enabled, bootconsole disabled
[0.744044] console [ttyS1] enabled, bootconsole disabled
[0.759431] brd: module loaded
[0.764707] loop: module loaded
[0.768357] logger: created 256K log 'log_main'
[0.773681] jz SADC driver registeres over!
[0.779141] jz TCU driver register completed
[0.784034] the id code = c22017, the flash name is MX25L6406F
[0.790149] JZ SFC Controller for SFC channel driver register 0
[0.796303] 5 cmdlinepart partitions found on MTD device jz_sfc
[0.802455] Creating 5 MTD partitions on "jz_sfc":
[0.807483] 0x000000000000-0x000000040000: "boot"
[0.813063] 0x000000040000-0x0000001b0000: "kernel"
[0.818793] 0x0000001b0000-0x0000002d0000: "root"
[0.824283] 0x0000002d0000-0x0000005d0000: "p2pcam"
[0.830031] 0x0000005d0000-0x000000800000: "system"
[0.835699] SPI NOR MTD LOAD OK
[0.839135] Bus Mode Reg after reset: 0x00020101, cnt = 0
[0.847857] libphy: jz_mii_bus: probed
[ 0.851821] =======>gmacdev = 0x819e8e80<================
[ 0.857445] =========>gmacdev->MacBase = 0xb34b0000 DmaBase = 0xb34b1000
[0.864391] Bus Mode Reg after reset: 0x00020101, cnt = 0
[0.870881] eth% d: Do not found any phy device at all
[0.876019] jz_mac jz_mac.0: MII Probe failed!
[0.881054] jzmmc_v1.2 jzmmc_v1.2.0: vmmc regulator missing
[0.926591] jzmmc_v1.2 jzmmc_v1.2.0: register success!
[0.932268] TCP: cubic registered
[0.935709] NET: Registered protocol family 17
[0.942385] input: gpio-keys as / devices / platform / gpio-keys / input / input0
[0.949611] drivers / rtc / hctosys.c: unable to open rtc device (rtc0)
[0.961379] VFS: Mounted root (squashfs filesystem) readonly on device 31: 2.
[0.969180] Freeing unused kernel memory: 200K (8042e000 - 80460000)
[1.116528] usb 1-1: new high-speed USB device number 2 using dwc2
can not run '/ sbin / swapoff': No such file or directory
can not run '/ bin / hostname': No such file or directory
mdev is ok ......
[1.805633] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb74: 0x1544 instead
[1.815492] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb78: 0x0048 instead
[1.825336] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb7c: 0x81ff instead
[1.835177] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb84: 0x000a instead
[1.845020] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb88: 0x30f1 instead
[1.854860] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb8c: 0x30f1 instead
[1.864700] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb90: 0x30f1 instead
[1.874540] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb98: 0x000a instead
[1.884381] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfb9c: 0x000a instead
[1.894223] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x000cfba4: 0x931a instead
[1.904060] jffs2: Further such events for this erase block will not be printed
[2.291796] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x0022000c: 0x1900 instead
[2.301645] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220014: 0x8105 instead
[2.311489] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220018: 0x1543 instead
[2.321332] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x0022001c: 0x0003 instead
[2.331175] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220020: 0x81ff instead
[2.341015] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220028: 0x0308 instead
[2.350855] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x0022002c: 0xdccb instead
[2.360693] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220030: 0xdccb instead
[2.370534] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220034: 0x0002 instead
[2.380375] jffs2: jffs2_scan_eraseblock (): Magic bitmask 0x1985 not found at 0x00220044: 0xde00 instead
[2.390209] jffs2: Further such events for this erase block will not be printed
[2.403260] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00224b00: Read 0x00000000, calculated 0x12e422f8
[2.414199] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00224c10: Read 0x00000000, calculated 0x5b081fb5
[2.425134] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00224d20: Read 0x00000000, calculated 0xed63a67b
[2.436104] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225010: Read 0x00000000, calculated 0x15a53001
[2.447044] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225120: Read 0x00000000, calculated 0x5b9c4260
[2.459367] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x002256dc: Read 0x000001e8, calculated 0xa5fa5226
[2.470295] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225728: Read 0x00000044, calculated 0x45c63c38
[2.481225] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x002257a8: Read 0x000001e8, calculated 0x5b20d2e1
[2.492149] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x002257f4: Read 0x00001343, calculated 0x24bc7191
[2.503078] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x0022587c: Read 0x00000044, calculated 0xaf42672f
[2.514013] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225940: Read 0x00000000, calculated 0x4a0d0b9b
[2.524933] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225984: Read 0x0000001e, calculated 0x868bb876
[2.535856] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x002259d0: Read 0x98f7fb1d, calculated 0x76a94985
[2.546795] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225a94: Read 0x00000330, calculated 0x6969cfa5
[2.557719] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225ad8: Read 0x000000b9, calculated 0x6be1d378
[2.568647] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225b60: Read 0x000000c3, calculated 0x638d5264
[2.579572] jffs2: jffs2_scan_inode_node (): CRC failed on node at 0x00225bac: Read 0x00000000, calculated 0x7d81c211

(None) login: ln: /home/lib/libverify.so: File exists
[3.339766] exFAT: Version 1.2.9
[3.388008] jz_codec_register: probe () successful!
[3.736868] dma dma0chan24: Channel 24 have been requested (phy id 7, type 0x06 desc a1ec3000).
[3.746157] dma dma0chan25: Channel 25 have been requested (phy id 6, type 0x06 desc a1ead000).
insmod: unexpected EOF
insmod: can not insert '/lib/modules/tx-isp.ko.lzma': invalid module format
[4.034137] name: i2c-gpio0 nr: 0
[4.127077] sensor_read: addr = 0xa value = 0x0
[4.217176] error: sensor_read, 214 ret = -6
[4.221499] sensor_read: addr = 0x300a value = 0x0
[4.226358] err sensor read addr = 0x300a, value = 0x0
[4.317174] error: sensor_read, 214 ret = -6
[4.321497] sensor_read: addr = 0x300b value = 0x0
[4.326357] err sensor read addr = 0x300b, value = 0x0
[4.417067] sensor_read: addr = 0xa value = 0x0
[4.507222] sensor_read: addr = 0x580b value = 0x0
[4.597220] sensor_read: addr = 0x580b value = 0x0
[4.602898] sensor_read: addr = 0x2148 value = 0x0
[4.697240] sensor_read: addr = 0x3107 value = 0x21
[4.787227] sensor_read: addr = 0x3107 value = 0x21
[4.877177] error: sensor_read, 214 ret = -6
[4.881499] sensor_read: addr = 0x3000 value = 0x0
[4.886358] err sensor read addr = 0x3000, value = 0x0
[4.977065] sensor_read: addr = 0xa value = 0x0
[5.067174] error: sensor_read, 214 ret = -6
[5.071497] sensor_read: addr = 0xf0 value = 0x0
[5.076177] err sensor read addr = 0xf0, value = 0x0
[5.167173] error: sensor_read, 214 ret = -6
[5.171495] sensor_read: addr = 0xf0 value = 0x0
[5.176175] err sensor read addr = 0xf0, value = 0x0
[5.267175] error: sensor_read, 214 ret = -6
[5.271497] sensor_read: addr = 0xf0 value = 0x0
[5.276177] err sensor read addr = 0xf0, value = 0x0
[5.367174] error: sensor_read, 214 ret = -6
[5.371496] sensor_read: addr = 0xfc value = 0x0
[5.376176] err sensor read addr = 0xfc, value = 0x0
[5.467174] error: sensor_read, 214 ret = -6
[5.471496] sensor_read: addr = 0x3004 value = 0x0
[5.476356] err sensor read addr = 0x3004, value = 0x0
[5.567175] error: sensor_read, 214 ret = -6
[5.571497] sensor_read: addr = 0x300a value = 0x0
[5.576356] err sensor read addr = 0x300a, value = 0x0
[5.667178] error: sensor_read, 214 ret = -6
[5.671501] sensor_read: addr = 0x301c value = 0x0
[5.676360] err sensor read addr = 0x301c, value = 0x0
[5.767222] sensor_read: addr = 0x3107 value = 0x21
[5.772990] sensor_read: addr = 0x3108 value = 0x35
[5.777957] info: success sensor find: sc2135
[5.782565] name: i2c-gpio1 nr: 1
[5.823903] gio driver init successful!
exec factory_tool.sh .......
ls: /mnt/*-hwcfg.ini: No such file or directory
ls: /mnt/*-VOICE.tgz: No such file or directory
ls: /mnt/*-ptz.cfg: No such file or directory
ls: /mnt/*-hardinfo.bin: No such file or directory
/home/factory_tool.sh: line 77: can not create /mnt/INFO.txt: Read-only file system
umount: can not umount / mnt: Invalid argument
[6.642504] usbcore: registered new interface driver rtl8188fu
ifconfig: SIOCGIFFLAGS: No such device
14: 6B: 9C: CF: 36: 7D

ifconfig: SIOCSIFHWADDR: No such device
ifconfig: SIOCGIFFLAGS: No such device
/system/start.sh: line 108: / tmp / tees: not found
listen on port 3201.
[10.524232] initlializing ptz ...
[ 10.529885]
[10.529885] Parameters of PTZ driver:
[10.535221] test_max_pos = 1
[10.538377] max_pps = 300
[10.541182] pulse interval: 100/300 = 0
[10.545333] xchg_dir = 2
[10.548078] hspd_slfck = 30
[10.551060] vspd_slfck = 30
[10.554041] hspd_normal = 30
[10.557157] vspd_normal = 30
[10.560229] hspd_reloc = 30
[10.563211] vspd_reloc = 10
[10.566191] spd_zoom = 3
[10.568921] hmotor_upbound = 500
[10.572353] vmotor_upbound = 164
[10.575783] zmotor_upbound = 130
[10.579244] no_selfck = 0
[10.582045] other_flags = 32
[10.585122] other_flags:
[10.585122] 0x0001 --- Return to center when power on
[10.585122] 0x0002 --- Z-Motor only
[10.585122] 0x0004 --- No self-check
[10.585122] 0x0008 --- Ignore position
[10.585122] 0x0010 --- Respect spd_slfck
[10.585122] 0x0020 --- No posotion-switch detection
[10.615705] motor pins: 68,69,70,71,49,82,66,67
[10.621055] Ingenic Tx0 gpio ptz device driver [2018.03.12] initialized.
rsyscall_suc
/ P2pcam / p2pcam: can not load library 'libface_inf.so'
umount: can not remount / dev / mtdblock4 read-only
umount: tmpfs busy - remounted read-only
Sent SIGKILL to all processesd
Requesting system reboot
[13.157954] codec_codec_ctl: set CODEC_TURN_OFF ...
[13.162957] codec_codec_ctl: set CODEC_SHUTDOWN ...
[13.167983] Restarting system.
[13.171147] Restarting after 4 ms



Prompt as it flashed through the terminal, my address is different from the one shown here.
Thank .
PS Sorry for the bad rusky :)



Rep: (60)
* vesli12,
first test: RxTx connect the adapter, connect the terminal type. characters must be split in two. if it is not - a problem in the adapter.

* stefp,
card is removed?



Rep: (0)
Log without card if UTB question .Bekap made on the card.



Rep: (72)
stefp @ 17.04.19, 15:53*
/ P2pcam / p2pcam: can not load library 'libface_inf.so'
umount: can not remount / dev / mtdblock4 read-only
umount: tmpfs busy - remounted read-only
Sent SIGKILL to all processesd
Requesting system reboot

problem with one of the last two sections.
If there is a backup of only sew them, like the rest intact.

well, or loaded into a single.

These files (boot.img, kernel.img, root.img, p2pcam.img, system.img) can send a PM?



Rep: (1)
* Proshaaa the adapter is OK tested, connect the camera without a card



Rep: (60)
* vesli12,
then connect the gnd and Rx (to Tx). Tx Adapter Do not connect. so goes infa?



Rep: (72)
* stefp,
You've got a new camera, as of April 2018 are subject to these chambers until they slipped.

I can advise - to boot into single (search by topic).

Here rcS
#! / bin / sh

# Set mdev
echo / sbin / mdev>/ Proc / sys / kernel / hotplug
/ Sbin / mdev -s && echo "mdev is ok ......"

# Create console and null node for nfsroot
600 #mknod -m / dev / console c May 1
666 #mknod -m / dev / null c January 3

# Set Global Environment
export PATH = / bin: / sbin: / usr / bin: / usr / sbin
export PATH = / system / bin: $ PATH
export LD_LIBRARY_PATH = / system / lib

# networking
ifconfig lo up
#ifconfig eth0 192.168.1.80

# Start telnet daemon
telnetd &

# Set the system time from the hardware clock
#hwclock -s

# Mount system partition
mount -t squashfs / dev / mtdblock3 / p2pcam
mount -t jffs2 / dev / mtdblock4 / home

# Format system patition if it is invalid
formatMTD3 ()
{
if [! -f /system/.system]; then
echo "Format system partition ..."
umount -f / home
flash_eraseall / dev / mtd4
mount -t jffs2 / dev / mtdblock4 / home
cd / home
mkdir -p bin init etc / sensor lib / firmware lib / modules
echo "#! / bin / sh">init / app_init.sh
chmod 755 init / app_init.sh
touch .system
cd /
echo "Done"
fi
}
# formatMTD3

##########################################
# Update from TF card
#
getHwInfo ()
{
grep $ 1 /home/hardinfo.bin | awk -F '>'' {print $ 2} '| awk -F '<'' {print $ 1} '
}

mkdir / tmp / mnt
BOARD_ID = $ (getHwInfo BoardType)
if [ "" = "$ BOARD_ID"]; then BOARD_ID = "1004"; fi
sdc_tool -d $ BOARD_ID -c /home/model.ini -i ipc-tx0
rm -fr / tmp / mnt
##########################################


# Run init script
if [-f /system/start.sh]; then
/system/start.sh &
fi

But with this problem - mount -t jffs2 / dev / mtdblock4 / home
Try to see what's alive.



Rep: (0)
The single loaded.
[Root @ (none): ~] # ls
bin home media p2pcam run system var
dev lib mnt proc sbin tmp
etc linuxrc opt root sys usr



But it does not motivate Forums .Where's my fault?

[Root @ (none): ~] # mount -t squashfs / dev / mtdblock3 / p2pcam
mount: mounting / dev / mtdblock3 on / p2pcam failed: No such file or directory
[Root @ (none): ~] # mount -t jffs2 / dev / mtdblock4 / home
mount: mounting / dev / mtdblock4 on / home failed: No such file or directory




Rep: (72)
stefp @ 22.04.19, 10:44*
Where is my mistake?

RcS take the file from the previous post and executes all the commands to mount (you can just copy-paste) and then later montiruesh.
Look mount errors or have the files in / home

Here it is necessary to perform
#! / bin / sh

# Set mdev
echo / sbin / mdev>/ Proc / sys / kernel / hotplug
/ Sbin / mdev -s && echo "mdev is ok ......"

# Create console and null node for nfsroot
600 #mknod -m / dev / console c May 1
666 #mknod -m / dev / null c January 3

# Set Global Environment
export PATH = / bin: / sbin: / usr / bin: / usr / sbin
export PATH = / system / bin: $ PATH
export LD_LIBRARY_PATH = / system / lib

# networking
ifconfig lo up
#ifconfig eth0 192.168.1.80

# Start telnet daemon
telnetd &

# Set the system time from the hardware clock
#hwclock -s

# Mount system partition
mount -t squashfs / dev / mtdblock3 / p2pcam
mount -t jffs2 / dev / mtdblock4 / home



Post has been editedGosudar - 22.04.19, 11:20



Rep: (0)
The command is executed, but something is wrong.
[Root @ (none): ~] # echo / sbin / mdev>/ Proc / sys / kernel / hotplug
- / bin / sh: can not create / proc / sys / kernel / hotplug: nonexistent directory
[Root @ (none): ~] # mknod -m 600 / dev / console c May 1
mknod: / dev / console: Read-only file system
[Root @ (none): ~] # mknod -m 666 / dev / null c 1 March
mknod: / dev / null: Read-only file system
[Root @ (none): ~] # export PATH = / bin: / sbin: / usr / bin: / usr / sbin
[Root @ (none): ~] # export PATH = / system / bin: $ PATH
[Root @ (none): ~] # export LD_LIBRARY_PATH = / system / lib
[Root @ (none): ~] # ifconfig lo up
[Root @ (none): ~] # telnetd &
[Root @ (none): ~] # hwclock -s
- / bin / sh: hwclock: not found
[1] + Done telnetd
[Root @ (none): ~] # mount -t squashfs / dev / mtdblock3 / p2pcam
mount: mounting / dev / mtdblock3 on / p2pcam failed: No such file or directory
[Root @ (none): ~] # mount -t jffs2 / dev / mtdblock4 / home
mount: mounting / dev / mtdblock4 on / home failed: No such file or directory


[Root @ (none): ~] # cd proc
[Root @ (none): proc] # ls
[Root @ (none): proc] #


proc - empty.



Rep: (72)
* stefp,
See your inittab
# / Etc / inittab
#
# Copyright (C) 2001 Erik Andersen<[email protected]>
#
# Note: BusyBox init does not support runlevels. The runlevels field is
# Completely ignored by BusyBox init. If you want runlevels, use
# Sysvinit.
#
# Format for each entry:<id>:<runlevels>:<action>:<process>
#
# Id == tty to run on, or empty for / dev / console
# Runlevels == ignored
# Action == one of sysinit, respawn, askfirst, wait, and once
# Process == program to run

# Startup the system
:: sysinit: / sbin / swapoff -a
:: sysinit: / bin / mount -t tmpfs tmpfs / dev
:: sysinit: / bin / mkdir -p / dev / pts
:: sysinit: / bin / mkdir -p / dev / shm
:: sysinit: / bin / mount -a
:: sysinit: / bin / hostname -F / etc / hostname



Rep: (0)
Nameko error.
If it is not difficult to tell how flashed through the terminal.
Tell me the exact address for sf erase, sf write.

[Root @ (none): ~] # / bin / mount -t tmpfs tmpfs / dev
[Root @ (none): ~] # / bin / mkdir -p / dev / pts
[Root @ (none): ~] # / bin / mkdir -p / dev / shm
[Root @ (none): ~] # / bin / mount -a
[Root @ (none): ~] # / bin / hostname -F / etc / hostname
- / bin / sh: / bin / hostname: not found
[Root @ (none): ~] # echo / sbin / mdev>/ Proc / sys / kernel / hotplug
[Root @ (none): ~] # mknod -m 600 / dev / console c May 1
[Root @ (none): ~] # mknod -m 666 / dev / null c 1 March
[Root @ (none): ~] # export PATH = / bin: / sbin: / usr / bin: / usr / sbin
[Root @ (none): ~] # export PATH = / system / bin: $ PATH
[Root @ (none): ~] # export LD_LIBRARY_PATH = / system / lib
[Root @ (none): ~] # ifconfig lo up
[Root @ (none): ~] # telnetd &
[Root @ (none): ~] # mount -t squashfs / dev / mtdblock3 / p2pcam
mount: mounting / dev / mtdblock3 on / p2pcam failed: No such file or directory
[1] + Done telnetd
[Root @ (none): ~] # mount -t jffs2 / dev / mtdblock4 / home
mount: mounting / dev / mtdblock4 on / home failed: No such file or directory




Rep: (0)
Flashed system, camera alive :)
Short free.



Rep: (1)
Hello!
I flashed a custom web interface from Gosudar to the camera from the message (WiFi IP camera on Ingenic T10 processor (I21AG, HX-I2110T2, HW0036 and others) (Fasting Gosudar # 63287978). Everything works, but now the distorted image, as if the sensor is not properly configured.
How can I return it back, Luggage Sannce I41CB, firmware zabekapil in advance by the method of the cap.
Please tell me how pofiksit?
Thank.

Post has been editedt.tt - 23.04.19, 14:24



Rep: (72)
* stefp,
I am very pleased that the camera worked.
Very strange way: I have this system somehow clumsily mounted. And you can look at what is there?
I understand that it works this
[SERVERINFO]
server_name = arcsoft.com
xmpp_server_ip = xmpp.icloseli.com.
relay_server_ip = relayus-w.arcsoftcloud.com
auto_update_server_ip = update.icloseli.com.
lecam_purchase_server_ip = esd.icloseli.com.
upns_pnserver = upns.icloseli.com.
upns_xmpp_name = arcsoft.com
upns_xmpp_ip = xmpp.icloseli.com.
argus_api_server_ip = argus.icloseli.com.
argus_server_ip = argus.icloseli.com.
relay_server_domain_name = relay.icloseli.com.
stun_server_ip =
cloud_auth_server_name = api.icloseli.com.
bell_server_ip =


* t.tt, Resetting to factory default settings do?

Post has been editedGosudar - 23.04.19, 23:34



Rep: (1)
Fixed. Thank Gosudar.

Planted from the backup into the chamber ftp directories sytem / param / / system / profile / system / www /.

Sensor settings and all the other old + web interface back.



Rep: (0)
Gosudar @ 23.04.19, 18:11*
Very strange way: I have this system somehow clumsily mounted. And you can look at what is there?


And what you are specifically interested in this file does not open and I.
But if you say like that, I'll show you.

Gosudar @ 23.04.19, 18:11*
I understand that it works this


UTB content file - cloud.ini from home folder (system, the same).



Rep: (10)
There are 2 cameras on the sites are already 2 years with firmware Gosudar. sometimes the camera loses p2p and can not reconnect to. reboot helps. you can somehow make the trigger, so that when a long time can not connect to p2p rebutalas and better kill the process of connecting to the cloud and re-run it?


Full version    

Help     rules

Time is now: 25/11/19, 20:42