ESpec - мир электроники для профессионалов


Видеорегистратор st dvr-1604 light нет картинки (прошивка)

  Список форумов » Другая аппаратура
На страницу Пред.  1, 2, 3, 4, 5, 6, 7  След.
Следующая тема · Предыдущая тема
АвторСообщение
GeParDos 
Участник
Сообщения: 106
 
Сообщение #81 от 25/04/2017 17:44 цитата  

n max писал:
А штатным способом что не даёт прошить подмигивание

что имеете в виду? по USB? нет возможности войти в интерфейс
по UART посылать посылаю а процесс прошивки не знаю как запустит, прогера для Nand у меня нет еще, только postal-3
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #82 от 25/04/2017 17:47 цитата  

Если все ОК, то далее вводим в консоли следующую команду
erase 0x9f020000 +0x3c0000
Т.е сначала надо стереть флеш перед тем как писать

ДОБАВЛЕНО 23/04/2017 22:41

После этого введите следующую команду
cp.b 0x80000000 0x9f020000 0x3c0000

После чего роутер начнет прошиваться
и когда он прошьется то напишет Вам

ДОБАВЛЕНО 25/04/2017 17:47

Это не катит подмигивание
GeParDos 
Участник
Сообщения: 106
 
Сообщение #83 от 25/04/2017 17:55 цитата  

нет не катит.
1. команда erase не поддерживается а как стереть по другому не знаю
2. адрес 0x9f020000 это не мой адрес флешки помните спрашивал как определить этот адрес
3. запускал команду cp.b 0x80000000 0x9f020000 0x3c0000 только со своими значениями аппарат как будто зависает не происходит не чего просто видно что он принял команду курсив переходит на новую чистую строчку и на этом все

ДОБАВЛЕНО 25/04/2017 17:57

так стоит и при этом не могу ввести команды даже ctrl+c (отмена) не действует

ДОБАВЛЕНО 25/04/2017 18:00

а как вы сказали что прошивка пишется 2-3 минуты, но я ждал и пол часа не чего и адрес я так и не выяснил свой может в этом пречина
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #84 от 25/04/2017 18:34 цитата  

16. U-Boot Loader – Kernel Boot • Boot from NAND – nand read.i 0x81000000 280000 500000 – bootm 0x81000000 • Boot from SPI – sf read 0x81000000 0x42000 0x200000 – bootm 0x81000000 • Boot from NOR – cp.w 0x08060000 0x81000000 0x200000 – bootm 0x81000000 • Boot over Network – tftp 0x81000000 uImage – bootm 0x81000000
вот нашёл какие-то команды от этого проца х.з. подойдут иль нет
GeParDos 
Участник
Сообщения: 106
 
Сообщение #85 от 05/05/2017 21:09 цитата  

В каком разделе происходит инициализация железа в бут или в кернел уже??

по моей логике инициализация железа должна происходить в бут, а потом бут передает переменные в кернел для работы
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #86 от 05/05/2017 23:34 цитата  

В буте происходит минимальная инициализация устройств необходимых для запуска или аварийного восстановления п.о.,содержится перечень бэд блоков нанд флешки,логотип заргузки(естественно в низком разрешении)+опрос нужных кнопок клавиатуры если они участвуют в обновлении п.о. или рековери меню.Это из мобильников-думается в регистраторе не много отличий
GeParDos 
Участник
Сообщения: 106
 
Сообщение #87 от 06/05/2017 15:21 цитата  

n max писал:
В буте происходит минимальная инициализация устройств необходимых для запуска или аварийного восстановления п.о.,содержится перечень бэд блоков нанд флешки,логотип заргузки(естественно в низком разрешении)+опрос нужных кнопок клавиатуры если они участвуют в обновлении п.о. или рековери меню.Это из мобильников-думается в регистраторе не много отличий


в общем такая ситуация восстановил прошивку, но что то не так не могу понять что, аппарат стал пищать как сумасшедший и не выводит изображение на экран, раньше хоть логотип появлялся
вот лог загрузки:
Код:
U-Boot 2010.06 (Dec 08 2012 - 18:27:16)

TI8148-GP rev 2.1

ARM clk: 1000MHz
DDR clk: 533MHz
IVA clk: 480MHz
ISS clk: 480MHz
DSS clk: 220MHz
DSP clk: 750MHz

DRAM:  1 GiB
NAND:  HW ECC BCH8 Selected
128 MiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x20000, size 0x40000
 262144 bytes read: OK
## Starting application at 0x81000000 ...


U-Boot 2010.06 (Oct 14 2013 - 11:23:25)

TI8148-GP rev 2.1

ARM clk: 1000MHz
DDR clk: 580MHz
L3 clk: 220MHz
IVA clk: 528MHz
ISS clk: 560MHz
DSS clk: 240MHz
DSP clk: 750MHz

I2C:   ready
DRAM:  1 GiB
NAND:  HW ECC BCH8 Selected
128 MiB
MMC:   OMAP SD/MMC: 0
enable wdt to 240 s
Net:   Ethernet clocking: 0x0
Detected MACID:0:17:eb:a2:b8:d6
change phyid to:1
cpsw
Hit any key to stop autoboot:  0
mfgid=ad
nand read success 2097152
Data (writethrough) Cache is OFF
VPDMA Firmware Version = 0x4d0001b7
Data (writethrough) Cache is ON

