Объявление

**nitrogen14** · 18-09-2010, 12:16

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

ищем дружно эти два файла xrpc_xload_vmlinux_ES4_prod.bin, vmlinux.bin

Spoiler

архив назывался так:
xrpc_xload_vmlinux_ES4_prod.bin_vmlinux.bin.tar.gz

и пытаемся загрузится одним из двух способов:

xrpc_xload_vmlinux_ES4_prod.bin:
YAMON> net init
YAMON> load -b tftp://172.30.11.222/xrpc_xload_vmlinux_ES4_prod.bin 0x90020000
YAMON> dump romfs 0x90020000
ROMFS found at 0x90020000, Volume name = MIPS_LINUX_XRPC
90020040 : Name = ., Type = dir, Size = 00000000, Next = 00000040
90020060 : Name = .., Type = hard link, Size = 00000000, Next = 00000060
90020090 : Name = xrpc_xload_vmlinux_ES4_dev.bin, Type = file, Size = 00326444, Next = 00000000
YAMON> xrpc 0x90020090
YAMON> load zbf 0xb3000000
YAMON> go

vmlinux.bin:
YAMON> net init
YAMON>load -b tftp://172.30.11.222/vmlinux.bin 0X9002000
YAMON>go

тк у тебя один файл имеется то после загрузлки его в облать памяти 0X9002000 запусти его коммандой гоу.
не знаю какой из файлов выше 4й раздел, а какой 5й, но видно, что запускаются они одинакого

пс. если ты не заметил, то на прошлой странице я написал еще пару сообщений

**nitrogen14** · 18-09-2010, 12:29

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

вот еще интересная инфа

Verifying the Kernel Image

* First, you need to find the address of the kernel image (xrpc_xload_vmlinux) on the flash via the 'dump romfs' command:

>YAMON> dump romfs 0x80000
ROMFS found at 0xa4080000, Volume name = MIPS_LINUX_XRPC
a4080040 : Name = ., Type = dir, Size = 00000000, Next = 00000040
a4080060 : Name = .., Type = hard link, Size = 00000000, Next = 00000060
a40800a0 : Name = xrpc_xload_vmlinux_8634_ES4_dev.bin, Type = file, Size = 003a0

* In this case the address is 0xa40800a0. At the YAMON prompt, load the kernel image from its location on the flash to RAM. The ZBF headers and xload take care of the gory details:

YAMON> pflash probe
YAMON> xrpc 0xa40800a0
xrpc succeeded
YAMON> load zbf 0xb3000000

* Pass any kernel boot parameters to the a.linux_cmd xenv key (see Documentation/kernel-parameters.txt in the kernel source tree).
* Start the kernel using the go command with any optional parameter.

host> go

* After the kernel boots up, enter root at the login prompt and press return.
* You are now logged in on and running the Linux on your standalone SMP8634!

вобщем для тестов найдено достаточно инфы

**VVZ** · 18-09-2010, 13:10

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

@nitrogen14 - спасибо за инфу!

  После работы (сижу уже как на иголках) я в онлайне и пробуем.

xrpc_xload_vmlinux_ES4_prod.bin_vmlinux.bin.tar.gz (12.59 MB) - скачал
В архиве 2 файла:
                              vmlinux.bin
                              xrpc_xload_vmlinux_ES4_prod.bin

**Gennadyi** · 18-09-2010, 19:58

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

список переменных xenv

Spoiler

