Starting kernel uncompressing linux done booting the kernel

Форум по системам видеонаблюдения и безопасности.

Форум по системам видеонаблюдения, безопасности, пожарным и охранным сигнализациям, контролю доступа.

Как прошить камеру через загрузчик U-Boot по Telnet.

Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 25 май 2015, 08:53

Пробовал зайти в систему, не получается, перебрав кучу паролей оставил эту затею.
root:
xmhdipc
xc3511
123456
jvbzd
Ничего не подходит.

Остался у меня вариант оживить её через загрузчик, но как ?

kROOT писал(а): Случайно нашел сентябрьскую прошивку для таких камер

на плате камеры написано ipc18e_9712_v2.0
https://yadi.sk/d/5hvTXnZKdhcjJ» onclick=»window.open(this.href);return false;
что изменилось даже не знаю, но думаю свежая прошивка это всегда лучше

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Dim32 » 25 май 2015, 09:55

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 25 май 2015, 10:21

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Dim32 » 25 май 2015, 11:02

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение iTuneDVR » 25 май 2015, 11:10

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 25 май 2015, 13:32

У меня цель оживить этот кирпич.

Что я не понял:
Зачем команда: sf probe 0 и sf read 0x82000000 0x580000 0x200000

Что понял(вроде):
tftp 0x82000000 kernel.img 0x200000 — этой командой он слил на ТФТП сервер файл с названием kernel.img предположу 0x82000000 это начало, 0x200000 — длина файла?

Если просто ввести команду tftp, то получим:

Я так понял он пытается загрузить с сервера файл с именем uImage.

Куда дальше рыть?
В идеале я так предполагаю нужно сделать полный бэкап того что есть.

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Dim32 » 25 май 2015, 13:42

У меня цель оживить этот кирпич.

Что я не понял:
Зачем команда: sf probe 0 и sf read 0x82000000 0x580000 0x200000

Что понял(вроде):
tftp 0x82000000 kernel.img 0x200000 — этой командой он слил на ТФТП сервер файл с названием kernel.img предположу 0x82000000 это начало, 0x200000 — длина файла?

Если просто ввести команду tftp, то получим:

Я так понял он пытается загрузить с сервера файл с именем uImage.

Куда дальше рыть?
В идеале я так предполагаю нужно сделать полный бэкап того что есть.

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 26 май 2015, 06:32

Всё, рут получен!
Думаю данный способ подойдёт к большинству подобных камер.

На этом радость кончилась, почитав стандартные команды для сброса настроек сделал следующие:

/etc/starts: line 3: /mnt/mtd/ipc/run: not found

Видимо я снёс не только файл настроек, но и загрузчик оболочки.
Блин.. Что дальше сделать, чтоб она заработала?

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 27 май 2015, 11:28

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 27 май 2015, 12:08

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение SSSergeich » 08 сен 2015, 22:21

Re: Как прошить камеру через загрузчик U-Boot по Telnet.

Сообщение Bespredel » 05 окт 2015, 06:18

Заказал камеру на похожей плате(90%)и таким же софтом. Слил прошивку и залил в эту. Заработала.
Пароль ROOT сбросить не получилось из под загрузчика. Стандартные не подходят.
Учитывая, что камера у меня висит в облаке, а ID изменить нельзя, дамп выкладывать не буду.

Стёклышко перед камерой оказалось ИК фильтром. Т.к. основное предназначение её снимать ночью, то стекло удалил. Днём всё в розовом.
Взял 3 ИК светодиода по 3 ватта и посадил рядом с камерой. Теперь ночью снимает отлично и в цвете.

Источник

Welcome to AT91SAM Community Discussions

Kernel hang after Uncompressing . done booting the kernel

Moderator: nferre

Kernel hang after Uncompressing . done booting the kernel

Sun Jul 08, 2007 6:44 pm

My board is an at91rm9200 based board, AT45DB642D dataflash
We successfully build u-boot and linux-2.6.17 kernel and everythink is OK
But when we try compil another kernel (like 2.6.21) the kernel doesn’t start, we got:

Uncompressing Linux. done, booting the kernel

