Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

мля пиши подробнее.
в какое меню зашел? которое в меню ресивера или которое должно быть при старте с усб стиком?

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

В ресивере выбрал обновление с USB, пошла распаковка, прошивка - 100%, перезагрузка и BOOTING... Надо zboot искать?

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

а как насчет провести обновление не из меню ресивера? как в доку?
почему ты всё делаешь по своему, зачем тогда просишь совета?
мне это уже начинает надоедать

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

А как, вставил флеху, перезагружаюсь и BOOTING.
Я сейчас снова в меню ресивера, что можно сделать? Вот лог

Spoiler

YAMON> load -b tftp://192.168.0.10/xrpc_xload_vmlinux_ES4_prod.bin 0xx90020000
About to load tftp://192.168.0.10/xrpc_xload_vmlinux_ES4_prod.bin
Press Ctrl-C to break
.................................................. ..............
.................................................. ..............
.................................................. ..............
.........

Start = 0x90020000, range = (0x90020000,0x9066bf43), format = BINARY
Length = 0x64bf44 (6602564)
Checksum = 0xb57b7a66

YAMON> xrpc 0x90020000
xrpc succeeded
YAMON> load zbf 0xb3000000
Checking zboot signature.. it's a zboot file, signature OK.
Decompressing to 0x90020000 ..
Output length: 0x0096843a(9864250)
load compressed zboot file from 0xb3000000 to 0x90020000 OK
YAMON> go
em86xx_eth ethernet stop
Linux version 2.6.15-sigma (kevin@kevin-laptop) (gcc version 3.4.2) #138 PREEMPT
Thu Jan 22 21:35:07 KST 2009
Configured for SMP863x (revision ES6/RevA), detected SMP8634 (revision ES9/RevC)
.
SMP863x/SMP865x Enabled Devices under Linux/XENV 0x48000000 = 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
Valid MEMCFG found at 0x10000fc0.
CPU revision is: 00019069
Determined physical RAM map:
memory: 02fe0000 @ 10020000 (usable)
User-defined physical RAM map:
memory: 06ae0000 @ 10020000 (usable)
On node 0 totalpages: 92928
DMA zone: 92928 pages, LIFO batch:31
DMA32 zone: 0 pages, LIFO batch:0
Normal zone: 0 pages, LIFO batch:0
HighMem zone: 0 pages, LIFO batch:0
Built 1 zonelists
Kernel command line: mem=107m console=ttyS0,115200
Primary instruction cache 16kB, physically tagged, 2-way, linesize 16 bytes.
Primary data cache 16kB, 2-way, linesize 16 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 2048 (order: 11, 32768 bytes)
Using 150.188 MHz high precision timer.
Console: colour dummy device 80x25
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 96256k/109440k available (4425k kernel code, 13156k reserved, 1007k data
, 4200k init, 0k highmem)
Calibrating delay loop... 296.96 BogoMIPS (lpj=148480)
Mount-cache hash table entries: 512
Checking for 'wait' instruction... available.
NET: Registered protocol family 16
tangox: creating TLB mapping for 0x20000000 at 0xc0000000, size 0x08000000.
PCI: Initializing SMP863x/SMP865x PCI host controller
PCI: Remapped PCI I/O space 0x58000000 to 0xc8020000, size 64 kB
PCI: Remapped PCI config space 0x50000000 to 0xc8004000, size 10 kB
PCI: device 1 disabled
PCI: device 4 disabled
PCI: Configured SMP863x/SMP865x as PCI slave with 128MB PCI memory
PCI: Region size is 16384KB
PCI: Map DMA memory 0x10020000-0x16b00000 for PCI at 0x11000000
SCSI subsystem initialized
usbcore: registered new driver usbfs
usbcore: registered new driver hub
tangox frequency scaling module installed.
Created /proc/cpucache_info entry.
NTFS driver 2.1.25 [Flags: R/W DEBUG].
JFFS2 version 2.2. (C) 2001-2003 Red Hat, Inc.
SGI XFS with no debug enabled
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
Software Watchdog Timer: 0.07 initialized. soft_noboot=0 soft_margin=60 sec (now
ayout= 0)
Serial: 8250/16550 driver $Revision: 1.90 $ 2 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 9) is a 16550A
serial8250: ttyS1 at MMIO 0x0 (irq = 10) is a 16550A
loop: loaded (max 8 devices)
nbd: registered device at major 43
tango2_enet: ethernet driver for SMP863x internal mac
tango2_enet: detected phy at address 0x01
tango2_enet: mac address 00:02:14:16:b6:35
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: SMP863x/SMP865x Bus Mastering IDE controller
Probing IDE interface ide0...
hda: DM255610V010, ATA DISK drive
hda: no 80 conductors cable, falling back to lower udma mode
hda: set to Ultra DMA mode 2
ide0: DMA enabled for ATA DISK hda
ide0 at 0x223c0-0x223c7,0x22398 on irq 26
hda: max request size: 128KiB
hda: 501760 sectors (256 MB) w/1KiB Cache, CHS=980/16/32, UDMA(33)
hda: cache flushes not supported
hda: hda1 hda2 hda3 hda4
physmap flash device CS2: 800000 at 48000000
CS2: Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
Amd/Fujitsu Extended Query Table at 0x0040
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Using physmap partition definition
Adding partition #1-#5
Creating 5 MTD partitions on "CS2: Physically mapped flash":
0x00000000-0x00020000 : "CS2-Part1"
0x00020000-0x00040000 : "CS2-Part2"
0x00040000-0x00080000 : "CS2-Part3"
0x00080000-0x00700000 : "CS2-Part4"
0x00700000-0x00800000 : "CS2-Part5"
Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
mice: PS/2 mouse device common for all mice
Advanced Linux Sound Architecture Driver Version 1.0.10rc3 (Mon Nov 07 13:30:21
2005 UTC).
usbcore: registered new driver snd-usb-audio
ALSA device list:
No soundcards found.
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 4, 65536 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
TCP bic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Freeing unused kernel memory: 4200k freed
mount: /etc/mtab: No such file or directory
Initializing random number generator... done.
===> Starting system configuration...
===> [0] replace busybox 1.15.2(udhcpc, ftpget, ftpput)
===> [1] VFD initializing...
[td210] INITIALIZED END
[td210] SLEEP MODE OFF
===> [2] USB 2.0 driver loading...
Using /lib/modules/2.6.15-sigma/kernel/drivers/usb/host/uhci-hcd.ko
USB Universal Host Controller Interface driver v2.3
PCI: Enabling device 0000:00:02.0 (0000 -> 0001)
uhci_hcd 0000:00:02.0: UHCI Host Controller
uhci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 1
uhci_hcd 0000:00:02.0: irq 22, io base 0x58000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
PCI: Enabling device 0000:00:02.1 (0000 -> 0001)
uhci_hcd 0000:00:02.1: UHCI Host Controller
uhci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:02.1: irq 22, io base 0x58000020
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
Using /lib/modules/2.6.15-sigma/kernel/drivers/usb/host/ehci-hcd.ko
PCI: Enabling device 0000:00:02.2 (0000 -> 0002)
ehci_hcd 0000:00:02.2: EHCI Host Controller
ehci_hcd 0000:00:02.2: new USB bus registered, assigned bus number 3
ehci_hcd 0000:00:02.2: irq 22, io mem 0x60008000
ehci_hcd 0000:00:02.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 4 ports detected
===> [3] File system checking...
check hda
Disk /dev/hda: 256 MB, 256901120 bytes
/dev/hda1 1 560 143359+ 83 Linux
/dev/hda2 561 624 16384 83 Linux
/dev/hda3 625 656 8192 83 Linux
/dev/hda4 657 980 82944 83 Linux
EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda2, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda3, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on hda4, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
check hdb
Cannot find HDD
===> [4] Make device files
mknod: /dev/mum0: File exists
mknod: /dev/em8xxx0: File exists
===> [5] Export hostname
Starting network...
>> pre-up start...
route: SIOC[ADD|DEL]RT: No such process
>> pre-up end...
eth0: link up, 100Mbps, full-duplex, lpa 0x41E1
===> Starting services...
===> [1] telnetd starting...
===> Starting MMP custom setting...

