ipctool upload bug #232

Can not send report with backup

./ipctool upload --note club-HNCP-W4AP

chip:
vendor: HiSilicon
model: 3516CV300

board:
vendor: Xiongmai
possible-IR-cut-GPIO: 0,1,2,24,26,29,48,63,64,66
ethernet:
mac: " "
u-mdio-phyaddr: 1
phy-id: 0x001cc816
d-mdio-phyaddr: 0
rom:

• type: nor
  block: 64K
  partitions:
  • name: boot
    size: 0x40000
    sha1: 77800f8b
    contains:
    • name: uboot-env
      offset: 0x20000
  • name: defcfg
    size: 0x10000
    sha1: a2eb411e
  • name: kernel
    size: 0x1f0000
    sha1: f9f73e28
  • name: root
    size: 0x960000
    path: /,squashfs
    sha1: 11e3a2e7
  • name: custom
    size: 0x400000
    path: /mnt/special,squashfs
    sha1: ac743e3c
  • name: config
    size: 0x60000
    path: /mnt/mtd,jffs2,rw
    size: 16M
    addr-mode: 3-byte
    ram:
    total: 256M
    media: 144M
    firmware:
    kernel: "3.18.20 (Thu Dec 27 21:06:54 CST 2018)"
    toolchain: gcc version 4.9.4 20150629 (prerelease) (Hisilicon_v500_20150831)
    libc: uClibc 0.9.33.2
    sdk: "Hi3516CV300_MPP_V1.0.0.0 B010 Release (May 19 2018, 19:56:23)"
    main-app: hunter
    sensors:
• vendor: Sony
  model: IMX307
  control:
  bus: 0
  type: i2c
  addr: 0x34
  data:
  type: LVDS
  lane-id:
  - 0
  - 1
  - 2
  - 3
  lvds-wdr-en: 0
  lvds-wdr-mode: 0
  lvds-wdr-num: 0
  raw-data-type: RAW_DATA_12BIT
  sync-mode: LVDS_SYNC_MODE_SAV
  data-endian: LVDS_ENDIAN_BIG
  sync-code-endian: LVDS_ENDIAN_BIG
  sync-code:
  - - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  - 0xab0, 0xb60, 0x800, 0x9d0
  clock: 37.125MHz

This sends the report above to http://openipc.org/api/v1/reports, over plain HTTP (stock camera firmware has no TLS).
It is reviewed before it is published, and the MAC, chip ID and cloud ID in the report are replaced with hashes.

A backup of the whole flash, sent with the report, is what porting OpenIPC
to this board starts from. It holds everything the camera keeps: its
settings, Wi-Fi keys, passwords, cloud IDs.
no send the report only
private send the backup too; only OpenIPC's maintainers can read it
public send the backup too, and let anyone download it once the
report is reviewed, with the MAC, chip ID and cloud ID in clear
Send a backup? [no/private/public]: public
Backing up 6 partitions, 16384 KB.
Sending 0%

and stay zero %

--host openipc.ru

Backing up 6 partitions, 16384 KB.
Sending 100%
openipc.ru did not take the report (502): openipc.org answered 502 without an explanation

--host openipc.kz

Backing up 6 partitions, 16384 KB.
Sending 100%
openipc.kz did not take the report (413): openipc.org answered 413 without an explanation

(https://t.me/c/1247643198/358989/359243)