PDA

View Full Version : Rsi e2 v 0.2



Carp95
21-11-2011, 07:26 PM
Second version of RSI E2 for Azbox HD. This E2 RSI image is 100% based on the RTi 1.4.

Skin: PingFlood
Bootlogo: Daconi
Maincode: RTi team (www.azbox-enigma.eu)
Little code changes: RSi team (www.rsi-images.org)

http://www.rsi-images.org/site/downloads.php?cat_id=5&download_id=19

freshmaker
21-11-2011, 09:37 PM
so just skin chang nothing els ???

voki081
21-11-2011, 10:35 PM
so just skin chang nothing els ???

perhaps it may be my ilusions, but I think the RSI made some more work than skin change.

zeini
21-11-2011, 11:00 PM
This image refers to RTI 1.4

So, what is new:

- Many changes in smp8634dvb.ko main driver which will result in better overall stabillity, especially on audio part, faster zapping.

- Fixed audio selection in DVB part.

- New Media Center files inside, with new keymap and better support for PCM and RAW over HDMI, added support for some specific divx formats.

- Better support for Teletext and added caching support

Ceaser
22-11-2011, 12:29 AM
What about the Wi-fi , is that working now ?

Carp95
22-11-2011, 06:53 AM
Yes

freshmaker
22-11-2011, 06:38 PM
ey voki if u can see i talk about RSI Image not RTI :cuss:

voki081
22-11-2011, 11:20 PM
ey voki if u can see i talk about RSI Image not RTI :cuss:
Where I wrote RTI?
Please read again my post!
I also spoke about RSI.
:dupe:

Carp95
23-11-2011, 04:06 PM
perhaps it may be my ilusions, but I think the RSI made some more work than skin change.

Thats correct there are some code changes in RSI that aren't in RTI, drivers off course are RTI job (as in all E2 images for Azbox drivers come from RTI and are read-only and no sources )

freshmaker
24-11-2011, 10:11 PM
i need help i was updating my azbox and my pc was restart soo now i have on azbox just bootingggg nothing els sooo can you help me how to fixxxxxxx

voki081
24-11-2011, 10:46 PM
try with this>
https://www.satpimps.co.uk/showthread.php?141544-Tutorial-How-to-recover-dead-AZBox&highlight=recovery
regards

Ceaser
25-11-2011, 01:31 PM
Does the timeshift work with this image on hd channels ?

zeini
25-11-2011, 03:06 PM
No timeshift don't work on HD channels. Box allways freeze if you go to timeshift on HD channels.

Dig Deep
25-11-2011, 06:27 PM
i need help i was updating my azbox and my pc was restart soo now i have on azbox just bootingggg nothing els sooo can you help me how to fixxxxxxx

This is a BIG problem with the AZ images for E2

Hope they will find a good helping fix for this !!

freshmaker
25-11-2011, 09:39 PM
hmm i look and i make on cabel for rs232 with dku-5 and i make o connect with putty all is okay but i can't write in putty with comand sooo just look


õxosPe0 serial#631e84636a466ac8a752865635 80caf3 subid 0x50
xenv cs2 ok
xosPe0 serial#631e84636a466ac8a752865635 80caf3 subid 0x50
xenv cs2 ok
power supply: ok
dram0 ok (8)
dram1 ok (9)
zboot (0) ok
>
********************************* *****
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use 8KB DRAM as stack.
* Support XLoad format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0/1.
********************************* *****
Boot from flash (0x48000000) mapped to 0x8c000000.
Found XENV block at 0x8c000000.
CPU clock frequency: 300.37MHz.
System clock frequency: 200.25MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a8787).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a6676).
Using UART port 0 as console.
Board ID.: "852-E2"
Chip Revision: 0x8634:0x86 .. Matched.
Setting up H/W from XENV block at 0x8c000000.
Setting <SYSCLK avclk_mux> to 0x00000000.
Setting <SYSCLK hostclk_mux> to 0x00000100.
Setting <IRQ rise edge trigger lo> to 0xff28ca00.
Setting <IRQ fall edge trigger lo> to 0x0000c000.
Setting <IRQ rise edge trigger hi> to 0x0000009f.
Setting <IRQ fall edge trigger hi> to 0x00000000.
Setting <IRQ GPIO map> to 0x20090820.
Setting <PB default timing> to 0x10101010.
Setting <PB timing0> to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Setting <PB timing1> to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
PB cs config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
MAC: 00:02:14:15:51:6f
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 block processing completed.
Found existing memcfg: DRAM0(0x08000000), DRAM1(0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Default boot index: 0
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
Checking zboot file signature .. Not found.
Trying xrpc_xload format .. OK
Checking zboot file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load time total 173/255 msec.
Execute final at 0x91200000 ..



********************************* *
* YAMON ROM Monitor
* Revision 02.06-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 YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

xrpc failed (9)--- if a xtask is using a cipher or if you reboot
--- xrpc will fail with RM_BUSY
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff
YAMON>

voki081
25-11-2011, 10:42 PM
Pressing Ctrl and C didn't help you?

freshmaker
25-11-2011, 10:49 PM
yes m8 but after ctrl+c i can't write on putty :( just stay block :( i can't write comands for ip :(

voki081
25-11-2011, 11:32 PM
Did you try to press Ctrl+C earlier?

I think that you should press before :
********************************* *
* YAMON ROM Monitor
* Revision 02.06-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 YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

But later after below message will don't work.
xrpc failed (9)--- if a xtask is using a cipher or if you reboot
--- xrpc will fail with RM_BUSY
Checking zboot signature.. it's not zboot file.
Error : Internal, code = ffffffff
YAMON>

freshmaker
25-11-2011, 11:59 PM
hmm voki i don't know m8 i tryyyy milon time after 1 secon and beffor but no succest with CTRL C so :(:frown::o10:

voki081
26-11-2011, 10:35 PM
It seems that everything OK is with interface. I can not remember what else will help you.
Maybe someone from the team with more experience, can provide some solution.
P.S.
Did you try to press Break instead of Ctrl+C?

freshmaker
29-11-2011, 08:22 PM
how can i pres break ? can u help mee

just to type break ore i have too hit some of keyboord ?

voki081
29-11-2011, 08:56 PM
You should have button (pause or Break) on keyboard. Try to press that instead of ctrl+c.

pr2
29-11-2011, 09:15 PM
Cable is wrong, it is working to receive data from the box but not to send what you type on the keyboard.
Carefully check your cable and COM port settings.

Smudger
01-12-2011, 11:46 PM
What an excellent image.

scopus
02-12-2011, 12:02 AM
What an excellent image.

Agreed...except sometimes I have no sound when coming out of standby, only a reboot cures it.

ManikM
02-12-2011, 12:24 AM
u can try changing HDMI mode from one to another, this can bring back sound.

scopus
02-12-2011, 09:44 AM
u can try changing HDMI mode from one to another, this can bring back sound.

Thanks...I have two receivers with this image, and have changed the skin in one receiver to HD Glass16 and so far this seems to have cured the problem, whereas the other receiver with the Az Pro skin still causes this problem.