Still cant pass HDMI initialization on dfb compilation.
Currently I dont work on that problem, someone else is working on it.
Still cant pass HDMI initialization on dfb compilation.
Currently I dont work on that problem, someone else is working on it.
you probably already know that when you start SDecoderserver with "-h" arguments that you can see hdmi init? they use the old dvi_hdmi method from mruaOriginally Posted by The_Ripper
your friend is here, and he wants to explain
I attach picture, all is clear i think ?
If you didn't have rs232 on your PC - You can use usb2serial adapter or if you need - i can attach usb variant of UART/serial interface
rgs,
telesat
Last edited by @telesat; 05-04-2010 at 12:47 AM.
for the noobs......like me!@voki081
You will need osdbuf_control application from MRUA package to create OSD memory buffer and then to pass some memory allocation datas that osdbuf_control app will give you after creation, to em8xxxfb.ko driver because he is attaching to that OSD memory buffer, it's simple sceleton driver, after that he use all software functions for drawing :S.
@all
Good news regarding new linux kernel 2.6.22.19-19 + libc , I menage to compile it and bring it up, some small output logs
It needs a lot of changing in startup scripts because I just copy all Azbox startup scripts so not all of this script works ...Code:YAMON> net init Ethernet driver for EM86XX (v1.0) (MAC 00:02:xx:xx:xx:ec, tx_desc/rx_desc = 16/32) em86xx_eth::open(em86xx_eth) - Full-duplex mode em86xx_eth::open(em86xx_eth) - 100 Mbit/s em86xx_eth ethernet start ipaddr: 192.168.1.5 subnetmask: 255.255.255.0 gateway: 192.168.1.1 YAMON> net initpci net have been initialized ipaddr: 192.168.1.5 subnetmask: 255.255.255.0 gateway: 192.168.1.1 YAMON> net up em86xx_eth ethernet start YAMON> load -b tftp://192.168.1.3/vmlinux.bin 0***020000 About to load tftp://192.168.1.3/vmlinux.bin Press Ctrl-C to break ................................................................ ................................................................ ................................................................ ........................................................... Start = 0***020000, range = (0***020000,0***7fec02), format = BINARY Length = 0x7dec03 (8252419) Checksum = 0xca181ecb YAMON> go 0***020000 Linux version 2.6.22.19-19-the_ripper (root@debian) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #64 Sun Apr 4 20:33:29 CEST 2010 Configured for SMP863x (revision ES6+/RevA+), detected SMP8634 (revision ES9/RevC). Detected CPU/System/DSP Frequencies: 300.37/200.25/300.37MHz SMP86xx 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: 040e0000 @ 10020000 (usable) Wasting 2098176 bytes for tracking 65568 unused pages Initrd not found or empty - disabling initrd On node 0 totalpages: 82176 DMA zone: 642 pages used for memmap DMA zone: 0 pages reserved DMA zone: 81534 pages, LIFO batch:15 Normal zone: 0 pages used for memmap Built 1 zonelists. Total pages: 81534 Kernel command line: mem=65m console=ttyS0,115200 Primary instruction cache 16kB, 2-way, physically tagged, linesize 16 bytes. Primary data cache 16kB, 2-way, virtually tagged, cache aliases, 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, 8192 bytes) Using 150.188 MHz high precision timer. Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 55168k/66432k available (2564k kernel code, 11228k reserved, 427k data, 5064k init, 0k highmem) Calibrating delay loop... 296.96 BogoMIPS (lpj=148480) Mount-cache hash table entries: 512 NET: Registered protocol family 16 tangox: creating TLB mapping for 0x20000000 at 0xc0000000, size 0x08000000. PCI: Initializing SMP86xx 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 SMP86xx as PCI slave with 128MB PCI memory PCI: Region size is 16384KB PCI: Map DMA memory 0x10020000-0x14100000 for PCI at 0x11000000 SCSI subsystem initialized usbcore: registered new interface driver usbfs usbcore: registered new interface driver hub usbcore: registered new device driver usb Time: TANGOX clocksource has been installed. NET: Registered protocol family 2 IP route cache hash table entries: 4096 (order: 2, 16384 bytes) TCP established hash table entries: 16384 (order: 5, 131072 bytes) TCP bind hash table entries: 16384 (order: 4, 65536 bytes) TCP: Hash tables configured (established 16384 bind 16384) TCP reno registered Created /proc/cpucache_info entry. Tango2 frequency scaling module installed. JFFS2 version 2.2. © 2001-2006 Red Hat, Inc. io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) 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: module loaded 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:xx:xx:xx:xx Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ide0: SMP86xx Bus Mastering IDE controller Probing IDE interface ide0... hda: DMS55610V010, ATA DISK drive hda: no 80 conductors cable, falling back to lower udma mode hda: selected mode 0x42 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: hda1 hda2 hda3 hda4 physmap flash device CS2: 0x800000 at 0x48000000 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-Par**" 0x00080000-0x00700000 : "CS2-Part4" 0x00700000-0x00800000 : "CS2-Part5" pktgen v2.68: Packet Generator for packet performance testing. TCP cubic registered NET: Registered protocol family 1 NET: Registered protocol family 17 Freeing unused kernel memory: 5064k freed Algorithmics/MIPS FPU Emulator v1.5 mount: cannot read /proc/mounts: No such file or directory hostname: /etc/hostname: No such file or directory /etc/init.d/S01sysinit: line 9: /sbin/ldconfig: No such file or directory Initializing random number generator... done. Starting network... udh*** (v1.5.0) started eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Sending discover... Sending select for 192.168.1.5... Lease of 192.168.1.5 obtained, lease time 86400 deleting routers route: SIOC[ADD|DEL]RT: No such process adding dns 192.168.1.1 Starting MMP custom setting... (none) login: root login[659]: root login on 'ttyS0' BusyBox v1.5.0 (2010-04-04 18:30:26 CEST) multi-call binary
Ahhh yes, finally CCcam can be run with no patching, no fakeroot
PS. This is just small step people,left to compile MRUA kernel drivers/apps and to see if it will work on new kernel and on libc not anymore on uclibc.
this means original firmwares by opensat could include this new kernel update? and we would be able to run cccam native without emulation or any other libs?
what other improvements this would bring?
thank you very much.
@hfmls
original fw from opensat contains 2.6.15 kernel, device drivers e.t.c.
also it boots from flash. the above is compiled kernel with library needed for enigma and other apps that was booted via network.
so probably you can flash it to azbox and use cccam like on other linux box. without tv so far :\ next step is to recompile all specific
to azbox drivers, some gui for channel zappingand make it bootable from the flash.
i see, talking about enigma 2 then
cool
best thing to fix is cccam and zapping
so go go go riper
@hfmls
Tx0 explain it.
Some TO DO list.
1. new kernel+new ramfs with LIBC inside, not UCLIBC
2. MRUA kernel drivers needs to be compiled for new kernel version (It will work?)
4. MRUA apps needs to be compiled against LIBC not the UCLIBC (It will work?)
5. VFD driver, Azbox receivers use external chip, not one inside sigma(Who will code this ?)
6. Remote IR driver,again Azbox receivers use externel chip,not one inside sigma(Who will code this ?)
7. FB driver, em8xxxfb driver forget it, this DFB someone needs to figure it out how to init HDMI, @sattomy We tried that(to see what it send/how it init), but it cant work. You can try for your self if you know anything about compilation on linux, dfb support for Sigma is in DCCHD package.
8. DVB API, tuners driver, ...
Again,Who will code all this stuff?
@telesat
Thx my friend
Last edited by The_Ripper; 05-04-2010 at 09:32 AM.
Faith is taking the first step, even when you don't see the whole staircase
- Martin Luther King jr.
4 nob like me we wil have somthing new 4 azbox ore not ?@hfmls
Tx0 explain it.
Some TO DO list.
1. new kernel+new ramfs with LIBC inside, not UCLIBC
2. MRUA kernel drivers needs to be compiled for new kernel version (It will work?)
4. MRUA apps needs to be compiled against LIBC not the UCLIBC (It will work?)
5. VFD driver, Azbox receivers use external chip, not one inside sigma(Who will code this ?)
6. Remote IR driver,again Azbox receivers use externel chip,not one inside sigma(Who will code this ?)
7. FB driver, em8xxxfb driver forget it, this DFB someone needs to figure it out how to init HDMI, @sattomy We tried that(to see what it send/how it init), but it cant work. You can try for your self if you know anything about compilation on linux, dfb support for Sigma is in DCCHD package.
8. DVB API, tuners driver, ...
Again,Who will code all this stuff?
@telesat
Thx my friend
i mean 4 cccam and zapping ?
I already tried compiling. Got him to find the chip, but hang on CEC. didn't have much time since then. Will look into it again today. Problem is I can compile, change some code. But not really write code. So i can't help besides trying to get HDMI working can't help that much.@hfmls
Tx0 explain it.
Some TO DO list.
1. new kernel+new ramfs with LIBC inside, not UCLIBC
2. MRUA kernel drivers needs to be compiled for new kernel version (It will work?)
4. MRUA apps needs to be compiled against LIBC not the UCLIBC (It will work?)
5. VFD driver, Azbox receivers use external chip, not one inside sigma(Who will code this ?)
6. Remote IR driver,again Azbox receivers use externel chip,not one inside sigma(Who will code this ?)
7. FB driver, em8xxxfb driver forget it, this DFB someone needs to figure it out how to init HDMI, @sattomy We tried that(to see what it send/how it init), but it cant work. You can try for your self if you know anything about compilation on linux, dfb support for Sigma is in DCCHD package.
8. DVB API, tuners driver, ...
Again,Who will code all this stuff?
@telesat
Thx my friend
I do have serial to azbox if you need any additional tests.
As far as IR controll go, opensat seemed to include a new executable in one of the lasts firmware called EStar, when it is started it takes of IR-controll.
@sattommy
Problem is that we cant change main sigma dfb source code, because code is allready compiled and they are object files now. It's just left to play with arguments/options that we passed to HDMI and try to bring it up.
Ripper is working hard doing alot of stuff that takes time.
But there is still alot that needs to be done and it's simply not possible for him to do it all by himself. Saying that alot of progess has been made and Ripper is offering this box new hope.
I'm not sure if there are any other teams working on Enigma2 for the box?
I think that The Ripper (and some great friends of his like Telesat) is the first & the last of the mohicans for this box.
If there were other teams, wouldn't they contact him to share their work & knowledge and distribute it in order to avoid double work and achieve faster and better results???
I hope I'm wrong but for the moment I thank him for trying and I hope he won't give up until he does something great for this box.
Hi,
what is the exact tuner types shipped with azbox (dvb-s, dvb-t)?
what is the type of ir and vfd controller ?
I can check for you tommorow if you want. For the IR controll I found a driver which reroutes the IRcontroll to a tcp stack. Which can then be used again as input device.
I think the VFD is last priority, as this is not 100% neccessary for enigma to run. Really should need dvbapi, but don't know if there is any progress on that.
I have been busy with HDMI today, but did not succeed yet. Seems that SDecoder server somehow sets gpio's to meet the board. Anyone any ideas?
Does anybody know if there are any ucode (mircocodes) files for azbox?
Maybe help:
OSD buffer size : 720x480
OSD format : tc:16bpp_565
videomemory=0x17957000 videomemorysize=691200 palette=0x79000 mode=720:480:16
Using /tmp/modules/em8xxxfb.ko
Segmentation fault
MMP[~]$ [HDMI] ========================== creating pDH ==========================
[HDMI] Resetting transmitter chip with GPIO pin 25.
[HDMI] Detected part at I2C device address 0x72: vendor 0x0001, device 9253, rev.0x03 (Silicon Image)
[HDMI] Using the part: SiI9030 (4), Vendor ID is 0x0001 / 0x9253
[HDMI] Resetting transmitter chip with GPIO pin 25.
[HDMI] *** HotPlug changed, is now ON
[HDMI] *** Clock changed, is now STABLE
[HDMI] DHUpdateVideoPixelClock(27000000)
[HDMI] DHSetHDMIMode(TRUE)
[HDMI] Sending blank AudioInfoFrames
[HDMI] Sending null packet
outports_options.c: Application did not specify HDCP SRM, providing empty SRM!
[HDMI] DHCancelHDCP()
I'm not sure lads probably you have to look for 863xsamples.zip file which contain some source for sigma hdmi and other video operations. its quite outdated but might clear some things. I can UL it as well as EIA standard if you dont have it already.
Last edited by tx0; 06-04-2010 at 12:53 AM.
The_Ripper, one question I have, is it possible the firmware Hybrid and you do not have space problems in the DOM?
Yes, this is a good question!
Is it possible to have a Hybrid firmware with the actual size of memory space?
@Raskino & Hfmls
Have You news about E2 release (I means not The_Ripper work status)
Posting Permissions
Reply With Quote
Bookmarks