Skip to content

Latest commit

 

History

History
222 lines (181 loc) · 10.6 KB

device-smartwares-cip-37210.md

File metadata and controls

222 lines (181 loc) · 10.6 KB
Raw

OpenIPC Wiki

Table of Content

Smartwares CIP-37210

Device info

System Description
SoC HI3518EV200
Sensor OmniVision OV9732
Flash 16Mb (Winbond 25Q128JVSQ)
WiFi RTL8188FU

Step-by-step flashing guide

Beside the camera you'll need the following tools:

  • PH0 screwdriver or bit
  • Small blade screwdriver, e.g. 0.6 × 3.5 mm
  • A USB to TTL adapter for UART communication. (I used a CP2102 based device, but there are many other good options)
  • A microSD card (I used an old 2 GB one)
  • Some jumper wires
  • A multimeter
  • A computer running GNU/Linux

The preferred method to flash an OpenIPC camera is via tftp, but the CIP-37210 does not have an ethernet port. Another problem is that the stock u-boot is password protected and fatload (reading access to a FAT filesystem) does not work.

Because of that we will need to combine two methods deviating from the standard procedure to flash the Smartwares CIP-37210: The burn utility to directly boot into a u-boot bootloader compiled by the OpenIPC project to be able to flash from a microSD card and of course the flashing from a microSD card.

Opening the device

Unscrew the visbile phillips screw on the back of the camera's stand with the PH0 screwdriver. unscrew

Use the blade screwdriver to pry open the camera's case, where the stand was attached: pry_open

Establishing the UART connection

After opening the device, it's time to establish the UART connection. Power on the open camera with the included micro USB power supply. Now it's time to check the suspicious 4 pin holes on top of the pcb: Measure the voltage of the pin holes with your multimeter, by connecting them to GND (I used one of the pads around the screws in the middle).

I found two pin holes with 3.3 V, one pin hole with slightly less than 3.3 V and one pin hole with 0 V. Now it's time to watch the 3.3 V pins during boot – the one with oscillating voltage is the TX pin and the stable 3.3 V pin is the Vcc.

In summary: The pin hole closest to the black screw is RX, the one next to it is TX, the one next to it is GND. Connect GND to GND, TX to RX and RX to TX.

uart_cip-37210

I used simple male-to-female DuPont jumper wires to connect to the pin holes. There are of course better solutions like soldering a connector onto the pin holes or using test hooks, but as long the jumper wires don't touch, it will work fine.

uart_cip-37210_action

Saving the stock firmware

Before flashing OpenIPC it might be clever to save the stock firmware, in case you don't like OpenIPC and want to roll back or brick something. Since tftp is not possible we will save the contents of the flash to a microSD card. Since the device runs Linux you don't need to worry about formatting the microSD card now. Boot the camera while connected to your USB to TTL adapter and start screen:

sudo screen -L /dev/ttyUSB0 115200

Now it's time to login as root with the password I81ou812 I found on the internet. The microSD card got mounted automatically to the mount point /mnt/sd/, so lets make a new directory on the sd card and dump the contents of the flash:

