Another 'How to unbrick' a Huisun Mini PTZ V2 ...

Good evening, thank you for your help. I started working and I reached this step:
amboot> show netboot
eth0_mac: 11: 22: 33: 01: 02: 03
eth0_ip: 192.168.0.190
eth0_mask: 255.255.255.0
eth0_gw: 192.168.0.1
eth1_mac: 00: 00: 00: 00: 00: 00
eth1_ip: 0.0.0.0
eth1_mask: 0.0.0.0
eth1_gw: 0.0.0.0
auto_dl: 1
tftpd: 192.168.0.101
pri_addr: 0x00208000
pri_file: hs_mtdblock3
pri_comp: 0
rmd_addr: 0x00800000
rmd_file: my_initrd.gz
rmd_comp: 0
dsp_addr: 0x00000000
dsp_file:
dsp_comp: 0
amboot> tftp boot console = ttyS0 root = / dev / ram rootfstype = ext2 init = / bin / busybox sh
link down ...
amboot> cd / tmp
'cd / tmp' is not a recognized command! Type 'help' for help ...
amboot>
I changed the data according to my LAN. He does not want to recognize the last command: cd / tmp and previously I do not know if it's OK response: link down. I'm waiting for you a solution.
 
I see that I do not have a link on the camera port to the router in my LAN. I tried to give him a ping to the camera IP, but he did not answer me, I went into the router and found nothing on the ARP List.
 
Maybe it does not synchronize with the tftp server, on the webcam I have the card slot, can not put the files there, and then they are launched? What format should the SD card have?
 
With 'link down' the Ethernet connection is not working, and tftp will not work and the camera will not boot.
There is no 'link detect' LED on the switch/router?
Try powering off and on few times to see if the link detect comes on.
If it does, try the boot command.

The command
cd /tmp
will only work when it has booted.

What do you get if you just use 'boot' at the amboot prompt?
 
On my router I have control LEDs, as I said we went in there, where I checked the ARP List, I pinged the camera but did not see the webcam. I've launched the boot command, I'm sending you the answer to the webcam:

amboot> boot
bst: 0x489D3636 1.3 (2016/12/29) 0x00000000 0x00000001 (2048)
bld: 0x82B96245 1.3 (2016/12/29) 0x00000000 0x00000000 (153264)
pri: 0x4DA5D661 0.1 (2016/12/29) 0x00208000 0x00000000 (1630992)
lnx: 0xBFAD9CCD 0.1 (2016/12/29) 0x00000000 0x00000001 (11075584)

