Avtech AVN801Z нет связи вдруг

Все вопросы по IP камерам, IP серверам и по программному обеспечению для IP видеонаблюдения.
UAP
Новичок
Сообщения: 9
Зарегистрирован: 22 окт 2017, 14:40

Re: Avtech AVN801Z нет связи вдруг

Сообщение UAP » 23 окт 2017, 00:29

Зачем ими делится? Они в общем доступе в архиве пошивки: fboot_4.bin, kernel_4.bin, AppImg_4.bin, xml_4.bin.
меню загрузчика содержит такие варианты:
TFTP Update BootLoader Firmware
TFTP Update Kernel Firmware
TFTP Update Application (AppImg)
TFTP Update XML
TFTP Update Initialize Bitmap
TFTP Update FullInOne Image

Аватара пользователя
VirtualLink
Специалист
Сообщения: 1846
Зарегистрирован: 09 апр 2016, 12:38

Re: Avtech AVN801Z нет связи вдруг

Сообщение VirtualLink » 23 окт 2017, 00:30

UAP писал(а):Зачем ими делится? Они в общем доступе в архиве пошивки: fboot_4.bin, kernel_4.bin, AppImg_4.bin, xml_4.bin.
меню загрузчика содержит такие варианты:
TFTP Update BootLoader Firmware
TFTP Update Kernel Firmware
TFTP Update Application (AppImg)
TFTP Update XML
TFTP Update Initialize Bitmap
TFTP Update FullInOne Image
Это хорошо, но как понимаете все точно знают где оно лежит и только мой вопрос оффтопом!

UAP
Новичок
Сообщения: 9
Зарегистрирован: 22 окт 2017, 14:40

Re: Avtech AVN801Z нет связи вдруг

Сообщение UAP » 23 окт 2017, 01:05

MP SPI-NOR Bootstrap v0.2
Decompress from TEMP_ADDR:0x04000000 image size=118834
Boot image offset: 0x0. Booting Image .....
0

U-Boot 2008.10-dirty (Nov 4 2011 - 13:57:56)

I2C: ready
DRAM: 128 MB
CustomerID : 0x81262107
Manufacturer ID : 0018
Device ID : 009F
Device Code 2 : 0018
Using default environment

flash no default environment
=== Normal boot ===
MAC addr: 00:0E:53:EB:26:65
In: serial
Out: serial
Err: serial
go...
---------------------------------------------------------
PLL1: 800 MHz PLL2: 540 MHz DDR: 800 MHz
CPU : 540 MHz HCLK: 270 MHz
H.264: 270 MHz MPEG4: 200 MHz
---------------------------------------------------------
Start GPIO initial... 01. 1. 2. 3. 4. 5. 6. 7. 8. 9. a. b. c. Finished.
Net: FTMAC110#0
SF: Got idcode ef 40 18
Press SPACE to abort autoboot in 1 seconds

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************

Прошивка http://www.avtech.su/img/filez/Firmware ... (1051).zip

UAP
Новичок
Сообщения: 9
Зарегистрирован: 22 окт 2017, 14:40

Re: Avtech AVN801Z нет связи вдруг

Сообщение UAP » 23 окт 2017, 12:42

Вообщем сделал, перепрошил через TFTP и камера заработала.

MP SPI-NOR Bootstrap v0.2
Decompress from TEMP_ADDR:0x04000000 image size=118834
Boot image offset: 0x0. Booting Image .....
0

U-Boot 2008.10-dirty (Nov 4 2011 - 13:57:56)

I2C: ready
DRAM: 128 MB
CustomerID : 0x81262107
Manufacturer ID : 0018
Device ID : 009F
Device Code 2 : 0018
Using default environment

