Doorbell boot loop

This Forum its to discuss the new Smart Home Devices.
Post Reply
mrsc
Posts: 1
Joined: Tue May 19, 2020 1:32 pm

Doorbell boot loop

Post by mrsc »

Hi - I have a AD110 Doorbell that have stopped working and I cannot do a hardreset. I opened it op and found the UART port. From that I found that linux kernel is not booting.
Is there a way to flash the firmware from USB or SD-card?
Where can I download the firmware for the doorbell?
Is there another way to get the doorbell to work again?

UART terminal:

Code: Select all

System startup


System startup


U-Boot 2010.06-svn5172 (Nov 14 2017 - 16:12:11)
DRAM: 64 MiB
gBootLogPtr:80b80008.
Check Flash Memory Controller v100 ... Found
SPI Nor(cs 0) ID: 0xc8 0x40 0x18
Block:64KB Chip:16MB Name:"GD25Q128"
SPI Nor total size: 16MB
hifmc100_get_erasesize:10000.
Fail to get uboot hd.
partition file version 2
rootfstype squashfs root /dev/mtdblock5
gParameter[0]:node=bootargs, parameter=mem=190M console=ttyS0,115200 root=/dev/mtdblock4 rootfstype=squashfs.
gParameter[1]:node=sdupdate, parameter=gpio=10 offset=0 ledtype=exLed.
In: serial
Out: serial
Err: serial
TEXT_BASE:81000000
gpio:10, offset:0x0, ledtype:exLed
MMC: Hisilicon ETH net controler
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Try again use backup_serverip
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Failed to get info.txt
Fail to get info file!
Init error!
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1248360 Bytes = 1.2 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ...OK
OK
partition file version 2
rootfstype squashfs root /dev/mtdblock5
cmdLine mem=190M console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs
crashflasg:1, logmagic:54410011.

Starting kernel ...
Uncompressing Linux... done, booting the kernel.



System startup


System startup


U-Boot 2010.06-svn5172 (Nov 14 2017 - 16:12:11)
DRAM: 64 MiB
gBootLogPtr:80b80008.
Check Flash Memory Controller v100 ... Found
SPI Nor(cs 0) ID: 0xc8 0x40 0x18
Block:64KB Chip:16MB Name:"GD25Q128"
SPI Nor total size: 16MB
hifmc100_get_erasesize:10000.
Fail to get uboot hd.
partition file version 2
rootfstype squashfs root /dev/mtdblock5
gParameter[0]:node=bootargs, parameter=mem=190M console=ttyS0,115200 root=/dev/mtdblock4 rootfstype=squashfs.
gParameter[1]:node=sdupdate, parameter=gpio=10 offset=0 ledtype=exLed.
In: serial
Out: serial
Err: serial
TEXT_BASE:81000000
gpio:10, offset:0x0, ledtype:exLed
MMC: Hisilicon ETH net controler
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Try again use backup_serverip
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Failed to get info.txt
Fail to get info file!
Init error!
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1248360 Bytes = 1.2 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ...OK
OK
partition file version 2
rootfstype squashfs root /dev/mtdblock5
cmdLine mem=190M console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs

Starting kernel ...
Uncompressing Linux... done, booting the kernel.
If I hold in the reset while connection power I get this:

Code: Select all


System startup


System startup


U-Boot 2010.06-svn5172 (Nov 14 2017 - 16:12:11)
DRAM: 64 MiB
gBootLogPtr:80b80008.
Check Flash Memory Controller v100 ... Found
SPI Nor(cs 0) ID: 0xc8 0x40 0x18
Block:64KB Chip:16MB Name:"GD25Q128"
SPI Nor total size: 16MB
hifmc100_get_erasesize:10000.
Fail to get uboot hd.
partition file version 2
rootfstype squashfs root /dev/mtdblock5
gParameter[0]:node=bootargs, parameter=mem=190M console=ttyS0,115200 root=/dev/mtdblock4 rootfstype=squashfs.
gParameter[1]:node=sdupdate, parameter=gpio=10 offset=0 ledtype=exLed.
In: serial
Out: serial
Err: serial
TEXT_BASE:81000000
gpio:10, offset:0x0, ledtype:exLed
MMC:
EMMC/MMC/SD controller initialization.
Card did not respond to voltage select!
No EMMC/MMC/SD device found !
Do not find sd card
Hisilicon ETH net controler
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Try again use backup_serverip
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
Failed to get info.txt
Fail to get info file!
Init error!
Hisilicon ETH net controler
miiphy_register: non unique device name '0:31'
miiphy_register: non unique device name '0:2'
MAC: 00-13-34-56-78-9A
Up/Down PHY not link.
## Booting kernel from Legacy Image at 82000000 ...
Image Name: Linux-3.4.35
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1248360 Bytes = 1.2 MiB
Load Address: 80008000
Entry Point: 80008000
Loading Kernel Image ...OK
OK
partition file version 2
rootfstype squashfs root /dev/mtdblock5
cmdLine mem=190M console=ttyS0,115200 root=/dev/mtdblock5 rootfstype=squashfs

Starting kernel ...
Uncompressing Linux... done, booting the kernel.
User avatar
Revo2Maxx
Site Admin
Posts: 6717
Joined: Sat Jun 15, 2019 3:05 pm

Re: Doorbell boot loop

Post by Revo2Maxx »

Well I can't say if there is or isn't one in Support for the Camera..

Hello and Welcome to the Forum..

Sadly I would said that is might be able to be replaced by RMA however it seems that you opened it and it may now not be covered because everything under normal use is able to be accessed without taking apart...

I can't say as I don't work for Amcrest I am only going on what I know when I have taken other peoples things apart I am always told No longer in Warranty. However most times I only take things apart that are long out of Warranty anyway lol...

Anyway might want to email support at amcrest and see if maybe they are willing to send you a FW that you can try and Flash..
Be Safe.
Post Reply