mkdir /mnt/sd/image
for mtd in $(ls /dev/mtdblock*); do dd if=${mtd} of=/mnt/sd/image/${mtd##/*/}.bin; done

You may want to repeat this step with another folder and compare the md5 checksums of the binary files to assure that the dump was successful. Exit screen with C-a followed by d, insert the microSD card back into your computer and backup the binaries.

Flashing OpenIPC

Time to format the microSD card, so u-boot will be able to fatload the image. Those steps may vary depending on your Linux distribution. There is already a script which works on Debian Sid, but sadly not on my machine. (Different fdisk version and different naming of the device and partitions). Those are the commands I ran:

# create the partition table
sudo parted /dev/mmcblk0 mklabel msdos
# create first partition
sudo parted /dev/mmcblk0 mkpart primary fat32 1MB 64MB
sudo mkfs.vfat -F32 /dev/mmcblk0p1
# create second partition
sudo parted /dev/mmcblk0 mkpart primary fat32 64MB 128MB
sudo mkfs.vfat -F32 /dev/mmcblk0p2

Now it's time to mount the first partition and download the correct firmware and copy it on the mounted partition. Umount the partition and insert the microSD card into the camera.

Next, the burn utility needs to be set up:

git clone https://github.com/OpenIPC/burn
cd burn
sudo pip install -r requirements.txt

Now we need to download the correct uboot-binary

wget -P ./u-boot/ https://github.com/OpenIPC/firmware/releases/download/latest/u-boot-hi3518ev200-universal.bin

Make sure, that no process is blocking your USB to TTL adapter:

sudo lsof /dev/ttyUSB0

Kill the process if necessary:

sudo kill 230002

Power off the camera and also disconnect and reconnect your USB to TTL adapter. Now enter the following command and power on the camera:

./burn --chip hi3518ev200 --file=./uboot/u-boot-hi3518ev200-universal.bin --break; screen -L /dev/ttyUSB0 115200

Hit any key to stop autoboot and you are greeted by the OpenIPC u-boot shell!

OpenIPC #

First we need to check, if our microSD card is ready to use:

fatls mmc 0

The following output is expected:

 16777216   openipc-hi3518ev200-ultimate-16mb.bin

1 file(s), 0 dir(s)

Nice! Now it's time to load the binary into the memory. The variables are environment variables the OpenIPC u-boot knows to resolve, so you just need to copy and paste:

mw.b ${baseaddr} 0xff 0x1000000; fatload mmc 0:1 ${baseaddr} openipc-${soc}-ultimate-16mb.bin

This should result in the following output:

reading openipc-hi3518ev200-ultimate-16mb.bin

16777216 bytes read

Now it's time to write and keep your fingers crossed:

sf probe 0; sf erase 0x0 0x1000000; sf write ${baseaddr} 0x0 ${filesize}

The expected output looks like this:

16384 KiB hi_fmc at 0:0 is now current device
Erasing at 0x1000000 -- 100% complete.
Writing at 0x1000000 -- 100% complete.

It anything goes wrong here, don't power off the device and ask the mentioned Telegram group for help! Otherwise enter reset and get into the freshly flashed u-boot by hitting any key to stop autoboot. Run the following command and you are done:

run setnor16m

Now it's time for another reboot, so enter reset again and you'll be greeted like this:

Welcome to OpenIPC
openipc-hi3518ev200 login: root

    /######                                    /######  /#######    /######
   /##__  ##                                  |_  ##_/ | ##__  ##  /##__  ##
  | ##  \ ##   /######    /######   /#######    | ##   | ##  \ ## | ##  \__/
  | ##  | ##  /##__  ##  /##__  ## | ##__  ##   | ##   | #######/ | ##
  | ##  | ## | ##  \ ## | ######## | ##  \ ##   | ##   | ##____/  | ##
  | ##  | ## | ##  | ## | ##_____/ | ##  | ##   | ##   | ##       | ##    ##
  |  ######/ | #######/ |  ####### | ##  | ##  /###### | ##       |  ######/
   \______/  | ##____/   \_______/ |__/  |__/ |______/ |__/        \______/
             | ##
             | ##                              build
             |__/                             master+01a1348a, 2023-03-05

 Please help the OpenIPC Project to cover the cost of development and
 long-term maintenance of what we believe is going to become a stable,
 flexible Open IP Network Camera Framework for users worldwide.

 Your contributions could help us to advance the development and keep
 you updated on improvements and new features more regularly.

 Please visit https://openipc.org/sponsor/ to learn more. Thank you.

There is no root password set, so don't forget to set it with passwd after the first login!

If you are struggling with this tutorial and still want to try OpenIPC on a Smartwares CIP-37210, you can buy it with OpenIPC v2.2 firmware pre-installed at open collective.

Connecting to wifi

Now it's time to connect the camera to your 2.4 GHz Wi-Fi network. First of all, make sure that the firmware environment variables are set correctly. This is necessary so that udhcpc gets a DNS lease (because it is requesting $ipaddr) and the gateway is set correctly.

fw_printenv ipaddr
fw_printenv gatewayip
fw_printenv netmask

Set the correct values according to your needs, for example:

fw_setenv ipaddr 10.42.42.42

The last step is to configure the wlan0 interface:

vi /etc/network/interfaces

Delete or outcomment the eth0 block, the device doesn't have ethernet and the auto setting will slow down boot. Add the following lines to your interfaces file, alter your SSID and password accordingly.

auto wlan0
iface wlan0 inet dhcp
    pre-up echo 3 > /sys/class/gpio/export
    pre-up echo out > /sys/class/gpio/gpio3/direction
    pre-up echo 1 > /sys/class/gpio/gpio3/value
    pre-up modprobe mac80211
    pre-up sleep 1
    pre-up insmod /lib/modules/4.9.37/extra/rtl8188fu.ko
    pre-up sleep 1
    pre-up wpa_passphrase "YOUR_WIFI_SSID" "YOUR_PASSWORD" >/tmp/wpa_supplicant.conf
    pre-up sed -i '2i \\tscan_ssid=1' /tmp/wpa_supplicant.conf
    pre-up ifconfig wlan0 up
    pre-up wpa_supplicant -B -Dnl80211 -iwlan0 -c/tmp/wpa_supplicant.conf
    pre-up sleep 3
    post-down killall -q wpa_supplicant
    post-down echo 0 > /sys/class/gpio/gpio3/value
    post-down echo 3 > /sys/class/gpio/unexport

No it's time to check whether it's working:

ifup wlan0
ip addr

Check whether you can ping and ssh into the camera. Reboot and check, if the camera connects automatically to your wifi network. Reassamble the camera, now it's time so say goodbye to UART and use ssh and the web interface. (The credentials are root and the password you set earlier.)