Registered a URL and setup a forum as the IPCam stuff really needed its own site vs my irregular blog posts about IPCam hacking at

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Topics - admin

Pages: 1 [2] 3 4 ... 6
Site Announcements / BSP's
« on: February 13, 2012, 12:29:23 pm »
We have a number of BSP (Board Support Packages) in the files section.

I've split them into 2 different sections - ARM7 and ARM9.
The ARM7 ones are for the "older" camera's - e.g. the one in the site logo.

The ARM9 ones are for the newer gen camera's - most of the H.264 ones are ARM9.

I've updated the Grain Media ARM9 8126 BSP to 1.1 as of Feb 14 2012.
We also have the HiVision BSP in there also.

If people are interested in other BSP's I can source, upload (although they usually cost money to buy/procure sadly, even though its usually 99% open source code base).
PM me, or Skype me if you are interested, and I can see whats available.


Hacking & Modding / MOVED: network connection??
« on: December 28, 2011, 02:10:03 am »

Feature Suggestions / OIT Integration
« on: December 28, 2011, 01:40:51 am »
I've been taking a look at the different options for net enabling the ipcams -
This looks interesting -

Pachube is an API based on the unfortunately named IoT (Internet of Things)
IOT is also an existing acronym for Interoperability Testing, so searching for decent info on it gets a bit annoying..

It solves some of the issues that need to be addressed -

OnBoard includes:
1. Device bulk-registration: Manufacturers can provision devices onto Pachube and specify
data profiles.
2. End-user account integration: Device owners can now claim their devices and their data directly on Pachube.
3. Dashboards: Once devices are claimed, device owners view dashboards hosted within their accounts.

Not sure if video feed or captures will be supported, but will have a chat to them...


General Discussion / OCX Replacement
« on: October 21, 2011, 02:14:24 am »
While doing some ZoneMinder related stuff I noticed that they use Cambozola for video streaming.

This is an open source jar file we can also use in the camera for streaming video.  Its light, and easily integrated.

Its something we should look at in custom firmwares.

General Discussion / Overview of China IP CAM Market
« on: July 19, 2011, 09:05:59 am »

Good overview of the market - which will explain things to people ;)


China offers IP cameras in bullet, dome and speed dome types. These products typically have CCD or CMOS 39sensors, digital signal processor or DSP, or ASIC chipset solutions, MPEG-4 or H.264 compression formats, CIF to D1 resolutions and built-in Web servers. Network interface is via an RJ-45 10/100M Ethernet port or 802.11b/g Wi-Fi. PoE has become a common configuration as well.
Suppliers are also adding functions to increase product value. They incorporate microphones, a PTZ control, alarm I/O ports, a night-vision function and either a multimedia card slot or USB port for storage. Units with water and vandal resistance, and wide dynamic range are also available. The devices feature modular designs.

Current models are based on two different hardware architectures, namely, CPU+DSP and CPU+ASIC. The CPU generally utilizes an ARM9 or corresponding processor.

DSP solutions afford makers the flexibility to add various compression algorithms and functions. These, however, require higher R&D capability. Products based on such are therefore classified as high-end.

ASIC chip providers, on the other hand, offer comprehensive reference designs, including hardware, software and software development kits or SDKs. The components are primarily found in low-priced and midrange products.

Some of the popular ASIC solutions are sourced from domestic companies. Hisilicon's Hi3510 and Hi3512 series are popular because the provider offers technical support.

Certain price-sensitive buyers request makers to provide devices designed with Taiwan-based Faraday's FIC8120 and FIE8180 chipsets. International enterprises, including Vweb and Freescale, also occasionally supply ASIC components to mainland China makers.

DSPs, meanwhile, come from companies in the US and Europe such as TI, ADI and NXP.

TI offers reference designs and solutions with powerful processing capability. Its TMS320DM64x series has high frequency and a strong processor that enables video analytics and other advanced functions. The TMS320DM3x has low power consumption and cost, and an optimized video coprocessor. Because of prohibitive costs, only large factories can often afford these products.