NAND read: device 0 offset 0x280000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2750608 Bytes = 2.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (zr@pub-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #27 Thu Dec 5 14:23:29 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: dm385evm
vram size = 6291456 at 0x0
bootconsole [earlycon0] enabled
ti81xx_reserve: ### Reserved DDR region @8bf00000
reserved size = 6291456 at 0x0
FB: Reserving 6291456 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.1
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 46976
Kernel command line: console=ttyO0,115200n8 noinitrd root=/dev/mtdblock4 mem=192M vram=6M earlyprintk notifyk.vpssm3_sva=0xbffd0000 i2c_bus=3,400
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 184MB 1MB = 185MB total
Memory: 181736k/181736k available, 14872k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xcc800000 - 0xf8000000   ( 696 MB)
    lowmem  : 0xc0000000 - 0xcc000000   ( 192 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0042000   ( 232 kB)
      .text : 0xc0042000 - 0xc0538000   (5080 kB)
      .data : 0xc0538000 - 0xc0585ac0   ( 311 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
omap_hwmod: gpio1: softreset failed (waited 10000 usec)
omap_hwmod: gpio2: softreset failed (waited 10000 usec)
omap_hwmod: gpio3: softreset failed (waited 10000 usec)
omap_hwmod: gpio4: softreset failed (waited 10000 usec)
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0x8bf00000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
_omap_mux_init_gpio: Could not set gpio38
cpu_is_ti8107
ti814x_sata_pllcfg: LIXUEQIANG (cpu_is_ti814x()) && (!cpu_is_dm385()))
clk get on i2c3 fck failed
Cannot clk_get ck_32
omap2_init_devices: LIXUEQIANG begin 8
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xcc820000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
ti81xx_pcie: PCI scan done.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
tps65910 1-002d: read from reg 3f failed
tps65910 1-002d: read from reg 1e failed
set_machine_constraints: failed to enable VRTC
tps65910 1-002d: failed to register tps65910-pmic regulator
tps65910-pmic: probe of tps65910-pmic failed with error -121
tps65910 1-002d: No interrupt support, no core IRQ
omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(28 14 13)
usb2phy: override computed values rxcalib(15)DACs(28 14 13)
usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f6e5d6e
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at cc81e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(22 13 16)
usb2phy: override computed values rxcalib(15)DACs(22 13 16)
usb2phy_config: musb(1) rxcalib done, rxcalib read value 6f6b5b86
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at cc826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
fuse init (API version 7.15)
msgmni has been set to 354
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Maf ID: 0xad, Chip ID: 0xf1 (Hynix, NAND 128MiB 3,3V 8-bit)
 erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 12 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000260000 : "U-Boot-reserved"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x0000012c0000 : "File System"
0x0000012c0000-0x000001ec0000 : "Application"
0x000001ec0000-0x0000026c0000 : "Param"
0x0000026c0000-0x0000028c0000 : "logo"
0x0000028c0000-0x000008000000 : "Reserved"
0x000000000000-0x000008000000 : "Whole"
0x0000028c0000-0x0000047c0000 : "http source"
0x0000047c0000-0x0000048c0000 : "uid"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usb 1-1: new high speed USB device using musb-hdrc and address 2
usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1: Product: USB2.0 Hub
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 2-1: new high speed USB device using musb-hdrc and address 2
usb 2-1: New USB device found, idVendor=05e3, idProduct=0718
usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
usb 2-1: Product: USB Storage
usb 2-1: SerialNumber: 000000000033
scsi1 : usb-storage 2-1:1.0
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
rtc-ds1307: probe of 1-0068 failed with error -5
rtc-isl1208 1-006f: chip found, driver version 0.3
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbffd0000
usbcore: registered new interface driver snd-usb-audio
function cs4334_modinit,line:219
function cs4334_codec_probe,line:192
Registered tvp5158 audio codec
asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
function cs4334_probe,line:164
function cs4334_init,line:158
asoc: cs4334 <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX SOUND0
  #1: TI81XX SOUND1
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=0:17:eb:a2:b8:d6
rtc-isl1208 1-006f: setting system clock to 2011-12-20 20:33:56 UTC (1324413236)
scsi 1:0:0:0: Direct-Access     USB TO I DE/SATA Device   0009 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Attached SCSI disk
ata1: SATA link down (SStatus 0 SControl 300)
cramfs_fill_nand blocks is 96
VFS: Mounted root (cramfs filesystem) readonly on device 31:4.
devtmpfs: mounted
Freeing init memory: 232K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (86): /proc/86/oom_adj is deprecated, please use /proc/86/oom_score_adj instead.
Remounting root file system...
Caching udev devnodes
ALSA: Restoring mixer settings...
Configuring network interfaces... PHY 0:08 not found
PHY 0:1f not found

CPSW phy found : id is : 0x2430c54 on slave 1
done.
Setting up IP spoofing protection: rp_filter.
mount nfs...
INIT: Entering runlevel: 5
Starting telnet daemon.
Starting syslogd/klogd: done
usb is not ready for autoexec
cramfs_fill_nand blocks is 96
cramfs_fill_nand blocks is 248
cramfs: wrong magic
mount: wrong fs type, bad option, bad superblockcramfs_fill_nand blocks is 8
 on /dev/mtdblock10,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
    cramfs: wrong magic
   dmesg | tail  or so

mount: wrong fs type, bad option, bad superblock on /dUBI: attaching mtd6 to ubi0
ev/mtdblock11,
UBI: physical eraseblock size:   131072 bytes (128 KiB)
       missing cUBI: logical eraseblock size:    129024 bytes
odepage or helpeUBI: smallest flash I/O unit:    2048
r program, or otUBI: sub-page size:              512
her error
     UBI: VID header offset:          512 (aligned 512)
  In some cases UBI: data offset:                2048
useful info is found in syslog - try
       dmesg | tail  or so

UBI: max. sequence number:       3636705
UBI: attached mtd6 to ubi0
UBI: MTD device name:            "Param"
UBI: MTD device size:            8 MiB
UBI: number of good PEBs:        64
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             9
UBI: total number of reserved PEBs: 55
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 57364/56824
UBI: image sequence number:  1245645685
UBI: background thread "ubi_bgt0d" started, PID 798
UBI device number 0, total 64 LEBs (8257536 bytes, 7.9 MiB), available 9 LEBs (1161216 bytes, 1.1 MiB), LEB size 129024 bytes (126.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "para"
UBIFS: file system size:   5160960 bytes (5040 KiB, 4 MiB, 40 LEBs)
UBIFS: journal size:       1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  243764 bytes (238 KiB)
/etc/rc5.d/S81appinit: line 21: ./logo: not found
chmod: env.sh: Read-only file system
chmod: init.sh: Read-only file system
chmod: load.sh: Read-only file system
chmod: run.sh: Read-only file system
chmod: unload.sh: Read-only file system
chmod: validate.sh: Read-only file system
chmod: ./bin/fw_load.out: Read-only file system
chmod: ./bin/i2c_rdwr.out: Read-only file system
chmod: ./bin/mem_rdwr.out: Read-only file system
chmod: ./bin/mem_stats.out: Read-only file system
chmod: ./bin/remote_debug_client.out: Read-only file system
chmod: ./bin/sys_pri.out: Read-only file system
chmod: ./bin/vpdma_dump.out: Read-only file system
chmod: ./scripts/load_video.sh: Read-only file system
chmod: ./scripts/load_vpss.sh: Read-only file system
chmod: ./scripts/osa_kermod_load.sh: Read-only file system
chmod: ./scripts/osa_kermod_unload.sh: Read-only file system
chmod: ./scripts/send_cmd.sh: Read-only file system
chmod: ./scripts/wait_cmd.sh: Read-only file system
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
Kernel bootargs validated
./init.sh: line 18: amixer: not found
 [c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
 [m3video] Remote Debug Shared Memory @ 0xbfff5020
 [m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
SysLink version : 2.10.02.17
SysLink module created on Date:Aug 21 2013 Time:14:37:00
Trace enabled
Trace SetFailureReason enabled
 Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[3,3] BW=2000, WM Cycles=4000]
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
Attached to slave procId 2.
Loaded file ../firmware/dvr_rdk_fw_m3vpss.xem3 on slave procId 2.
Started slave procId 2.
After Ipc_loadcallback status [0x00000000]
 [m3vpss ] system_vpass_freq value is:0xe4e1c00
 [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3vpss ] notify_attach  rtnVal  0
 [m3vpss ] initProxyServer  rtnVal  0
 [m3vpss ]
 [m3vpss ]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3vpss ]
 [m3vpss ]  53: SYSTEM: IPC init in progress !!!
 [m3vpss ]  53: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1053: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1054: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3vpss ]  1054: SYSTEM: Attaching to [VIDEO-M3] ...
After Ipc_startcallback status [0x097d2000]
Attached to slave procId 1.
Loaded file ../firmware/dvr_rdk_fw_m3video.xem3 on slave procId 1.
Started slave procId 1.
After Ipc_loadcallback status [0x00000000]
 [m3video] system_video_freq value is:0xe4e1c00
 [m3vpss ]  2054: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3video]
 [m3video]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3video]
 [m3video]  1429: SYSTEM: IPC init in progress !!!
 [m3video] DMA: Module install successful, device major num = 250
 1429: SYSTEM: ADRV: Module install successful