AZBox login: llad: module license 'LGPL' taints kernel.
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1570] init_module: begun
em8xxx0 [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP8
634_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.w
ork/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1431] identify: board as unkno
wn subid
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1556] identify: device 0x8634 0
x86 accepted with software tango2revA
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1635] mumk_register_tasklet 0xc
809a000
mumk_register_tasklet: (0) tasklet c809a000 status @c8da3ea4
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[0] 0xc80a7000: pE=0xc8da3c80 ch_idx=33 module_id=0x3c 0xc8da3ca0
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[1] 0xc80a9000: pE=0xc8da3c80 ch_idx=35 module_id=0x3c 0xc8da3cac
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[2] 0xc80ab000: pE=0xc8da3c80 ch_idx=41 module_id=0x13c 0xc8da3cb8
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[3] 0xc80ad000: pE=0xc8da3c80 ch_idx=43 module_id=0x13c 0xc8da3cc4
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[4] 0xc80af000: pE=0xc8da3c80 ch_idx=37 module_id=0x23c 0xc8da3cd0
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[5] 0xc80b1000: pE=0xc8da3c80 ch_idx=39 module_id=0x23c 0xc8da3cdc
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:353] mumk_register_channel_task
let[6] 0xc80b3000: pE=0xc8da3c80 ch_idx=69 module_id=0x3f 0xc8da3ce8
em8xxx [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP86
34_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.wo
rk/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1732] init_module: done. Found
1 em8xxx
>>>>>>> CONFIG_TANGO2 :: HZ = 1000
scard: SMP8634 driver loaded (rd_buffer_size = 288, wr_buffer_size = 288, freq =
3600000)
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial Driver core
drivers/usb/serial/usb-serial.c: USB Serial support registered for FTDI USB Seri
al Device
usbcore: registered new driver ftdi_sio
drivers/usb/serial/ftdi_sio.c: v1.4.3:USB FTDI Serial Converters Driver
cdfs 2.6.27 loaded.
fuse: Unknown symbol r4k_flush_cache_page
PCI: Enabling device 0000:00:03.0 (0000 -> 0002)
RT61: Vendor = 0x1814, Product = 0x0301
PCI: Setting latency timer of device 0000:00:03.0 to 64
rtusb init --->
usbcore: registered new driver rt2870
RT61: RfIcType= 3
em8xxx0 [/DATA/Yellow.mine/Working/SigmaDesign8634/SMP8634-2850.gcc3.4/mrua_SMP8
634_v2_8_5_1_celrun_lg_branch_10212009-HDMI-fix_facsprod_legacy_dev.mips.nodts.w
ork/MRUA_src/rua/emhwlib_kernel/kernel_src/krua.c:1237] EMhwlibUnregisterCleanab
le module 45, prop 4543 (from rmmod em8xxx_id 827): not found

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