ADI's Blackfin DSP includes the BF52x, BF53x and BF56x series. These are mainly used in midrange models.

A number of IP cameras from China are designed with NXP's PNX13xx and PNX15xx DSP solutions.

SoC solution providers integrate CPU and DSP/ASIC into a single chip to lower production outlay and simplify circuit design. They use royalty-free Linux RTOS for the software platforms to save on expenses as well.

These measures are driving the popularity of SOCs particularly among IP camera manufacturers looking to cut costs and reduce risks in R&D. The preferred SoC solutions are TI's TMS320DM3x, Hisilicon's Hi351x, and Faraday's FIC8120 and FIE8180 series.

Product prices depend on the camera type and IP module. Suppliers are predicting stable quotes in the low-end segment and further cuts for the high-end in the next six to 12 months. This comes after IP module rates dropped to $15 to $40 with the adoption of low-cost solutions.

Product development

Since most IP cameras from China are ASIC-based, product homogeneity has become a problem. ASIC's fixed architecture results in similar functions and specifications across different models.

Companies are therefore developing new functions to differentiate their devices. Network adaptability and optimization, higher resolution and intelligent technologies top makers' R&D agenda.

Suppliers are working to reduce bandwidth consumption and network latency during transmissions. They expect that H.264 will replace MPEG-4 as the mainstream format in this line within the next two years. New versions incorporate the latest networking functions, including adaptive multistreaming and activity-controlled frame rate.

Homegrown ICs are also enabling makers to develop high-definition or megapixel products. The 720 and 1080p are projected to gradually become the HD standard. New chipsets, including TI's DM365 and Faraday's FIE8180, support 720 or 1080p realtime compression. Some of the recently launched models of megapixel cameras are equipped with a 1.3MP CCD or 2MP CMOS sensor.

Moreover, companies are cooperating with video analytics experts to develop intelligent systems. Current applications include vehicle license plate and face recognition, object detection and action identification. Incorporating intelligence into surveillance, however, can take its toll on hardware performance. Makers, therefore, prefer DSP solutions for these.

Some DSP providers offer assistance to IP camera manufacturers to enhance their systems. ADI, for example, give China suppliers an SDK called Image Tool Box to help in video analytics development and improvement. Hangzhou Hikvision Digital Technology Co. Ltd works with TI and ObjectVideo.

Other R&D priorities are 3G network introduction, cosmetic design upgrades, product diversity and reliability, simpler installation and debugging.

China IP camera suppliers are classified into three tiers. The biggest group is comprised of traditional camera manufacturers that have ample experience in CCTV production, a range of models encompassing most key categories, and large in-house capacity. Major players, including Sunell and Shenzhen Hongtianzhi offer a comprehensive selection of analog and IP products. Small companies, on the other hand, handle product assembly only.

IP surveillance camera suppliers develop the line's core technology of IP cameras, which covers compression algorithm, communication and control protocol, software platform, DSP programming and intelligent image processing. They provide packages that are compatible with most IP systems. Many can also furnish downstream makers with SDKs for redevelopment. Hangzhou Hikvision and Launch Digital Technology Co. Ltd are among the suppliers in this tier.

Recently, network equipment manufacturers began entering the line to widen their product range and increase profitability. Since such operations specialize

in network performance optimization and offer switches, routers and other related devices, their knowledge helps upgrade the IP surveillance industry's technical capability.

In coming years, China makers expect that the creation of an IP surveillance standard will be the main concern of the sector. There are currently two contenders to the move, namely, the Open Network Video Interface Forum or ONVIF and the Physical Security Interoperability Alliance or PSIA. Both are international IP surveillance organizations seeking for compatibility among all players in the line. They have released their draft standards and have attracted supporters from various countries.