ttaching to [HOSDRV: Module built on Nov  1 2013 16:28:15
T] ...
 [m3video]  2429: SYSTEM: Attaching to [HOST] ...
 [m3video]  2431: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3video]  2431: SYSTEM: Attaching to [VPSS-M3] ...
After Ipc_startcallback status [0x00000000]
 [c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
 [m3video] Remote Debug Shared Memory @ 0xbfff5020
 [m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
 [m3vpss ]  3054: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video]  3431: SYSTEM: Attaching to [VPSS-M3] ...
 [m3video]  4054: SYSTEM: Attaching to [VPSS-M3] ... SUCCESS !!!
 [m3vpss ]  4054: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video]  4054: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
 [m3vpss ]  4054: SYSTEM: Attaching to [VIDEO-M3] ... SUCCESS !!!
 [m3vpss ]  4054: SYSTEM: Creating MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
 [m3vpss ]  4054: SYSTEM: Creating MsgQ [VPSS-M3_MSGQ] ...
 [m3vpss ]  4055: SYSTEM: Creating MsgQ [VPSS-M3_ACK_MSGQ] ...
 [m3vpss ]  4057: SYSTEM: Notify register to [HOST] line 0, event 15 ...
 [m3vpss ]  4057: SYSTEM: Notify register to [VIDEO-M3] line 0, event 15 ...
 [m3vpss ]  4057: SYSTEM: IPC init DONE !!!
 [m3vpss ] Unhandled Exception:
 [m3vpss ] Exception occurred in ThreadType_Task
 [m3vpss ] handle: 0x37b68298.
 [m3vpss ] stack base: 0x37e5b100.
 [m3vpss ] stack size: 0x8000.
 [m3vpss ] R0 = 0x00000000  R8  = 0xffffffff
 [m3vpss ] R1 = 0x00000000  R9  = 0xffffffff
 [m3vpss ] R2 = 0x96d59715  R10 = 0xffffffff
 [m3vpss ] R3 = 0xfffffff1  R11 = 0xffffffff
 [m3vpss ] R4 = 0xffffffff  R12 = 0x0033d8a1
 [m3vpss ] R5 = 0xffffffff  SP(R13) = 0x37e630c8
 [m3vpss ] R6 = 0xffffffff  LR(R14) = 0x96d459d9
 [m3vpss ] R7 = 0xffffffff  PC(R15) = 0x0033d8a0
 [m3vpss ] PSR = 0x61000000
 [m3vpss ] ICSR = 0x0440f803
 [m3vpss ] MMFSR = 0x00
 [m3vpss ] BFSR = 0x01
 [m3vpss ] UFSR = 0x0000
 [m3vpss ] HFSR = 0x40000000
 [m3vpss ] DFSR = 0x00000000
 [m3vpss ] MMAR = 0xe000ed34
 [m3vpss ] BFAR = 0xe000ed38
 [m3vpss ] AFSR = 0x00000000
 [m3vpss ] Terminating Execution...
 [m3video]  5054: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...