Re: Kernel hang after Uncompressing . done booting the ke

Mon Jul 09, 2007 5:06 am

I’m seeing the same issue with 2.6.22-rc1 on an at91sam9260. During the compile there was a warning message from module ./init/main.c that compiler version gcc-4.1.0 is «known to miscompile the kernel». And that is the version of the compiler I was using. I plan on trying a different compiler version tomorrow.

The warning message is not in the 2.6.19 kernel source. The warning is in 2.6.20.

Kernel hang after Uncompressing Linu . done booting the ke

Mon Jul 09, 2007 7:47 am

Thanks for the response
But I got the problem even with linux kernel > 2.6.17

I tried to use 3.4.3(gnuarm) and 4.1.1(crosstool) arm gcc on both kernel
I had the same issue

Mon Jul 09, 2007 8:54 am

you must asure to pass the right machine ID to kernel from u-boot. A search will tell you how it should be done.

Kernel hang after Uncompressing Linux. done booting the ke

Mon Jul 09, 2007 1:33 pm

Thanks for the reply

When you said » pass the right machine ID to kernel from u-boot», can you please explain the procedure ?

Because when I use 2.6.17 kernel, I just overwrite the board-dk.c file with mine, and did the same (with some modification to fit the new kernel fonctions) with 2.6.21

I will apreciate to have the procedure

Mon Jul 09, 2007 6:08 pm

try adding behind this line in kernel/printk.c (around line 538):

This will show you any messages which generated before the output starts. So you can see what really the problem is.

Maybe you have to enable printascii somewhere.

Tue Jul 10, 2007 5:39 am

For my variation of this synptom, I see the following:

Starting kernel .

Uncompressing Linux. done, booting the kernel.
Linux version 2.6.22-rc1-PCSC-Quantum-0.6 (gerard@spiff) (gcc version 4.2.0)
#27 Mon Jul 9 20:23:45 PDT 2007
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: PCSC AT91SAM9260-MC
Memory policy: ECC disabled, Data cache writethrough
On node 0 totalpages: 16384
DMA zone: 128 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 16256 pages, LIFO batch:3
Normal zone: 0 pages used for memmap

. and that’s all folks.
Had to do a `make menuconfig` and enable low-level kernel debugging.
Guess I need to try this on a working kernel, like 2.6.19
Thanks Mike for this trick.

Obkar,
Are you getting any warning messages about section mismatch at the end of the kernel build, just before the image is made?

• SYSMAP System.map
  SYSMAP .tmp_System.map
  MODPOST vmlinux
  WARNING: init/built-in.o — Section mismatch: reference to .init.text: from .text between ‘rest_init’ (at offset 0x160) and ‘try_name’
  WARNING: mm/built-in.o — Section mismatch: reference to .init.text: from .text between ‘kmem_cache_create’ (at offset 0x17800) and ‘cache_reap’
  WARNING: mm/built-in.o — Section mismatch: reference to .init.text: from .text between ‘kmem_cache_create’ (at offset 0x17834) and ‘cache_reap’

There were 2 section mismatches in my drivers (when built with 2.6.22) that I was able to eliminate/fix. But I have no clue about these.

Tue Jul 10, 2007 8:17 am

A good 2.6.19 kernel boot prints out:

Starting kernel .

Uncompressing Linux. done, booting the kernel.
Linux version 2.6.19-PCSC-Quantum-0.5 (gerard@susie) (gcc version 4.1.2) #2 Mon Jul 9 23:02:21 PDT 2007
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
Machine: PCSC AT91SAM9260-MC
Memory policy: ECC disabled, Data cache writethrough
On node 0 totalpages: 16384
DMA zone: 128 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 16256 pages, LIFO batch:3
Normal zone: 0 pages used for memmap
Clocks: CPU 147 MHz, master 73 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
CPU0: D cache: 8192 bytes, associativity 4, 32 byte lines, 64 sets
Built 1 zonelists. Total pages: 16256
Kernel command line: mem=16M console=ttyS0,115200 ip=192.168.2.13. 255.255.255.0:quantum03:eth0:on
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80×30

Regards