The ONVIF is an open industry forum aimed at developing a global standard for the interface of network video products. Its specification defines a common protocol for information exchange between network video devices, including automatic device discovery, video streaming and intelligence metadata.

Hangzhou Hikvision Digital Technology Co. Ltd has joined this group.

The PSIA, on the other hand, is a consortium of nearly 50 physical security manufacturers and system integrators. They are promoting interoperability of IP-enabled devices across all segments of the security industry, including video, access control, analytics and software.

Since some China makers expect the single standard will not be achieved in the near future, they have chosen to wait and see which one will prevail.

Basically where I fit in currently is that I'm doing software development, and can talk to the factories in their own language :)

uCLinux / Creating a RAMFS image (How to make a ram disk image)
« on: July 17, 2011, 02:53:36 am »
I generate a ramdisk image using simple tools.

See below for sample script I use.

I run this from my images folder.  You'll need to change the path to your ramfs files location to something appropriate for you to use.
Code: [Select]

#Dangerous, but i'm  lazy
rm tmpramfs.img OPENIPCAMramfs.img
mkdir /tmp/ramfs

dd if=/dev/zero of=tmpramfs.img bs=1k count=1024
mkfs.minix -c  tmpramfs.img
mount -o loop -t minix tmpramfs.img /tmp/ramfs