стоит какое-то время и уходит в перезагрузку

бывает такая фигня

Код:
U-Boot 2010.06 (Dec 08 2012 - 18:27:16)

TI8148-GP rev 2.1

ARM clk: 1000MHz
DDR clk: 533MHz
IVA clk: 480MHz
ISS clk: 480MHz
DSS clk: 220MHz
DSP clk: 750MHz

DRAM:  1 GiB
NAND:  HW ECC BCH8 Selected
128 MiB
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x20000, size 0x40000
 262144 bytes read: OK
## Starting application at 0x81000000 ...


U-Boot 2010.06 (Oct 14 2013 - 11:23:25)

TI8148-GP rev 2.1

ARM clk: 1000MHz
DDR clk: 580MHz
L3 clk: 220MHz
IVA clk: 528MHz
ISS clk: 560MHz
DSS clk: 240MHz
DSP clk: 750MHz

I2C:   ready
DRAM:  1 GiB
NAND:  HW ECC BCH8 Selected
128 MiB
MMC:   OMAP SD/MMC: 0
enable wdt to 240 s
Net:   Ethernet clocking: 0x0
Detected MACID:0:17:eb:a2:b8:d6
change phyid to:1
cpsw
Hit any key to stop autoboot:  0
mfgid=ad
nand read success 2097152
Data (writethrough) Cache is OFF
VPDMA Firmware Version = 0x4d0001b7
Data (writethrough) Cache is ON