loading pri to 0x00208000
rmd image absent... skipping
Jumping to 0x00208000 ...
cpux_jump: 0x00000000
initrd2_start: 0x00000000 initrd2_size: 0x00000000
kernelp: 0x00200000 kernels: 0x07E00000
idspp: 0x08000000 idsps: 0x08000000
flspinor addr = 0x00200000, size = 0x00DF0000
flspinor addr = 0x00050000, size = 0x001B0000
flspinor addr = 0x00040000, size = 0x00010000
flspinor addr = 0x00010000, size = 0x00030000
flspinor addr = 0x00000000, size = 0x00010000
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.10.73 (robot@dev-ubuntu-14) (gcc version 4.9.1 20140625 (prerelease) (crosstool-NG - Ambarella Linaro Multilib GCC [CortexA9 & ARMv6k] 2014.06) ) #594 PREEMPT Thu Dec 29 10:17:59 CST 2016
[ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: Ambarella S2L (Flattened Device Tree), model: Ambarella S2LM Kiwi Board
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] Ambarella: AHB = 0xe0000000[0xe0000000],0x01000000 0
[ 0.000000] Ambarella: APB = 0xe8000000[0xe8000000],0x01000000 0
[ 0.000000] Ambarella: PPM = 0x00000000[0xdfe00000],0x00200000 9
[ 0.000000] Ambarella: AXI = 0xf0000000[0xf0000000],0x00030000 0
[ 0.000000] Ambarella: DRAMC = 0xdffe0000[0xef000000],0x00020000 0
[ 0.000000] Ambarella: DBGBUS = 0xec000000[0xec000000],0x00200000 0
[ 0.000000] Ambarella: DBGFMEM = 0xee000000[0xee000000],0x01000000 0
[ 0.000000] Ambarella: IAVMEM = 0x08000000[ ],0x08000000
[ 0.000000] CPU: All CPU(s) started in SVC mode.
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32004
[ 0.000000] Kernel command line: console=ttyS0 root=/dev/mtdblock4 rw rootfstype=jffs2 init=/linuxrc
[ 0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[ 0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.000000] Memory: 126MB = 126MB total
[ 0.000000] Memory: 123380k/123380k available, 5644k reserved, 0K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] vmalloc : 0x88000000 - 0xff000000 (1904 MB)
[ 0.000000] lowmem : 0x80000000 - 0x87e00000 ( 126 MB)
[ 0.000000] modules : 0x7f000000 - 0x80000000 ( 16 MB)
[ 0.000000] .text : 0x80008000 - 0x803e4b2c (3955 kB)
[ 0.000000] .init : 0x803e5000 - 0x8040721c ( 137 kB)
[ 0.000000] .data : 0x80408000 - 0x80433b70 ( 175 kB)
[ 0.000000] .bss : 0x80433b70 - 0x80453934 ( 128 kB)
[ 0.000000] NR_IRQS:240
[ 0.000000] sched_clock: 32 bits at 54MHz, resolution 18ns, wraps every 79536ms
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] console [ttyS0] enabled
[ 0.232536] Calibrating delay loop... 597.60 BogoMIPS (lpj=2988032)
[ 0.292602] pid_max: default: 32768 minimum: 301
[ 0.297307] Mount-cache hash table entries: 512
[ 0.304401] CPU: Testing write buffer coherency: ok
[ 0.309562] Setting up static identity map for 0x802db940 - 0x802db998
[ 0.318466] devtmpfs: initialized
[ 0.323134] pinctrl core: initialized pinctrl subsystem
[ 0.328602] NET: Registered protocol family 16
[ 0.333830] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.341261] L310 cache controller enabled
[ 0.345262] l2x0: 8 ways, CACHE_ID 0x410000c8, AUX_CTRL 0x32020000, Cache size: 131072 B
[ 0.354958] ambarella-pinctrl e8009000.pinctrl: Ambarella pinctrl driver registered
[ 0.363010] ambarella-gpio gpio.0: Ambarella GPIO driver registered
[ 0.373419] bio: create slab <bio-0> at 0
[ 0.378571] ambarella-dma e0005000.dma: Ambarella DMA Engine
[ 0.384518] ####spi by sy 20160910
[ 0.388135] ambarella-spi e0020000.spi: master is unqueued, this is deprecated
[ 0.396229] ambarella-spi e0020000.spi: ambarella SPI Controller 0 created
[ 0.404781] ambarella-i2c e8003000.i2c: Ambarella I2C adapter[0] probed!
[ 1.909965] ambarella-i2c e8007000.i2c: No ACK from address 0xe8, 0:0!
[ 1.916481] pca953x 2-0074: failed reading register
[ 1.921367] pca953x: probe of 2-0074 failed with error -16
[ 1.926844] ambarella-i2c e8007000.i2c: Ambarella I2C adapter[2] probed!
[ 1.934259] Switching to clocksource ambarella-cs-timer
[ 1.946861] ambarella-sd e0002000.sdmmc0: Slot0 use bounce buffer[0x87720000<->0x07920000]
[ 1.955158] ambarella-sd e0002000.sdmmc0: Slot0 req_size=0x00020000, segs=32, seg_size=0x00020000
[ 1.964028] ambarella-sd e0002000.sdmmc0: Slot0 use ADMA
[ 2.039584] ambarella-sd e0002000.sdmmc0: 1 slots @ 50000000Hz
[ 2.045573] NET: Registered protocol family 2
[ 2.050919] TCP established hash table entries: 1024 (order: 1, 8192 bytes)
[ 2.057885] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[ 2.065361] TCP: Hash tables configured (established 1024 bind 1024)
[ 2.071783] TCP: reno registered
[ 2.075003] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 2.080849] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 2.087282] NET: Registered protocol family 1
[ 2.091955] RPC: Registered named UNIX socket transport module.
[ 2.097858] RPC: Registered udp transport module.
[ 2.102593] RPC: Registered tcp transport module.
[ 2.107275] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 2.114095] ambarella-adc e801d000.adc: Ambarella ADC driver init
[ 2.121866] jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 2.128084] msgmni has been set to 240
[ 2.133247] NET: Registered protocol family 38
[ 2.137766] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)
[ 2.145313] io scheduler noop registered
[ 2.149220] io scheduler deadline registered
[ 2.153529] io scheduler cfq registered (default)
[ 2.158561] e8005000.uart: ttyS0 at MMIO 0xe8005000 (irq = 9) is a ambuart
[ 2.166448] brd: module loaded
[ 2.172312] loop: module loaded
[ 2.175705] Ambarella read-only mtdblock
[ 2.179885] 5 ofpart partitions found on MTD device amba_spinor
[ 2.185786] Creating 5 MTD partitions on "amba_spinor":
[ 2.191028] 0x000000000000-0x000000010000 : "bst"
[ 2.196491] 0x000000010000-0x000000040000 : "bld"
[ 2.201939] 0x000000040000-0x000000050000 : "ptb"
[ 2.207318] 0x000000050000-0x000000200000 : "pri"
[ 2.212768] 0x000000200000-0x000000ff0000 : "lnx"
[ 2.218157] SPI NOR Controller probed
[ 2.279527] libphy: Ambarella MII Bus: probed
[ 2.283882] mdio_bus e000e000.etherne: /ahb@e0000000/ethernet@e000e000/phy@0 has invalid PHY address
[ 2.293016] mdio_bus e000e000.etherne: scan phy phy at address 0
[ 2.299089] mdio_bus e000e000.etherne: scan phy phy at address 1
[ 2.305175] mdio_bus e000e000.etherne: scan phy phy at address 2
[ 2.311257] mdio_bus e000e000.etherne: scan phy phy at address 3
[ 2.317325] mdio_bus e000e000.etherne: scan phy phy at address 4
[ 2.323405] mdio_bus e000e000.etherne: scan phy phy at address 5
[ 2.329485] mdio_bus e000e000.etherne: scan phy phy at address 6
[ 2.335553] mdio_bus e000e000.etherne: scan phy phy at address 7
[ 2.341631] mdio_bus e000e000.etherne: scan phy phy at address 8
[ 2.347698] mdio_bus e000e000.etherne: scan phy phy at address 9
[ 2.353777] mdio_bus e000e000.etherne: scan phy phy at address 10
[ 2.359943] mdio_bus e000e000.etherne: scan phy phy at address 11
[ 2.366097] mdio_bus e000e000.etherne: scan phy phy at address 12
[ 2.372262] mdio_bus e000e000.etherne: scan phy phy at address 13
[ 2.378416] mdio_bus e000e000.etherne: scan phy phy at address 14
[ 2.384582] mdio_bus e000e000.etherne: scan phy phy at address 15
[ 2.390748] mdio_bus e000e000.etherne: scan phy phy at address 16
[ 2.396902] mdio_bus e000e000.etherne: scan phy phy at address 17
[ 2.403067] mdio_bus e000e000.etherne: scan phy phy at address 18
[ 2.409222] mdio_bus e000e000.etherne: scan phy phy at address 19
[ 2.415388] mdio_bus e000e000.etherne: scan phy phy at address 20
[ 2.421553] mdio_bus e000e000.etherne: scan phy phy at address 21
[ 2.427707] mdio_bus e000e000.etherne: scan phy phy at address 22
[ 2.433872] mdio_bus e000e000.etherne: scan phy phy at address 23
[ 2.440038] mdio_bus e000e000.etherne: scan phy phy at address 24
[ 2.446192] mdio_bus e000e000.etherne: scan phy phy at address 25
[ 2.452356] mdio_bus e000e000.etherne: scan phy phy at address 26
[ 2.458510] mdio_bus e000e000.etherne: scan phy phy at address 27
[ 2.464676] mdio_bus e000e000.etherne: scan phy phy at address 28
[ 2.470841] mdio_bus e000e000.etherne: scan phy phy at address 29
[ 2.476995] mdio_bus e000e000.etherne: scan phy phy at address 30
[ 2.483160] mdio_bus e000e000.etherne: scan phy phy at address 31
[ 2.489317] ambarella-eth e000e000.ethernet: No PHY device.
[ 2.494962] PPP generic driver version 2.4.2
[ 2.499397] PPP BSD Compression module registered
[ 2.504117] PPP Deflate Compression module registered
[ 2.509161] PPP MPPE Compression module registered
[ 2.513951] NET: Registered protocol family 24
[ 2.518405] SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256).
[ 2.525444] CSLIP: code copyright 1989 Regents of the University of California.
[ 2.533069] ambarella-rtc e8015000.rtc: rtc core: registered rtc-ambarella as rtc0
[ 2.540797] i2c /dev entries driver
[ 2.544900] TCP: cubic registered
[ 2.548201] Initializing XFRM netlink socket
[ 2.552514] NET: Registered protocol family 17
[ 2.557019] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[ 2.564677] ThumbEE CPU extension supported.
[ 2.569775] ambarella-rtc e8015000.rtc: setting system clock to 1970-01-01 08:18:22 UTC (29902)
[ 2.578783] ##########485 test
[ 4.091604] VFS: Mounted root (jffs2 filesystem) on device 31:4.
[ 4.097795] devtmpfs: mounted
[ 4.101022] Freeing unused kernel memory: 136K (803e5000 - 80407000)
/linuxrc: symbol lookup error: /lib/libc.so.6: undefined symbol: stderr, version GLIBC_2.4
[ 4.629568] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00
[ 4.629568]
[ 4.638690] CPU: 0 PID: 1 Comm: linuxrc Not tainted 3.10.73 #594
[ 4.644717] [<800123e4>] (unwind_backtrace+0x0/0x118) from [<80010c64>] (show_stack+0x10/0x14)
[ 4.653316] [<80010c64>] (show_stack+0x10/0x14) from [<802d5df4>] (panic+0x88/0x1c4)
[ 4.661047] [<802d5df4>] (panic+0x88/0x1c4) from [<80021624>] (do_exit+0x410/0x844)
[ 4.668687] [<80021624>] (do_exit+0x410/0x844) from [<8002289c>] (do_group_exit+0x4c/0xc8)
[ 4.676932] [<8002289c>] (do_group_exit+0x4c/0xc8) from [<80022928>] (__wake_up_parent+0x0/0x18)
 