a.avclk_mux = 0x00000000 # 0
a.board_id = "852-E2"
a.cd2_freq = 0x05b8d800 # 96000000
a.cd4_freq = 0x01fca055 # 33333333
a.cd5_freq = 0x017d7840 # 25000000
a.cd6_freq = 0x01312d00 # 20000000
a.cd7_freq = 0x01312d00 # 20000000
a.chip_rev = 0x86340086 # -2043412346
a.enable_devices = 0x00021ace # 137934
a.gpio_data = 0x76000000 # 1979711488
a.gpio_dir = 0x76000038 # 1979711544
a.gpio_irq_map = 0x20090820 # 537462816
a.hostclk_mux = 0x00000100 # 256
a.irq_fall_edge_hi = 0x00000000 # 0
a.irq_fall_edge_lo = 0x0000c000 # 49152
a.irq_rise_edge_hi = 0x0000009f # 159
a.irq_rise_edge_lo = 0xff28ca00 # -14104064
a.pb_cs_config = 0x000e0040 # 917568
a.pb_def_timing = 0x10101010 # 269488144
a.pb_timing0 = 0x10101010 # 269488144
a.pb_timing1 = 0x00110101 # 1114369
a.pb_timing2 = 0x105f1010 # 274665488
a.pb_use_timing0 = 0x000003f4 # 1012
a.pb_use_timing1 = 0x000003f3 # 1011
a.pb_use_timing2 = 0x000003f8 # 1016
a.pcidev1_irq_route = 0x01010101 # 16843009
a.pcidev2_irq_route = 0x01010101 # 16843009
a.pcidev3_irq_route = 0x02020202 # 33686018
a.pcidev4_irq_route = 0x02020202 # 33686018
a.scard_5v_pin = 0x00000001 # 1
a.scard_cmd_pin = 0x00000002 # 2
a.scard_off_pin = 0x00000000 # 0
a.uart0_baudrate = 0x0001c200 # 115200
a.uart0_gpio_data = 0x00000000 # 0
a.uart0_gpio_dir = 0x00000000 # 0
a.uart0_gpio_mode = 0x00007f6e # 32622
a.uart1_baudrate = 0x00002580 # 9600
a.uart1_gpio_data = 0x00000000 # 0
a.uart1_gpio_dir = 0x00000000 # 0
a.uart1_gpio_mode = 0x00007f6e # 32622
a.uart_console_port = 0x00000000 # 0
a.uart_used_ports = 0x00000002 # 2
l.cs0_size = 0x00000000 # 0
l.cs1_size = 0x00000000 # 0
l.cs2_part1_offset = 0x00000000 # 0
l.cs2_part1_size = 0x00020000 # 131072
l.cs2_part2_offset = 0x00020000 # 131072
l.cs2_part2_size = 0x00020000 # 131072
l.cs2_part3_offset = 0x00040000 # 262144
l.cs2_part3_size = 0x00040000 # 262144
l.cs2_part4_offset = 0x00080000 # 524288
l.cs2_part4_size = 0x00680000 # 6815744
l.cs2_part5_offset = 0x00700000 # 7340032
l.cs2_part5_size = 0x00100000 # 1048576
l.cs2_parts = 0x00000005 # 5
l.cs2_size = 0x00800000 # 8388608
l.cs3_size = 0x00000000 # 0
x.boot = 0x00020000 # 131072
x.csf = 0x00000002 # 2
x.d0.cfg = 0xf34111ba # -213839430
x.d0.dl0 = 0x000a4444 # 672836
x.d1.cfg = 0xf34111ba # -213839430
x.d1.dl0 = 0x000a4444 # 672836
x.ds = 0x00020080 # 131200
x.dt = 0x00000001 # 1
x.mux = 0x00000701 # 1793
x.pll3 = 0x01020057 # 16908375
y.gateway = "10.0.1.1"
y.ipaddr = "10.0.1.199"
y.start = "xrpc 0xac080090; load zbf 0xb3000000; go"
y.startdelay = "1"
y.subnetmask = "255.255.0.0"
z.boot0 = 0x00040000 # 262144
z.boot1 = 0x00080000 # 524288
z.boot2 = 0x00040000 # 262144
z.boot3 = 0x00080000 # 524288
a.build_date = "TD210:20090123"
a.eth_mac = "00.02.14.14.41.BA"
a.linux_cmd = "mem=107m console=ttyS0,115200"

конкретно -

Spoiler

**nitrogen14** · 18-09-2010, 20:18

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

@Gennadyi
давай уже по существу, твои посты никак не относятся к теме.
повторюсь, здес речь идет о азбокс, а не о других сигможелеяках

@VVZ

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

**Gennadyi** · 18-09-2010, 20:22

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

я ваш азбокс в глаза не видел