NAND read: device 0 offset 0x280000, size 0x300000
 3145728 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
   Image Name:   Linux-2.6.37
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2750608 Bytes = 2.6 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (zr@pub-desktop) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #27 Thu Dec 5 14:23:29 CST 2013
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: dm385evm
vram size = 6291456 at 0x0
bootconsole [earlycon0] enabled
ti81xx_reserve: ### Reserved DDR region @8bf00000
reserved size = 6291456 at 0x0
FB: Reserving 6291456 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 2.1
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 46976
Kernel command line: console=ttyO0,115200n8 noinitrd root=/dev/mtdblock4 mem=192M vram=6M earlyprintk notifyk.vpssm3_sva=0xbffd0000 i2c_bus=3,400
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
Memory: 184MB 1MB = 185MB total
Memory: 181736k/181736k available, 14872k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
    vmalloc : 0xcc800000 - 0xf8000000   ( 696 MB)
    lowmem  : 0xc0000000 - 0xcc000000   ( 192 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .init : 0xc0008000 - 0xc0042000   ( 232 kB)
      .text : 0xc0042000 - 0xc0538000   (5080 kB)
      .data : 0xc0538000 - 0xc0585ac0   ( 311 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
omap_hwmod: gpio1: softreset failed (waited 10000 usec)
omap_hwmod: gpio2: softreset failed (waited 10000 usec)
omap_hwmod: gpio3: softreset failed (waited 10000 usec)
omap_hwmod: gpio4: softreset failed (waited 10000 usec)
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
TI81XX: Map 0x8bf00000 to 0xfe500000 for dram barrier
TI81XX: Map 0x40300000 to 0xfe600000 for sram barrier
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
_omap_mux_init_gpio: Could not set gpio38
cpu_is_ti8107
ti814x_sata_pllcfg: LIXUEQIANG (cpu_is_ti814x()) && (!cpu_is_dm385()))
clk get on i2c3 fck failed
Cannot clk_get ck_32
omap2_init_devices: LIXUEQIANG begin 8
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xcc820000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
ti81xx_pcie: PCI scan done.
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 400 kHz
tps65910 1-002d: read from reg 3f failed
tps65910 1-002d: read from reg 1e failed
set_machine_constraints: failed to enable VRTC
tps65910 1-002d: failed to register tps65910-pmic regulator
tps65910-pmic: probe of tps65910-pmic failed with error -121
tps65910 1-002d: No interrupt support, no core IRQ
omap_i2c omap_i2c.3: bus 3 rev4.0 at 400 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(28 14 13)
usb2phy: override computed values rxcalib(15)DACs(28 14 13)
usb2phy_config: musb(0) rxcalib done, rxcalib read value 6f6e5d6e
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at cc81e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
usb2phy: computed values rxcalib(15)DACs(22 13 16)
usb2phy: override computed values rxcalib(15)DACs(22 13 16)
usb2phy_config: musb(1) rxcalib done, rxcalib read value 6f6b5b86
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at cc826800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
fuse init (API version 7.15)
msgmni has been set to 354
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled, bootconsole disabled
console [ttyO0] enabled, bootconsole disabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 irq_stat 0x00400040, connection status changed irq 16
omap2-nand driver initializing
ONFI flash detected
ONFI param page 0 valid
NAND device: Maf ID: 0xad, Chip ID: 0xf1 (Hynix, NAND 128MiB 3,3V 8-bit)
 erasesize: 0x20000, writesize: 2048, oobsize: 64
Creating 12 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000040000 : "U-Boot"
0x000000040000-0x000000260000 : "U-Boot-reserved"
0x000000260000-0x000000280000 : "U-Boot Env"
0x000000280000-0x0000006c0000 : "Kernel"
0x0000006c0000-0x0000012c0000 : "File System"
0x0000012c0000-0x000001ec0000 : "Application"
0x000001ec0000-0x0000026c0000 : "Param"
0x0000026c0000-0x0000028c0000 : "logo"
0x0000028c0000-0x000008000000 : "Reserved"
0x000000000000-0x000008000000 : "Whole"
0x0000028c0000-0x0000047c0000 : "http source"
0x0000047c0000-0x0000048c0000 : "uid"
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffffd
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
PPP generic driver version 2.4.2
PPP Deflate Compression module registered
PPP BSD Compression module registered
PPP MPPE Compression module registered
NET: Registered protocol family 24
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
usbcore: registered new interface driver usbserial
usbserial: USB Serial Driver core
USB Serial support registered for GSM modem (1-port)
usb 1-1: new high speed USB device using musb-hdrc and address 2
usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1: Product: USB2.0 Hub
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 2-1: new high speed USB device using musb-hdrc and address 2
usb 2-1: New USB device found, idVendor=05e3, idProduct=0718
usb 2-1: New USB device strings: Mfr=0, Product=1, SerialNumber=2
usb 2-1: Product: USB Storage
usb 2-1: SerialNumber: 000000000033
scsi1 : usb-storage 2-1:1.0
usbcore: registered new interface driver option
option: v0.7.2:USB Driver for GSM modems
mice: PS/2 mouse device common for all mice
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
rtc-ds1307: probe of 1-0068 failed with error -5
rtc-isl1208 1-006f: chip found, driver version 0.3
rtc-isl1208 1-006f: rtc core: registered rtc-isl1208 as rtc0
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated  for  remote proc id 2 at physical Address 0xbffd0000
usbcore: registered new interface driver snd-usb-audio
function cs4334_modinit,line:219
function cs4334_codec_probe,line:192
Registered tvp5158 audio codec
asoc: tvp5158-hifi <-> davinci-mcasp.0 mapping ok
function cs4334_probe,line:164
function cs4334_init,line:158
asoc: cs4334 <-> davinci-mcasp.1 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
  #0: TI81XX SOUND0
  #1: TI81XX SOUND1
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=0:17:eb:a2:b8:d6
rtc-isl1208 1-006f: setting system clock to 2011-12-21 10:05:55 UTC (1324461955)
usb 1-1.3: new high speed USB device using musb-hdrc and address 3
usb 1-1.3: New USB device found, idVendor=1307, idProduct=0190
usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.3: Product: USB
usb 1-1.3: Manufacturer: USB
usb 1-1.3: SerialNumber: 00000000001624
scsi2 : usb-storage 1-1.3:1.0
scsi 1:0:0:0: Direct-Access     USB TO I DE/SATA Device   0009 PQ: 0 ANSI: 0
sd 1:0:0:0: Attached scsi generic sg0 type 0
sd 1:0:0:0: [sda] Attached SCSI disk
scsi 2:0:0:0: Direct-Access              silicon-power    0.00 PQ: 0 ANSI: 2
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0:0:0: [sdb] 7897088 512-byte logical blocks: (4.04 GB/3.76 GiB)
sd 2:0:0:0: [sdb] Write Protect is off
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Assuming drive cache: write through
 sdb: unknown partition table
sd 2:0:0:0: [sdb] Assuming drive cache: write through
sd 2:0:0:0: [sdb] Attached SCSI removable disk
ata1: SATA link down (SStatus 0 SControl 300)
cramfs_fill_nand blocks is 96
VFS: Mounted root (cramfs filesystem) readonly on device 31:4.
devtmpfs: mounted
Freeing init memory: 232K
INIT: version 2.86 booting
Please wait: booting...
Error opening /dev/fb0: No such file or directory
Starting udev
udevd (89): /proc/89/oom_adj is deprecated, please use /proc/89/oom_score_adj instead.
Remounting root file system...
Caching udev devnodes
ALSA: Restoring mixer settings...
Configuring network interfaces... PHY 0:08 not found
PHY 0:1f not found

CPSW phy found : id is : 0x2430c54 on slave 1
done.
Setting up IP spoofing protection: rp_filter.
mount nfs...
INIT: Entering runlevel: 5
Starting telnet daemon.
Starting syslogd/klogd: done
usb is not ready for autoexec
cramfs_fill_nand blocks is 96
cramfs_fill_nand blocks is 248
cramfs: wrong magic
mount: wrong fs type, bad option, bad superblockcramfs_fill_nand blocks is 8
 on /dev/mtdblock10,
       missing codepage orcramfs: wrong magic
 helper program, or other error
       In some cases useful info is found in syUBI: attaching mtd6 to ubi0
slog - try
    UBI: physical eraseblock size:   131072 bytes (128 KiB)
   dmesg | tail UBI: logical eraseblock size:    129024 bytes
 or so

mount:UBI: smallest flash I/O unit:    2048
 wrong fs type, UBI: sub-page size:              512
bad option, bad UBI: VID header offset:          512 (aligned 512)
superblock on /dUBI: data offset:                2048
ev/mtdblock11,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so

UBI: max. sequence number:       3636737
UBI: attached mtd6 to ubi0
UBI: MTD device name:            "Param"
UBI: MTD device size:            8 MiB
UBI: number of good PEBs:        64
UBI: number of bad PEBs:         0
UBI: number of corrupted PEBs:   0
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     1
UBI: available PEBs:             9
UBI: total number of reserved PEBs: 55
UBI: number of PEBs reserved for bad PEB handling: 2
UBI: max/mean erase counter: 57364/56825
UBI: image sequence number:  1245645685
UBI: background thread "ubi_bgt0d" started, PID 821
UBI device number 0, total 64 LEBs (8257536 bytes, 7.9 MiB), available 9 LEBs (1161216 bytes, 1.1 MiB), LEB size 129024 bytes (126.0 KiB)
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "para"
UBIFS: file system size:   5160960 bytes (5040 KiB, 4 MiB, 40 LEBs)
UBIFS: journal size:       1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)
UBIFS: media format:       w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root:  243764 bytes (238 KiB)
/etc/rc5.d/S81appinit: line 21: ./logo: not found
chmod: env.sh: Read-only file system
chmod: init.sh: Read-only file system
chmod: load.sh: Read-only file system
chmod: run.sh: Read-only file system
chmod: unload.sh: Read-only file system
chmod: validate.sh: Read-only file system
chmod: ./bin/fw_load.out: Read-only file system
chmod: ./bin/i2c_rdwr.out: Read-only file system
chmod: ./bin/mem_rdwr.out: Read-only file system
chmod: ./bin/mem_stats.out: Read-only file system
chmod: ./bin/remote_debug_client.out: Read-only file system
chmod: ./bin/sys_pri.out: Read-only file system
chmod: ./bin/vpdma_dump.out: Read-only file system
chmod: ./scripts/load_video.sh: Read-only file system
chmod: ./scripts/load_vpss.sh: Read-only file system
chmod: ./scripts/osa_kermod_load.sh: Read-only file system
chmod: ./scripts/osa_kermod_unload.sh: Read-only file system
chmod: ./scripts/send_cmd.sh: Read-only file system
chmod: ./scripts/wait_cmd.sh: Read-only file system
*** Bootargs Validated for mem param ***
*** Bootargs Validated for notifyk.vpssm3 params ***
Kernel bootargs validated
./init.sh: line 18: amixer: not found
 [c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
 [m3video] Remote Debug Shared Memory @ 0xbfff5020
 [m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
SysLink version : 2.10.02.17
SysLink module created on Date:Aug 21 2013 Time:14:37:00
Trace enabled
Trace SetFailureReason enabled
PHY: 0:01 - Link is Up - 100/Full
 Setting L3 bandwidth regulator for [HDVICP0 ] to [press=[3,3] BW=2000, WM Cycles=4000]
 Setting DMM priority for [DUCATI  ] to [0] ( 0x4e000624 = 0x08000000 )
 Setting DMM priority for [HDVICP0 ] to [2] ( 0x4e000634 = 0x0000000a )
Attached to slave procId 2.
Loaded file ../firmware/dvr_rdk_fw_m3vpss.xem3 on slave procId 2.
Started slave procId 2.
After Ipc_loadcallback status [0x00000000]
 [m3vpss ] system_vpass_freq value is:0xe4e1c00
 [m3vpss ] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3vpss ] notify_attach  rtnVal  0
 [m3vpss ] initProxyServer  rtnVal  0
 [m3vpss ]
 [m3vpss ]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3vpss ]
 [m3vpss ]  53: SYSTEM: IPC init in progress !!!
 [m3vpss ]  53: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1052: SYSTEM: Attaching to [HOST] ...
 [m3vpss ]  1054: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3vpss ]  1054: SYSTEM: Attaching to [VIDEO-M3] ...