Tue Jul 10, 2007 9:51 am

To blue_z:
here are the end of the compilation

KSYM .tmp_kallsyms2.S
AS .tmp_kallsyms2.o
LD vmlinux
SYSMAP System.map
SYSMAP .tmp_System.map
MODPOST vmlinux
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
GZIP arch/arm/boot/compressed/piggy.gz
AS arch/arm/boot/compressed/piggy.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
UIMAGE arch/arm/boot/uImage
Image Name: Linux-2.6.21
Created: Tue Jul 10 01:40:34 2007
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1333552 Bytes = 1302.30 kB = 1.27 MB
Load Address: 0x20008000
Entry Point: 0x20008000
Image arch/arm/boot/uImage is ready

To mwolfram:
I did what you told me (enable degug, add the line you write) and here for the first time I get:

U-Boot 1.1.4 (Jan 16 2007 — 20:34:30)

U-Boot code: 21F80000 -> 21F97008 BSS: -> 21FB4004
RAM Configuration:
Bank #0: 20000000 32 MB
Atmel: Flash: 0 kB
DataFlash:AT45DB642
Nb pages: 8192
Page Size: 1056
Size= 8650752 bytes
Logical address: 0xC0000000
Area 0: C0000000 to C0007FFF (RO)
Area 1: C0008000 to C001FFFF (RO)
Area 2: C0020000 to C0027FFF
Area 3: C0028000 to C083FFFF
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
No Link
No Link
MAC: error during MII initialization (unplugged network cable?)
## Booting image at c0040000 .
Image Name: Linux-2.6.21
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1333552 Bytes = 1.3 MB
Load Address: 20008000
Entry Point: 20008000
Verifying Checksum . OK
OK

