Thanx to The_Ripper:
Guys, there is 2 type of "install" for E2,
-first one is over standard UPDATE screen and it's only flashing new linux kernel 2.6.22 over old one 2.6.15 , so if this is where you stuck on flash, there is no need for jtag ,just serial interface and then over YAMON bootloader reflashing kernel.
-Second "install" over Azup it's just install to DOM. So if first "install" go okey you should not stuck on BOOTING.
1) Thanx to milix (using online translation service, of course):
Original Manual:
Code:
http://www.azboxhd.es/foro/index.php?showtopic=6735#
Well seeing that many users have called for a tuto on how to use the RS232 port of Azbox and then use the console Yamón I make a little tuto of how.
Our Azbox has 4 pin connector on the motherboard as seen in the picture below, this port can not connect directly to the PC because it emits low-level signals and the PC serial port not readable data would arrive so we have to use TTL to RS232 converter chip or Max233 Max232 this converter you can buy on e_bay for about 8 euros and not worth building it, is worth any converter that whenever tengais adapteis connections like this in the graph.
Depending on the converter that I buy some will need a cable in my case what I did was take a power connector and a 3.5 floppy with a pin or needle You will be able remove their pins and then solder the wires in and inserts described Ordes new way you can use the device as many times as you want about how commode and easily.
Here I put a screenshot of TTL to RS232 converter with Max232:
After this you can connect to the PC we will use a serial cable OJO simplente important but not a simple nullmodem cable or DB9 serial cable, the connection must be made with both teams while Azbox PC or off.
THE START:
The Azbox when we light the first thing is to start the zboot that passes control to Yamón which is software that is recorded in a part of the flash deficil delete access to prevent and is responsible for loading the kernel, has a series of basic commands that allow you to read, modify, flash and SDRAM in real time.
This has many advantages:
To change to change the kernel or load the kernel in the SDRAM Yamón exit and pass control to the kernel firmware and try to shut down the computer then becomes the original kernel stored in flash that is ideal for rapid testing without having to flash all day.
So that we understand the Jtag Yamón is like a very simple to use and with very simple stories with a serial cable and that anyone can do, that if, if we delete the portion of the flash where the Yamón if we have to use a Verderosa JTAG to recover azbox why probeis tell you, whatever you do it knowing where you do it.
Now you must use either the putty or hyperteminal to logically connect the cable converter having previously connected the azbox kindle the back button and you will get a log like this:
Code:
serial # eeb58f965774f62c6348aa0bdfca3a17 subid xosPe0 0x50
ok cs2 xenv
power supply: ok
dram0 ok (9)
dram1 ok (a)
zboot (0) ok
>
********************************* *****
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use as 8KB DRAM stack.
* Support xload format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0 / 1.
********************************* *****
Boot from flash (0x48000000) 0x8c000000 mapped to.
Found at 0x8c000000 XENV block.
CPU clock frequency: 300.37MHz.
System clock frequency: 200.25MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a8788).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x00098887).
Using UART port 0 as console.
Board ID.: "852" E2 "
Chip Revision: 0x8634: 0x86 .. Matched.
Setting up H / W from block at 0x8c000000 XENV.
Avclk_mux> <SYSCLK Setting to 0x00000000.
Hostclk_mux> <SYSCLK Setting to 0x00000100.
Setting <IRQ lo> rise to edge trigger 0xff28ca00.
Setting <IRQ lo> to fall 0x0000c000 edge trigger.
Setting trigger edge hi> <IRQ rise to 0x0000009F.
Setting <IRQ hi> trigger edge to fall 0x00000000.
Setting GPIO <IRQ map> to 0x20090820.
Setting default <PB timing> to 0x10101010.
Timing0> <PB Setting to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Timing1> <PB Setting to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
Cs PB config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM / IDE PCIHost USB Ethernet I2CS PCIDev2 PCIDev3 I2CM scard
MAC: 00:02:14:13: ef: f9
PCI IRQ routing:
IDSEL 2: INTA (# 14) INTB (# 14) INTC (# 14) INTD (# 14)
IDSEL 3: INTA (# 15) INTB (# 15) INTC (# 15) INTD (# 15)
Smartcard pin assignments:
OFF pin = 0
5V pin = 1
CMD pin = 2
Setting up Clean Divider 2 to 96000000Hz.
Setting up Clean Divider 4 to 33333333Hz.
Setting up Clean Divider 5 to 25000000Hz.
Setting up Clean Divider 6 to 20000000Hz.
Setting up Clean Divider 7 to 20000000Hz.
GPIO dir / data = 0x76000038/0x76000000
UART0 GPIO mode / dir / data = 0x6e/0x00/0x00
UART1 GPIO mode / dir / data = 0x6e/0x00/0x00
XENV completed processing block.
Existing memcfg Found: DRAM0 (0x08000000), DRAM1 (0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Index boot Default: 0
Scanning image romfs at 0x8c040000 (0x48040000) .. Found.
Romfs found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file (s) to be processed in romfs.
Xrpc_xload_yamon_ES4_prod.bin Processing (start: 0x8c040090, size: 0x0002fe84)
Zboot Checking signature file .. Not found.
Trying xrpc_xload format .. OK
Zboot Checking file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load 173/255 msec total time.
Execute final at 0x91200000 ..
********************************* *
* Yamón ROM Monitor
* Revision 2.6-SIGMADESIGNS-01-2.8.0.1
********************************* *
Memory: code: 0x11000000-0x11040000, 0x11200000, 0x11204000
reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000
Environment variable 'start' EXISTS. After 1 seconds
it will be Interpreted as a Yamón command and execute.
Press Ctrl-C (or do BREAK) to bypass this.
And when it comes to this point is to press Control + C to access the console then Yamón below to upload / send things we need to establish or authorize our Ethernet port with the following command:
ethernet disconnected
Code:
Yamón> setenv bootserver 192.168.1.2
PC's IP address or server
Code:
Yamón> setenv gateway 192.168.1.1
address network gateway
Code:
Yamón> set ipaddr 192.168.1.80
's IP address azbox
Code:
Yamón> set netmask 255.255.255.0
netmask
started the network and the start.
We now have network connection to the PC I will now detail some commands:
1) KERNEL TESTING PROCESS IN THE RAM
In Linux we will have to activate the TFTP server and then the folder you've created for this purpose we put the file miarchivo.ram.srec this format is to load into RAM is obtained with this compiler and the kernel still must be studied how to get it.
How to install and boot ubuntu TFTP:
http://infrabeta.com/tutoriales/item.php?itemid=18
Code:
Yamón> load tftp: / / 192.168.1.2/vmlinux.flash.srec
With the load command can load the kernel in this case the eye is not in SDRAM flash.
Code:
Yamón> go. / Root = dev/mtdblock/0
go execute the command kernel that is already in RAM from the first bone block 0.
2) RECORD IN THE PROCESS CAN NOT FLASH WHEN THE START.
The file format to copy it in the TFTP sever will miarchivo.flash.srec this format is to burn the flash. I have to look more closely at the offset and size ± or messing them for no fat, hehe seguire widely across the tuto with more progress.
And here is a list of all available commands Yamón system and its functioning:
http://pvtridvs.net/pool/docs/mips/M...-USM-02.01.pdf
The FLASH
The Azbox has an 8-MB Flash NOR type your mapping is as follows:
Code:
Creating 5 MTD partitions on "CS2: Physically mapped flash":
0x00000000-0x00020000: "CS2-Part1" Size = 131 072 20 000 bytes hex
0x00020000-0x00040000: "CS2-Part2" Size = 131 072 20 000 bytes hex
0x00040000-0x00080000: "CS2-Par**" Size = 262 144 40 000 bytes hex
0x00080000-0x00700000: "CS2-Part4" Size 620 000 = 6,422,528 bytes hex
0x00700000-0x00800000: "CS2-Part5" Size 100,000 = 1,048,576 bytes hex
With the following telnet command mounted vestments can see how our system including different mtd flash and then that race will detail each part:
Code:
MMP [~] $ cat / proc / mtd
dev: size erasesize name
mtd0: 00.8 million 00.01 million "CS2: Physically mapped flash"
mtd1: 00.02 million 00.01 million "CS2-Part1"
mtd2: 00.02 million 00.01 million "CS2" Part2 "
mtd3: 00.04 million 00.01 million "CS2-Par**"
mtd4: 00.68 million 00.01 million "CS2-Part4"
mtd5: 00.1 million 00.01 million "CS2-Part5"
MTD0: Contains the 8mb of flash
MTD1 Part1: I am not sure but I think is the boot Boot
MTD2 Part2: Contains Zboot
MTD3 Par**: Contains the Yamón (xrpc_xload_yamon_ES4_prod.bin)
MTD4 Part4: Contains the Kernel (xrpc_xload_vmlinux_ES4_prod.bin)
MTD5 Part5: Contains the folder DISK1 azbox responsible for starting.
With this info and tweak and test You will be able I hope you help, now I'm very short of time so far I have stopped everything but what I hope will soon resume the investigations, however for tinkering You will be able to load the data in SDRAM so dañareis not flash and never turn it off and keep you that you had before.
Salu2
2) Thanx to Kanber_Kav:
Two types of problems with installation and how to solve them...
Reply With Quote
Originally Posted by Dig Deep
Bookmarks