Технический форум по настройке и эксплуатации АТС http://www.atsvtule.ru/forum/ |
|
ipecs-mg 100 http://www.atsvtule.ru/forum/viewtopic.php?f=5&t=2044 |
Страница 1 из 1 |
Автор: | kryuchkov [ 11 апр 2017, 09:36 ] |
Заголовок сообщения: | ipecs-mg 100 |
Добрый день, Столкнулся с данной АТС ipecs-mg 100 впервые. Есть проблемы при загрузке Код: ARMboot Bz17934_1 lge NORFLASHBOOT (Aug 22 2011 - 15:01:41) ARMboot code: 03f00000 -> 03f410f4 NAND CHIP : 0 NAND MID:0xec, Chip ID:0xf1 (Samsung NAND 128MB 3,3V) NAND CHIP : 1 NAND MID:0xec, Chip ID:0xf1 (Samsung NAND 128MB 3,3V) Comcerto info: CPU: M828xx EVM: MPB100 SDC Version: 0x560e SDC Device ID: 0x130 Bounding option: 0xecc9 CFG HZ: 132000000 NAND MSP start: 1 NAND MSP size: 31 NAND CSP start: 0 NAND CSP size: 0 NOR Base addr: 0x11000000 EPROM Base addr: 0x00000000 DRAM Configuration: Bank #0: 00800000 56 MB Bank #1: 04000000 47 MB *** sdram start 0x00800000 *** sdram size 0x03800000 *** 2nd sdram start 0x04000000 *** 2nd sdram size 0x02f00000 *** boot param addr 0x00800100 Hit Ctrl-C key to stop autoboot: 0 Start DeMerge Kernel DeMerge:: unzip MSP success [size is 1948976] DeMerge:: CSP size is 1613000 [112f1a05 >> 00f89cc8] DeMerge Success (MSP) at 0x01000000, (CSP) at 0x00E00000 ... Downloading MSP Image from 0x1000000 ... code_offset=0x80 code_base=8000 data_offset=cd3d0 code_size=cd350 data_base=d5350 data_size=ec418 zeroinit_base=1c1768 prog_entry=100 AIFHEADER: BL_DecompressCode=e1a00000 BL_SelfRelocCode=e1a00000 BL_DbgInitZeroInit=eb00000c EntryPointOffset=ffff8100 ProgramExitInstr=ef000011 ImageReadOnlySize=cd350 ImageReadWriteSize=ec418 ImageDebugSize=1e0fc ImageZeroInitSize=dd64 ImageDebugType=1df041 ImageBase=8000 WorkSpace=0 AddressMode=20 DataBase=0 FirstFatOffset=1d78e4 Reserved2=0 DebugInitInstr=e1a00000 ZeroInitCode[0]=e04ec00f Booting ARM0 (CSP) at 0x00E00000 ... Booting ARM1 (MSP) at 0x00000100 ... Linux version 2.6.11.7-1.07.0malindi (chows@ipecsmg.lgericsson.com) (gcc version 3.3.2 20030820 (prerelease)) #180 Mon Aug 22 10:59:58 KST 2011 CPU: ARM920Tid(wb) [41129200] revision 0 (ARMv4T) 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 Machine: ARM-M828xx Comcerto Memory policy: ECC disabled, Data cache writeback Built 1 zonelists Kernel command line: console=ttyS0,115200 root=/dev/mtdblock1 rw ip=10.10.10.1:10.10.10.10:10.10.10.254:255.255.255.0::eth0 PID hash table entries: 512 (order: 9, 8192 bytes) timer1 enable######### timer2 disable $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ timer3 disable $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Memory: 56MB 47MB = 103MB total Memory: 100864KB available (2557K code, 637K data, 308K init) Mount-cache hash table entries: 512 (order: 0, 4096 bytes) CPU: Testing write buffer coherency: ok NET: Registered protocol family 16 Comcerto GPIO: init Comcerto GPIO: GPIOs 0 configured as IRQ source(s) Comcerto PCI: init Comcerto PCI: Comcerto device is not configured in PCI host Verify that HBMODE_n(low) pin is high and HBBURSTEN_n(high) pin is low On Mindspeed MH02-D370-xxx board, remove jumper JPCISLV1 SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub SPI core: loaded version 0.2 NetWinder Floating Point Emulator V0.97 (double precision) NTFS driver 2.1.22 [Flags: R/W DEBUG]. JFFS2 version 2.2. (NAND) (C) 2001-2003 Red Hat, Inc. yaffs Aug 20 2011 11:46:08 Installing. Initializing Cryptographic API Crypto engine S/W registered Serial: 8250/16550 driver $Revision: 1.1.1.3 $ 2 ports, IRQ sharing disabled Serial: Comcerto 16550 serial driver $Revision: 1.4 $ ttyS0 at MMIO 0x10090000 (irq = 41) is a 16550A ttyS1 at MMIO 0x10094000 (irq = 58) is a 16550A io scheduler noop registered loop: loaded (max 8 devices) nbd: registered device at major 43 skb pool filled with 512 skb m828xx_msp_start() stop EMAC0 control stop_emac0: already stopped m828xx_msp_ready() MSP version : $Version: m828_v2_06_6 $ msp_ready: MSP is running switch eth0 to VED mode smi_memory_phy = 6f0000 SharedMemoryRxControlStructure(PA): 0x800023c SharedMemoryRxControlStructure(VA): 0xf800023c SharedMemoryTxControlStructure(PA): 0x800023c SharedMemoryTxControlStructure(VA): 0xf800023c drivers/net/comcerto_ved.c: 1630: SetupSMIBuffers: 1280 buffers allocated Comcerto SMI: fpq(PA): 0x8001350 Comcerto SMI: fpq(VA): 0xf8001350 Comcerto SMI: fpq(PA): 0x8001370 Comcerto SMI: fpq(VA): 0xf8001370 Comcerto SMI: fpq(PA): 0x800021c Comcerto SMI: fpq(VA): 0xf800021c Comcerto SMI: fpq(PA): 0x800022c Comcerto SMI: fpq(VA): 0xf800022c Comcerto SMI: fpq(PA): 0x8001360 Comcerto SMI: fpq(VA): 0xf8001360 Comcerto SMI: fpq(PA): 0x8001380 Comcerto SMI: fpq(VA): 0xf8001380 PPP generic driver version 2.4.2 PPP Deflate Compression module registered PPP BSD Compression module registered MPPE/MPPC encryption/compression module registered NET: Registered protocol family 24 SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). mtd: NAND opt=c0779e34, ale-cycles=4, blk(rd=16, wr=16), ce=1, tR=0 NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 682 at 0x05540000 Bad eraseblock 975 at 0x079e0000 Creating 2 MTD partitions on "NAND 128MiB 3,3V 8-bit": 0x00000000-0x00400000 : "NAND#0 Kernel partition" 0x00400000-0x08000000 : "NAND#0 Comcerto Filesystem partition" mtd: NAND opt=c0779a34, ale-cycles=4, blk(rd=16, wr=16), ce=2, tR=0 NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 477 at 0x03ba0000 Bad eraseblock 480 at 0x03c00000 Creating 3 MTD partitions on "NAND 128MiB 3,3V 8-bit": 0x00000000-0x01800000 : "NAND#1 prompt message partition" 0x01800000-0x02800000 : "NAND#1 system announcement partition" 0x02800000-0x08000000 : "NAND#1 all nation prompt rom partition" m828xx-ohci m828xx-ohci: at 0xd00e0400, irq 13 m828xx-ohci m828xx-ohci: new USB bus registered, assigned bus number 1 usb usb1: Product: M828xx OHCI usb usb1: Manufacturer: Linux 2.6.11.7-1.07.0malindi ohci_hcd usb usb1: SerialNumber: m828xx-ohci hub 1-0:1.0: USB hub found hub 1-0:1.0: 2 ports detected USB Universal Host Controller Interface driver v2.2 Initializing USB Mass Storage driver... usbcore: registered new driver usb-storage USB Mass Storage support registered. i2c /dev entries driver SPI core: add adapter comcerto-spi ISDN subsystem Rev: 1.1.1.3/1.1.1.2/1.1.1.2/1.1.1.3/none/1.1.1.1 PPP BSD Compression module registered isdnloop-ISDN-driver Rev 1.1.1.2 Register LDKPPP Device Driver. isdnloop: (loop0) virtual card added Crypto engine MSPD IPsec2 registered NET: Registered protocol family 2 IP: routing cache hash table of 512 buckets, 4Kbytes TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 2, 16384 bytes) TCP: Hash tables configured (established 4096 bind 4096) IPv4 over IPv4 tunneling driver Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 15 IP-Config: Complete: device=eth0, addr=10.10.10.1, mask=255.255.255.0, gw=10.10.10.254, host=10.10.10.1, domain=, nis-domain=(none), bootserver=10.10.10.10, rootserver=10.10.10.10, rootpath= yaffs: dev is 32505857 name is "mtdblock1" yaffs: Attempting MTD mount on 31.1, "mtdblock1" yaffs: MTD device does not support have the right page sizes yaffs: dev is 32505857 name is "mtdblock1" yaffs: Attempting MTD mount on 31.1, "mtdblock1" block 651 is bad ,so Try to clean!! Clean block 651 Fail!! block 944 is bad ,so Try to clean!! Clean block 944 Fail!! yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs: Allocation block 384 was not highest sequence id: block seq = 5693, dev seq = 5694 yaffs tragedy: attempting to use non-directory as a directory in scan. Put in lost+found. VFS: Mounted root (yaffs2 filesystem). Freeing init memory: 308K init started: BusyBox v1.01 (2006.02.06-07:50+0000) multi-call binary Starting pid 17, console /dev/console: '/etc/rc' Bummer, could not run '/etc/rc': Exec format error Bummer, could not run '/etc/rc': Exec format error Starting pid 22, console /dev/console: '/sbin/getty' Документации ровным счетом никакой с атс не предоставили Проблема, по моему мнению в нанд памяти. В связи с чем вопросы: Как прошивается данное устройство? можно ли полностью очистить нанд память. Если не составит труда участникам, то не откажусь от мануала по прошивке и программ.)) и самой прошивки. Очень жду ответа. Заранее благодарен |
Автор: | Dron [ 11 апр 2017, 09:43 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Я бы посоветовал процедуру рекавери. При рекавери тестируется память и исключаются битые сектора. Используется специальная прошивка recavery. |
Автор: | kryuchkov [ 11 апр 2017, 09:49 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Dron писал(а): Я бы посоветовал процедуру рекавери. При рекавери тестируется память и исключаются битые сектора. Используется специальная прошивка recavery. Не могли бы вы, если это возможно предоставить инструкцию? |
Автор: | Dron [ 11 апр 2017, 09:52 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
https://yadi.sk/d/ppJn2HJgqyxtR |
Автор: | kryuchkov [ 11 апр 2017, 09:54 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Премного благодарен, буду разбираться. |
Автор: | kryuchkov [ 11 апр 2017, 11:07 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Уточните в каком положении должны находится переключатели MODE? on или off? |
Автор: | Dron [ 11 апр 2017, 11:15 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Я думал, вы уже все сделали! Где-нибудь в инструкции по процедуре рекавери вы видели что-нибудь про эти переключатели? Там этого нет, значит, и трогать их не надо! |
Автор: | kryuchkov [ 12 апр 2017, 11:56 ] |
Заголовок сообщения: | Re: ipecs-mg 100 |
Все получилось вчера, при запуске все же мелькают сообщения о битых блоках памяти, но атс стартует корректно. Спасибо за помощь. |
Страница 1 из 1 | Часовой пояс: UTC + 3 часа |
Powered by phpBB® Forum Software © phpBB Group https://www.phpbb.com/ |