Jump to content

Schlbuditz

Members
  • Content Count

    3
  • Joined

  • Last visited

Everything posted by Schlbuditz

  1. Hi there! I have a problem, I have this Anran IP camera: http://www.anranhtshop.com/views.asp?hw_id=1132 (IPC model with HI3516C SoC) and was doing a firmware update per Anrans instructions via e-mail the other day. (This firmware https://pan.sohu.net/f/MTY4MDQsaGR1Ym0.htm (IPC53H20L V4.0.R11.00001532.1)) and I was upgrading from V4.02.R11.00001532.10010 with build date 2014-02-26. The update bricked the camera and it doesn´t get an IP-address anymore. I have been able to connect to the camera using a serial cable and connecting to U-boot works fine, but I can´t get further. I have the .bin file for the firmware for both the advised firmware by Anran and an older .bin-file with the same build date as the one that was on the camera from the beginning. Is it possible to rebuild this to the required update.img-file to flash via serial and TFTP-server? Or better, does anyone know where I can get the file? Anran doesn´t answer me anymore, convinient huh? If I extract the .img-files from the .bin and rename them to update.img I can upload them to the camera using the run up command and flash them one by one, but the camera still doesn´t work after that. Worth to mention is that I can only do this with the firmware with build date 2014-02-26. If I try with the newer firmware, I get messages from U-boot saying it doesn´t match with the memory or something like that. One other thing, if I ping my router from U-boot, it actually shows up in the routers device list for a minute or so. Everything is there, and I feel that it has to be possible to recover it in some way? Please help me, I will be forever grateful! (And please forgive my english, it´s not my native language)
  2. This is the result of the fload command: hisilicon # fload CFG_BOOT_ADDR:0x58080000 16384 KiB hi_sfc at 0:0 is now current device ### boot load complete: 3064516 bytes loaded to 0x82000000 ### SAVE TO 80008000 ! This is the startup message and then it stops. After a while the camera reboots by it self. U-Boot 2010.06-svn (Dec 31 2013 - 11:09:55) DRAM: 256 MiB Check spi flash controller v350... Found Spi(cs1) ID: 0xEF 0x40 0x18 0x00 0x00 0x00 Spi(cs1): Block:64KB Chip:16MB Name:"W25Q128B" MMC: MMC FLASH INIT: No card on slot! envcrc 0xad194eb7 ENV_SIZE = 0x3fffc In: serial Out: serial Err: serial Press Ctrl+C to stop autoboot CFG_BOOT_ADDR:0x58080000 16384 KiB hi_sfc at 0:0 is now current device ### boot load complete: 3064516 bytes loaded to 0x82000000 ### SAVE TO 80008000 ! ## Booting kernel from Legacy Image at 82000000 ... Image Name: linux Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 3064452 Bytes = 2.9 MiB Load Address: 80008000 Entry Point: 80008000 load=0x80008000,_bss_end=808c1f30,image_end=802f4284,boot_sp=807971d8 Loading Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. The camera does not have an SD-slot.
  3. Wow, thanks for trying to help me! iminfo is an unknown command, as well as tftpboot help shows this: ? - alias for 'help' base - print or set address offset boot - boot default, i.e., run 'bootcmd' bootd - boot default, i.e., run 'bootcmd' bootm - boot application image from memory bootp - boot image via network using BOOTP/TFTP protocol cmp - memory compare cp - memory copy crc32 - checksum calculation ext2load- load binary file from a Ext2 filesystem ext2ls - list files in a directory (default /) fatinfo - print information about filesystem fatload - load binary file from a dos filesystem fatls - list files in a directory (default /) fload - fload - load binary file from a filesystem image for system boot flwrite - SPI flash sub-system getinfo - print hardware information go - start application at address 'addr' help - print command description/usage lip - lip - set local ip address but not save to flash loadb - load binary file over serial line (kermit mode) loady - load binary file over serial line (ymodem mode) loop - infinite loop on address range mac - mac - set mac address and save to flash md - memory display mii - MII utility commands mm - memory modify (auto-incrementing address) mmc - MMC sub system mmcinfo - mmcinfo <dev num>-- display MMC info mtest - simple RAM read/write test mw - memory write (fill) nm - memory modify (constant address) ping - send ICMP ECHO_REQUEST to network host printenv- print environment variables rarpboot- boot image via network using RARP/TFTP protocol reset - Perform RESET of the CPU run - run commands in an environment variable saveenv - save environment variables to persistent storage setenv - set environment variables sf - SPI flash sub-system sip - sip - set server ip address but not save to flash tftp - tftp - download or upload image via network using TFTP protocol usb - USB sub-system usbboot - boot from USB device version - print monitor version If it helps, the command printenvshows this: bootargs=mem=64M console=ttyAMA0,115200 root=/dev/mtdblock1 rootfstype=cramfs mt dparts=hi_sfc:512K(boot),5M(romfs),7424K(user),1536K(web),256K(custom),256K(logo ),1280K(mtd) bootcmd=fload;bootm 0x82000000 bootdelay=1 baudrate=115200 ipaddr=192.168.1.10 serverip=192.168.1.107 netmask=255.255.255.0 bootfile="uImage" da=tftp 0x82000000 u-boot.bin.img;sf probe 0;flwrite du=tftp 0x82000000 user-x.cramfs.img;sf probe 0;flwrite dr=tftp 0x82000000 romfs-x.cramfs.img;sf probe 0;flwrite dw=tftp 0x82000000 web-x.cramfs.img;sf probe 0;flwrite dl=tftp 0x82000000 logo-x.cramfs.img;sf probe 0;flwrite dc=tftp 0x82000000 custom-x.cramfs.img;sf probe 0;flwrite up=tftp 0x82000000 update.img;sf probe 0;flwrite ua=mw.b 0x82000000 ff 1000000;tftp 0x82000000 upall_verify.img;sf probe 0;flwrit e tk=tftp 0x82000000 uImage; bootm 0x82000000 dd=tftp 0x82000000 mtd-x.jffs2.img;sf probe 0;flwrite ethaddr=00:00:23:34:45:66 ID=000000000000000000 restore=0 stdin=serial stdout=serial stderr=serial verify=n ver=U-Boot 2010.06-svn (Dec 31 2013 - 11:09:55)
×