Viorel Brinzac said:
I've launched the boot command, I'm sending you the answer to the webcam:
Click to expand...
That changes everything - there is not a lot wrong with the kernel at least, though there may be a problem with the root file system and its associated kernel libraries.
You do not need to do anything with the recovery instructions that I sent above.

Viorel Brinzac said:
[ 2.293016] mdio_bus e000e000.etherne: scan phy phy at address 0
[ 2.299089] mdio_bus e000e000.etherne: scan phy phy at address 1
[ 2.305175] mdio_bus e000e000.etherne: scan phy phy at address 2
[ 2.311257] mdio_bus e000e000.etherne: scan phy phy at address 3
Click to expand...
These entries, and also the 'link down' seen at the amboot bootloader, indicate that the ethernet interface is not working.
I believe that may be the root cause of the problem with the camera - a damaged ethernet interface.
But just in case it is some kind of initiallisation problem, which I have seen, power cycle the camera a few times and check each time if the ethernet scan failure still occurs.
 
As much as I can understand, when the webcam was functional, the PTZ was making a move, since it's failing to make the tour. However, can not upload those files sent from the SD card, as well as a new firmware?
 
Viorel Brinzac said:
when the webcam was functional, the PTZ was making a move, since it's failing to make the tour.
Click to expand...
Yes, but right now the kernel is aborting as it can't load the needed modules, so it does not get far enough to load up the main app which would operate the PTZ.
Whilst that does indicate that the root file system has a problem, the ethernet interface problem occurs before that point, so I'm assuming that's a fatal error.