flash no default environment
=== Normal boot ===
MAC addr: 00:0E:53:EB:26:65
In: serial
Out: serial
Err: serial
go...
---------------------------------------------------------
PLL1: 800 MHz PLL2: 540 MHz DDR: 800 MHz
CPU : 540 MHz HCLK: 270 MHz
H.264: 270 MHz MPEG4: 200 MHz
---------------------------------------------------------
Start GPIO initial... 01. 1. 2. 3. 4. 5. 6. 7. 8. 9. a. b. c. Finished.
Net: FTMAC110#0
SF: Got idcode ef 40 18
Press SPACE to abort autoboot in 1 seconds

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> 2
TFTP Configuration
ipaddr: 192.168.1.150
serverip: 192.168.1.100

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> T4
image name("AppImg.bin"):
Using eth0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.150
Filename 'AppImg.bin'.
Load address: 0x4000000
Loading: t RD_REQ, file: AppImg.bin
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
###############################
done
Bytes transferred = 7126936 (6cbf98 hex)
Firmware image "AppImg.bin" loaded
checksum: 0x3564AE23(RAM)
checksum: 0x3564AE23(Flash)
144 * 64k blocks will be erased (0x00600000 to 0x00F00000)
------------------------------------------------------------------------------------------------------------------------------------------------ done!
144 * 64k blocks will be writed (0x00600000 to 0x00F00000)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ done!
1 * 64k blocks will be erased (0x000A0000 to 0x000B0000)
- done!
1 * 64k blocks will be writed (0x000A0000 to 0x000B0000)
+ done!
emergency_recovery: 0x0

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> T1
image name("fboot.bin"):
Using eth0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.150
Filename 'fboot.bin'.
Load address: 0x4000000
Loading: t RD_REQ, file: fboot.bin
###########
done
Bytes transferred = 147962 (241fa hex)
Firmware image "fboot.bin" loaded
checksum: 0xFE8CCF(RAM)
checksum: 0xFE8CCF(Flash)
6 * 64k blocks will be erased (0x00000000 to 0x00060000)
------ done!
6 * 64k blocks will be writed (0x00000000 to 0x00060000)
++++++ done!
1 * 64k blocks will be erased (0x000A0000 to 0x000B0000)
- done!
1 * 64k blocks will be writed (0x000A0000 to 0x000B0000)
+ done!
emergency_recovery: 0x0

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> T3
image name("kernel.bin"):
Using eth0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.150
Filename 'kernel.bin'.
Load address: 0x4000000
Loading: t RD_REQ, file: kernel.bin
#################################################################
#################################################################
#################################################################
#######
done
Bytes transferred = 2960432 (2d2c30 hex)
Firmware image "kernel.bin" loaded
checksum: 0x167A8010(RAM)
checksum: 0x167A8010(Flash)
80 * 64k blocks will be erased (0x00100000 to 0x00600000)
-------------------------------------------------------------------------------- done!
80 * 64k blocks will be writed (0x00100000 to 0x00600000)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ done!
1 * 64k blocks will be erased (0x000A0000 to 0x000B0000)
- done!
1 * 64k blocks will be writed (0x000A0000 to 0x000B0000)
+ done!
emergency_recovery: 0x0

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> T2
image name("xml.bin"):
Using eth0 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.150
Filename 'xml.bin'.
Load address: 0x4000000
Loading: t RD_REQ, file: xml.bin
#######
done
Bytes transferred = 91319 (164b7 hex)
Firmware image "xml.bin" loaded
checksum: 0x5C873E(RAM)
checksum: 0x5C873E(Flash)
5 * 64k blocks will be erased (0x000B0000 to 0x00100000)
----- done!
5 * 64k blocks will be writed (0x000B0000 to 0x00100000)
+++++ done!
1 * 64k blocks will be erased (0x000A0000 to 0x000B0000)
- done!
1 * 64k blocks will be writed (0x000A0000 to 0x000B0000)
+ done!
emergency_recovery: 0x0

***********************************************************
* Please select option:
* 1 : Kermit Update Bootloader Firmware
* 2 : TFTP Configuration
* T0 : TFTP load kernel and run
* T1 : TFTP Update Bootloader Firmware
* T2 : TFTP Update XML Data
* T3 : TFTP Update Kernel Firmware
* T4 : TFTP Update Application
* T5 : TFTP Update FullInOne Image (Full erase!)
* S0 : SD load image and run
* S1 : SD Update Bootloader Firmware
* S2 : SD Update Factory Default
* S3 : SD Update Kernel Firmware
* S4 : SD Update Application Firmware
* S5 : SD Update XML Data
* S6 : SD Update FullInOne Firmware
* N0 : HTTP load image and run
* N1 : HTTP Update Bootloader Firmware
* N2 : HTTP Update XML Data
* N3 : HTTP Update Kernel Firmware
* N4 : HTTP Update Application Firmware
* N5 : HTTP Update FullInOne Image (Full erase!)
* o : GPIO test
* z : Start Linux
* r : Reboot
***********************************************************
=> r

sergei moroz
Новичок
Сообщения: 14
Зарегистрирован: 14 фев 2017, 20:06

Re: Avtech AVN801Z нет связи вдруг

Сообщение sergei moroz » 21 окт 2018, 18:01

не знаю, приветствуется ли некропостинг, но подскажите - перепрошивал купольную avtech через веб-морду, видимо что-то пошло не так, на ресет не реагирует, в сети не ищется. решил подключиться через UART, а в нем - тишина. Вроде кучу форумов перешерстил, землю и 3.3 вольта нашел, значит Rx и Tx можно подобрать методом тыка, а там в обоих концах - молчок. Что может быть?

Ответить

Вернуться в «IP видеонаблюдение»