After Ipc_startcallback status [0x097d2000]
Attached to slave procId 1.
Loaded file ../firmware/dvr_rdk_fw_m3video.xem3 on slave procId 1.
Started slave procId 1.
After Ipc_loadcallback status [0x00000000]
 [m3video] system_video_freq value is:0xe4e1c00
 [m3vpss ]  2053: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video] ***** SYSTEM  : Frequency <ORG> - 200000000, <NEW> - 240000000
 [m3video]
 [m3video]  *** UTILS: CPU KHz = 480000 Khz ***
 [m3video]
 [m3video]  1429: SYSTEM: IPC init in progress DMA: Module install successful, device major num = 250
!!!
 [m3video] DRV: Module install successful
 1429: SYSTEM: ADRV: Module built on Nov  1 2013 16:28:15
ttaching to [HOST] ...
 [m3video]  2429: SYSTEM: Attaching to [HOST] ...
 [m3video]  2431: SYSTEM: Attaching to [HOST] ... SUCCESS !!!
 [m3video]  2431: SYSTEM: Attaching to [VPSS-M3] ...
After Ipc_startcallback status [0x00000000]
 [c6xdsp ] Remote Debug Shared Memory @ 0xbfff0000
 [m3video] Remote Debug Shared Memory @ 0xbfff5020
 [m3vpss ] Remote Debug Shared Memory @ 0xbfffa040
 [m3vpss ]  3053: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video]  3431: SYSTEM: Attaching to [VPSS-M3] ...
 [m3vpss ]  4053: SYSTEM: Attaching to [VIDEO-M3] ...
 [m3video]  4054: SYSTEM: Attaching to [VPSS-M3] ... SUCCESS !!!
 [m3vpss ]  4054: SYSTEM: Attaching to [VIDEO-M3] ... SUCCESS !!!
 [m3video]  4054: SYSTEM: Opening MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
 [m3vpss ]  4054: SYSTEM: Creating MsgQ Heap [IPC_MSGQ_MSG_HEAP] ...
 [m3video]  4054: SYSTEM: Creating MsgQ [VIDEO-M3_MSGQ] ...
 [m3vpss ]  4054: SYSTEM: Creating MsgQ [VPSS-M3_MSGQ] ...
 [m3video]  4054: SYSTEM: Creating MsgQ [VIDEO-M3_ACK_MSGQ] ...
 [m3vpss ]  4054: SYSTEM: Creating MsgQ [VPSS-M3_ACK_MSGQ] ...
 [m3video]  4056: SYSTEM: Notify register to [HOST] line 0, event 15 ...
 [m3vpss ]  4056: SYSTEM: Notify register to [HOST] line 0, event 15 ...
 [m3video]  4057: SYSTEM: Notify register to [VPSS-M3] line 0, event 15 ...
 [m3vpss ]  4056: SYSTEM: Notify register to [VIDEO-M3] line 0, event 15 ...
 [m3video]  4057: SYSTEM: IPC init DONE !!!
 [m3vpss ]  4057: SYSTEM: IPC init DONE !!!
 [m3vpss ] Unhandled Exception:
 [m3vpss ] Exception occurred in ThreadType_Task
 [m3vpss ] handle: 0x37b68298.
 [m3vpss ] stack base: 0x37e5b100.
 [m3vpss ] stack size: 0x8000.
 [m3vpss ] R0 = 0x00000000  R8  = 0xffffffff
 [m3vpss ] R1 = 0x00000000  R9  = 0xffffffff
 [m3vpss ] R2 = 0x96d59715  R10 = 0xffffffff
 [m3vpss ] R3 = 0xfffffff1  R11 = 0xffffffff
 [m3vpss ] R4 = 0xffffffff  R12 = 0x0033d8a1
 [m3vpss ] R5 = 0xffffffff  SP(R13) = 0x37e630c8
 [m3vpss ] R6 = 0xffffffff  LR(R14) = 0x96d459d9
 [m3vpss ] R7 = 0xffffffff  PC(R15) = 0x0033d8a0
 [m3vpss ] PSR = 0x61000000
 [m3vpss ] ICSR = 0x0440f803
 [m3vpss ] MMFSR = 0x00
 [m3video]  4064: MEM: Shared Region 2: Base = 0xb8100000, Length = 0x07650000 (118 MB)
 [m3vpss ] BFSR = 0x01
 [m3vpss ] UFSR = 0x0000
 [m3vpss ] HFSR = 0x40000000
 [m3vpss ] DFSR = 0x00000000
 [m3vpss ] MMAR = 0xe000ed34
 [m3vpss ] BFAR = 0xe000ed38
 [m3vpss ] AFSR = 0x00000000
 [m3vpss ] Terminating Execution...
 [m3video]  4064: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4074: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4084: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4094: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4104: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4114: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4124: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4134: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4144: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4154: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4164: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4174: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4184: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4194: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4204: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4214: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4224: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4234: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4244: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4254: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4264: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4274: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4284: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4294: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4304: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4314: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4324: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4334: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4344: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4354: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4364: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4374: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4384: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4394: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4404: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4414: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4424: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4434: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4444: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4454: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4464: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4474: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4484: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4494: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4504: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4514: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4524: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4534: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4544: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4554: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4564: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4574: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4584: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4594: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4604: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4614: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4624: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4634: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4644: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4654: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4664: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4674: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4684: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4694: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4704: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4714: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4724: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4734: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4744: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4754: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4764: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4774: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4784: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4794: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4804: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4814: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4824: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4834: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4844: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4854: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4864: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4874: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4884: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4894: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4904: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4914: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4924: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4934: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4944: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4954: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4964: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4974: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)
 [m3video]  4984: MEM: ERROR: SharedRegion_setEntry (2, 0x36cb1b00) FAILED !!!  (status=-1)