Viorel Brinzac said:
However, can not upload those files sent from the SD card, as well as a new firmware?
Click to expand...
If you can get to a root shell, at this point :
tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/busybox sh

At this point, if all is well, the camera Linux should start and give a root # prompt.
Click to expand...
then it may be possible to transfer mtdblock4 (the root file system) from the SD card instead of using tftp.
At the root shell prompt, check if the SD card gets automatically mounted with the 'mount' command.
And if not mounted, check if it is visible by inspecting the result of
ls -al /dev/mm*
looking for something like mmc01
 
I can copy the files sent to you on the SD card, but I do not know what file format it should have: NTFS, Fat32, and then put it in the camera slot. The sent order does not work.
amboot> ls -al /dev/mm*
'ls' is not a recognized command! Type 'help' for help...
amboot>
 
I have come to an end of my knowledge, I have not learned linux and I do not know what to do. There are other solutions to solve the problem with the link on the network "link down ..."
 
Viorel Brinzac said:
I have come to an end of my knowledge, I have not learned linux and I do not know what to do.
Click to expand...
It can be a cryptic and complicated topic for everyone.
But well done for trying, it's not easy to do over back and forth forum posts.
At the amboot > prompt - the bootloader is running. That's a bit like the BIOS in a PC. It's not the operating system, just a small program that initiallises the hardware and is used to find and launch the main operating system.

The root shell is the command-level interface that can be accessed when the full operating system has successfully started up.

alastairstevenson said:
tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/busybox sh
Click to expand...
What is the end result of using the command above at the 'amboot > ' prompt?
 
the cause of the failure was an electrical discharge on the audio port.
Click to expand...

Perhaps there is some collateral damage from this. The audio goes straight to the main processor, as does the Ethernet interface after the coupling transformers and interface chip.
 
I have a question: are webcams that can load their good firmware directly from the SD card without having a serial connection with a PC? And what format should it have?
 
These commands that I specified earlier would load the firmware using tftp.
Nearly the same commands could also load the same firmware from an SD card, if it was 'mounted' as a file system.
mtdblock3 is the Linux kernel.
mtdblock4 is the root file system.
Code: 
At this point, if all is well, the camera Linux should start and give a root # prompt.

cd /tmp
tftp -g -r mtdblock3 192.168.1.21
flashcp mtdblock3 /dev/mtd3
tftp -g -r mtdblock4 192.168.1.21
flashcp mtdblock4 /dev/mtd4
reboot

But with no ethernet interface, the camera would not be able to be used.
 
Ok, then I can hope with your help to try installing the necessary files on the SD card with the set of related commands, this way we bypass the network side and ..can be repaired.
 
You must log in or register to reply here.
Top Bottom