OpenIPC
/
wiki
mirror of https://github.com/OpenIPC/wiki.git
1
0
Fork 0
Code Activity

Merge remote-tracking branch 'origin/master' 

# Conflicts:
#	ru/index.md
#	ru/participate.md
pull/28/head
Paul Philippov 2022-07-08 06:49:15 -04:00
parent 2d551b7f07 9ddd275f1c
commit 4a1de2325e
55 changed files with 2255 additions and 437 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

674
LICENSE 100644
View File

@ -0,0 +1,674 @@
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Programs
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
state the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <https://www.gnu.org/licenses/>.
Also add information on how to contact you by electronic and paper mail.
If the program does terminal interaction, make it output a short
notice like this when it starts in an interactive mode:
<program> Copyright (C) <year> <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
The hypothetical commands `show w' and `show c' should show the appropriate
parts of the General Public License. Of course, your program's commands
might be different; for a GUI interface, you would use an "about box".
You should also get your employer (if you work as a programmer) or school,
if any, to sign a "copyright disclaimer" for the program, if necessary.
For more information on this, and how to apply and follow the GNU GPL, see
<https://www.gnu.org/licenses/>.
The GNU General Public License does not permit incorporating your program
into proprietary programs. If your program is a subroutine library, you
may consider it more useful to permit linking proprietary applications with
the library. If this is what you want to do, use the GNU Lesser General
Public License instead of this License. But first, please read
<https://www.gnu.org/licenses/why-not-lgpl.html>.

44
README.md
View File