как и 301
думать вам никто не запрещал
хелп к YAMON для 863х

Spoiler

YAMON> help

Available commands :

. . (repeat last command line)
; ; (command separator)
+ + <repeat count> ;
cache cache [ <value> | off | on | wb | wt | wtall ]
cksum cksum <address> <size>
compare compare <address1> <address2> <size>
copy copy [-f] <src> <dst> <size>
cp0 cp0 [ (<name> | ([-<0..7>] <regnum&gt

) [<value>] ]
dis dis [-m] [-16] <address> [<count>]
disk disk [-f] (id [hda|hdb] )|
(read|readdma hda|hdb <sector> <count> <addr&gt

|
(write|writedma hda|hdb <sector> <count> <addr&gt

|
(readpart|writepart hda|hdb <part> <subpart> <count> <addr&gt

|
(writeimg hda|hdb <part> <subpart> <length> <addr&gt

|
(romfs [-z] <romfsaddr> <filename> [<loadaddr>]) |
(zbf <address> [<loadaddr>]) |
[-r] (-b tftp://<ipaddr>/<filename(bin)> <loadaddr&gt

|
(tftp://<ipaddr>/<filename(srec)&gt

|
(init | disp ) --mambo host
(dmawrite | dmaread) -- PC host

pflash pflash (probe [<bus_width>] [<gbus_addr>]) |
(write [-f] <flash offs addr> <ram addr> <length&gt

|
(erase <flash offs addr> <length&gt

|
(eraseall)
ping ping ipaddr [<datagramsize>]
port port [-a] [-8|-16|-32] <address> [<value>]

**Gennadyi** · 18-09-2010, 20:25

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

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

Spoiler

..............................compare

SYNOPSIS
compare <address1> <address2> <size>

DESCRIPTION
Compares the two specified memory areas. If a difference is
encountered during the compare, the address of the first mis-match
will be reported.

..............................copy

SYNOPSIS
copy [-f] <src> <dst> <size>

DESCRIPTION
The number of bytes specified by <size> are copied from <src> to <dst>.
Both the source and destination can be located anywhere in the
address space. The copy command knows the address areas for the
flash memories in the system and is able to program them.

If the destination is flash, the destination area must be cleared
using the 'erase' command prior to the copy operation.

Note that the copy command prevents the user from overwriting the
environment flash area.

Unless the -f option is applied, caches are flushed before and after
the copy operations (D-cache writeback and invalidate,
I-cache invalidate).

OPTIONS
-f Do not flush caches

..............................dis

SYNOPSIS
dis [-m] [-16] <address> [<count>]

DESCRIPTION
Disassemble code starting at <address>.

Disassembles MIPS64/MIPS32 instructions.
Includes MIPS-3D(TM) and MIPS16e(TM) ASEs.
Includes MIPS64/MIPS32 Release 2 instructions.

<count> (default 16) specifies the number of instructions to disassemble.

The continuation command '.' works together with 'dis'.

OPTIONS
-m Prompt user for keypress after each screen of data
-16 Disassemble MIPS16e code

..............................flush

SYNOPSIS
flush [-i|-d]

DESCRIPTION
Flush cache(s). By default, the D-cache is flushed first, followed
by an I-cache invalidate. This behaviour can be changed by the '-i'
and '-d' options.

The D-cache flush operation is in reality a write-back of dirty lines
(write-back caches only) followed by an invalidate operation.

OPTIONS
-i Invalidate I-cache
-d Flush D-cache

..............................fread

SYNOPSIS
fread tftp://<ipaddr>/<filename> <address>

DESCRIPTION

Load binary image to RAM or flash (depending on address) from TFTP server.

Note that the exact limitation on the filesize in the TFTP protocol
is 33553919 bytes (appr. 32 Mbytes). Any file larger than this size
cannot be transferred.

OPTIONS

..............................load

SYNOPSIS
load (uu [-z] <address&gt

|
(romfs [-z] <romfsaddr> <filename> [<loadaddr>]) |
(zbf <address> [<loadaddr>]) |
[-r] (-b tftp://<ipaddr>/<filename(bin)> <loadaddr&gt

|
(tftp://<ipaddr>/<filename(srec)&gt

(asc:[//(tty0|tty1)])

DESCRIPTION
load uu <address>: from serial port load uuencode data to ram.
-z is for zipped data.
load romfs <romfsaddr> <filename> [<loadaddr>]:load romfs image from
container to <loadaddr>, or address specified in
romfs.
-z is for no-romfs zipped image in container
load zbf <address> [<loadaddr>]:load zbf file in memory
to <loadaddr>, or address specified in zbf header.
load -b tftp://<ipaddr>/<filename> <loadaddr>: load binary file from ethern
et
port to loadaddr.
load tftp://<ipaddr>/<filename>: load S-record (S3) file from ethernet port
to memory.
load asc://(tty0|tty1): load S-record (S3) file from serial port to memory.

Load image from serial port or Ethernet to RAM or flash (depending
on address). The image type currently supported is SREC or binary.

On platforms supporting both Ethernet and serial port, the default
protocol is taken from the environment variable 'bootprot'. On
platforms without Ethernet, the only (and default) protocol is 'asc'.

If loading from serial port, the default port is taken from the
environment variable 'bootserport'.

If loading from Ethernet, the IP address of the TFTP server and
the filename may be specified. If an IP address is not specified,
it is taken from the environment variable 'bootserver'. If a
filename is not specified, it is taken from the environment
variable 'bootfile'.
Note that the exact limitation on the filesize in the TFTP protocol
is 33553919 bytes (appr. 32 Mbytes). Any file larger than this size
cannot be transferred.

For the currently supported formats, the execution entrypoint of the
image is embedded in the image. This address is saved such that the
'go' command can use it as the default entrypoint.

During the load operation, the current load address will be shown on
the 8-position hex display (if present).

Note that the load command prevents the user from overwriting the
environment flash area.

OPTIONS
-z load zip file
-b load binary file
-r Retry on ARP timeout (until load succeeds or Ctrl-c is typed)

..............................pflash

SYNOPSIS
pflash (probe [<bus_width>] [<gbus_addr>]) |
(write [-f] <flash offs addr> <ram addr> <length&gt

|
(erase <flash offs addr> <length&gt

|
(eraseall)

DESCRIPTION
pflash probe : probe PFLASH information
pflash write : erase PFLASH first, then write ram data into PFLASH
-f: force write. Even if it is invalid signature block
pflash erase : erase one or more sectors of PFLASH memory
pflash eraseall : erase all PFLASH memory

OPTIONS
-f force write to pflash addr 0

..............................port

SYNOPSIS
port [-a] [-8|-16|-32] <address> [<value>]

DESCRIPTION
Perform a read or write operation to the specified <address> with
the specified data width (default 32 bits). If <value> is specified,
this value is written, otherwise a read operation is performed and
the result is displayed.

The command checks the validity of the specified address.
This check can be turned off using the '-a' option.

The port command will result in exactly one read or write operation
with the specified data width. This makes it useful for accessing
registers in peripheral devices.

OPTIONS
-8 Access data byte
-16 Access data halfword
-32 Access data word
-a Allow invalid addresses

..............................scpu

SYNOPSIS
scpu ( [-i|-d|-m]+ [-a|-u|(-r|-p)+] ) |
( (-i|-d) <bpw> [<assoc>] [-p] ) |
( (-i|-d) <assoc> [<bpw>] [-p] ) |
( (tlb|fixed) [-p] )

DESCRIPTION
Configure or view current cpu configuration.

scpu does not by default modify the semi-permanent scpu
setting recorded in the environment variable 'cpuconfig'.
By default, cpuconfig is an empty string, implying processor
specific hardware reset configuration.
Use the '-p' option if you want to set the environment variable.
Use 'unsetenv cpuconfig' if you wish to reset cpuconfig to an
empty string.

The following operations are available :

Display available settings.
Display current configuration.
Edit configuration.
Setup configuration based on environment variable.
Reset configuration to hardware default.
Store current configuration in environment variable.

'scpu' without options or parameters displays the current
configuration.

OPTIONS
-a Display available configurations.
-u Configure based on environment variable.
-r Reset
configuration to hardware reset value.
-p Commit configuration to environment variable.
-i Display/configure instruction-cache settings.
-d Display/configure data-cache settings.
-m Display/configure MMU type.

______________ scpu -a
Available settings :
I-Cache bytes per way : 0x2000, 0x1000, 0x800, 0x400, 0x0
I-Cache associativity : 2, 1
D-Cache bytes per way : 0x2000, 0x1000, 0x800, 0x400, 0x0
D-Cache associativity : 2, 1
MMU types : tlb, fixed

..............................search

SYNOPSIS
search [-asc|-hex] <address> <size> <string>

DESCRIPTION
Search for string in the memory area specified by <address> and <size>.
Default string type is ASCII. If the search string contains spaces,
remember to use quotes around the string.

If searching for a hex string, the search pattern must be entered as
a number of two-digit hexcodes without spaces inbetween.

OPTIONS
-asc Search for ascii string
-hex Search for hex string

..............................setxenv

SYNOPSIS
setxenv [-b] [<key> [<value>]]

DESCRIPTION
Set the specified XENV key with given value, -b for binary mode.
If no key is specified, all XENV keys are displayed.

OPTIONS

YAMON> setxenv
(0x00) 8 a.board_id "852-E2"
(0x00) 4 a.cd2_freq 0x05b8d800
(0x00) 4 a.cd4_freq 0x01fca055
(0x00) 4 a.enable_devices 0x00023efe
(0x00) 10 a.eth_mac "00:16:e8"
(0x00) 4 a.gpio_irq_map 0x0d090800
(0x00) 4 a.hostclk_mux 0x00000100
(0x00) 4 a.irq_fall_edge_hi 0x00000000
(0x00) 4 a.irq_fall_edge_lo 0x0000c000
(0x00) 4 a.irq_rise_edge_hi 0x0000009f
(0x00) 4 a.irq_rise_edge_lo 0xff28ca00
(0x00) 4 a.pb_cs_config 0x000c10c0
(0x00) 4 a.pb_def_timing 0x10101010
(0x00) 4 a.pb_timing0 0x10101010
(0x00) 4 a.pb_timing1 0x00110101
(0x00) 4 a.pb_use_timing0 0x000003fc
(0x00) 4 a.pb_use_timing1 0x000003f3
(0x00) 4 a.pcidev1_irq_route 0x01010101
(0x00) 4 a.pcidev2_irq_route 0x01010101
(0x00) 4 a.pcidev3_irq_route 0x01010101
(0x00) 4 a.pcidev4_irq_route 0x02020202
(0x00) 4 a.scard_5v_pin 0x00000001
(0x00) 4 a.scard_cmd_pin 0x00000002
(0x00) 4 a.scard_off_pin 0x00000000
(0x00) 4 a.uart0_gpio_data 0x00000000
(0x00) 4 a.uart0_gpio_dir 0x00000000
(0x00) 4 a.uart0_gpio_mode 0x0000006e
(0x00) 4 a.uart1_gpio_data 0x00000000
(0x00) 4 a.uart1_gpio_dir 0x00000000
(0x00) 4 a.uart1_gpio_mode 0x0000006e
(0x00) 4 a.uart_console_port 0x00000000
(0x00) 4 a.uart_used_ports 0x00000001
(0x00) 4 l.cs0_size 0x00000000
(0x00) 4 l.cs1_size 0x00000000
(0x00) 4 l.cs2_part1_offset 0x00000000
(0x00) 4 l.cs2_part1_size 0x00020000
(0x00) 4 l.cs2_part2_offset 0x00020000
(0x00) 4 l.cs2_part2_size 0x00020000
(0x00) 4 l.cs2_part3_offset 0x00040000
(0x00) 4 l.cs3_part1_offset 0x00000000
(0x00) 4 l.cs3_part1_size 0x04000000
(0x00) 4 l.cs3_parts 0x00000001
(0x00) 4 l.cs3_size 0x04000000
(0x00) 4 x.boot 0x00020000
(0x00) 4 x.csf 0x00000002
(0x00) 4 x.dt 0x00000001
(0x00) 4 z.boot0 0x00040000
(0x00) 4 z.boot2 0x00040000
(0x00) 4 z.boot3 0x00080000
(0x00) 4 l.cs2_part7_size 0x00020000
(0x00) 4 l.cs2_part8_size 0x00020000
(0x00) 4 l.cs2_part9_size 0x00020000
(0x00) 4 l.cs2_parts 0x00000009
(0x00) 4 a.premux 0x00000203
(0x00) 4 a.avclk_mux 0x2a4aa741
(0x00) 4 a.cd8_div 0x1bae147a
(0x00) 4 a.cd9_div 0x2c000000
(0x00) 4 a.cd10_div 0x2c000000
(0x00) 4 z.default_boot 0x00000001
(0x00) 4 a.chip_rev 0x86350086
(0x00) 4 l.cs2_size 0x02000000
(0x00) 4 l.cs2_part3_size 0x000c0000
(0x00) 4 l.cs2_part4_offset 0x00100000
(0x00) 4 l.cs2_part7_offset 0x01fa0000
(0x00) 4 x.d0.cfg 0xf34111ba
(0x00) 4 z.boot1 0x00100000
(0x00) 4 l.cs2_part8_offset 0x01fc0000
(0x00) 4 l.cs2_part9_offset 0x01fe0000
(0x00) 4 a.gpio_data 0x80100000
(0x00) 4 l.cs2_part4_size 0x00500000
(0x00) 4 l.cs2_part5_offset 0x00600000
(0x00) 4 x.ds 0x00020080
(0x00) 4 x.d1.cfg 0xf34111ba
(0x00) 22 a.linux_cmd console=ttyS0 mem=102M
(0x00) 4 l.cs2_part5_size 0x01780000
(0x00) 4 l.cs2_part6_size 0x00220000
(0x00) 4 l.cs2_part6_offset 0x01d80000
(0x00) 6 a.gpio16_pulse 120u,-
(0x00) 4 a.gpio_dir 0x88114400
(0x00) 2 y.subnetmas ""
(0x00) 12 y.gateway "172.17.3.1"
(0x00) 15 y.ipaddr "192.168.1.100"
(0x00) 15 y.subnetmask "255.255.255.0"
(0x00) 13 y.gataway "192.168.1.1"
(0x00) 6 y.bootport "4836"
85 records, 1824 bytes

..............................stty

SYNOPSIS
stty [-tty<0|1>] [-b|-u|[-p][<baudrate>][n|o|e][7|8][1|2][hw|none]]

DESCRIPTION
Setup or view serial port setup. Default port is tty0.
-b,-u,-p apply to the default port if no port is specified.

The possible baudrates are generally 75-460800, but not all baudrates
are supported by all platforms. Use 'stty -ttyx -b' to get a list of
the supported baudrates for a specific port.

Available parity settings are n (none), o (odd), e (even).
Available databits are 7 and 8.
Available stopbits are 1 and 2.
Available flowctrl settings are hw and none.

When changing the parameters for a tty which is being used (e.g. the
console), some strange characters may appear as a result.

Also note that stty does not by default modify the semi-permanent tty
setting recorded in the environment variables. Use the '-p' option if
you want to set the environment variable for the specific tty as well.

OPTIONS
-u Force environment settings for port to take effect
-p Transfer current settings for port to environment
-b List supported baud rates for port
-tty0 Setup port 0 - default
-tty1 Setup port 1

..............................tlb

SYNOPSIS
tlb ( -i [-s] ) | ( <index> <pagesize> <va> <g> <asid>
<pa0> <c0> <d0> <v0>
<pa1> <c1> <d1> <v1> )

DESCRIPTION
Display or edit TLB.

Some CPUs (MIPS32/MIPS64 Release 2 or later only) may support
small pages (1kB).
The '-s' option is only available when running on such a CPU.
'-s' is used to toggle between enabling and disabling small pages.
It may only be used in conjunction with '-i' since toggling this state
requires the TLB to be reinitialised.

In case there are no parameters, the contents of the TLB is displayed.
If small pages are available, the state of this feature (enabled/disabled)
is also displayed.

In case (all) parameters are available, the TLB entry at the requested
index is written.

The number of TLB entries is CPU specific.

Available settings of 'pagesize' are :
0x400 | 1kB (if small pages are enabled)
0x1000 | 4kB
0x4000 | 16kB
0x10000 | 64kB
0x40000 | 256kB
0x100000 | 1MB
0x400000 | 4MB
0x1000000 | 16MB

Available settings of c0/c1 (cache algorithm for even/odd page) are
processor specific. However, the values 2 and 3 are typically reserved
for Uncached (2) and Cacheable (3) modes. Values 0..7 are available.

Other parameters are :
va : Virtual base address of even/odd pair of pages.
The va specified is the one used for the even page, so
it must be aligned to pagesize * 2.
g : GLOBAL setting ('n' -> ASID is used, 'y' -> Ignore ASID).
asid : ASID setting (only relevant if g = 'n&#039

.
pa0 : Physical base address of even page.
Must be aligned to pagesize.
d0 : DIRTY setting of even page ('y' -> write enabled,
'n' -> write protected).
v0 : VALID setting of even page ('y' -> valid,
'n' -> not valid).
pa1 : Physical base address of odd page.
Must be aligned to pagesize.
d1 : DIRTY setting of odd page ('y' -> write enabled,
'n' -> write protected).
v1 : VALID setting of odd page ('y' -> valid,
'n' -> not valid).

Example :

TLB index = 2
Pagesize = 4kB
Global mapping (i.e. ASID ignored)
ASID = 0xff (but ignored)
Cache algorithm = 3 (Cacheable)
Both pages valid

Virtual address Physical address Dirty (i.e. write enabled)
-------------------------------------------------------------
0x00000000 0x00200000 Yes
0x00001000 0x00300000 No

tlb 2 4kB 0 y ff 200000 3 y y 300000 3 n y

OPTIONS
-i Initialise TLB

..............................watch

SYNOPSIS
watch s/l/i address

DESCRIPTION
program a watchpoint on store / load / instruction fetch at given address.
Note that watchpoint actually triggers on address&(~7) or address&(~7)+4.

OPTIONS

..............................xrpc

SYNOPSIS
xrpc <xrpc.bin address>
-v | -s | -r

DESCRIPTION
xrpc <xrpc.bin address>: Run provided xrpc.bin

**nitrogen14** · 18-09-2010, 20:31

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

и о чем теперь думать, дай совет по существу!!!я вот смотрю на твою писанину и не могу понять, как это ему поможет...

**VVZ** · 18-09-2010, 21:02

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

@nitrogen14 http://www.multiupload.com/8O4KKE6UI7

**Gennadyi** · 18-09-2010, 21:25

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

[quote author=VVZ link=topic=5763.msg86146#msg86146 date=1284832934]
@nitrogen14 http://www.multiupload.com/8O4KKE6UI7
[/quote]
два ядра не шифрованных

**VVZ** · 18-09-2010, 22:03

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

@Gennadyi не те?

**VVZ** · 18-09-2010, 22:12

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

YAMON> load -b tftp://172.30.20.20/vmlinux.bin 0x90020000

Вложения

vmlinux.bin.txt (11.5 Кб, Просмотров: 419)

**VVZ** · 18-09-2010, 22:20

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

YAMON> go бла-бла висит

Вложения

vmlinux.bin-2.txt (13.2 Кб, Просмотров: 405)

**VVZ** · 18-09-2010, 23:03

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

YAMON> dump romfs 0x80000
YAMON> pflash probe
YAMON> xrpc 0xa4080090

Вложения

xrpc 0xa4080090.txt (13.5 Кб, Просмотров: 291)

**VVZ** · 18-09-2010, 23:54

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

Флешка не сдохла?
Осталось прошиться xrpc_xload_vmlinux_ES4_prod.bin

Объявление

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

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Комментарий

Festbottom on all