И так бесконечно.

[u:e7
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #88 от 06/05/2017 16:14 цитата  

Ну тут либо видео драйвер некорректен\не инсталирован,либо повреждена данная область памяти куда драйвер грузит данные для вывода изо.Сам видеочип то похоже,что иницмализируется
GeParDos 
Участник
Сообщения: 106
 
Сообщение #89 от 06/05/2017 16:18 цитата  

n max писал:
Ну тут либо видео драйвер некорректен\не инсталирован,либо повреждена данная область памяти куда драйвер грузит данные для вывода изо.Сам видеочип то похоже,что иницмализируется


а как исправить не подскажете ?
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #90 от 06/05/2017 16:48 цитата  

В случаи неисправности памяти тут уж только менять.Если нанд прибита то можно вытянуть с планшета или флеш накопителя,если оперативка то с видеокарт или планок озу.Оперативу можно и перекатать мож шар отвалился--можно погреть с хорошим флюсом мож и законтачит(в целях диагностики),а потом перекатывать.Не поможет оператива,тогда проц греть\катать.В планшетах и телефонах такое было чаще из-за проца

ДОБАВЛЕНО 06/05/2017 16:49

Снимаешь проц,а там серые пятаки со стороны проца-очень часто,на заводе незалудили...
GeParDos 
Участник
Сообщения: 106
 
Сообщение #91 от 06/05/2017 17:01 цитата  

если с планшета брать как ее шить у меня прогера нет для нандов, греть я уже грел толку нет, шары катать нужны трафареты которых нет
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #92 от 06/05/2017 17:48 цитата  

Пробовать с чистой флешкой отправить образ прошивки он ведь грузится в озу потом стирает флешь,потом пишется.Шить лучше в том устройстве где она будет работать,чтоб бед блоки прописались и система их не использовала.Пробовать пока так.Или в другом устройстве через джитаг или через штатный прошивальщик этого устройства(навигатора,планшета телефона),если он сможет читать прошивку.
GeParDos 
Участник
Сообщения: 106
 
Сообщение #93 от 06/05/2017 18:01 цитата  

n max писал:
Пробовать с чистой флешкой отправить образ прошивки он ведь грузится в озу потом стирает флешь,потом пишется.Шить лучше в том устройстве где она будет работать,чтоб бед блоки прописались и система их не использовала.Пробовать пока так.Или в другом устройстве через джитаг или через штатный прошивальщик этого устройства(навигатора,планшета телефона),если он сможет читать прошивку.


маленько не понял, можно по подробнее
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #94 от 06/05/2017 18:02 цитата  

Я до покупки программатора шил нанды на планшете 3Q туда запаял панельку и через джитаг шил и читал.Причём достаточно только платы от него,питание через штатный усб разъём батарею можно выкинуть.До 4гБит шил без проблем,больше мозги проца не могли адресовать
GeParDos 
Участник
Сообщения: 106
 
Сообщение #95 от 06/05/2017 18:03 цитата  

так а как я в озу загружу прошивку если флешка чистая будет там же через бут все делается
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #96 от 06/05/2017 18:04 цитата  

Да и программатор нижнего ценового диапазона(тритон и же с ним) вам может не помочь.Т.к. в новой флешке могут быть бед блоки с завода и не все программаторы грамотно их обходят или не обходят

ДОБАВЛЕНО 06/05/2017 18:05

GeParDos писал:
так а как я в озу загружу прошивку если флешка чистая будет там же через бут все делается


Бут в маленькой микросхеме
GeParDos 
Участник
Сообщения: 106
 
Сообщение #97 от 06/05/2017 18:05 цитата  

n max писал:
Я до покупки программатора шил нанды на планшете 3Q туда запаял панельку и через джитаг шил и читал.Причём достаточно только платы от него,питание через штатный усб разъём батарею можно выкинуть.До 4гБит шил без проблем,больше мозги проца не могли адресовать


вариант с jtag на планшете интересный надо попробовать

ДОБАВЛЕНО 06/05/2017 18:06

а процесс работы с таким способом можно подробнее
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #98 от 06/05/2017 18:06 цитата  

Производитель шьёт прямо в девайсе эти нанды через какую-то дырочку

ДОБАВЛЕНО 06/05/2017 18:09

GeParDos писал:
n max писал:
Я до покупки программатора шил нанды на планшете 3Q туда запаял панельку и через джитаг шил и читал.Причём достаточно только платы от него,питание через штатный усб разъём батарею можно выкинуть.До 4гБит шил без проблем,больше мозги проца не могли адресовать


вариант с jtag на планшете интересный надо попробовать

ДОБАВЛЕНО 06/05/2017 18:06

а процесс работы с таким способом можно подробнее


Ищете девайс,чтоб процессор в нём был в списке поддерживаемых прогой H-jtag делаете приблуду припаиваетесь к пятакам и вперёд
GeParDos 
Участник
Сообщения: 106
 
Сообщение #99 от 06/05/2017 18:12 цитата  

то есть родную флеш не надо отпаивать а на ее место паять прошиваеваемую? нужно нанд подпаять как то по верх родной правильно понял?
n max 
Модератор
<B>Модератор</B>
Сообщения: 12131
 
Сообщение #100 от 06/05/2017 18:14 цитата  

Можно и навигатор заюзать на проце сирф атлас на 4пна(не пда) есть инфа по этому вопросу

ДОБАВЛЕНО 06/05/2017 18:16

GeParDos писал:
то есть родную флеш не надо отпаивать а на ее место паять прошиваеваемую? нужно нанд подпаять как то по верх родной правильно понял?


Родная флеш выпаивается и на неё место ставиться панелька и получается программатор из планшета,и можно читать и писать--планшетом он больше не будет

Перейти: 
Следующая тема · Предыдущая тема
На страницу Пред.  1, 2, 3, 4, 5, 6, 7  След.
Показать/скрыть Ваши права в разделе

Интересное от ESpec


Другие темы раздела Другая аппаратура



liveinternet.ru RadioTOP Rambler's Top100 Рейтинг@Mail.ru