# Change the folder below to the location you store your files and folders for the ramdisk
cp -av ../romdisknew/* /tmp/ramfs

umount /tmp/ramfs
gzip -v9 -c tmpramfs.img >OPENIPCAMramfs.img

General Discussion / MOVED: ONVIF
« on: July 15, 2011, 11:02:10 pm »

ONVIF and PSIA / What is PSIA
« on: July 11, 2011, 12:55:35 pm »
PSIA is a competing open standard for Network Video devices.

PSIA stands for  Physical Security Interoperability Alliance

PSIA looks like the people who weren't invited to the ONVIF party looked at their specs, and went hmm, then implemented something better.

PSIA uses REST instead of SOAP, so its a lot smaller sizewise for implementing from a client perspective.
No SOAP XML verboseness for a start!

PSIA site is here -

Unfortunately they're less open than ONVIF with their documents, so nothing freely available for the moment.

ONVIF and PSIA / What is ONVIF?
« on: July 11, 2011, 11:50:20 am »
ONVIF is a standard for talking to Network Camera Devices and other similar security hardware.
It was established in 2008 by Axis Communications, Bosch and Sony.

ONVIF stands for - Open Network Video Interface Forum

A camera is called an NVT in the ONVIF spec's.

A client for ONVIF can be downloaded here -

The base elements of ONVIF are:
Standardization of communication between network video devices.
Interoperability among network video products, regardless manufacturer.
Open to all companies and organizations (hopefully including ours haha)

ONVIF Specification can be downloaded here -

ONVIF looks like its mostly  a verbose SOAP/ XML based service.

Devices supporting ONVIF advertise this by providing services on a DEVICENAME/onvif url.

Spec details for device management:

Application programmers guide:'s_Guide.pdf

Support Documents (onsite)

Complete ONVIF documentation here -

A very good page describing pluses and minuses of ONVIF here -

« on: July 11, 2011, 11:24:15 am »
Anyone interested in onvif implementation for the camera?

Looks a bit painful, but doable.

General Discussion / 2.6
« on: July 03, 2011, 12:31:16 am »
I have 2.6 working, just finishing up romfs and drivers.
I'll upload a zip of my files later.

Its a bit tight on 8M devices though.

Code: [Select]
Executing image 7 ...
Uncompressing Linux... done, booting the kernel.
Linux version (root@t60loz) (gcc version 4.2.4) #4 Sat Jul 2 15:23:01 CST 2011
CPU: Nuvoton-nuc700 [41807000] revision 0 (ARMv4T), cr=00000000
CPU: VIVT data cache, VIVT instruction cache
Machine: NUC745EVB
CPU type 0x00000745 is NUC745
The GPIO_CFG4 is 0x55555,  not equal to 0x155555, maybe using by boot!
The GPIO_CFG5 is 0x15555555,  not equal to 0x0, maybe using by boot!
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 2032
Kernel command line: root=/dev/ram0 console=ttyS0,115200n8 rdinit=/bin/init  mem=8M
PID hash table entries: 32 (order: -5, 128 bytes)
Dentry cache hash table entries: 1024 (order: 0, 4096 bytes)
Inode-cache hash table entries: 1024 (order: 0, 4096 bytes)
Memory: 8MB = 8MB total
Memory: 5776k/5776k available, 2416k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0x00000000 - 0x00001000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0x00000000 - 0xffffffff   (4095 MB)
    lowmem  : 0x00000000 - 0x00800000   (   8 MB)
    modules : 0x00000000 - 0x00800000   (   8 MB)
      .init : 0x00008000 - 0x0001e000   (  88 kB)
      .text : 0x0001e000 - 0x001ff000   (1924 kB)
      .data : 0x00200000 - 0x002158a0   (  87 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Console: colour dummy device 80x30
Calibrating delay loop... 39.42 BogoMIPS (lpj=197120)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 512 (order: 0, 4096 bytes)
TCP bind hash table entries: 512 (order: -1, 2048 bytes)
TCP: Hash tables configured (established 512 bind 512)
TCP reno registered
NET: Registered protocol family 1
NetWinder Floating Point Emulator V0.97 (double precision)
ROMFS MTD (C) 2007 Red Hat, Inc.
msgmni has been set to 16
io scheduler noop registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xfff80000 (irq = 9) is a 16550
console [ttyS0] enabled
brd: module loaded
loop: module loaded
nbd: registered device at major 43
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
nuc700-ohci nuc700-ohci: NUC700 OHCI
nuc700-ohci nuc700-ohci: new USB bus registered, assigned bus number 1
nuc700-ohci nuc700-ohci: irq 15, io mem 0xfff05000
usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: NUC700 OHCI
usb usb1: Manufacturer: Linux ohci_hcd
usb usb1: SerialNumber: ohci_hcd
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
TCP cubic registered
NET: Registered protocol family 17

General Discussion / NC541 White Disassembly
« on: June 26, 2011, 06:23:11 am »
Some naked hardware porn, this time from NC541. 

Different wifi and sensor than my older models.  Otherwise similar.
Board has i/r cut provisioning, although its not installed.  Looks like they use a gpio port for that, but haven't traced it backwards.

IMG_0035_2 by sheedl, on Flickr

Untitled by sheedl, on Flickr

IMG_0045_2 by sheedl, on Flickr

Untitled by sheedl, on Flickr

Untitled by sheedl, on Flickr

Untitled by sheedl, on Flickr

Untitled by sheedl, on Flickr

PAP7501V VGA Camera SoC by sheedl, on Flickr

General Discussion / request - /proc/ksyms
« on: June 20, 2011, 01:56:24 pm »
Can someone paste a copy of their /proc/ksyms in here for me.

Need to compare against a normal camera, thx.

uCLinux / USB Network drivers
« on: June 19, 2011, 01:57:01 pm »
Anyone want to start on backporting the rest of the usb network drivers?

We need -

vt6556 (VIA Networking Wireless LAN USB Driver 1.13)
rt73 (covers a few of the ralink devices)
ZD1211B / Atheros AR5007UG  - version

I've put some random drivers for them here - /files/uCLinux/drivers

Shouldn't be too hard actually.
I haven't had time to do more than the one I need for myself (rt73).

General Discussion / Interesting teardown on gumsize camera's
« on: June 19, 2011, 11:08:57 am »
Cool blog post on similar stuff to this and other stuff I've done.

I also did a similar teardown here -

His is better though :)

Pages: 1 [2] 3 4 ... 6