Uncompressing Linux.
. done, booting the kernel.
Linux version 2.6.21 (larbi@Larbi) (gcc version 3.4.3) #3 PREEMPT Tue Jul 10
01:39:58 CEST 2007
CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
Machine: Atmel AT91RM9200-DK
Memory policy: ECC disabled, Data cache writeback
On node 0 totalpages: 8192
DMA zone: 64 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 8128 pages, LIFO batch:0
Normal zone: 0 pages used for memmap
Clocks: CPU 179 MHz, master 59 MHz, main 18.432 MHz
CPU0: D VIVT write-back cache
CPU0: I cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
CPU0: D cache: 16384 bytes, associativity 64, 32 byte lines, 8 sets
Built 1 zonelists. Total pages: 8128
Kernel command line: mem=32M console=ttyS0,115200 rootdelay=8 root=/dev/sda1
rw
AT91: 96 gpio irqs in 3 banks
PID hash table entries: 128 (order: 7, 512 bytes)
Console: colour dummy device 80×30
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Memory: 32MB = 32MB total
Memory: 29708KB available (2464K code, 180K data, 84K init)
Calibrating delay loop. 89.70 BogoMIPS (lpj=448512)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Bluetooth: Core ver 2.11
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NetWinder Floating Point Emulator V0.97 (double precision)
JFFS2 version 2.2. (NAND) (C) 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler anticipatory registered (default)
at91_spi: Baud rate set to 5990400
AT91 SPI driver loaded
PPP generic driver version 2.4.2
NET: Registered protocol family 24
eth0: Link down.
eth0: AT91 ethernet at 0xfefbc000 int=24 10-HalfDuplex (aa:bb:cc:00:11:22)
eth0: Micrel KS8721 PHY
at91_dataflash: AT45DB642 detected [spi0] (8650752 bytes)
Creating 3 MTD partitions on «AT45DB642.spi0»:
0x00000000-0x00042000 : «bootloader»
0x00042000-0x0018c000 : «kernel»
0x0018c000-0x00840000 : «filesystem»
ohci_hcd: 2006 August 04 USB 1.1 ‘Open’ Host Controller (OHCI) Driver
ohci_hcd: block sizes: ed 64 td 64
at91_ohci at91_ohci: start
at91_ohci at91_ohci: AT91 OHCI
drivers/usb/core/inode.c: creating file ‘devices’
drivers/usb/core/inode.c: creating file ‘001’
at91_ohci at91_ohci: new USB bus registered, assigned bus number 1
at91_ohci at91_ohci: supports USB remote wakeup
at91_ohci at91_ohci: irq 23, io mem 0x00300000
at91_ohci at91_ohci: created debug files
at91_ohci at91_ohci: resetting from state ‘reset’, control = 0x0
at91_ohci at91_ohci: OHCI controller state
at91_ohci at91_ohci: OHCI 1.0, NO legacy support registers
at91_ohci at91_ohci: control 0x083 HCFS=operational CBSR=3
at91_ohci at91_ohci: cmdstatus 0x00000 SOC=0
at91_ohci at91_ohci: intrstatus 0x00000004 SF
at91_ohci at91_ohci: intrenable 0x8000001a MIE UE RD WDH
at91_ohci at91_ohci: hcca frame #0024
at91_ohci at91_ohci: roothub.a 02000202 POTPGT=2 NPS NDP=2(2)
at91_ohci at91_ohci: roothub.b 00000000 PPCM=0000 DR=0000
at91_ohci at91_ohci: roothub.status 00008000 DRWE
at91_ohci at91_ohci: roothub.portstatus [0] 0x00000100 PPS
at91_ohci at91_ohci: roothub.portstatus [1] 0x00000100 PPS
usb usb1: default language 0x0409
usb usb1: new device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: AT91 OHCI
usb usb1: Manufacturer: Linux 2.6.21 ohci_hcd
usb usb1: SerialNumber: at91
usb usb1: uevent
usb usb1: usb_probe_device
usb usb1: configuration #1 chosen from 1 choice
usb usb1: adding 1-0:1.0 (config #1, interface 0)
usb 1-0:1.0: uevent
hub 1-0:1.0: usb_probe_interface
hub 1-0:1.0: usb_probe_interface — got id
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
hub 1-0:1.0: standalone hub
hub 1-0:1.0: no power switching (usb 1.0)
hub 1-0:1.0: global over-current protection
hub 1-0:1.0: power on to power good time: 4ms
hub 1-0:1.0: local power source is good
hub 1-0:1.0: no over-current condition exists
hub 1-0:1.0: trying to enable port power on non-switchable hub
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0000
drivers/usb/core/inode.c: creating file ‘001’
Initializing USB Mass Storage driver.
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
i2c /dev entries driver
at91_i2c at91_i2c: AT91 i2c bus driver.
Bluetooth: HCI USB driver ver 2.9
usbcore: registered new interface driver hci_usb
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCI H4 protocol initialized
Bluetooth: HCI BCSP protocol initialized
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Bluetooth: L2CAP ver 2.8
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO (Voice Link) ver 0.5
Bluetooth: SCO socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00010301 CSC LSDA P
PS CCS
hub 1-0:1.0: port 2, status 0301, change 0001, 1.5 Mb/s
Waiting 8sec before mounting root device.
hub 1-0:1.0: debounce: port 2: total 100ms stable 100ms status 0x301
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: new low speed USB device using at91_ohci and address 2
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: device descriptor read/64, error -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: device descriptor read/64, error -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: new low speed USB device using at91_ohci and address 3
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: device descriptor read/64, error -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0in 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: device descriptor read/64, error -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: new low speed USB device using at91_ohci and address 4
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 —> status -62
usb 1-2: device not accepting address 4, error -62
at91_ohci at91_ohci: GetStatus roothub.portstatus [1] = 0x00100303 PRSC LSDA
PPS PES CCS
usb 1-2: new low speed USB device using at91_ohci and address 5
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 —> status -62
at91_ohci at91_ohci: urb c1c0f120 path 2 ep0out 5ec20000 cc 5 —> status -62
usb 1-2: device not accepting address 5, error -62
hub 1-0:1.0: state 7 ports 2 chg 0000 evt 0004
Root-NFS: No NFS server available, giving up.
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device «sda1» or unknown-block(2,0)
Please append a correct «root=» boot option
Kernel panic — not syncing: VFS: Unable to mount root fs on unknown-block(2,0

What do you you think about that ?
Thanks for your help again

Источник