@ -1,44 +0,0 @@
OpenIPC Wiki
============
[English](en/index.md) | [Русский](ru/index.md)
> "Improving the world, one patch at a time."
### This is an open project, so you can help, too.
We try to collect, organize and share as much information regarding different
aspects of the project as we can. But sometimes we overlook things that seem
obvious to us, developers, but are not so obvious to end-users, people who are
less familiar with nuts and bolts behind the scene. That is why we set up this
wiki and let anyone having a GitHub account to make additions and improvements
to the knowledgebase.
### How to contribute.
Sign in into your GitHub account, or [get yourself one][gh-signup] if you don't
have it yet. It's free.
Go to [the wiki repository](https://github.com/openIPC/wiki/) and fork it.
![GitHub Fork](images/gh-fork.png)
Make changes (correct a typo, add another record into a table, or write a new
article) and commit them to your own fork of the repository.
From your repository, create a pull request, so we could review and incorporate
your changes into our version of the wiki.
![GitHub Contribute](images/gh-contribute.png)
### Small corrections, typos.
It is even easier to deal with small corrections while using GitHub. Spotted a
typo? Have an idea of a better wording? Noticed a broken link? Just hit this
pencil-looking button and make corrections.
![GutHub Correction](images/gh-correction.png)
[gh-signup]: https://github.com/signup

1
README.md 120000
View File

@ -0,0 +1 @@
index.md

2
en/acme-v2.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
How to install HTTPS certificates on your camera
------------------------------------------------

45
en/board-manufacturers.md 100644
View File

@ -0,0 +1,45 @@
# OpenIPC Wiki
[Table of Content](../index.md)
## Board manufacturers
* [ACTi](https://www.acti.com/)
* [Anjvision](http://www.anjvision.com/), <http://icamra.cn/>
* [Ansjer](https://www.ansjer.com/)
* [Anviz](http://www.anviz.com/)
* [Brovotech](https://brovotech.com/)
* [Cantonk](http://cantonk.com/)
* [CCDCAM](http://www.ccdcam.com/) th?
* [Filsion/Camasmart](http://www.camasmart.com/)
* [FSAN](http://www.fsan.cn/)
* [GeoVision](https://www.geovision.com.tw/)
* [Haicam](https://haicam.tech)
* [Herospeed](http://www.herospeed.net/en/)
* [Hichip](http://hichip.net/en/)
* [Huatu](http://huatudigital.com/)
* [Huishi](https://web.archive.org/web/20220209053811/http://hscctvcn.com/ProductInfoCategory?categoryId=400431,400432,400433,400434,400435,400436&PageInfoId=0)
* [Hupuu](https://hupuu.com/category/camera-board)
* [IPCAM](http://www.ipcam.xin/)
* [Jovision](http://www.jovision.com/)
* [JVT](http://www.jvt.cc/)
* [LENOTEL](http://www.lenoteltechnology.com/) th?
* [Longse](http://www.longse.com/)
* [Milesight](http://www.milesight.com/)
* [Powerview](http://powerview.cn/en/)
* [Raysharp](http://raysharp.cn/en/)
* [Ruision](http://www.ruision.com/col/70560?lang=en)
* [Safer](http://www.safer.net.cn/) th?
* [Synuwo](http://www.sunywo.com/cn/product/41_0.shtml)
* [Tiandy](http://en.tiandy.com/)
* [Topsee](http://www.en.tpsee.com/product.html)
* [Topper](http://toppervision.com/index2.asp)
* [TVT](http://www.tvt.net.cn/)
* [UNIVIEW](http://uniview.com/)
* [VandSec/Yoosee](http://vandsec.com/) th?
* [VStarcam](http://www.vstarcam.com/) th?
* [Wansview](http://wansview.com/)
* [XM](http://www.xiongmaitech.com/en/)
* [Z-BEN](http://www.z-ben.cn/) th?
* [ZOSI](https://www.zositech.com/)
_th? -- possibly a trading house_

21
en/company-names.md 100644
View File

@ -0,0 +1,21 @@
# OpenIPC Wiki
[Table of Content](../index.md)
## Company names
- Hangzhou Ezviz Software Co., Ltd.
- Shanghai Fullhan Microelectronics Co., Ltd
- Shenzhen Huishi Electronics Co., Ltd.
- Shenzhen Topper Vision, Ltd.
- Shenzhen Gainstrong Technology Co., Ltd.
- Yutong Optical Technology Co.,Ltd.
- Shenzhen Hanvision Technology Co., Ltd.
- Hangzhou Xiongmai Technology Co., Ltd
- Shenzhen Gospell Smarthome Electronic, Ltd.
- Shenzhen Zhangwo Technology Co., Ltd.
- Sunivision Technology Development Co., Ltd.
- Longse Technology Co., Ltd.
- Zhejiang Uniview Technologies Co., Ltd.
- Shenzhen Zhongwei Century Technology Co., Ltd.
- Shenzhen Hichip Vision Technology Co., Ltd.
- Chengdu Powerview Science and Technology Co., Ltd.

40
en/contribute.md 100644
View File

@ -0,0 +1,40 @@
# OpenIPC Wiki
[Table of Content](../index.md)
> "Improving the world, one patch at a time."
### This is an open project, so you can help, too.
We try to collect, organize and share as much information regarding different
aspects of the project as we can. But sometimes we overlook things that seem
obvious to us, developers, but are not so obvious to end-users, people who are
less familiar with nuts and bolts behind the scene. That is why we set up this
wiki and let anyone having a GitHub account to make additions and improvements
to the knowledgebase.
### How to contribute.
Sign in into your GitHub account, or [get yourself one][gh-signup] if you don't
have it yet. It's free.
Go to [the wiki repository](https://github.com/openIPC/wiki/) and fork it.
![GitHub Fork](../images/gh-fork.png)
Make changes (correct a typo, add another record into a table, or write a new
article) and commit them to your own fork of the repository.
From your repository, create a pull request, so we could review and incorporate
your changes into our version of the wiki.
![GitHub Contribute](../images/gh-contribute.png)
### Small corrections, typos.
It is even easier to deal with small corrections while using GitHub. Spotted a
typo? Have an idea of a better wording? Noticed a broken link? Just hit this
pencil-looking button and make corrections.
![GutHub Correction](../images/gh-correction.png)
[gh-signup]: https://github.com/signup

2
en/dev-ffmpeg-usage.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
FFMPEG, RTSP and SRT examples
-----------------------------

2
en/dev-nfs-boot.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Boot device with NFS
--------------------

2
en/dev-tricks.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Interesting tricks
------------------

2
en/developers.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
OpenIPC Developers
------------------

79
en/device-chacon-ipcam-ri01.md
View File

@ -4,27 +4,27 @@
[Product datasheet](https://chacon.com/datasharing/doc/IPCAM-RI01/ipcam-ri01_user_manual.pdf)
This camera is a rebrand of a manufacturing company identified by "PPStrong".
This camera is a rebranding of a manufacturing company identified by "PPStrong".
I'm sure there are other cameras out there that are using the same hardware (or similar with minor changes).
## Hardware
| System | Description |
|--------|-------------------|
| SoC | HI3518EV300 |
| Sensor | JXF23 |
| System | Description |
|--------|--------------------------------------|
| SoC | HI3518EV300 |
| Sensor | JXF23 |
| Flash | 16Mb (XM25QH128A) or 8Mb (XM25QH64A) |
| WiFi | RTL8188FU |
| WiFi | RTL8188FU |
#### OpenIPC status
| Component | Status |
|-----------|--------|
| WiFi | [Working](https://github.com/OpenIPC/firmware/issues/48) |
| Motors | [Working](#motor-driver) (patched driver) |
| Red/Blue leds | [Working](#leds) |
| IR Led | Working |
| IR Cut | Working |
| Component | Status |
|---------------|----------------------------------------------------------|
| WiFi | [Working](https://github.com/OpenIPC/firmware/issues/48) |
| Motors | [Working](#motor-driver) (patched driver) |
| Red/Blue LEDs | [Working](#leds) |
| IR LED | Working |
| IR Cut | Working |
#### Hardware details
@ -34,7 +34,7 @@ The camera mainboard is identified by "SPEED5S-H1MB_F23".
![device_chacon_ipcam-ri01_board_top](https://user-images.githubusercontent.com/1659543/149513254-d326f57f-902b-4c58-98e6-73bfe7fa33d2.jpg)
At the top of the mainboard:
- a micro sdcard slot on the right
- connector labeled "IR" powers the IR led, a red led and a blue led
- connector labeled "IR" powers the IR LED, a red LED and a blue LED
- connector "ICR" powers the IR cut filter
- non-identified connector is an input for the microphone
- SPI NOR flash chip (QH128A)
@ -83,24 +83,24 @@ At the bottom of the mainboard:
### GPIOs
| nr | Description |
|-----|-------------|
| 0x0f (15) | irCut_1 |
| 0x0c (12) | irCut_2 |
| 0x28 (40) | IR Led |
| 0x33 (51) | Red Led |
| 0x32 (50) | Blue Led |
| 0x0d (13) | wlan power |
| 0x00 (0) | AcShdn |
| 0x09 (9) | Reset button |
| nr | Description |
|-----------|---------------|
| 0x0f (15) | irCut_1 |
| 0x0c (12) | irCut_2 |
| 0x28 (40) | IR LED |
| 0x33 (51) | Red LED |
| 0x32 (50) | Blue LED |
| 0x0d (13) | wlan power |
| 0x00 (0) | AcShdn |
| 0x09 (9) | Reset button |
| 0x3b (59) | Tilt motor A1 |
| 0x3a (58) | Tilt motor A2 |
| 0x39 (57) | Tilt motor B1 |
| 0x38 (56) | Tilt motor B2 |
| 0x47 (71) | Pan motor A1 |
| 0x45 (69) | Pan motor A2 |
| 0x46 (70) | Pan motor B1 |
| 0x44 (68) | Pan motor B2 |
| 0x47 (71) | Pan motor A1 |
| 0x45 (69) | Pan motor A2 |
| 0x46 (70) | Pan motor B1 |
| 0x44 (68) | Pan motor B2 |
### Mods
#### USB Serial port
@ -121,7 +121,7 @@ If you find it hard to solder the wires on the camera micro usb connector get a
The camera uBoot is password protected with "pps_password".
### Creating a backup
To backup the original firmware you need a usb serial adapter connected to the board and a sdcard.
To back up the original firmware you need a USB serial adapter connected to the board and a sdcard.
Find out your flash chip size:
```
@ -131,7 +131,7 @@ D:0x20 0x70 0x17
Name:"XM25QH64AHIG"
```
uBoot commands to backup the entire flash memory on the sdcard (**all sdcard contents will be lost**).
uBoot commands to back up the entire flash memory on the sdcard (**all sdcard contents will be lost**).
Depending on your camera flash memory size replace \<size1\>/\<size2\> with:
- 0x800000/0x4000 for 8M flash
- 0x1000000/0x8000 for a 16Mb flash
@ -160,7 +160,7 @@ pps #
This will write the entire flash to the mmc card in "raw mode" (no filesystem).
**WARNING**: if you leave the card inserted in the camera and it boots the original FW, the card will be formated and the backup lost!
**WARNING**: if you leave the card inserted in the camera, and it boots the original FW, the card will be formated and the backup lost!
Then to save the dump to a file, insert the card in a system running linux and:
```
@ -429,7 +429,7 @@ Content-Length: 129
}
```
In the latest FW they have removed the "telnetd" binary so you need to place it on the sdcard:
In the latest FW they have removed the "telnetd" binary, so you need to place it on the sdcard:
[telnetd.zip](https://github.com/ljalves/wiki/files/7875319/telnetd.zip)
@ -775,23 +775,22 @@ nightMode:
```
### LEDs
The camera has a dual color led (red/blue) connected to gpio's 50 and 51.
To control those leds you can use the /sys api:
The camera has a dual color LED (red/blue) connected to GPIO's 50 and 51.
To control those LEDs you can use the /sys api:
```
# make the gpios accessible
# make the GPIOs accessible
echo 50 > /sys/class/gpio/export
# and set direction (only need to do once)
echo out > /sys/class/gpio50/direction
echo out > /sys/class/gpio51/direction
# turn on blue led
# turn on blue LED
echo 1 > /sys/class/gpio50/value
# turn off blue led
# turn off blue LED
echo 0 > /sys/class/gpio50/value
# turn on red led
# turn on red LED
echo 1 > /sys/class/gpio51/value
# turn off red led
# turn off red LED
echo 0 > /sys/class/gpio51/value
```

2
en/example-ipctool.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Run ipctool
-----------

20
en/gpio-settings.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
GPIO Settings
-------------
@ -22,10 +22,13 @@ GPIO Settings
| Hi3516Cv100 | | | | |
| Hi3516Cv200 | | | | |
| Hi3516Cv300 | | | | |
| Hi3516Ev100 | | | | |
| Hi3516Ev200 | | | | 9i |
| Hi3516Ev300 | 10 | 11 | | 7i |
| Hi3518Ev200 | 1 | 2 | 48 | |
| Hi3518Ev300 | | | | |
| | | | | |
| T31 | 57 | 58 | | |
_i - inverted value_
@ -35,11 +38,11 @@ _i - inverted value_
|-------------|--------|--------|----------|-------|--------|---------|---------|
| Gk7205v200 | 12 | 13 | | 4 | 15 | 14 | |
| | | | | | | | |
| Hi3516Cv100 |
| Hi3516Cv100 | 18 | 19 |
| Hi3516Cv200 |
| Hi3516Cv300 |
| Hi3518Ev200 | 64 | 65 |
| Hi3516Ev200 |
| Hi3516Ev200 | 12 | 13 | | 4 |
| Hi3516Av300 | 5 | 6 |
### Jabsco boards
@ -83,10 +86,11 @@ _i - inverted value_
| GK7205V200 | 8 | 9 | 15 | 16 | 4, 53 | 55 | 14 | 12 | 0 | |
| GK7205V300 | 10 | 11 | 66 | 52 | 4 | | 30 | 31 | | |
| | | | | | | | | | | |
| Hi3516Cv100 | | | | | | | | | | |
| Hi3516Cv100 | 38 | 39 | 24 | | 49 | 26 | | | | |
| Hi3516Dv100* | 14 | 15 | | | | | | | | |
| Hi3516Cv200 | | | | | | | | | | |
| Hi3516Cv300 | 53 | 54 | 64 | 66 | 55 | 1 | | | 2 | 63 |
| Hi3516Ev100 | 53 | 24 | | | | | | | | |
| Hi3516Ev200 | 8 | 9 | 15 | 16 | 4, 53 | 55 | 14 | 12 | 0 | |
| Hi3516Ev300 | 10 | 11 | 66 | 52 | 4, 67 | 65 | 30 | 31 | 0 | |
| Hi3518Ev200 | 33 | 34 | | | 61 | 35 | | | | |
@ -98,3 +102,11 @@ _i - inverted value_
| Processor | IRCUT1 | IRCUT2 | IRLED | DEVICE ID |
|-------------|--------|--------|-------|--------------------------|
| Hi3516Ev300 | 40 | 41 | 65 | unknown |
### Jovision boards
| Processor | IRCUT1 | IRCUT2 | LIGHT | TESTED BOARDS |
|-------------|--------|--------|-------|-----------------|
| Hi3516Ev200 | 53 | 52 | 4 | |
| Hi3516Cv100 | 42 | 43 | 6 | IPG5020A-H-V1.0 |

49
en/guide-supported-devices.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Supported devices
-----------------
@ -44,8 +44,55 @@ _If you have another supported device to add, please do it [here][2]._
| | | | | | | | | |
| Xiaomi | MJSXJ02HL | HI3518EV300 | | | No | | | Yes |
| | | | | | | | | |
| XM | BLK18EV-0062-0035 | HI3518EV200 | JXH62 | | Yes | | | Yes |
| | | | | | | | | |
| Zenotech | HI3516D_MB_V13_RA | HI3516DV100 | OV9689 | GD25Q128CSIG | Yes | No | | No |
| Processor | Sensor | Vendor | SKU | Board identification |
|-------------|------------------|------------|--------------|---------------------------------|
| Hi3516Cv100 | IMX222_spi_dc | XM | | [BLK18C-0222-38X38_S-V1.03][1] |
| Hi3516Cv100 | OV2710_i2c_dc | Jovision | | IPG5020A-H-V1.0 |
| | | | | |
| Hi3516Cv200 | IMX323_i2c_dc | XM | | BLK16CV-0323-38X38-V1.01 |
| Hi3516Cv200 | IMX323_i2c_dc | JVT | S323H16VF | IPS323-H16V-38X38-V2 |
| Hi3516Cv200 | IMX323_i2c_mipi | XM | | |
| | | | | |
| Hi3516Cv300 | AR0237_i2c_dc | XM | | BLK16CV3-0237P-38X38-S-V1.01 |
| Hi3516Cv300 | IMX307_i2c_lvds | Raysharp | | RS-CM-188D 2018-03-16 E150111 |
| Hi3516Cv300 | IMX323_i2c_dc | Longse/HS | | HI3516CV300-IMX323-POE-TF V1.1 |
| Hi3516Cv300 | IMX323_i2c_dc | Sunywo | ZB6323 | IPG5020A-T-N6-V0.1 |
| Hi3516Cv300 | IMX323_i2c_dc | XM | | IVG-HP201Y-AE |
| Hi3516Cv300 | IMX291_i2c_lvds | XM | | IVG-HP203Y-AE |
| Hi3516Cv300 | IMX323_spi_dc | JVT | S323H16XF | IPS323-H16X-38X38-V2/V3 |
| Hi3516Cv300 | JXF22_i2c_dc | XM | | BLK16CV3-0022-38X38-S-V1.01 |
| | | | | |
| Hi3516Ev100 | IMX323_i2c_dc | XM | | BLK16E-0323-38X38-B-V1.01 |
| Hi3516Ev100 | SC2235P_i2c_dc | XM | 80HE20PS-S | BLK16E-0235-38X38-S-V2.03 |
| | | | | |
| Hi3516Ev200 | IMX307_i2c_mipi | XM | | IVG-85HF20PY-S |
| Hi3516Ev200 | SC4239P_i2c_mipi | XM | | IVG-85HF30PS-S |
| | | | | |
| Hi3516Ev300 | IMX335_i2c_mipi | XM | | IVG-85HG50PYA-S |
| | | | | |
| Hi3518Ev100 | OV9712_i2c_dc | CamHi/Xin | | IPC18E_9712_V2.0/V3.1 |
| | | | | |
| Hi3518Ev200 | AR0130_i2c_dc | XM | | BLK18EV-0732-0035-38X38-V1.01 |
| Hi3518Ev200 | JXF22_i2c_dc | XM | | BLK18EV-0002-2035-38X38-V1.01 |
| Hi3518Ev200 | JXF22_i2c_dc | XM | | BLK18EV-0022-0130-38X38-V1.01 |
| Hi3518Ev200 | OV2735_i2c_dc | Dahua | DH-IPC-C22P | E305654 JX02 94V-0 |
| Hi3518Ev200 | OV9732_ | XM | | BLK18EV-0732-0035-38X38-V1.01 |
| Hi3518Ev200 | OV9732_i2c_dc | Longse/HS | LS-IP100/40 | 3518EV200-OV9732-V1.0 |
| Hi3518Ev200 | OV9732_i2c_dc | Rostelecom | QVC-IPC-136W | E305654 JX02 94V-0 |
| Hi3518Ev200 | SC2135_i2c_dc | XM | | BLK18EV-0035-0042-38X38_S-V1.01 |
| Hi3518Ev200 | SC2235_i2c_dc | XM | | BLK18EV-0235-38X38-B-V1.01 |
| | | | | |
| | | | | |
| SSC335 | SC3335 | Uniview | | Uniview |
[1]: https://github.com/OpenIPC/firmware#current-development-status-
[2]: https://github.com/OpenIPC/wiki/blob/master/en/guide-supported-devices.md
[3]: https://github.com/OpenIPC/wiki/blob/master/en/device-chacon-ipcam-ri01.md

157
en/help-uboot.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Help: U-boot
------------
@ -20,3 +20,158 @@ __OpenIPC Linux:__
root@openipc-hi3518ev100:~# fw_setenv uk 'mw.b 0x82000000 ff 1000000; tftp 0x82000000 uImage.${soc}; sf probe 0; sf erase 0x50000 0x200000; sf write 0x82000000 0x50000 ${filesize}'
root@openipc-hi3518ev100:~#
```
### Saving original firmware without using tftp.
In the terminal program you use connect to UART port with, enable saving a log
file of the session. I like to use `screen` for that, and my command to connect
to the UART adapter with logging of the active session into a file would look
like this:
```
$ screen -L -Logfile fulldump.log /dev/ttyUSB0 115200
```
After connecting to the bootloader console, run a set of commands for reading
whole amount of data from flash memory chip into RAM, and then dumping it as
hexadecimal values into terminal window.
Use hexadecimal notation for addresses, where 0 is 0x0, 8 MB is 8x00000, and
16 MB is 0x1000000.
For reading whole 8 MB flash memory run
```
mw.b 0x82000000 ff 0x800000
sf probe 0
sf read 0x82000000 0x0 0x800000
md.b 0x82000000 0x800000
```
and for 16 MB flash memory run
```
mw.b 0x82000000 ff 0x1000000
sf probe 0
sf read 0x82000000 0x0 0x1000000
md.b 0x82000000 0x1000000
```
Since the process of reading is going to take a considerable amount of time
(literally hours), you might want to disconnect from the terminal session to
avoid accidental keystrokes contaminating the output. Press `Ctrl-a` followed
by `d` to detach the session from active terminal. Run `screen -r` when you
need to reconnect it later, after the size of the log file will stop growing.
Reading of an 8 MB flash memory should result in a ~40 MB log file, and for a
16 MB chip the file should be twice that size.
Convert the hex dump into a binary firmware file and use it for further research
or restoring camera to its pristine state.
```
xxd -r fulldump.log > fulldump.bin
```
Use [binwalk](https://github.com/ReFirmLabs/binwalk) to unpack the binary file.
#### Saving firmware via SD card.
Sometimes your camera only has a wireless connection, which does not work
directly from the bootloader. Very often such cameras have a microSD card slot.
In this case you can try to save a copy of the original firmware using an
SD card as an intermediary medium.
Since you're going to save firmware in its binary form, the amount of data will
be either 8 MB or 16 MB, depending on the size of camera's flash memory chip.
So any SD card will do, even the smallest one.
Insert the card into the card slot on the camera, connect the serial adapter to
the UART port, supply power to the camera and stop the boot process to get into
the bootloader console.
Initialize access to the card, and clear some space to save firmware on.
Data is written onto card in blocks of 512 bytes. You need to erase 16384 blocks
to clear 8 MB, 32768 blocks for 16 MB, which are 0x4000 and 0x8000 hexadecimal,
respectively.
Note that we are going to write directly to the card registers, bypassing the
partition table. To avoid conflicts when accessing card data later from your PC,
offset 8 kilobytes from the beginning of the card (8 * 1024 = 8192 bytes or 16
blocks of 512 bytes, or 0x10 blocks in hexadecimal representation).
```
mmc dev 0
mmc erase 0x10 0x8000
```
Now you need to copy the contents of the firmware from the flash memory chip to
the RAM of the camera. To do that, clear a section of RAM (0x800000 bytes for a
8MB chip or 0x1000000 bytes for a 16MB chip), read the flash memory and copy
the entire contents to the prepared space in RAM. Then export the copied data
from RAM to the card.
NB! In the example below we use the starting address 0x2000000, but it varies
for different cameras. Please consult SoC data sheet, or seek help on
[our Telegram channel][telegram].
```
mw.b 0x2000000 ff 0x1000000
sf probe 0
sf read 0x2000000 0x0 0x1000000
mmc write 0x2000000 0x10 0x8000
```
Remove the card from the camera and insert it into a computer running Linux.
Use `dd` command to copy data from the card to a binary file on the computer.
```
dd bs=512 skip=16 count=32768 if=/dev/sdc of=./fulldump.bin
```
### Uploading binary image via serial connection.
There are cameras that only have wireless connection unavailable directly from
bootloader. Most of such cameras also have SD card slot but some don't, or it does
not work for some reason, or you don't have a card, or something. Anyway, you still
can upload a binary image onto camera and either run it, or save it into the flash
memory. Here's how.
First of all, you'll need to install `lrzsz` package on your desktop computer.
I presume it runs Linux and preferrably of a Debian family, that'll be easier on
examples. So, run this command to satisfy prerequisites:
```
apt install lrzsz
```
Now you are ready.
Place the binary file you are going to upload into the same directory where you will
be starting a `screen` session to your camera from. Start the session and boot into
the bootloader console interrupting booting routine with a key combo.
Now you can run `help` and check what data transfer protocols are supported by your
version of bootloader. If you see `loady` in the list of commands, then you can use
ymodem protocol. Run `loady` on you camera, then press `Ctrl-a` followed by `:`
(semi-colon). It will switch you into command line at the very bottom of the screen.
Enter `exec !! sz --ymodem filename.bin` where _filename.bin_ and see your file
uploading via serial connection. At 115200 bps. Slow, very slow.
After the file is uploaded, you can do the usual magic. Either boot from the memory
image right away using `bootm`, or write it into the flash memory.
### Bypassing password-protected bootloader.
Changing the bootloader is a risky operation. There's a high probability of
turning your camera into a paperweight if something goes wrong. So before you
flash a new bootloader you have to weigh up all the risks and benefits. In most
cases the original bootloader plus new kernel and new operating system should
work just fine. But there are exceptions.
Today, we see more and more cameras where access to bootloader console is
protected with a password. Thus, even if you connect to the camera's UART port,
all you will see after interrupting the standard boot cycle is a prompt for
password. In that case, a relatively safe solution is to downgrade the firmware
to a version where the password protection was not yet implemented. For example,
for Xiongmai cameras the bootloader password protection started popping up
somewhere around July 2021, hence you need a firmware for your camera from an
earlier date. After you successfully downgrade your camera to a password-free
bootloader, you could install the OpenIPC firmware in a regular way.

12
en/help-webui.md
View File

@ -1,13 +1,13 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Help: Web UI
------------
### Updating Web UI from Web UI
In some cases, especially if you think something does not work as it should, try
to update Web UI once again, overriding version checking for the second update.
This may be required because we've made some changes to the updating routine,
thus you need to update the routine code with the first update, and then to use
the updated code during the second round of updating.
In some cases, especially if you think that something does not work as it should,
try to update Web UI once more, overriding version checking for the second update.
This may be required because of some changes we have possibly made to the updating
routine, thus you shall retrieve the updating routine code with the first update,
and then use it for the consecutive update.

2
en/image-quality-tuning.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Overview
--------

71
en/index.md
View File

@ -1,71 +0,0 @@
# OpenIPC Wiki
[Table of Content](index.md)
## Introduction
- [About the project](menu-index.md)
- [Supported devices](guide-supported-devices.md)
- [Changelog](show-changelog.md)
## Subprojects
- [coupler](https://openipc.org/coupler)
- [firmware](https://openipc.org/firmware)
- [ipctool](https://openipc.org/ipctool)
- [telemetry](https://openipc.org/telemetry)
- [Firmware Partitions Calculation](https://themactep.com/tools/firmware-partitions-calculation)
## Installation
- [Installation on Goke based boards](install-goke.md)
- [Installation on HiSilicon based boards](install-hisi.md)
- [Installation on Novatek based boards](install-novatek.md)
- [Installation on SigmaStar based boards](install-ssc335.md)
- [Installation on XM510 based boards](install-xm510.md)
- [Installation on XM530 based boards](install-xm530.md)
- [Very old full manual](old-manual.md)
## Usage
- [System features](system-features.md)
- [Majestic streamer](majestic-streamer.md)
- [Microbe web interface](microbe-web.md)
- [Upgrade firmware](sysupgrade.md)
- [Image quality tuning](image-quality-tuning.md)
- [Memory tuning](memory-tuning.md)
- [Using ipctool](example-ipctool.md)
- [GPIO settings](gpio-settings.md)
- [ACMEv2](acme-v2.md)
- [YouTube streaming](youtube-streaming.md)
- [WiFi XM530](wifi-xm530.md)
## Firmware
- [Releases in GitHub](https://github.com/OpenIPC/firmware/releases/tag/latest)
- [Releases in Telegram](https://t.me/s/openipc_dev)
- [Source code](source-code.md)
## Development
- [Interesting tricks](dev-tricks.md)
- [Boot device with NFS](dev-nfs-boot.md)
- [FFMPEG usage](dev-ffmpeg-usage.md)
- [Kernel configuration for adding new platforms](integration-kernel.md)
## Help, Tips, and Tricks
- [U-boot](help-uboot.md)
- [Web UI](help-webui.md)
## Contacts
- [Bug reports](https://github.com/OpenIPC/firmware/issues)
## Our resources
- [OpenIPC](https://openipc.org/)
- [OpenCollective](https://opencollective.com/openipc)
- [Twitter](https://twitter.com/OpenIPC)
- [Telegram](https://t.me/openipc)
## Roadmap
- [ToDo](todo-all.md)
- [Developers](developers.md)
- [Notes from old sources](notes-for-resorting.md)
## Resources for recycling and integration
- <https://github.com/OpenIPC/camerasrnd>
- <https://openwrt.org/docs/techref/hardware/soc/soc.hisilicon.hi35xx>
[logo]: ../images/logo_openipc.png

2
en/install-goke.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For XM boards with SoC GK7202V300, GK7205V200, GK7205V300 ONLY!!!
-----------------------------------------------------------------

38
en/install-hisi.md
View File

@ -1,9 +1,12 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For XM boards with Hi35{16Ev200,16Ev300,18Ev300} SoC ONLY!!!
------------------------------------------------------------
Other boards may have different memory layout like HI3518Ev200
uses 0x82000000 instead 0x42000000
### Supported sensors
Please look up your sensor in [the list of supported devices][1].
@ -65,3 +68,36 @@ reset
```
[1]: guide-supported-devices.md
### Uboot without tftp command
```
setenv uk 'mw.b 0x42000000 ff 1000000; setenv bootfile uImage.${soc} && tftpboot && sf probe 0; sf erase 0x50000 0x200000; sf write 0x40080000 0x50000 ${filesize}'
setenv ur 'mw.b 0x42000000 ff 1000000; setenv bootfile rootfs.squashfs.${soc} && tftpboot && sf probe 0; sf erase 0x250000 0x500000; sf write 0x40080000 0x250000 ${filesize}'
```
### backup device
```
setenv ipaddr 192.168.1.10
setenv serverip 192.168.1.254 # Your TFTP server IP address.
sf read 0x42000000 0x0 0x800000
tftpput 0x42000000 0x800000 backup.img
```
### restore device
if something goes wrong uboot can be bricked!
```
setenv bootfile backup.img
tftpboot
sf probe 0
sf erase 0x0000 0x800000
sf write 0x40080000 0x0 ${filesize}
reset
```

2
en/install-novatek.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For XM vendor boards with NT98562 and NT98566 SoC ONLY!!!
---------------------------------------------------------

2
en/install-ssc335.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For Anjoy/Brovotech/Gospell/Uniview boards with SSC335 Soc ONLY!!!
------------------------------------------------------------------

2
en/install-xm510.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For XM vendor boards with XM510 SoC ONLY!!!
-------------------------------------------

33
en/install-xm530.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
For XM vendor boards with XM530/XM550 SoC ONLY !!!
--------------------------------------------------
@ -38,4 +38,33 @@ run uk; run ur; reset
After you have finished flashing new firmware, please run `firstboot` command
to format jffs2 partition used to store settings.
### Known issues
### Known issues
### Uboot with out tftp command
```
setenv uk1 'mw.b 0x81000000 ff 1000000; setenv bootfile uImage.${soc}; tftpboot'
setenv uk2 'sf probe 0; sf erase 0x50000 0x200000; sf write 0x81000000 0x50000 ${filesize}'
setenv uk 'run uk1 ; run uk2'
setenv ur1 'mw.b 0x81000000 ff 1000000; setenv bootfile rootfs.squashfs.${soc}; tftpboot'
setenv ur2 'sf probe 0; sf erase 0x250000 0x500000; sf write 0x81000000 0x250000 ${filesize}'
setenv ur 'run ur1 ; run ur2'
saveenv
run uk; run ur; reset
```
### Backup device (no tftpput)
open the serial console with a logfile
Note: dumping via Serial takes long
```
sf probe 0
sf read 0x81000000 0x0 0x800000
md.b 0x81000000 0x800000
```
use `cut -b 11-57 | xxd -r -p` to reconstruct the binary from `md.b` output

542
en/installation.md 100644
View File

@ -0,0 +1,542 @@
# OpenIPC Wiki
[Table of Content](../index.md)
OpenIPC firmware installation, step by step.
------------------------------
### Step 1. Determine the CPU chip
![SoC Marking](../images/soc-hisilicon.jpg)
_Hisilicon Hi3518EV100 SoC marking. Relevant symbols highlighted with yellow._
### Step 2. Download the firmware.
Go to <https://github.com/OpenIPC/firmware> and find your SoC in the table of
supported hardware. Make sure there is a downloadable binary file for that SoC.
If you are lucky and there is a pre-compiled firmware file for your processor --
download it onto your PC.
### Step 3. Install and set up a TFTP server.
TFTP stands for _Trivial File Transfer Protocol_. As the name implies, it is a
very simple protocol intended for transferring files over a local computer
network. TFTP does not support authentication. Its code is so tiny and simple
that TFTP-clients are widely used in thin-clients and embedded systems for
retrieving bootable images from a designated boot server on the local network.
#### If you have Linux...
...then it's easy. Pre-compiled and ready-to-use binary package for your distro
most likely already exists in distro's repo, and you only need to install it and
set it up.
```
sudo apt install tftpd-hpa
sudo sed -i '/^TFTP_OPTIONS/s/"$/ --create"/' /etc/default/tftpd-hpa
sudo systemctl restart tftpd-hpa.service
```
Now you've got your own TFTP server serving files from `/srv/tftp` directory.
Extract files from the bundle you downloaded in step two into that directly.
```
sudo tar -C /srv/tftp/ -xvf openipc.*.tgz
```
### Step 4. Connect to UART port of your camera.
In order to make a connection to UART port you will need a
[serial port adapter][FTDI] for your PC.
__Before you connect that adapter to you camera, make sure that it's working
voltage is set to 3.3 volt!__
Sometimes, you only need to flip a jumper to achieve that. But in some cases you
might need to solder a wire, a zero Ohm resistor, or make a connection between
two contacts with a blob of solder. Some adapters support only 5 volt. In that
case, you will need an additional [logic level converter][TLLC] connected
between the adapter and UART port on your camera.
One of the contact pads you will need to connect you adapter to is GND (ground).
It is easy to discover using a multimeter in continuity mode. Put one of the
leads onto a well-known exposed ground pads. Usually, these are large open
copper contact areas around mounting screw holes, USB port housing, SD card slot
metallic walls. Use another lead to slightly touch control pads until you see or
hear a notification from your multimeter that the circuit is closed. That means,
you found the ground. Now, you need to find two more: `RX` and `TX`, both used
for receiving and transmitting data, respectively. Start with `TX`. It transmits
series of characters and quite easy to spot.
Be aware that you are looking for a contact with 3.3v potential between it and
the ground. Test possible connection points with a multimeter and mark those
showing 3.3 volt. This way you won't have to test everything, and you save
yourself from hitting say a 12 volt connector intended for infrared LED array
or whatnot.
Connect `GND` pin on your camera to `GND` pad of the adapter, connect USB
connector of the adapter to a USB port on your PC, start a terminal emulator
application and connect to your adapter. Use connection speed of 115200 bps,
no flow control, no parity bit.
Then, connect `RX` pin on the adapter to a possible `TX` contact of UART port
on your camera. Power the camera with its standard power adapter. If you had a
lucky guess then you'll start seeing booting log in your terminal window. In
some cases, if you see garbled text on you screen instead of booting kernel,
you might need to change the connection speed to 57600 bps and try again.
If your screen remains blank, try another UART contact, and then another, until
you hit the proper one.
After you found the `TX` pad, connect it to `RX` pin on your adapter. Yes, it is
a cross-connection. Whatever transmits goes into a receiver and vice-versa. Now,
put a heavy object -- a railroad nut, an antique tin solder, a shot of vodka
(full) -- on any letter key of your computer keyboard and start connect
remaining `TX` pin of your adapter to different pads on the camera until you see
it backfeeding to the terminal. As it happens, you have successfully completed
a UART connection to you camera. Now you may drink the vodka.
NB! Usually, there is a fourth contact on a UART connector marked `VCC`. It is
used for powering camera during initial programming by manufacturer. We strongly
advise not to power your camera though that pin, but use the OEM power connector
for this purpose.
### Step 5. Get access to the bootloader.
Reboot the camera and try to interrupt its boot sequence in order to access
bootloader console by pressing a key combination on your computer keyboard,
between the time the bootloader starts and before Linux kernel kicks in.
Key combinations differ from vendor to vendor but, in most cases, it is
`Ctrl-C`, less commonly -- `Enter`, `Esc` or just any key. Carefully read text
appearing on screen while booting, you might see a hint there. Some cameras
require more exotic combinations not revealed in booting logs. You may try to
look them up on the internet, or ask on [our Telegram channel][telegram].
Chances are, we have already dealt with such a camera and know the combo.
If you succeeded and got a command prompt then congrats, you've got access to
your camera's bootloader.
From this point on, we strongly advise you to keep a record of everything you do.
Enable session logging in your terminal. Even better, create a text file on your
computer and write down all commands you run and how system responses to them.
### Step 6. Save the original firmware.
After you get access to the bootloader console, run `help` to get a list of
available commands. Check if you have `tftp` among them. If you do, then saving
the original firmware should be a breeze. You only need to set up access to your
TFTP server from step 3.
NB! If your bootloader does not have `tftp`, you can still make a copy of the
original firmware. [Read here for more](help-uboot.md).
Check the system environment using `printenv` command. Look for `ipaddr`,
`netmask`, `gatewayip` and `serverip` parameters. The first three set IP address,
netmask of your camera, and the IP address of the network gateway for accessing
local network. The fourth parameter is an IP address of your TFTP server. Assign
the values by `setenv` command (use IP addresses and netmask corresponding to
your local network), then save the new values into environment with `saveenv`
command.
```
setenv ipaddr 192.168.1.253
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
saveenv
```
Most IP cameras nowadays are equipped with 8 or 16 MB NOR or NAND flash memory.
You can check the type and size of the chip installed on of your camera in the
bootloader log output. You'll see something like this:
```
U-Boot 2010.06-svn (Oct 21 2016 - 11:21:29)
Check Flash Memory Controller v100 ... Found
SPI Nor(cs 0) ID: 0xс2 0x20 0x18
spi_general_qe_enable(294): Error: Disable Quad failed! reg: 0x2
Block:64KB Chip:16MB Name:"MX25L128XX"
SPI Nor total size: 16MB
```
To dump the original firmware, you need to save the contents of camera's flash
memory to a file. For that, you must first load the contents into RAM. Here's
how you do that. Initialize the Flash memory. Clean a region of RAM of 0x1000000
bytes long starting from address 0x82000000*. Read contents of the Flash from
address 0x0 0x1000000 bytes long and place it into the prepared region or RAM.
Now, you only have to export it to a file on the TFTP server.
```
sf probe 0
mw.b 0x82000000 ff 0x1000000
sf read 0x82000000 0x0 0x1000000
tftp 0x82000000 firmware-full.bin 0x1000000
```
NB! Please note, that the starting address and length will be different for
different cameras with different Flash memory chips. Consult data sheets or
seek help on [our Telegram channel][telegram].
### Step 7. Install OpenIPC firmware.
#### Part one.
No two camera models are alike. Different camera models consist of different
sets of components. The most important of them, the central processor and the
image sensor, directly affect the image quality and the range of functions
inherent in a particular camera. Unlike desktop computer CPU, camera's processor
handles so many functions that it got a specific name -- System-on-Chip or SoC,
for short.
But even seemingly less significant components can set limitations on the camera
and its firmware capabilities. For example, different cameras may have different
flash memory chips installed. Some cameras may have 8MB of flash memory, while
others may have 16MB or more. More flash memory can fit more software code and
allow the camera to run additional services that are not available on cameras
with less flash memory. So we decided to build two versions of our firmware:
the basic version (_Lite_) for cameras with 8 MB of flash memory and the
advanced version (_Ultimate_) with additional features for cameras with 16 MB
flash memory.
As said before, firmware installation routine differs for different cameras.
There are different memory addresses and different environment parameters,
so before proceeding, determine what kind of SoC is in your camera, what sensor,
what flash memory chip and what amount of memory is has.
Below we describe the procedure for installing the OpenIPC Lite firmware on a
camera with 8 MB of flash memory, as an example. Even if your camera has larger
flash memory, do not skip this text. Read it carefully to understand the
principle and the sequence of operations. We will provide specific commands
for different cameras in the second part of this section.
##### Preparation.
So, we have a guinea pig, a camera with hi3518ev100 SoC, equipped with a OV9712
sensor and 64 MB of RAM.
Connect to the camera via the UART port and access the bootloader console.
Set the component parameters to the appropriate environment variables:
```
setenv soc hi3518ev100
setenv sensor ov9712
setenv totalmem 64M
```
Set environment variables for loading the Linux kernel and the root file system
of the new firmware:
```
setenv osmem 32M
setenv bootargs 'mem=${osmem:-32M} console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=hi_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'setenv setargs setenv bootargs ${bootargs}; run setargs; sf probe 0; sf read 0x82000000 0x50000 0x200000; bootm 0x82000000'
```
Set environment variables for the camera to access local network, where
`ethaddr` is the original camera MAC address, `ipaddr` is camera's IP address
on the network, `gatewayip` is the IP address of a router to access the network,
`netmask` is the subnet mask, and `serverip` is am IP address of the TFTP server
from step 3.
```
setenv ethaddr 00:12:16:00:00:00
setenv ipaddr 192.168.1.10
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
```
Save updated values to flash memory.
```
saveenv
```
##### Installation.
First, clear the memory region at address 0x82000000, 0x1000000 bytes long, by
writing 0xff to it. Then retrieve kernel file for the camera from the TFTP
server and place it into memory starting with address 0x82000000.
The `$soc` variable in the name of the requested file is substituted with its
value from the environment variables created earlier. In this example, the file
named `uImage.hi3518ev100` will be requested from the server.
```
mw.b 0x82000000 ff 1000000
tftp 0x82000000 uImage.${soc}
```
NB! Pay attention to the messages on the terminal screen! If any of the commands
throws an error, find out what went wrong. Maybe you made a typo? In any case,
do not continue the procedure until all previous commands succeed. Otherwise,
you might end up with a bricked camera!
So, you've made sure that the file is downloaded and placed in the camera's RAM.
Now you need to write it down to the flash memory. To do that, you need to get
access to the flash memory, then clean erase the region from address 0x50000
that is 0x200000 bytes long, and copy the contents of camera's RAM from address
0x82000000 and the size of the kernel file to the flash memory starting at
address 0x50000.
```
sf probe 0
sf erase 0x50000 0x200000
sf write 0x82000000 0x50000 ${filesize}
```
Next, you need to repeat the process for the root file system, saving it to the
next region starting from address 0x250000 of 0x500000 bytes long.
NB! 0x500000 bytes is a hexadecimal equivalent of 5242880 bytes in decimal
system, and equals 5120 kilobytes, exactly what we have prepared for rootfs
in `bootargs` parameter.
It is easy to memorize the sequence if you give it a little thought:
clean RAM, download file there, unlock flash chip, wipe the target region in
flash memory, write file from memory into there.
```
mw.b 0x82000000 ff 1000000
tftp 0x82000000 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x82000000 0x250000 ${filesize}
```
After both partitions have been successfully written to the flash memory and all
necessary changes have been made to the bootloader to prepare it for starting
the new firmware, it is time to reboot the camera. To do that, type this command
in the console:
```
reset
```
#### Part two.
If you have read the first part of this section (if not - go read it), then you
already know what manipulations and why you need to do to install the OpenIPC
firmware. And all you need are the commands suitable for your particular camera.
Below are samples of such commands for cameras equipped with [Goke](#goke),
[HiSilicon](#hisilicon), [SigmaStar/MStar](#sigmastarmstar), [XM](#xm) SoCs.
##### Goke
SoC: gk7202v300, gk7205v200, gk7205v300
```
setenv soc <processor> # gk7202v300, gk7205v200, or gk7205v300.
setenv sensor <sensor> #
setenv totalmem <memory> # 64M for gk7202v300, gk7205v200, 128M for gk7205v300.
setenv osmem 32M
setenv bootargs 'mem=${osmem:-32M} console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'setenv setargs setenv bootargs ${bootargs}; run setargs; sf probe 0; sf read 0x42000000 0x50000 0x200000; bootm 0x42000000'
setenv ethaddr 00:00:00:00:00:00
setenv ipaddr 192.168.1.10
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
saveenv
mw.b 0x42000000 ff 1000000
tftp 0x42000000 uImage.${soc}
sf probe 0
sf erase 0x50000 0x200000
sf write 0x42000000 0x50000 ${filesize}
mw.b 0x42000000 ff 1000000
tftp 0x42000000 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x42000000 0x250000 ${filesize}
reset
```
##### HiSilicon
SoC: hi3516ev200, hi3516ev300, hi3518ev300.
```
setenv soc <processor> # hi3516ev200, hi3516ev300, or hi3518ev300.
setenv sensor <sensor> #
setenv totalmem <memory> # 64M for hi3516ev200, hi3518ev300, 128M for hi3516ev300.
setenv osmem 32M
setenv bootargs 'mem=${osmem:-32M} console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=hi_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'setenv setargs setenv bootargs ${bootargs}; run setargs; sf probe 0; sf read 0x42000000 0x50000 0x200000; bootm 0x42000000'
setenv ethaddr 00:00:00:00:00:00
setenv ipaddr 192.168.1.10
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
saveenv
mw.b 0x42000000 ff 1000000
tftp 0x42000000 uImage.${soc}
sf probe 0
sf erase 0x50000 0x200000
sf write 0x42000000 0x50000 ${filesize}
mw.b 0x42000000 ff 1000000
tftp 0x42000000 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x42000000 0x250000 ${filesize}
reset
```
##### SigmaStar/MStar
SoC: ssc325, ssc335, ssc337.
```
setenv soc <processor> # ssc325, ssc335, or ssc337.
setenv sensor <sensor> # gc2053, imx307, or sc3335.
setenv totalmem 64M
setenv osmem 32M
setenv bootargs 'mem=${osmem:-32M} console=ttyS0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init LX_MEM=0x3fe0000 mma_heap=mma_heap_name0,miu=0,sz=0x1C00000 mma_memblock_remove=1 mtdparts=NOR_FLASH:256k(boot),64k(tech),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'setenv setargs setenv bootargs ${bootargs}; run setargs; sf probe 0; sf read 0x21000000 0x50000 0x200000; bootm 0x21000000'
setenv ethaddr 00:00:00:00:00:00
setenv ipaddr 192.168.1.10
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
saveenv
mw.b 0x21000000 ff 1000000
tftpboot 0x21000000 uImage.${soc}
sf probe 0
sf erase 0x50000 0x200000
sf write 0x21000000 0x50000 ${filesize}
mw.b 0x21000000 ff 1000000
tftpboot 0x21000000 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x21000000 0x250000 ${filesize}
reset
```
##### XM
SoC: xm510, xm530, xm550.
```
setenv soc <processor> # xm510 for xm510, xm530 for both xm530 and xm550.
setenv sensor <sensor> #
setenv totalmem <memory> # 32M for xm510, 64M for xm530, 128M for xm550.
setenv osmem <osmemory> # 18M for xm510, 35M for xm530, 64M for xm550.
setenv bootargs 'mem=35M console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=xm_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'sf probe 0; sf read 0x80007fc0 0x50000 0x200000; bootm 0x80007fc0'
setenv ethaddr 00:00:00:00:00:00
setenv ipaddr 192.168.1.10
setenv netmask 255.255.255.0
setenv gatewayip 192.168.1.1
setenv serverip 192.168.1.254
saveenv
mw.b 0x80007fc0 ff 1000000
tftp 0x80007fc0 uImage.${soc}
sf probe 0
sf erase 0x50000 0x200000
sf write 0x80007fc0 0x50000 ${filesize}
mw.b 0x80007fc0 ff 1000000
tftp 0x80007fc0 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x80007fc0 0x250000 ${filesize}
reset
```
### Step 8. First boot.
If all previous steps are done correctly, your camera should start with the new
firmware. Welcome to OpenIPC!
After the first boot with the new firmware you need to clean the overlay
partition. Run this in your terminal window:
```
firstboot
```
### Step aside.
To facilitate subsequent firmware upgrades directly from the bootloader console,
create two macros with sequences of commands needed to boot from the TFTP server
and write kernel and root file system for your camera model into flash memory.
We will use `uk` and `ur` for macro names, which can be decoded as `update kernel`
and `update rootfs`. Easy to remember.
As you remember, in the example above we used the following commands to install the kernel:
```
mw.b 0x42000000 ff 1000000
tftp 0x42000000 uImage.${soc}
sf probe 0
sf erase 0x50000 0x200000
sf write 0x42000000 0x50000 ${filesize}
```
To create the `uk` macro, join all the above commands into one line, alternating
them with semicolons. For added protection against writing invalid data to flash
memory in case file downloading from TFTP server fails, replace semicolon before
`sf probe 0` with logical AND operator (`&&`). It will make macro to abort if
file fails to download.
```
fw_setenv uk 'mw.b 0x42000000 ff 1000000; tftp 0x42000000 uImage.${soc} && sf probe 0; sf erase 0x50000 0x200000; sf write 0x42000000 0x50000 ${filesize}'
```
Do the same with the root file system commands:
```
mw.b 0x82000000 ff 1000000
tftp 0x82000000 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x82000000 0x250000 ${filesize}
```
saving result as `ur` macro:
```
fw_setenv ur 'mw.b 0x42000000 ff 1000000; tftp 0x42000000 rootfs.squashfs.${soc} && sf probe 0; sf erase 0x250000 0x500000; sf write 0x42000000 0x250000 ${filesize}'
```
Naturally, to create your own macro, you should use the commands suitable for
your specific camera, not mindlessly copying the above lines, but using them as
an example and understanding the actions to be taken.
NB! Although these commands create a macro to run in the bootloader console,
they must be executed inside Linux environment. This way we avoid the
restrictions on the number of arguments in the `setenv` command existing in
some older versions of the bootloader.
You will now be able to flash both kernel and root file system followed by
rebooting the camera directly from the bootloader console. It's as easy as that!
```
run uk; run ur; reset
```
[logo]: ../images/logo_openipc.png
[FTDI]: https://www.google.com/search?q=ftdi+usb+ttl
[TLLC]: https://google.com/search?q=logic+level+converter+3.3v+5v
[telegram]: https://t.me/OpenIPC

23
en/integration-kernel.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Additional requirements for kernel configuration
------------------------------------------------
@ -7,15 +7,28 @@ Additional requirements for kernel configuration
```
CONFIG_BLK_DEV=y
CONFIG_BLK_DEV_LOOP=y
```
```
CONFIG_IP_MULTICAST=y
```
```
CONFIG_IP_PNP=y
CONFIG_IP_PNP_DHCP=y
CONFIG_ROOT_NFS=y
```
## Patch file requirements
- Patch file name should follow format `<number>-<description>.patch`.
- Patch file should not contain any reference to package version in its name.
- The `<number>` part of patch's file name refers to the application order
starting from 1. It is preferred to left-pad the number with zeros up to total
of four digits, like `git-format-patch` does. _0001-foobar-the-buz.patch_
- Patch file should contain a commentary in its header, explaining what this
patch does, and why it is needed.
- Add a _Signed-off-by_ statement in the header of each patch file to help
tracking changes and certify that the patch is released under the same license
as the software it modifies.

6
en/majestic-streamer.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Majestic Streamer
-----------------
@ -36,7 +36,7 @@ With firmware running, you can access the camera using URLs below
and others are image width and height.
* http://192.168.1.10/image.heif - image snapshot in [HEIF][heif] format,
use `stream` parameter to specify channel (the same approach as for RTSP channels)
* http://192.168.1.10/image.yuv - image snapshot in [YUV420][yuv] format.
* http://192.168.1.10/image.yuv420 - image snapshot in [YUV420][yuv] format.
* http://192.168.1.10/image.dng - [raw image][raw] snapshot from the sensor in
[Adobe DNG][dng] format (only for v>=2 HiSilicon processors).
@ -50,7 +50,7 @@ convert -verbose -sampling-factor 4:2:0 -size 1920x1080 -depth 8 image.yuv image
where `1920x1080` is the picture resolution of video0, and `.png` is the target
image format.
### Audio input
### Audio
* http://192.168.1.10/audio.opus - [Opus][opus] audio stream.
* http://192.168.1.10/audio.m4a - [AAC][aac] audio stream.

2
en/memory-tuning.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
HiSilicon boards
----------------

2
en/menu-footer.md
View File

@ -1,2 +1,2 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)

11
en/menu-index.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
## Basic information
@ -107,16 +107,13 @@ You can help us to write a better documentation, proofread and correct our websi
You can just donate some money to cover the cost of development and long-term maintaining of what we believe
is going to be the most stable, flexible, and open IP Network Camera Framework for users like yourself.
You can make a financial contribution to the project
at [Open Collective](https://opencollective.com/openipc/contribute/backer-14335/checkout),
or via [PayPal](https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS),
or via [YooMoney](https://openipc.org/donation/yoomoney.html).
You can make a financial contribution to the project at [Open Collective](https://opencollective.com/openipc/contribute/backer-14335/checkout).
Thank you.
<p style="text-align:center">
<a href="https://opencollective.com/openipc/contribute/backer-14335/checkout" target="_blank"><img src="https://opencollective.com/webpack/donate/button@2x.png?color=blue" width="375" alt="Open Collective donate button"></a>
<a href="https://www.paypal.com/donate/?hosted_button_id=C6F7UJLA58MBS"><img src="https://www.paypalobjects.com/en_US/IT/i/btn/btn_donateCC_LG.gif" alt="PayPal donate button"></a>
<a href="https://openipc.org/donation/yoomoney.html"><img src="https://yoomoney.ru/transfer/balance-informer/balance?id=596194605&key=291C29A811B500D7" width="140" alt="YooMoney donate button"></a>
</p>
[burn]: https://github.com/OpenIPC/burn

16
en/microbe-web.md
View File

@ -1,7 +1,19 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Microbe web interface
---------------------
Default login/password: admin/12345
Web Interface is available on port 85 as _http://camera-ip:85_.
Default login and password are _admin_ and _12345_, respectively.
### Updating the web interface from the web interface
In some cases, especially if it seems that something is not working, you might
need to re-install the web interface update by checking the "Install even if
matches the existing version." checkbox.
Double updating of the web interface can be necessary if we've made some changes
to the code of updating procedure per se. In such case, the first update routine
will install the modified code, and the second round will be performed using
that updated code.

113
en/notes-for-resorting.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Installation: how to make OpenIPC running on certain hardware
-------------------------------------------------------------
@ -16,7 +16,8 @@ Here are some examples:
## How to upgrade OpenIPC
Currently full automatic system upgrade like [sysupgrade](https://github.com/openwrt/openwrt/blob/master/package/base-files/files/sbin/sysupgrade) in OpenWRT is not supported. Use partial manual update instead.
Currently, full automatic system upgrade like [sysupgrade][openwrtsysupgrade]
in OpenWRT is not supported. Use partial manual update instead.
### Partial manual update
@ -28,15 +29,20 @@ The process is described on the main site on [firmware page](https://openipc.org
* Can OpenIPC be installed on Raspberry Pi or other hardware?
No. Currently only HiSilicon HI35xx SoC are supported. But theoretically it is possible to support other architectures and boards. Though it will require a lot of efforts and thus it is not a near time focus of the project.
No. Currently, only HiSilicon HI35xx SoC are supported. But theoretically it is
possible to support other architectures and boards. Though it will require a lot
of efforts, and thus it is not a near time focus of the project.
* Can I flash OpenIPC image without using UART console and TFTP?
No. Currently it is not possible, though we are working on this.
No. Currently, it is not possible, though we are working on this.
* What the difference between OpenIPC based on BuildRoot and based on OpenWRT?
Buildroot is faster for initial development for new platforms as it is minimalistic and has no dependencies. OpenWRT is convenient for users as a final product, but there are a lot of complexities, dependencies, and there is no point in developing without a community.
Buildroot is faster for initial development for new platforms as it is
minimalistic and has no dependencies. OpenWRT is convenient for users as a final
product, but there are a lot of complexities, dependencies, and there is no
point in developing without a community.
### Other FAQs
@ -45,7 +51,7 @@ Buildroot is faster for initial development for new platforms as it is minimalis
## Network related stuff
Common network configuration can be done in Luci GUI:
Common network configuration can be done in Luci GUI:
`http://<your camera IP>`
@ -57,32 +63,34 @@ There are two branches of OpenIPC currently:
### OpenWRT based
GUI is based on Luci. There are menu sections for camera specific setup.
GUI is based on Luci. There are menu sections for camera specific setup.
### Buildroot based
Tere is a different interface planned... Still under development.
There is a different interface planned... Still under development.
## Hardware related recommendations
### Power Over Internet PoE
It is advised to use 48V power adapters with RJ-45 connectors instead of 12V. With 12V adapters the current will be 4 times higher. High current can burn RJ-45 connectors and wires.
It is advised to use 48V power adapters with RJ-45 connectors instead of 12V.
With 12V adapters the current will be 4 times higher. High current can burn
RJ-45 connectors and wires.
## How to stream video to Internet
* [[MiniHttp]] ➤ main audio/video streamer of the OpenIPC based system
* __MiniHttp__ ➤ main audio/video streamer of the OpenIPC based system.
* [[Мajestic]] ➤ new (in development) audio/video streamer of the OpenIPC based system
* __Мajestic__ ➤ new (in development) audio/video streamer of the OpenIPC based system.
* [[YouTube Sreaming]]
* __YouTube Streaming__
#### MiniHttp is the main streamer of the OpenIPC based system
It is important to tune configuration of MiniHttp by turning off unneeded protocols and features for better security and performance.
It is important to tune configuration of MiniHttp by turning off unneeded
protocols and features for better security and performance.
Config file is located in
`/etc/minihttp.ini`
Config file is located in `/etc/minihttp.ini`
#### Debug mode:
@ -97,17 +105,19 @@ Config file is located in
[Tools repository](https://github.com/OpenIPC/packages/tree/main/utils)
[ipctool](https://github.com/OpenIPC/ipctool) - gets information about hardware and outputs it in common format. Can also be used to make backup and restore of the camera software (still experimental feature).
[ipctool](https://github.com/OpenIPC/ipctool) - gets information about hardware
and outputs it in common format. Can also be used to make backup and restore of
the camera software (still experimental feature).
## Integration examples with Digital Video Recording systems
[[Recording stream locally]] with various utilities.
Recording stream locally with various utilities.
[[YouTube as DVR]] hack
YouTube as DVR hack.
## Tips and trick on monitoring OpenIPC system
## Tips and tricks on monitoring OpenIPC system
### How to get temperature from chip's internal sensor (not all devices supported):
### How to get temperature from chip's internal sensor (where supported):
`ipctool --temp`
@ -120,33 +130,35 @@ other commands to [[monitor temperature]]
[[prometheus-node]]
### Monitoring templates
* [[Zabbix monitoring templates]]
## Prometheus node configuration
[Prometheus](https://prometheus.io/) is an open-source systems monitoring and alerting toolkit.
[Prometheus](https://prometheus.io/) is an open-source systems monitoring and
alerting toolkit.
OpenIPC has prometheus node exporter as a package. The result output can be viewed as a plaintext:
http://192.168.1.10:9100/metrics
OpenIPC has prometheus node exporter as a package. The result output can be
viewed as plain text on http://192.168.1.10:9100/metrics
Or visualized if you install [proemetheus server and graphana](https://prometheus.io/docs/visualization/grafana/):
[[images/preometheus_node_graphana_example.jpg]]
You can configure the node here
`/etc/config/prometheus-node-exporter-lua`
You can configure the node in `/etc/config/prometheus-node-exporter-lua`.
### Meta package
https://github.com/ZigFisher/Glutinium/tree/master/prometheus-node-exporter-lua
<https://github.com/ZigFisher/Glutinium/tree/master/prometheus-node-exporter-lua>
## Experiments with I2C on Hi3518EV200
### Setting up i2c-x via device tree
The standard i2c-hisilicon driver does not give an option to set pins to i2c mode if they were previously set to dts. To automatically set the required pins to i2c mode you just need to add the following code to the beginning of hi_i2c_hw_init (linux/drivers/i2c/busses/i2c-hisilicon.c)
The standard i2c-hisilicon driver does not give an option to set pins to i2c
mode if they were previously set to dts. To automatically set the required pins
to i2c mode you just need to add the following code to the beginning of
hi_i2c_hw_init (linux/drivers/i2c/busses/i2c-hisilicon.c)
```
#ifdef CONFIG_ARCH_HI3518EV200 // Might be the same for other hardware devices
@ -173,7 +185,7 @@ if(pinfo->mem->start = 0x20250000 /* address i2c-2 */) {
### [[DevTools]]
### [[Docs on different IP cameras]]
### [[Docs on different IP cameras]]
### Groups in Telegram related to development:
@ -182,7 +194,9 @@ if(pinfo->mem->start = 0x20250000 /* address i2c-2 */) {
## Tools used in Research and Development
[hisi-trace](https://github.com/OpenIPC/hisi-trace) --> tool to run Sofia inside the OpenIPC. Allows porting stock Sofia functions to the target system without loading in the original firmware.
[hisi-trace](https://github.com/OpenIPC/hisi-trace) --> tool to run Sofia inside
the OpenIPC. Allows porting stock Sofia functions to the target system without
loading in the original firmware.
[some tools for dissassembling](https://github.com/TekuConcept/ArmElfDisassembler)
@ -192,7 +206,7 @@ if(pinfo->mem->start = 0x20250000 /* address i2c-2 */) {
Different hack & mod related to IP Cameras forums:
https://www.goprawn.com/
<https://www.goprawn.com/>
Below are some examples how to record video streams with various utilities.
@ -230,7 +244,7 @@ Password: xmhdipc
Welcome to HiLinux.
```
Also can try [other pairs](https://gist.github.com/gabonator/74cdd6ab4f733ff047356198c781f27d)
Also, can try [other pairs](https://gist.github.com/gabonator/74cdd6ab4f733ff047356198c781f27d)
### Optional: enable Linux kernel verbose boot (where armbenv exists)
@ -245,6 +259,7 @@ Or in case where XmEnv exists:
# XmEnv -s xmuart 0
# reboot
```
### Enable telnet without even open your camera (remotely)
* Find proper zip with recent firmware update using [link](https://translate.google.com/translate?hl=en&sl=ru&tl=en&u=https%3A%2F%2Fwww.cctvsp.ru%2Farticles%2Fobnovlenie-proshivok-dlya-ip-kamer-ot-xiong-mai) and download it.
@ -263,9 +278,10 @@ Or in case where XmEnv exists:
* Run `./add_xmaurt.sh` and then ensure that `u-boot.env.img` has
`xmuart=1telnetctrl=1` near the end of file.
* Repack `bin` file adding changed `u-boot.env.img` there like this: `zip -u General_IPC_HI3516EV200_85H30AI_S38.Nat.dss.OnvifS.HIK_V5.00.R02.20200507_all.bin u-boot.env.img`
* Repack `bin` file adding changed `u-boot.env.img` there like this:
`zip -u General_IPC_HI3516EV200_85H30AI_S38.Nat.dss.OnvifS.HIK_V5.00.R02.20200507_all.bin u-boot.env.img`
* Upgrade camera using new `bin` file
* Upgrade camera using new `bin` file.
Document origin is [here](https://github.com/OpenIPC/camerasrnd/blob/master/get_telnet.md)
@ -323,42 +339,43 @@ fi
## Direct streaming to YouTube
YouTube offers not only LiveStreming but also can record this stream.
YouTube offers not only LiveStreaming but also can record this stream.
Up to 12 hours of LiveStream can be recorded.
Up to 12 hours of LiveStream can be recorded.
Direct streaming to YouTube is possible but not currently supported by OpenIPC.
### Direct streaming can be done with MiniHttp
Direct streaming to YouTube could be done with the help of RTMP but there are currently no plans add this protocol to the main streamer MiniHttp.
Direct streaming to YouTube could be done with the help of RTMP but there are
currently no plans add this protocol to the main streamer MiniHttp.
### Direct streaming can be done with FFMPEG
There are two modes available: "old one", H264 over RTMP an a "new one", H265 over HLS.
There are two modes available: the old one, supporting H264 over RTMP,
and the new one, with H265 over HLS.
Both methods were not tested in production and still in development mode. See following links for details:
Both methods were not tested in production and still are in development mode.
See following links for details:
### H264 over RTMP
Navigate to the compiled package [H264 over RTMP](https://github.com/ZigFisher/Glutinium/tree/master/hi35xx-ffmpeg/files)
Copy file **silence.aac** to /usr/lib/
and file **ffmpeg** to /usr/sbin/
Copy file `silence.aac` to `/usr/lib/` and file `ffmpeg` to `/usr/sbin/`
Also set execution permission:
`chmod +x /usr/sbin/ffmpeg`
Run ffmpeg with the following parameters:
ffmpeg -stream_loop -1 -i /usr/lib/silence.aac -rtsp_transport udp -thread_queue_size 64 -i rtsp://127.0.0.1:554/stream=0 -c
:v copy -c:a copy -f flv rtmp://a.rtmp.youtube.com/live2/<your key>
Run `ffmpeg` with the following parameters:
`ffmpeg -stream_loop -1 -i /usr/lib/silence.aac -rtsp_transport udp -thread_queue_size 64 -i rtsp://127.0.0.1:554/stream=0 -c:v copy -c:a copy -f flv rtmp://a.rtmp.youtube.com/live2/<your key>`
[H265 over HLS](https://gist.github.com/widgetii/ec275524dd621cd55774c952bee4c622)
Some build instructions:
https://github.com/ZigFisher/Glutinium/blob/master/hi35xx-ffmpeg/0_Build.sh
<https://github.com/ZigFisher/Glutinium/blob/master/hi35xx-ffmpeg/0_Build.sh>
[openwrtsysupgrade]: https://github.com/openwrt/openwrt/blob/master/package/base-files/files/sbin/sysupgrade

85
en/old-manual.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Introduction
------------
@ -19,7 +19,7 @@ This page describes OpenWRT-based firmware variant.
* Run arbitrary command from u-boot ENV (linux_cmd=)
* Simple L2/L3 VPN with traffic shaping and compression (vtun)
* Simply sender Telegram bot (estgb)
* Low cost 3G USB modems support in hilink and ppp modes
* Low cost 3G/4G USB modems support in hilink mode
* µVPN tunnel service
* and more ...
@ -33,48 +33,6 @@ unable to deliver.
The list is constantly updated, please visit often and/or follow our Telegram
groups for new release notifications.
#### OpenIPC 1.0 (OpenWRT based)
| Processor | Sensor | Vendor | SKU | Board | Status |
|-------------|-----------------|------------|--------------|---------------------------------|--------|
| Hi3516Cv100 | IMX222_spi_dc | XM | | [BLK18C-0222-38X38_S-V1.03][1] | test |
| Hi3518Ev100 | OV9712_i2c_dc | CamHi/Xin | | IPC18E_9712_V2.0/V3.1 | test |
| | | | | | |
| Hi3516Cv200 | IMX323_i2c_dc | XM | | BLK16CV-0323-38X38-V1.01 | yes |
| Hi3516Cv200 | IMX323_i2c_dc | JVT | S323H16VF | IPS323-H16V-38X38-V2 | yes |
| Hi3516Cv200 | IMX323_i2c_mipi | XM | | | ? |
| Hi3518Ev200 | AR0130_i2c_dc | XM | | BLK18EV-0732-0035-38X38-V1.01 | yes |
| Hi3518Ev200 | JXF22_i2c_dc | XM | | BLK18EV-0002-2035-38X38-V1.01 | yes |
| Hi3518Ev200 | JXF22_i2c_dc | XM | | BLK18EV-0022-0130-38X38-V1.01 | yes |
| Hi3518Ev200 | OV2735_i2c_dc | Dahua | DH-IPC-C22P | E305654 JX02 94V-0 | wip |
| Hi3518Ev200 | OV9732_ | XM | | BLK18EV-0732-0035-38X38-V1.01 | yes |
| Hi3518Ev200 | OV9732_i2c_dc | Longse/HS | LS-IP100/40 | 3518EV200-OV9732-V1.0 | yes |
| Hi3518Ev200 | OV9732_i2c_dc | Rostelecom | QVC-IPC-136W | E305654 JX02 94V-0 | wip |
| Hi3518Ev200 | SC2135_i2c_dc | XM | | BLK18EV-0035-0042-38X38_S-V1.01 | yes |
| Hi3518Ev200 | SC2235_i2c_dc | XM | | BLK18EV-0235-38X38-B-V1.01 | yes |
| | | | | | |
| Hi3516Cv300 | AR0237_i2c_dc | XM | | BLK16CV3-0237P-38X38-S-V1.01 | yes |
| Hi3516Cv300 | IMX307_i2c_lvds | Raysharp | | RS-CM-188D 2018-03-16 E150111 | yes |
| Hi3516Cv300 | IMX323_i2c_dc | Longse/HS | | HI3516CV300-IMX323-POE-TF V1.1 | yes |
| Hi3516Cv300 | IMX323_i2c_dc | Sunywo | ZB6323 | IPG5020A-T-N6-V0.1 | yes |
| Hi3516Cv300 | IMX323_i2c_dc | XM | | [IVG-HP201Y-AE][2] | yes |
| Hi3516Cv300 | IMX291_i2c_lvds | XM | | [IVG-HP203Y-AE][3] | yes |
| Hi3516Cv300 | IMX323_spi_dc | JVT | S323H16XF | IPS323-H16X-38X38-V2/V3 | yes |
| Hi3516Cv300 | JXF22_i2c_dc | XM | | BLK16CV3-0022-38X38-S-V1.01 | yes |
| Hi3516Ev100 | IMX323_i2c_dc | XM | | BLK16E-0323-38X38-B-V1.01 | yes |
| Hi3516Ev100 | SC2235P_i2c_dc | XM | 80HE20PS-S | BLK16E-0235-38X38-S-V2.03 | yes |
#### OpenIPC 2.1 (Buildroot based)
| Processor | Sensor | Vendor | SKU | Board | Status |
|-------------|------------------|--------|-----|----------------------|--------|
| Hi3516Ev200 | IMX307_i2c_mipi | XM | | [IVG-85HF20PY-S][4] | yes |
| Hi3516Ev200 | SC4239P_i2c_mipi | XM | | [IVG-85HF30PS-S][5] | yes |
| Hi3516Ev300 | IMX335_i2c_mipi | XM | | [IVG-85HG50PYA-S][6] | yes |
| SSC335 | SC3335 | | | [Uniview][7] | yes |
More information about sensors: [https://cctvsp.ru][8] (translated from Russian
with Google Translate).
@ -627,7 +585,7 @@ reboot
### Recover backup firmware
If something goes horribly wrong and you want back your backed up firmware
If something goes horribly wrong, and you want your backed up firmware back
**Restore backup up firmware via serial**
@ -687,43 +645,6 @@ sf write 0x82000000 0x0 ${filesize}
To be written...
### Vendors
* [ACTi](https://www.acti.com/)
* [Anjvision](http://www.anjvision.com/), <http://icamra.cn/>
* [Ansjer](https://www.ansjer.com/)
* [Anviz](http://www.anviz.com/)
* [Brovotech](https://brovotech.com/)
* [Cantonk](http://cantonk.com/)
* [CCDCAM](http://www.ccdcam.com/) th?
* [Filsion/Camasmart](http://www.camasmart.com/)
* [FSAN](http://www.fsan.cn/)
* [GeoVision](https://www.geovision.com.tw/)
* [Herospeed](http://www.herospeed.net/en/)
* [Huatu](http://huatudigital.com/)
* [IPCAM](http://www.ipcam.xin/)
* [Jovision](http://www.jovision.com/)
* [JVT](http://www.jvt.cc/)
* [LENOTEL](http://www.lenoteltechnology.com/) th?
* [Longse](http://www.longse.com/)
* [Milesight](http://www.milesight.com/)
* [Raysharp](http://raysharp.cn/en/)
* [Ruision](http://www.ruision.com/?lang=en)
* [Safer](http://www.safer.net.cn/) th?
* [Synuwo](http://www.sunywo.com/)
* [Tiandy](http://en.tiandy.com/)
* [Topsee](http://www.en.tpsee.com/)
* [TVT](http://www.tvt.net.cn/)
* [UNIVIEW](http://uniview.com/)
* [VandSec/Yoosee](http://vandsec.com/) th?
* [VStarcam](http://www.vstarcam.com/) th?
* [Wansview](http://wansview.com/)
* [XM](http://www.xiongmaitech.com/en/)
* [Z-BEN](http://www.z-ben.cn/) th?
* [ZOSI](https://www.zositech.com/)
_th? -- possibly a trading house_
[1]: https://aliexpress.com/item/32493067946.html
[2]: https://aliexpress.com/item/32851596596.html
[3]: https://aliexpress.com/item/1005002315913099.html

2
en/show-changelog.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Changelog
---------

6
en/source-code.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Source code
-----------
@ -14,7 +14,7 @@ Install some packages to system and clone OpenIPC repo
```
sudo apt-get update -y
sudo apt-get install -y bc build-essential git unzip
sudo apt-get install -y bc build-essential git tcl unzip
git clone --depth=1 https://github.com/OpenIPC/firmware.git
cd firmware
```
@ -48,7 +48,7 @@ make BOARD=unknown_unknown_xm530_openipc all
## Statistical data
Software might do product usage data collection including SoC and sensor model name to gather statistics used in QA process..
Software might do product usage data collection including SoC and sensor model name to gather statistics used in QA process.
We guaranty that the data is fully anonymized, and does not contain anything that can arguably be considered data about an individual, that could be considered end-user data; or that could be sensitive or confidential to users.

2
en/system-features.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
System features
---------------

2
en/sysupgrade.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Upgrading firmware
------------------

2
en/todo-all.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
ToDo
----

6
en/wifi-xm530.md
View File

@ -1,8 +1,8 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
WiFi for XM530 based devices
----------------------------
Wi-Fi for XM530 based devices
-----------------------------
Save this script as `/usr/sbin/wifi`

6
en/youtube-streaming.md
View File

@ -1,11 +1,11 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Table of Content](../index.md)
Configuration requirements
--------------------------
To prevent accidental stream termination on temporary connection drops
schedule live streaming with a start date in the far future (e.g. December 31st
schedule live-streaming with a start date in the far future (e.g. December 31st
of the current year). It will work smoothly when you go live, disconnect the
camera and then continue streaming.
@ -37,7 +37,7 @@ for more information.
deselect 'API Key' option, then press 'Execute' button below.
- Authorize yourself using your YouTube connected account.
- Make sure that you got 200 response otherwise check errors and repeat.
Trivial error is when [live streaming](https://support.google.com/youtube/answer/2474026?hl=en)
Trivial error is when [live-streaming](https://support.google.com/youtube/answer/2474026?hl=en)
was not previously enabled in your account.
- Save "channelId" from the response (it looks like "UCPJRjbxYlq6h2cCqy8RCRjg").

113
index.md 100644
View File

@ -0,0 +1,113 @@
OpenIPC Wiki
============
> "Improving the world, one patch at a time."
## Table of Content
### Introduction
- [About the project](en/menu-index.md)
- [Supported devices](en/guide-supported-devices.md)
- [Changelog](en/show-changelog.md)
### Subprojects
- [coupler](https://openipc.org/coupler)
- [firmware](https://openipc.org/firmware)
- [ipctool](https://openipc.org/ipctool)
- [telemetry](https://openipc.org/telemetry)
- [Firmware Partitions Calculation](https://themactep.com/tools/firmware-partitions-calculation)
### Installation
- [Installation, step by step](en/installation.md)
- [Installation on Goke based boards](en/install-goke.md)
- [Installation on HiSilicon based boards](en/install-hisi.md)
- [Installation on Novatek based boards](en/install-novatek.md)
- [Installation on SigmaStar based boards](en/install-ssc335.md)
- [Installation on XM510 based boards](en/install-xm510.md)
- [Installation on XM530 based boards](en/install-xm530.md)
- [Very old full manual](en/old-manual.md)
### Usage
- [System features](en/system-features.md)
- [Majestic streamer](en/majestic-streamer.md)
- [Microbe web interface](en/microbe-web.md)
- [Upgrade firmware](en/sysupgrade.md)
- [Image quality tuning](en/image-quality-tuning.md)
- [Memory tuning](en/memory-tuning.md)
- [Using ipctool](en/example-ipctool.md)
- [GPIO settings](en/gpio-settings.md)
- [ACMEv2](en/acme-v2.md)
- [YouTube streaming](en/youtube-streaming.md)
- [WiFi XM530](en/wifi-xm530.md)
- [Board manufacturers](en/board-manufacturers.md)
### Firmware
- [Releases in GitHub](https://github.com/OpenIPC/firmware/releases/tag/latest)
- [Releases in Telegram](https://t.me/s/openipc_dev)
- [Source code](en/source-code.md)
### Development
- [Interesting tricks](en/dev-tricks.md)
- [Boot device with NFS](en/dev-nfs-boot.md)
- [FFMPEG usage](en/dev-ffmpeg-usage.md)
- [Kernel configuration for adding new platforms](en/integration-kernel.md)
### Help, Tips, and Tricks
- [U-boot](en/help-uboot.md)
- [Web UI](en/help-webui.md)
### Reference Book
- [Board manufacturers](en/board-manufacturers.md)
- [Company names](en/company-names.md)
### Contacts
- [Bug reports](https://github.com/OpenIPC/firmware/issues)
### Our resources
- [OpenIPC](https://openipc.org/)
- [OpenCollective](https://opencollective.com/openipc)
- [Twitter](https://twitter.com/OpenIPC)
- [Telegram](https://t.me/openipc)
### Roadmap
- [ToDo](en/todo-all.md)
- [Developers](en/developers.md)
- [Notes from old sources](en/notes-for-resorting.md)
### Resources for recycling and integration
- <https://github.com/OpenIPC/camerasrnd>
- <https://openwrt.org/docs/techref/hardware/soc/soc.hisilicon.hi35xx>
In Russian
----------
- [О проекте](ru/about.md)
- [Установка. Шаг за шагом.](ru/installation.md)
- [Темы для дискуссий разработчиков](ru/discussion.md)
- [Программный переход с openipc-1.0 (OpenWrt) на openipc-2.x (Buildroot)](ru/upgrade-from-1.md)
- [Вопросы и ответы](ru/faq.md)
- [Хочу помочь!](ru/contribute.md)
### Помощь
- [Веб-интерфейс](ru/help-webui.md)
### Камеры
- [Switcam HS-303](ru/hardware-hs303.md)
- [Ростелекомовская камера с NAND](ru/hardware-rtk-nand.md)
## Что можно прочитать про прошивку OpenIPC?
- [Часто задаваемые вопросы и ответы на них][faq1]
- [Заметки от Олега Левшина][faq3]
#### This is an open project, so you can help, too.
We try to collect, organize and share as much information regarding different
aspects of the project as we can. But sometimes we overlook things that seem
obvious to us, developers, but are not so obvious to end-users, people who are
less familiar with nuts and bolts behind the scene. That is why we set up this
wiki and let anyone having a GitHub account to make additions and improvements
to the knowledgebase. Read [How to contribute.](en/contribute.md)
[faq1]: https://github.com/OpenIPC/camerasrnd/blob/master/docs/XM-FAQ-ru.md
[faq3]: https://alarmsystem-cctv.ru/openipc-%D0%BE%D1%82%D0%BA%D1%80%D1%8B%D1%82%D1%8B%D0%B9-%D0%BA%D0%BE%D0%BB%D0%BB%D0%B5%D0%BA%D1%82%D0%B8%D0%B2/
[logo]: images/logo_openipc.png

6
ru/about.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Прошивка OpenIPC -- что это?
----------------------------
@ -35,7 +35,7 @@ OpenIPC. [Список таких процессоров][socs] пока огр
Аккуратно снимите объектив (он держится на двух винтах) и сделайте фото матрицы.
Одни и те же процессоры могут комплектоваться разными типами матриц, каждая из
них требует собственного кофигурационного файла.
них требует собственного конфигурационного файла.
Сделайте фотографии разъемов, чтобы не перепутать подключения, если вам
понадобится их разъединить, например для удобного доступа к матрице. _Маленькая
@ -69,7 +69,7 @@ UART. Как правило, это группа из трех, реже чет
Вам нужно будет самостоятельно определить порт на плате, выяснить его
распиновку, и либо распаять на него коннектор, либо припаять провода напрямую
к контактам порта. Так же можно использовать прищепку с пружинными щупами для
подключения адаптера к камере. В любом случае, соединение должно быть надежным,
подключения адаптера к камере. В любом случае соединение должно быть надежным,
иначе пропадание контакта во время записи/чтения может обернуться искажением
передаваемых данных, что в свою очередь может обернуться порчей содержимого
флэш-памяти и вывести камеру из строя. И тогда вам потребуется программатор

4
ru/discussion.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Темы для дискуссий
------------------
@ -73,7 +73,7 @@
* Сделать постоянно висящее сообщение о необходимости смены дефолтного пароля.
* Разделить уровни доступа для пользователей admin (настройка сети, даты, и
обновление стабильного релиза) и root (пролный доступ с массой диагностики).
обновление стабильного релиза) и root (полный доступ с массой диагностики).
Фичи

49
ru/faq.md
View File

@ -1,44 +1,61 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Вопросы и ответы
----------------
### Как настроить авторизацию ssh-сессии по ключу
#### На камере
Откройте ssh сессию и создайте непустой пароль пользователю root.
По умолчанию в нашей прошивке у пользователя root пароля нет.
Имейте в виду, что после того как вы создали пароль, все последующие
новые ssh сессии до момента настройки авторизации по публичному ключу,
а так же при попытке захода с компьютера, где такого ключа нет, будут
требовать авторизации именно с этим паролем. Не забудьте его!
__На камере__: Откройте ssh сессию и создайте непустой пароль пользователю root. По умолчанию в нашей прошивке у пользователя root пароля нет.
Имейте в виду, что после того как вы создали пароль, все последующие новые ssh сессии до момента настройки авторизации по публичному ключу,
а так же при попытке захода с компьютера, где такого ключа нет, будут требовать авторизации именно с этим паролем. Не забудьте его!
```
passwd
```
#### На десктопе
Скопируйте публичный ключ на камеру, авторизовавшись созданным выше паролем.
__На десктопе__: Скопируйте публичный ключ на камеру, авторизовавшись созданным выше паролем.
```
ssh-copy-id root@192.168.1.666
```
#### На камере
Создайте папку `.ssh` в домашней директории пользователя root
и скопируйте в неё файл с хранилищем авторизованных ключей.
__На камере__: Создайте папку `.ssh` в домашней директории пользователя root и скопируйте в неё файл с хранилищем авторизованных ключей.
```
mkdir ~/.ssh
cp /etc/dropbear/authorized_keys ~/.ssh/
```
#### На десктопе
Откройте новую сессию, чтобы проверить, что авторизация проходит по открытому ключу, без участия пароля.
__На десктопе__: Откройте новую сессию, чтобы проверить, что авторизация проходит по открытому ключу, без участия пароля.
```
ssh root@192.168.1.666
```
### Majestic
##### Можно-ли вывести данные для настройки автоматической фокусировки линз вместо текущего sample_af в стандартный /metrics?
#### Как получить дамп памяти для отладки?
Включите и настройте отсылку Core Dump в меню Majestic > Majestic Debugging.
#### Изображение с камеры имеет розовый оттенок
Вам нужно указать GPIO пины для управления инфракрасным фильтром. Настройки для некоторых камер можно найти [в таблице](https://openipc.org/wiki/en/gpio-settings.html). Если вашей камеры в таблице нет, то вам потребуется утилита [ipctool](https://github.com/OpenIPC/ipctool/releases/download/latest/ipctool).
Прошивка OpenIPC автоматически скачает свежую версию утилиты в каталог /tmp при первом вызове `ipctool`.
На родной прошивке вам потребуется скачать утилиту на камеру самостоятельно, используя имеющие в системе средства: wget, curl, tftp...
Например, скачайте утилиту ipctool на сервер TFTP в локальной сети, затем скачайте ее оттуда на камеру:
```
tftp -g -r ipctool -l /tmp/ipctool 192.168.1.1
chmod +x /tmp/ipctool
/tmp/ipctool
```
При наличии на камере доступа в интернет вы можете попробовать смонтировать публичный NFS шаринг и запустить утилиту с него, без скачивания на камеру:
```
mkdir -p /tmp/utils
mount -o nolock 95.217.179.189:/srv/ro /tmp/utils/
/tmp/utils/ipctool
```
После того как утилита скачана на камеру, выполните команд `ipctool gpio scan` в терминале и пару раз закройте-откройте объектив камеры ладошкой.
Следите за выводом ipctool, чтобы определить пины, отвечающие за управление шторкой ИК фильтра.
Внесите полученные значения в настройки ночного режима Majestic. Если розовый оттенок не исчез, возможно необходимо включить инверсию сигнала сенсора.
Не забудьте добавить модель камеры и найденные значения GPIO в таблицу!
#### Можно-ли вывести данные для настройки автоматической фокусировки линз вместо текущего sample_af в стандартный /metrics?
Нет, это отдельный тяжелый алгоритм, его нет смысла запускать просто так.

156
ru/hardware-hs303.md
View File

@ -1,37 +1,159 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Switcam HS-303
--------------
Публичные заметки по прошивке устройств Switcam HS303 (всех версий) в
[OpenIPC](https://openipc.org) v1.0 (на базе OpenWrt).
Компания-производитель выпускала IP камеры Switcam HS-303 в трёх версиях,
значительно отличающихся аппаратно между собой. На данный момент проект
OpenIPC поддерживает все три типа камер, однако установка альтернативного ПО
без разборки устройства возможна только на v1 и v2, причем на первый тип камеры
устанавливается более старая версия на базе OpenWrt.
Обсуждение проекта и возможностей прошивок (на русском языке) в группе
[Telegram](https://t.me/openipc_modding).
Мы работаем над созданием новой универсальной прошивки для всех трёх типов
видеокамеры Switcam HS-303. Обсуждение проекта и возможностей прошивок (на
русском языке) возможно в открытой группе [Telegram](https://t.me/openipc_modding).
Так-же в ближайшее время все информационные наработки по видеокамерам в виде
Q&A будут перенесены в данный документ общей Wiki.
## Начало работы
Для комфортной работы в камерами OpenIPC в Windows необходимо установить программы:
* Putty для доступа по протоколу ssh (вместо telnet)
* WinSCP для доступа к файловой системе по протоколу scp
* Notepad++ в качестве редактора файлов на Linux камере
Для входа использовать имя пользователя root, без пароля
## HS303(v1)
### Наиболее актуальные вопросы и ответы
#### Какие типы устройств поддерживаются в проекте OpenIPC v1.0?
На данный момент полноценно поддерживается Switcam HS-303 (v1).
В будущем планируется поддержка устройств v2 и v3.
#### Где можно взять прошивку для устройства Ростелеком Switcam HS303 (v1)?
#### Где можно взять прошивку для устройства Ростелеком Switcam HS303(v2)?
Обсуждение работы этих камер доступно по специальной подписке на
[OpenIPC paywall](https://paywall.pw/openipc).
#### Какой путь до SD карты необходимо указывать в `majestic.yaml` для прошивки
openipc-1.0?
#### Как зарегистрировать данный тип камеры на сервисе ipeye.ru ?
В личном кабинете IPeye добавить камеру по ID, в качестве которого использовать MAC
интерфейса eth0, написанный в нижнем регистре (маленькими буквами).
#### Какой путь до SD карты необходимо указывать в `majestic.yaml` ?
`/mnt/mmc/%Y/%m/%d/%H/%M.mp4`
## HS303(v2)
### Краткая инструкция установки OpenIPC v2.2
- отформатируйте SD/MMC карту как FAT (ограничение 2GB)
- распакуйте содержимое архива в корень SD/MMC карты
- вставьте карту памяти и подайте питание на камеру
- через 60 секунд (обновится загрузчик) сделайте выкл/вкл питания
- через 90 секунд камера щелкнет ИК фильтром два раза
- вытащите SD/MMC карту, камера готова к эксплуатации
По-умолчанию камера пытается соединиться с точкой доступа с именем OpenIPC_NFS
и паролем сети project2021. Для изменения имени сети и пароля перед прошивкой
устройства, откройте файл autoconfig/etc/network/interfaces на SD/MMC карте в
редакторе Notepad++ (для Windows), выбрав при этом кодировку UTF-8 и впишите
свои значения.
После прошивки устройства не забудьте удалить все файлы autoupdate* так как
при каждой подаче питания камера будет пытаться обновиться, что в итоге может
привести к неисправности.
Для некоторых старых версий прошивки может понадобится принудительно указать
тип сенсора устройства, если не сработал автодетект. Для этого зайдите на
камеру по протоколу SSH или в WEB-интерфейс (как это сделать описано ниже) и
выполните команду:
```
fw_setenv sensor ov9732; reboot -f
```
### Наиболее актуальные вопросы и ответы
#### Где можно взять прошивку для устройства Ростелеком Switcam HS303(v2)?
Обсуждение работы этих камер доступно по специальной подписке на
[OpenIPC paywall](https://paywall.pw/openipc).
#### Как узнать какой IP адрес у прошитой камеры и как зайти на неё ?
Если внесены корректные данные по настройке WiFi интерфейса в конфигурационный
файл (SSID и ключ), то вы можете найти IP адрес камеры на своём роутере в списке
подключенных устройств с пометкой "OpenIPC".
Интерфейс управления камерой доступен в браузере на порту 85, а доступ по SSH
возможен на стандартном порту 22 с использованием логина root, без пароля при
первом подключении.
#### Как можно обновить прошивку до последней актуальной версии через SSH ?
Зайдите на камеру по протоколу SSH через программу Putty (логин root, без пароля,
22 порт) и выполните команду:
```
sysupgrade -k -r
```
При наличии интернета, камера автоматически подключится к GitHub, скачает
и установит самые последние обновления.
В случае, если выполнение данной команды приводит к зависанию камеры, можно
воспользоваться специальной командой выполнения обновленного скрипта:
```
curl -s https://raw.githubusercontent.com/OpenIPC/firmware/master/general/overlay/usr/sbin/sysupgrade | sh -s -- -r -k
```
#### Как можно обновить прошивку до последней актуальной версии через WEB ?
Зайдите на камеру через браузер указав IP адрес камеры и порт подключения 85,
например вот так:
```
http://192.168.1.253:85
```
Введите дефолтные логин и пароль (логин admin, пароль 12345).
После захода на камеру, установите новый пароль (не забудьте его записать!) и
выберите язык интерфейса. В разделе Firmware/Прошивка выполните действия,
которые указаны в подсказках.
#### Как зарегистрировать данный тип камеры на сервисе ipeye.ru ?
В личном кабинете IPeye добавить камеру по ID, в качестве которого использовать MAC
написанный в нижнем регистре (маленькими буквами). MAC написан на титульной
странице WEB-интерфейса на 85 порту.
#### Как включить микрофон на камере при стриме на ipeye.ru ?
В свойствах основного видеопотока установите тип кодека как ```alaw```
Это можно сделать подключившись по ssh в редакторе vi, подключившись через
WinSCP по протоколу scp через редактор Notepad++, так и через WEB-интерфейс
на 85 порту в разделе Majestic.
```
audio:
enabled: true
volume: auto
srate: 8000
codec: alaw
```
`/mnt/mmc/%Y/%m/%d/%H.mp4`
### Специализированные настройки для Switcam HS303(v2)
Обсуждение работы этих камер доступно по специальной подписке на
[OpenIPC paywall](https://paywall.pw/openipc).
#### Модифицированный блок из файла /etc/network/interface
```

2
ru/hardware-rtk-nand.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Ростелекомовская камера с NAND
------------------------------

37
ru/help-uboot.md
View File

@ -1,3 +1,6 @@
# OpenIPC Wiki
[Оглавление](../index.md)
Помощь: U-boot
------------
@ -22,15 +25,16 @@ root@openipc-hi3518ev100:~#
В программе-терминале, используемой для подключения к порту UART, установите
сохранение лога сессии. В качестве примера мы используем программу-терминал
`screen`. В этом случае команда подлючения к UART-адаптеру с сохранением лога
`screen`. В этом случае команда подключения к UART-адаптеру с сохранением лога
сессии в файл _fulldump.log_ будет выглядеть примерно так:
```
$ screen -L -Logfile fulldump.log /dev/ttyUSB0 115200
```
После чего в консоли загрузчика запустите команду чтения данных из памяти длиной
в объем флэш-памяти начиная с нулевого адреса.
После чего в консоли загрузчика запустите серию команд для чтения полного объема
содержимого флэш памяти сначала в оперативную память камеры, а затем вывод
шестнадцатеричного представления этих данных из оперативной памяти на экран.
Используйте шестнадцатеричную запись для адресов памяти.
Так 0 в шестнадцатеричном представлении выглядит как 0x0,
@ -40,30 +44,39 @@ $ screen -L -Logfile fulldump.log /dev/ttyUSB0 115200
Чтение 8МБ флэш-памяти:
```
md.b 0x0 0x800000
mw.b 0x82000000 ff 0x800000
sf probe 0
sf read 0x82000000 0x0 0x800000
md.b 0x82000000 0x800000
```
Чтение 16МБ флэш-памяти:
```
md.b 0x0 0x1000000
mw.b 0x82000000 ff 0x1000000
sf probe 0
sf read 0x82000000 0x0 0x1000000
md.b 0x82000000 0x1000000
```
После запуска команды чтения содержимого памяти вы можете отсоедить сессию,
После запуска команды чтения содержимого памяти вы можете отсоединить сессию,
чтобы случайное нажатие клавиш не замусорило лог. В `screen` это делается
последовательным нажатием комбинации клавиш `Ctrl-a` и клавиши `d` (detach).
Для последующего присоединения к запущенной сессии используйте команду
```
screen -r
```
`screen -r`.
Будьте готовы к тому, что процесс передачи данных через серийное подключение
займет несколько часов. Зато в результате у вас будет полная копия оригинальной
прошивки, которую можно конвертировать в бинарный файл с помощью программы
[binwalk](https://github.com/ReFirmLabs/binwalk) и использовать для дальнейшего
прошивки, которую можно конвертировать в бинарный файл и использовать для дальнейшего
изучения или для восстановления камеры в её оригинальный вид.
```
xxd -r fulldump.log > fulldump.bin
```
Используйте [binwalk](https://github.com/ReFirmLabs/binwalk) для доступа к содержимому
бинарного файла.
#### Сохранение прошивки через SD карту.
Бывает, что у камеры есть только беспроводной доступ, который не работает

4
ru/help-webui.md
View File

@ -1,8 +1,10 @@
# OpenIPC Wiki
[Table of Content](index.md)
[Оглавление](../index.md)
Помощь: Веб-интерфейс
---------------------
После установки прошивки веб-интерфейс доступен на 85 порту камеры http://IP:85
Стандартный login/password: admin/12345
### Обновление веб-интерфейса из веб-интерфейса

28
ru/index.md
View File

@ -1,28 +0,0 @@
# OpenIPC Wiki
Оглавление
----------
- [О проекте](about.md)
- [Установка. Шаг за шагом.](installation.md)
- [Темы для дискуссий разработчиков](discussion.md)
- [Программный переход с openipc-1.0 (OpenWrt) на openipc-2.x (Buildroot)](upgrade-from-1.md)
- [Вопросы и ответы](faq.md)
- [Хочу помочь!](participate.md)
### Помощь
- [Веб-интерфейс](help-webui.md)
### Камеры
- [Switcam HS-303](hardware-hs303.md)
- [Ростелекомовская камера с NAND](hardware-rtk-nand.md)
## Что можно прочитать про прошивку OpenIPC?
* [Часто задаваемые вопросы и ответы на них][faq1]
* [Заметки от Олега Левшина][faq3]
[faq1]: https://github.com/OpenIPC/camerasrnd/blob/master/docs/FAQ-ru.md
[faq3]: https://alarmsystem-cctv.ru/openipc-%D0%BE%D1%82%D0%BA%D1%80%D1%8B%D1%82%D1%8B%D0%B9-%D0%BA%D0%BE%D0%BB%D0%BB%D0%B5%D0%BA%D1%82%D0%B8%D0%B2/

10
ru/installation.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Установка OpenIPC. Шаг за шагом.
--------------------------------
@ -64,7 +64,7 @@ __Прежде чем подключать адаптер к камере, уб
запустите на компьютере программу подключения к серийному порту и установите
соединение с адаптером. Используйте скорость подключения 115200 bps. После этого
соедините контакт `RX` адаптера с предполагаемым контактом `TX` порта UART.
Подайте питание на камеру. Если вы угадали правильно, на экране появится ло
Подайте питание на камеру. Если вы угадали правильно, на экране появится лог
загрузки. Если же экран остался чистым -- повторите процедуру с другим свободным
контактом UART. После того как вы определили порт `RX`, подключите порт `TX`
адаптера к оставшемуся свободному контакту порта UART. Попробуйте прервать
@ -421,7 +421,7 @@ setenv sensor <sensor> #
setenv totalmem <memory> # 32M for xm510, 64M for xm530, 128M for xm550.
setenv osmem <osmemory> # 18M for xm510, 35M for xm530, 64M for xm550.
setenv bootargs 'mem=$(osmem) console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=xm_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootargs 'mem=35M console=ttyAMA0,115200 panic=20 root=/dev/mtdblock3 rootfstype=squashfs init=/init mtdparts=xm_sfc:256k(boot),64k(env),2048k(kernel),5120k(rootfs),-(rootfs_data)'
setenv bootcmd 'sf probe 0; sf read 0x80007fc0 0x50000 0x200000; bootm 0x80007fc0'
setenv ethaddr 00:00:00:00:00:00
@ -442,7 +442,7 @@ mw.b 0x80007fc0 ff 1000000
tftp 0x80007fc0 rootfs.squashfs.${soc}
sf probe 0
sf erase 0x250000 0x500000
sf write 0x80007fc 0x250000 ${filesize}
sf write 0x80007fc0 0x250000 ${filesize}
reset
```
@ -531,4 +531,4 @@ _...to be continued._
[logo]: ../images/logo_openipc.png
[ftdi]: https://www.google.com/search?q=ftdi+usb+ttl
[ttlc]: https://google.com/search?q=logic+level+converter+3.3v+5v
[tllc]: https://google.com/search?q=logic+level+converter+3.3v+5v

19
ru/links.md
View File

@ -0,0 +1,19 @@
# OpenIPC Wiki
[Оглавление](../index.md)
SoC
---
- https://www.augentix.com/
- http://www.goke.com/
- https://www.hisilicon.com/
- http://www.ingenic.com.cn/
- http://www.novatek.com.tw/
- http://www.sigmastarsemi.com/
Полезные ссылки
---------------
- https://zftlab.org/
- http://www.ipcam.xin/
- https://ipcamtalk.com/
- https://www.nvripc.com/
- https://www.dvraid.com/

13
ru/participate.md
View File

@ -1,13 +1,12 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Хочу помочь! Что надо делать?
-----------------------------
Мы не откажемся от любой, даже самой малой помощи.
Проекту нужны как те, кто читает схемы, умеет отреверсить закрытый драйвер,
так и те, кто сможет увидить и поправить опечатку, написать инструкцию,
так и те, кто сможет увидеть и поправить опечатку, написать инструкцию,
нарисовать красивую картинку или может быть даже сложить красивую песню :)
### Я сделал поправки в код. Как его вам прислать?
@ -15,15 +14,15 @@
Для работы с кодом мы используем систему управления версиями [Git][gitdoc]
и репозитории, расположенные на сервисе GitHub.
Если у вас есть акаунт на GitHub, то все просто: сделайте копию нашего
Если у вас есть аккаунт на GitHub, то все просто: сделайте копию нашего
кода в своем аккаунте (fork).
![GitHub Fork](/images/gh-fork.png)
![GitHub Fork](../images/gh-fork.png)
Cделайте правки в своей копии, после чего отправьте запрос на включение
Сделайте правки в своей копии, после чего отправьте запрос на включение
ваших изменений в нашу ветку (pull request)
![GitHub Contribute](/images/gh-contribute.png)
![GitHub Contribute](../images/gh-contribute.png)
Если вы по какой-то причине не пользуетесь GitHub, вы всё-равно можете
прислать нам свои изменения в код. Для этого сделайте локальную копию

115
ru/resources.md 100644
View File

@ -0,0 +1,115 @@
# Полезные ссылки
Железо и его производители
--------------------------
### Процессоры
- [Ambarella](https://www.ambarella.com/)
- [Anyka](http://www.anyka.com/)
- [Fullhan](https://www.fullhan.com/)
- [Goke](http://www.goke.com/)
- [Grain Media (Novatek)](https://www.novatek.com.tw/)
- [Hisilicon](https://www.hisilicon.com/en/)
- [Ingenic](http://www.ingenic.com.cn/en/)
- [MStar (MediaTek)](http://www.mstarsemi.com/)
- [Nextchip](http://www.nextchip.com/)
- [Novatek](https://www.novatek.com.tw/)
- [SigmaStar](http://www.sigmastarsemi.com/)
- [XiongmaiTech](https://www.xiongmaitech.com/)
### Матрицы
- [Forza Silicon](https://www.forzasilicon.com/)
- [GalaxyCore](https://en.gcoreinc.com/)
- [OmniVision](https://www.ovt.com/)
- [ON Semiconductor](https://www.onsemi.com/)
- [Silicon Optronics](https://www.soinc.com.tw/)
- [SmartSens Technology](https://www.smartsenstech.com/)
- [Sony Semiconductor](https://www.sony-semicon.co.jp/)
### Периферия
- [Realtek](https://www.realtek.com/)
### Модули
- [Supertek](https://www.supertekmodule.com/)
Операционная система и программное обеспечение
----------------------------------------------
- [U-Boot](https://www.denx.de/wiki/U-Boot)
- [Buildroot](https://buildroot.org/)
- [Bootlin](https://github.com/bootlin)
- [HLS.js](https://github.com/video-dev/hls.js/)
- [VLC, x264](https://www.videolan.org/)
Стандарты и прочая документация
-------------------------------
- [MDN Web Docs](https://developer.mozilla.org/)
- [W3cubDocs API Documentation](https://docs.w3cub.com/)
- [MPEG-4 Standard](https://mpeg.chiariglione.org/standards/mpeg-4)
- [MPEG-DASH: Dynamic Adaptive Streaming over HTTP](https://mpeg.chiariglione.org/standards/mpeg-dash)
- [HLS: HTTP Live Streaming](https://developer.apple.com/streaming/)
- [Media Source Extensions. W3C Draft](https://w3c.github.io/media-source/)
- [Microsoft Media Foundation SDK](https://docs.microsoft.com/en-us/windows/win32/medfound/microsoft-media-foundation-sdk)
- [Chromium MediaSource Tests](https://chromium.googlesource.com/external/w3c/web-platform-tests/+/refs/heads/master/media-source)
### RFC
- [Hypertext Transfer Protocol HTTP/1.1. RFC2616](https://www.rfc-editor.org/info/rfc2616). Obsolete, see Obsoleted by/Updated by links.
- [Hypertext Transfer Protocol Version 2. HTTP/2. RFC7540](https://www.rfc-editor.org/info/rfc7540)
- [The Common Gateway Interface (CGI) Version 1.1. RFC3875](https://www.rfc-editor.org/info/rfc3875)
- [Scripting Media Types. RFC4329](https://www.rfc-editor.org/info/rfc4329)
- [JavaScript Object Notation (JSON) Pointer. RFC6901](https://www.rfc-editor.org/info/rfc6901)
- [JavaScript Object Notation (JSON) Patch. RFC6902](https://www.rfc-editor.org/info/rfc6902)
- [JavaScript Object Notation (JSON) Text Sequences. RFC7464](https://www.rfc-editor.org/info/rfc7464)
- [The JavaScript Object Notation (JSON) Data Interchange Format. RFC8259](https://www.rfc-editor.org/info/rfc8259)
- [HTTP Live Streaming. RFC8216](https://www.rfc-editor.org/info/rfc8216)
- [HTTP Live Streaming, 2nd Ed. Draft](https://datatracker.ietf.org/doc/html/draft-pantos-hls-rfc8216bis-10)
- [Real-Time Streaming Protocol Version 2.0. RFC7826](https://www.rfc-editor.org/info/rfc7826)
### PTZ Protocols
- [Pelco](https://shopdelta.eu/pelco-d-pelco-p_l2_aid1047.html)
- [Bosch OSRD](https://resources-boschsecurity-cdn.azureedge.net/public/documents/OSRD_Protocols_Configuration_Manual_enUS_20804604939.pdf)
- [Bosch BiCom](https://manualzz.com/doc/22138427/bicom-protocol-for-bosch-ptz-cameras)
- [Sony VISCA](https://www.epiphan.com/userguides/LUMiO12x/Content/UserGuides/PTZ/3-operation/VISCAcommands.htm)
- [Panasonic AW]
- [Panasonic WV]
- [Samsung]
- [LG Multix]
- [Canon]
- [Hitachi]
- [AD ASCII/Manchester/RS422/RS485]
- [LiLin]
- [Yoko]
Технические статьи и обучающие материалы
----------------------------------------
- [REST API Tutorial](https://restfulapi.net/)
- [Video Codec Guide](https://developer.mozilla.org/en-US/docs/Web/Media/Formats/Video_codecs)
- [The "codecs" parameter in common media types](https://developer.mozilla.org/en-US/docs/Web/Media/Formats/codecs_parameter)
- [Video Encoding and Playback With GStreamer (Linux)](https://developer.toradex.com/knowledge-base/video-playback-linux)
- [Xiongmai Open Platform](https://oppf.xmcsrv.com/)
Интересные ресурсы
------------------
- [CNX Software](https://www.cnx-software.com/)
- [Unifore](https://www.unifore.net/)
- [Image Sensors World](http://image-sensors-world.blogspot.com/)
- <https://www.goprawn.com/forum>
- <http://www.hasecu.com/>
- <http://www.hasecurity.com/>
- <http://www.hlong.asia/>

2
ru/upgrade-from-1.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Программный переход с openipc-1.0 (OpenWrt) на openipc-2.x (Buildroot) 👻
-------------------------------------------------------------------------

2
ru/user-notes-melcor.md
View File

@ -1,5 +1,5 @@
# OpenIPC Wiki
[Оглавление](index.md)
[Оглавление](../index.md)
Прошивка gk7205v300 + IMX335 + XM_XT25F128B
-------------------------------------------