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

Hello, With excuses I found in a post to your order:
"boot console=ttyS0 root=/dev/mtdblock4 rw rootfstype=jffs2 init=/bin/sh" replacing the existing one: "boot console=ttyS0 root=/dev/mtdblock4 rw rootfstype=jffs2 init=/linuxrc" used it and now does not pass this pass:
amboot> reboot
▒
the spinor flash ID is 0xC21820C2
### PTB check by sy 20161119
### gpio init ###
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
What happened? Good or bad?
 
Viorel Brinzac said:
What happened? Good or bad?
Click to expand...
It's not getting as far as booting the kernel.
Which did happen OK when you used the 'boot' command by itself previously.
This would be the normal startup when the kernel is booted.
Code: 
pinor flash ID is 0xC21820C2
###gpio init###
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) ) #6 PREEMPT Wed Nov 11 13:58:11 CST 2015
[    0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7), cr=10c53c7d
 
I checked if the link is high, but ..
___ ___ _________ _
/ _ \ | \/ || ___ \ | |
/ /_\ \| . . || |_/ / ___ ___ | |_
| _ || |\/| || ___ \ / _ \ / _ \ | __|
| | | || | | || |_/ /| (_) || (_) || |_
\_| |_/\_| |_/\____/ \___/ \___/ \__|
----------------------------------------------------------
Amboot(R) Ambarella(R) Copyright (C) 2004-2014
Boot From: SPI NOR
SYS_CONFIG: 0x3000404B POC: 101
Cortex freq: 600000000
iDSP freq: 216000000
Dram freq: 528000000
Core freq: 216000000
AHB freq: 108000000
APB freq: 54000000
UART freq: 24000000
SD freq: 50000000
SDIO freq: 50000000
SDXC freq: 60000000
amboot> tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/busybox sh
'tftp' is not a recognized command! Type 'help' for help...
amboot> tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/busybox sh
link down ...
amboot>
Other tests, kernel loading, etc. can be done.
 
With the rigorous excuses I come back with my problem. Today I looked closely at my router, more precisely at the port on which the webcam is located, and I noticed that when I energize the power supply and remain locked during the boot, the LED is on, but when I go through the ESCAPE procedure on AMBOOT, the LED is off. This makes me think that the ETH port on the physical webcam is good, but with internal commands it fails to get up. Do you have any suggestions yet?
 
If it would be possible to get to the Linux shell by the use of the
init=/bin/sh
boot param, then the command
ifconfig eth0 192.168.1.64 up
would normally configure the Ethernet port.
 
spinor flash ID is 0xC21820C2
###PTB check by sy 20161119

___ ___ _________ _
/ _ \ | \/ || ___ \ | |
/ /_\ \| . . || |_/ / ___ ___ | |_
| _ || |\/| || ___ \ / _ \ / _ \ | __|
| | | || | | || |_/ /| (_) || (_) || |_
\_| |_/\_| |_/\____/ \___/ \___/ \__|
----------------------------------------------------------
Amboot(R) Ambarella(R) Copyright (C) 2004-2014
Boot From: SPI NOR
SYS_CONFIG: 0x3000404B POC: 101
Cortex freq: 600000000
iDSP freq: 216000000
Dram freq: 528000000
Core freq: 216000000
AHB freq: 108000000
APB freq: 54000000
UART freq: 24000000
SD freq: 50000000
SDIO freq: 50000000
SDXC freq: 60000000
amboot>
 
amboot> tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/busybox sh
link down ...
amboot>
amboot> tftp boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/sh
link down ...
amboot>
 
amboot> boot console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/sh
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 ...
cmdline: console=ttyS0 root=/dev/ram rootfstype=ext2 init=/bin/sh
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
 
Good evening, with excuses come back to my problem. Post # 59 refers to folding the tftp server, but I do not come to it because I have "Link down". I want to use an SD card with these files on it, but I do not know what format the card should have ex. ntfs, fat32, or other format, and what capacity should they have. I also do not know what commands I give it to rewrite these files into the flash IP camera memory. Please make an effort to help me with this problem.
 
I'd guess that FAT32 will be most likely to be supported.
Copy the files to the SD card, and at the root shell command, see if the card has been automatically recognised and mounted with the 'mount' command.
Check if the device exists by looking at the result of the command
ls -l /dev
and look for a device that may begin with something like mmc
 
You must log in or register to reply here.
Top Bottom