это последнее, что я могу посоветовать
http://www.pristavka.de/index.php/to....html#msg87132
сделать то о чем ты писал сотню раз, других идей нет, надеюсь коллеги с сигмаплеер сайта тебе еще подкинут пару идей

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

[quote author=VVZ link=topic=5763.msg87115#msg87115 date=1285444055]
Прошил:
load -b tftp://192.168.0.20/backup_kernel 0xb0100000
pflash write -f 0x80000 0xb0100000 0x680000

Writing :
.................................................. ..............................
.................................................. ..............................
.................................................. ...............
Verifying (RAM 0xb0100000, size 0x680000) : OK.
YAMON>

Урааа, память жива, а что дальше?
[/quote]
Я делал это, BOOTING

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

после ручного ребута был бутинг, акромя комманд делал дальнейшие указания?
как по мне ты либо не договариваешь чегото, либо не делал и это очень сильно напрягает, пипец как напрягает, из тебя каждое слово нужно тянуть

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

.................................................. ...............
Verifying (RAM 0xb0100000, size 0x680000) : OK.
YAMON> и все - отключил ресивер - вставил флешку с прошивкой "patch.bin" - включил ресивер и BOOTING.
В архиве с "backup_kernel" есть файл "update", может его надо затем прошить, но куда?

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

может в этом случае нужно делать ребут по другому, без выдирания из розетки, чтобы прошивка висела в памяти? после выключения ресивера всё удаляется, тк ты вроде пишешь в рам память...
ну может я и ошибаюсь, но всёже когда пишут рестарт то наверное имеют ввиду рестарт а не выдергивание питания

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

Отключал только тумблером, а не из розетки.

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

я в шоке, а какая нах разнеца между отрублением тумблером и выхдергиваем из розетки?
что в лоб, что по лбу, всё одинаково или?

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

О,,, можно пультом попробовать YAMON> - вставил флеху и пультом ребут, как вариант? Ресивер мой реагирует на команды пульта.

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

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

[VVZ]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

Error : Command not found : reboot
Error : Command not found : restart
Error : Command not found : off
YAMON>

[nitrogen14]

Re: Azbox RS232(PC)->TTL(AZ) / USB(PC)->TTL(AZ) & YAMON - побеждаем вечный "BOOTING"

http://www.google.de/url?sa=t&source...jw&cad=rja


NAME reset (Atlas/Malta/SEAD-2)
SYNOPSIS reset
DESCRIPTION Performs a hardware reset of the board.
OPTIONS None

может оно?