MRUA sources

[The666MAC]

In addition to the files i posted yesterday, the mrua sources used in current firmware (4625)

mrua_SMP8634_2.8.5.1_facsprod_leg acy_dev.mips.dts.work
_http://www.sendspace.com/file/b8x66t

posted yesterday
mrua_SMP8634_2.8.7.0_dev.mips.zip
_http://www.sendspace.com/file/t1j8ml

dcchd_SMP8634_2.8.5.0_black_GCC4. mips.zip
_http://www.sendspace.com/file/ne9gex


Again, files anonomously "donated" to the community, thx alot :cup-006:

Developers have fun :biggrinjester:


// The666MAC

[tx0]

mrua_SMP8634_2.8.5.1_facsprod_leg acy_dev.mips.dts.work

is not gz but .bz2 file.

[The666MAC]

you're right tx0 :iagree:

file extension should be .bz2 and not .zip

Uploading new file done , first post fixed

//The666MAC

[alcomys]

thanks for the files.
:bravo-009:

[alcomys]

http://www.comsatweb.nl/az%20source.bmp

i have a idea.
i have so many source files for the smp86xx and also for azbox or popcornhour maybe it is better i put the files anywhere on a ftp server so that developers can chose the files they need.
maybe there are some interesting files we all can use.
let me know if you agree.

above i have a screenshot of the files.

:respect-040:

[sattommy]

Alcomys it would be nice to see if executables build for the popcornhour (like movie player) can be used on the azbox. Popcornhour is maybe a little different but the duneHD center uses exactly the same chipset.

However i did not succeed in extracting it's firmware

[fundidun]

I remind you that the Firmware OPENSAT uses nano-x and not directfb.

Not give information as TS packets, little can be done is to give shots in the dark

[sattommy]

fundidun I knolw. But there are DirectFB sources available, when these are compiled there might be a change to use exectuables from other players.

[fundidun]

All information is available for multimedia devices without tuner, as much DTT, I think it is very difficult without the information of the source.

Our firmware will not be worth for nothing, ie you can use one or the other but both is not possible, because they have different graphical interface.

I hope you geeko of information over a mower, and guide us the way forward

all would move faster

[dutchmatrix]

If im correct the_ripper already had some succes with DirectFb but didn't have enough information about the TS packages.

Maybe its an idea to make something like (semi) dualboot
1 for dvb (nano-x)
1 for mediacenter (DirectFb)

Alcomys great idea to make this all available, a place where you can add and get all information about developing for the Azbox

[fundidun]

mower said


I started on enigma maybe 10 days ago and on DVB API huhh long time ago(still waiting for OPENSAT and b*g as* geeko to grant me access to TS packets), so hfmls didnt talk about me when he started this thread (just to be clear)

Without this information we do not have a route to follow.

If anyone thinks he can get it, indicating it to be working, but we do not know which way to go without mower report

[FME_fta]

alcomys, you could pack all of those files into a zip or rar and upload it to a upload center as megaupload (1GB limit) or netload (400MB limit).

Regards!

[alcomys]

@FME
i can do that.
i,m at work now but when i,m home i collect all the files i have found the last year
and share them with us.

:respect-040:

[alcomys]

files are ready for sharing now.
temporary on my website but i will host the files this weekend to some other place then my website.
but i will let you know if i do that.

_http://www.comsatweb.nl/upload

regards :bowing-036:

[fundidun]

And this is the Register , if one wants to leave an anonymous Information Resources for work

_http://www.comsatweb.nl/upload/register.php?

:respect-051:

[alcomys]

And this is the Register , if one wants to leave an anonymous Information Resources for work

_http://www.comsatweb.nl/upload/register.php?

:respect-051:

anonymous are also allowed to upload files.
i have changed the settings.

[fundidun]

Perfect, we expect you to feel safe and can give us something more to keep working

[tx0]

I would also add some files from here:


ftp://armutils:sigmadesigns((@))gw.sigm adesigns.com/smp86xx


it would be nice if somebody will post some how-to for newbies about building sigma work environment (I mean gcc, gdb, make and other stuff)

[rfdomingos]

I would also add some files from here:


ftp://armutils:sigmadesigns((@))gw.sigm adesigns.com/smp86xx


it would be nice if somebody will post some how-to for newbies about building sigma work environment (I mean gcc, gdb, make and other stuff)

There is a great tutorial by a user named leandrpf in the official forum, including a zip with the full building environment. Here it is

hxxp://www.azbox.com/forum/viewtopic.php?f=38&t=917


Hi all.

I joined this material (in a hurry), and uploaded it in 4shared. It is available for those who want to venture in developing new plugins for AZBox HD. :)

You can download the file (85MB) here: _www.4shared.com/file/167937473/ec6fff5a/DevAzbox_by_leandrpf.html

This is a ZIP file with:
- A mini-tutorial (TXT file made by me in portuguese. I want to take some time to improve it)
- The Toolchain for AZBox HD (to build cross compiler for mipsel)
- AZBox plugins-SDK
- The Microwin (to build Microwin AKA Nano-X and some C program samples to run on it in a linux PC for example or compile to mipsel depending what is the choice in config file)
- 2 configuration files edited by me (for makefiles to build the MicroWin environment)
1- to build/compile programns for native linux in PC (it can work like an [####] for running new programs in nano-X localy for example)
2- or to build/compile to run in AZBox HD (mipsel arch)
As a practice, I have two separated folders with Microwin to avoid confusion and to do tests before install new programs in my Elite :)
- and some plugin files ready to install in AZBox HD (theese programs are samples from the Microwin - ntetris, nxterm and landmine).

All of these files I used to mount my development environment in a virtual machine using Ubuntu 9.
As I said, Microwin is nice to compile a program to run it on the nano-X in a native linux PC (or on a VM in my case) before going AZBox HD.

Note: I didn't have much time to adjust some problems in the sample programs, they don't work 100% in AZs.
For example: nxterm when runing in AZ does not differentiate UPPER and LOWER case when using a keyboard connected to the receiver (shift+key or caps lock on does not work).

More information can certainly be found on Google (I have some references in the TXT mini tuto) or you can contact me here in this topic to exchange ideas/experiences.

I hope more people are interested in and we can exchange some ideas here. If you find any problems/doubts, please post them here also to be adjusted/dicussed.

Best regards and thanks.
Leandro

- portuguese version
Buenas pessoal.

Juntei esse material meio as pressas porque estou sem muito tempo, e disponibilizo para quem quiser se arriscar a criar plugins para AZBox HD.

Podem baixar o arquivo (85MB) aqui: _www.4shared.com/file/167937473/ec6fff5a/DevAzbox_by_leandrpf.html

Trata-se de um arquivo ZIP onde estão:
- um minitutorial em TXT feito por mim (as pressas também - pretendo arrumar um tempo para melhorar o tuto)
- arquivo contendo o Toolchain para AZBox HD (to build cross compiler para mipsel)
- arquivo para build do Microwin (também conhecido como nano-X)
- AZBox plugins-SDK
- 2 arquivos de configuração (para makefiles - build do Microwin) editados por mim para compilação - um para [####] local de nano-X e outro para compilar para AZBox HD (eu tenho dois ambientes Microwin em pastas separadas para não dar confusão nas compilações e para poder fazer testes)
- alguns programas (que vêm de exemplo no ambiente para Microwin) compilados por mim - ntetris, nxterm, landmine em formato pronto para instalação de plugin (para serem instalados no AZBox HD).

Esses arquivos eu usei para montar o meu ambiente de desenvolvimento numa máquina virtual (VM w4re) com Ubuntu 9. O ambiente Microwin é legal que você pode compilar um programa em C para executar no próprio [####] de nano-X na sua máquina antes de colocar no AZBox HD.

Obs. Não tive tempo suficiente de ajustar os programas exemplos para funcionarem 100% nos AZs. Assim, adianto que há problema que não consegui fazer os programas compilados (o nxterm por exemplo) diferenciar letras maiúsculas usando um teclado direto no receptor (shift+tecla ou caps lock ligado).

Mais informações com certeza podem ser encontradas no Google (coloquei algumas referências dentro do TXT) ou podem me contatar aqui nesse tópico ou por MP.

Espero que mais pessoas tenham interesse e possamos trocar algumas idéias nesse espaço. Se encontrarem algum problema, também favor postarem aqui para que seja ajustado.

Abraço e obrigado.
Leandro

[tx0]

Just tried to build 2.8.7.0 MRUA, make apps were ok, but failed with MRUA drivers (make kernel). any ideas?






Standalone development kit for SMP86xx

The following targets are available:
a) kernel: to build the MRUA drivers per se.
b) apps : to build the sample applications. They will be available in
the 'bin' directory.

You will need to insert the drivers into your Linux kernel on your
target platform.

Other available targets are:
dcc : to build the DCC library in 'MRUA_src/dcc' and copy it to
'lib' where it is used by the sample applications.
smallapps : to build the small example applications and utilities. They
will be located in 'MRUA_src/llad_smallapps'
xtest : to build the xtest utilities. They will be located
in 'MRUA_src/llad_xtest'
i2c : to build the I2C module and test application. The produced
binaries will be located in 'MRUA_src/emhwlib_hal/i2c'
mambolfb : to build the Linux frame buffer driver for the SMP86xx. The
produced driver will be located in 'MRUA_src/mambolfb'
cleanrelease: to clean the package


[root@hqn:/1 mrua_SMP8634_2.8.7.0_dev.mips]#make kernel
make -C /root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src llad.ko
make[1]: Entering directory `/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
KBUILD_VERBOSE=1 make -C /root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux/ M="$PWD" modules
make[2]: Entering directory `/root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux'
make[2]: *** No rule to make target `modules'. Stop.
make[2]: Leaving directory `/root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux'
make[1]: *** [llad.ko] Error 2
make[1]: Leaving directory `/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
make: *** [/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.ko] Error 2
[root@hqn:/1 mrua_SMP8634_2.8.7.0_dev.mips]#cd /root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux
[root@hqn:/1 linux]#ll
total 20
drwxr-xr-x 4 4096 Mar 21 04:26 ./
drwxr-xr-x 13 4096 Mar 21 05:00 ../
-rw-r--r-- 1 0 Mar 21 04:26 .configured
-rw-r--r-- 1 0 Mar 21 04:26 .patched
-rw-r--r-- 1 0 Mar 21 04:26 .unpacked
-rw-r--r-- 1 129 Mar 21 04:26 Makefile
drwxr-xr-x 2 4096 Mar 14 2005 doc/
drwxr-xr-x 28 4096 Mar 21 04:26 include/

[alcomys]

Just tried to build 2.8.7.0 MRUA, make apps were ok, but failed with MRUA drivers (make kernel). any ideas?






Standalone development kit for SMP86xx

The following targets are available:
a) kernel: to build the MRUA drivers per se.
b) apps : to build the sample applications. They will be available in
the 'bin' directory.

You will need to insert the drivers into your Linux kernel on your
target platform.

Other available targets are:
dcc : to build the DCC library in 'MRUA_src/dcc' and copy it to
'lib' where it is used by the sample applications.
smallapps : to build the small example applications and utilities. They
will be located in 'MRUA_src/llad_smallapps'
xtest : to build the xtest utilities. They will be located
in 'MRUA_src/llad_xtest'
i2c : to build the I2C module and test application. The produced
binaries will be located in 'MRUA_src/emhwlib_hal/i2c'
mambolfb : to build the Linux frame buffer driver for the SMP86xx. The
produced driver will be located in 'MRUA_src/mambolfb'
cleanrelease: to clean the package


[root@hqn:/1 mrua_SMP8634_2.8.7.0_dev.mips]#make kernel
make -C /root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src llad.ko
make[1]: Entering directory `/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
KBUILD_VERBOSE=1 make -C /root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux/ M="$PWD" modules
make[2]: Entering directory `/root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux'
make[2]: *** No rule to make target `modules'. Stop.
make[2]: Leaving directory `/root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux'
make[1]: *** [llad.ko] Error 2
make[1]: Leaving directory `/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
make: *** [/root/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.ko] Error 2
[root@hqn:/1 mrua_SMP8634_2.8.7.0_dev.mips]#cd /root/smp86xx_toolchain.20080505/toolchain_build_mipsel_nofpu/linux
[root@hqn:/1 linux]#ll
total 20
drwxr-xr-x 4 4096 Mar 21 04:26 ./
drwxr-xr-x 13 4096 Mar 21 05:00 ../
-rw-r--r-- 1 0 Mar 21 04:26 .configured
-rw-r--r-- 1 0 Mar 21 04:26 .patched
-rw-r--r-- 1 0 Mar 21 04:26 .unpacked
-rw-r--r-- 1 129 Mar 21 04:26 Makefile
drwxr-xr-x 2 4096 Mar 14 2005 doc/
drwxr-xr-x 28 4096 Mar 21 04:26 include/



any progress on the compiling ??

[tx0]

not yet mate

[The666MAC]

To compile we need 2.8.7.0 toolchain, you used the old one. Unfortunally we don't have this toolchain (yet)

[fundidun]

To compile we need 2.8.7.0 toolchain, you used the old one. Unfortunally we don't have this toolchain (yet)

smp86xx_toolchain.20080505 (http://www.networkedmediatank.com/download/firmware/nmt/gpl/smp86xx_toolchain.20080505.tar.bz 2)

[tx0]

@fundidun - thats what I have already. Actually Im not sure we need a new one - but - Anyone tried to make a new toolchain with crosstool?


hxxp://ymorin.is-a-geek.org/dokuwiki/projects/crosstool

[fundidun]

OK Tx0 Then I look at it, I'll leave a link with any other manual for your review

MIPS Toolchain (PDF) (http://www.codesourcery.com/sgpp/lite/mips/portal/doc4593/MIPS-TOOLCHAIN.pdf)

[rfdomingos]

@fundidun - thats what I have already. Actually Im not sure we need a new one - but - Anyone tried to make a new toolchain with crosstool?


hxxp://ymorin.is-a-geek.org/dokuwiki/projects/crosstool

Did you try building with the smp86xx_toolchain_R3.4.tar.gz (http://www.comsatweb.nl/upload/index.php?action=downloadfile&filename=smp86xx_toolchain_R3.4.t ar.gz&directory=&) , or 2.8.0.1, wich I just uploaded, at alcomy's site?

[tx0]

3.4 toolkit builds ok.
when trying to compile mrua_SMP8634_2.8.7.0_dev.mips:


Makefile:141: *** Error: cannot infer the kernel version from the UCLINUX_KERNEL environment variable. Consider editing the 'kernel_version' variable in the Makefile.. Stop.

in Makefile


version_h := $(wildcard $(UCLINUX_KERNEL)/include/linux/version.h)
kernel_version := $(shell grep UTS_RELEASE $(version_h))




[root@hqnlenny:/0 mrua_SMP8634_2.8.7.0_dev.mips]#cat $UCLINUX_KERNEL/include/linux/version.h
#define LINUX_VERSION_CODE 132632
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))


so at least some files in mrua Makefile or in toolchain should be edited.
no smooth compiling with this 3.4 toolkit. :o15:

[rfdomingos]

3.4 toolkit builds ok.
when trying to compile mrua_SMP8634_2.8.7.0_dev.mips:


Makefile:141: *** Error: cannot infer the kernel version from the UCLINUX_KERNEL environment variable. Consider editing the 'kernel_version' variable in the Makefile.. Stop.

in Makefile


version_h := $(wildcard $(UCLINUX_KERNEL)/include/linux/version.h)
kernel_version := $(shell grep UTS_RELEASE $(version_h))




[root@hqnlenny:/0 mrua_SMP8634_2.8.7.0_dev.mips]#cat $UCLINUX_KERNEL/include/linux/version.h
#define LINUX_VERSION_CODE 132632
#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))


so at least some files in mrua Makefile or in toolchain should be edited.
no smooth compiling with this 3.4 toolkit. :o15:

If you've build your toolchain, for example, 2.8.0.1, you must then,
at toolchain directory :


ccc@ccc:/DATA/smp86xx_toolchain_2.8.0.1# source toolchain-path.env
ccc@ccc:/DATA/mrua_SMP8634_2.8.7.0_dev.mips# export UCLINUX_KERNEL="/DATA/smp86xx_toolchain_2.8.0.1/toolchain_build_mipsel_nofpu/linux/" (or wherever you have it)

and then you'll be able to make

[tx0]

have you tried it yourself? to build these modules?


[root@hqnlenny:/1 mrua_SMP8634_2.8.5.1_facsprod_leg acy_dev.mips.dts.work]#ll modules/2.6.15/
total 2612
drwxr-xr-x 2 4096 Aug 10 2009 ./
drwxr-xr-x 3 4096 Aug 10 2009 ../
-rw-r--r-- 1 2575937 Aug 10 2009 em8xxx.ko
-rw-r--r-- 1 78936 Aug 10 2009 llad.ko


they are pre-compiled in 2.851. in SMP8634_2.8.7.0 they are simply missed.
as soon as I get the whole toolchain and some new sources I'll try upload it. Hope it would be soon.

[tx0]

A slideshow on sigma8634 which can clear up some things
with this chip. here (https://www.satpimps.co.uk/showthread.php?t=129945)

[alcomys]

if i read that do***ent it looks like it is imposible to boot an other firmware without any signed keys.
if i understand it right it is also imposible to boot a ported enigma 2 image.
or am i wrong ?

[SAUS04]

https://www.satpimps.co.uk/showthread.php?t=126422&page=35

see post #686

[tx0]

if i read that do***ent it looks like it is imposible to boot an other firmware without any signed keys.
if i understand it right it is also imposible to boot a ported enigma 2 image.
or am i wrong ?

theoretically unless you have cpu keys nothing you can do - your box will ends in the deadend. guess sigma is making money of those certs and keys. nothing personal just a sigma business - love those guys for creativity =) so you can compile e2 for az but you can't boot it usual way. I have no knowledge if its possible when the box is already booted with original fw. lets see

[rfdomingos]

have you tried it yourself? to build these modules?


[root@hqnlenny:/1 mrua_SMP8634_2.8.5.1_facsprod_leg acy_dev.mips.dts.work]#ll modules/2.6.15/
total 2612
drwxr-xr-x 2 4096 Aug 10 2009 ./
drwxr-xr-x 3 4096 Aug 10 2009 ../
-rw-r--r-- 1 2575937 Aug 10 2009 em8xxx.ko
-rw-r--r-- 1 78936 Aug 10 2009 llad.ko


they are pre-compiled in 2.851. in SMP8634_2.8.7.0 they are simply missed.
as soon as I get the whole toolchain and some new sources I'll try upload it. Hope it would be soon.

No luck here also.

[tx0]

I've compiled MRUA 2.8.7.0 tho I'm not sure It will fit az.


[root@hqnlenny:/2 mrua_SMP8634_2.8.7.0_dev.mips]#cat ~/etc/log
make -C /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src llad.ko
make[1]: Entering directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
KBUILD_VERBOSE=1 make -C /home/user/work/linux-2.6.15 M="$PWD" modules
make[2]: Entering directory `/home/user/work/linux-2.6.15'
mkdir -p /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/.tmp_versions
make -f scripts/Makefile.build obj=/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src
Building modules, stage 2.
make -rR -f /home/user/work/linux-2.6.15/scripts/Makefile.modpost
scripts/mod/modpost -m -i /home/user/work/linux-2.6.15/Module.symvers /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.o
make[2]: Leaving directory `/home/user/work/linux-2.6.15'
make[1]: Leaving directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
cp /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.ko /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/modules/2.6.15/llad.ko
make -C /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src em8xxx.ko
make[1]: Entering directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src'
Makefile:121: FRAME BUFFER is ENABLED, your kernel headers are version 2.6.15 or newer
make -C /home/user/work/linux-2.6.15 SUBDIRS=$PWD modules
make[2]: Entering directory `/home/user/work/linux-2.6.15'
/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/Makefile:121: FRAME BUFFER is ENABLED, your kernel headers are version 2.6.15 or newer
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/home/user/work/linux-2.6.15'
make[1]: Leaving directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src'


[root@hqnlenny:/2 mrua_SMP8634_2.8.7.0_dev.mips]#find . -name \*ko -exec ls -la {} \;
-rw-r--r-- 1 root root 850062 Apr 4 00:16 ./modules/2.6.15/em8xxx.ko
-rw-r--r-- 1 root root 80236 Apr 4 00:17 ./modules/2.6.15/llad.ko
-rw-r--r-- 1 root root 850062 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxx.ko
-rw-r--r-- 1 root root 12162 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxfb.ko
-rw-r--r-- 1 root root 40821 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxoss.ko
-rw-r--r-- 1 root root 43750 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxalsa.ko
-rw-r--r-- 1 root root 80236 Apr 4 00:15 ./MRUA_src/llad/direct/kernel_src/llad.ko

[ni96286]

I've compiled MRUA 2.8.7.0 tho I'm not sure It will fit az.


[root@hqnlenny:/2 mrua_SMP8634_2.8.7.0_dev.mips]#cat ~/etc/log
make -C /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src llad.ko
make[1]: Entering directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
KBUILD_VERBOSE=1 make -C /home/user/work/linux-2.6.15 M="$PWD" modules
make[2]: Entering directory `/home/user/work/linux-2.6.15'
mkdir -p /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/.tmp_versions
make -f scripts/Makefile.build obj=/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src
Building modules, stage 2.
make -rR -f /home/user/work/linux-2.6.15/scripts/Makefile.modpost
scripts/mod/modpost -m -i /home/user/work/linux-2.6.15/Module.symvers /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.o
make[2]: Leaving directory `/home/user/work/linux-2.6.15'
make[1]: Leaving directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src'
cp /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/llad/direct/kernel_src/llad.ko /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/modules/2.6.15/llad.ko
make -C /home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src em8xxx.ko
make[1]: Entering directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src'
Makefile:121: FRAME BUFFER is ENABLED, your kernel headers are version 2.6.15 or newer
make -C /home/user/work/linux-2.6.15 SUBDIRS=$PWD modules
make[2]: Entering directory `/home/user/work/linux-2.6.15'
/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src/Makefile:121: FRAME BUFFER is ENABLED, your kernel headers are version 2.6.15 or newer
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/home/user/work/linux-2.6.15'
make[1]: Leaving directory `/home/user/work/mrua_SMP8634_2.8.7.0_dev.mips/MRUA_src/rua/emhwlib_kernel/kernel_src'


[root@hqnlenny:/2 mrua_SMP8634_2.8.7.0_dev.mips]#find . -name \*ko -exec ls -la {} \;
-rw-r--r-- 1 root root 850062 Apr 4 00:16 ./modules/2.6.15/em8xxx.ko
-rw-r--r-- 1 root root 80236 Apr 4 00:17 ./modules/2.6.15/llad.ko
-rw-r--r-- 1 root root 850062 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxx.ko
-rw-r--r-- 1 root root 12162 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxfb.ko
-rw-r--r-- 1 root root 40821 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxoss.ko
-rw-r--r-- 1 root root 43750 Apr 4 00:16 ./MRUA_src/rua/emhwlib_kernel/kernel_src/em8xxxalsa.ko
-rw-r--r-- 1 root root 80236 Apr 4 00:15 ./MRUA_src/llad/direct/kernel_src/llad.ko




"Makefile:121: FRAME BUFFER is ENABLED"

Interesting :)

Can you give more details on how you did it?
What toolchain did you use and what was being the problem?

[tx0]

Ive used toolchain+rootfs 2.8.0.0 and a 2.6.15 NMT kernel from


hxxp://www.networkedmediatank.com/download/firmware/nmt/gpl/

there was no major problems just minor ones.. (fixed permissions and Makefile)

[luky]

Hi, I need a little help
I successfully manage to compile 2.8.5.1 and 2.8.7.0 MRUA packages both kernel and apps.
I managed to unload original llad and em8xxx modules and insert new 2851 kernel modules, Unfortunatelly 2870 seems to have some issue, but it can solved later
The problem is that I am not able to initialize HDMI. FW is initializing HDMI using SDecoderServer, some of the builded MRUA apps can initialize it as well, but not in the new version of modules and I got stuck with some error.
I noticed somebody has mentioned that he overcomes that issue, but didn't explain how
Can somebody give me hint how it can be done?

[halabessa]

In addition to the files i posted yesterday, the mrua sources used in current firmware (4625)

mrua_SMP8634_2.8.5.1_facsprod_leg acy_dev.mips.dts.work
http://www.sendspace.com/file/b8x66t

posted yesterday
mrua_SMP8634_2.8.7.0_dev.mips.zip
http://www.sendspace.com/file/t1j8ml

dcchd_SMP8634_2.8.5.0_black_GCC4. mips.zip
http://www.sendspace.com/file/ne9gex


Again, files anonomously "donated" to the community, thx alot :cup-006:

Developers have fun :biggrinjester:


// The666MAC

Some other useful files for developers added (thanks to medmed on another forum):
originaly posted by medmed:
"pour les DEVs :
http://www.2shared.com/file/12466979/2396e44/25811255smp8634_do***entation_.ht ml
http://www.2shared.com/file/12479527/f4ef7784/37724068SSignmal_SMP8634_SDK.html

Sigma bootloader package (the 2.8.4.1 version):
http://en.pudn.com/downloads152/sourcecode/embed/detail667613_en.html
http://www.2shared.com/file/12486552/11f7924b/75448144smp86xx_boot_loader_28.ht ml

autre do***entation :
www.mediafire.com/?idyjyzzo2k3
Citation

jtag_tutorial
Release_Notes_SMP8634_2.8.2.0
Release_Notes_SMP8634_2.8.3.0
Release_Notes_SMP8634_2.8.4.1
security
smp8634_do***entation_2.8.0
smp8634_do***entation_2.8.5.0
SMP8634-DS-A-06.pdf
SMP8634-DS-A-07.pdf
SMP863x_Memory_Design_1[1].1.pdf "


:respect-048:

[luky]

have seen that already :(

[single]

Hi because of cpuinfo we can tell board is tango, but what config he use?

849/852/885??

# Hardware config file for SMP863x platform (xenv)
# Default for 885-E2 board (a.k.a BD reference)

# Hardware config file for SMP863x platform (xenv)
# Default for 849-E2 board (a.k.a Odyssey)

# Hardware config file for SMP863x platform (xenv)
# Default for 852-E2 board (a.k.a Envision)

On working_sdk we have a genxenv, then they are using 8XX-E2 board?

What you think?


And about Tango? What version they use?

Because of genzbf we can see emhwlib_registers_tango2, then they use tango 2

[HighHD]

mrua_SMP8634_2.8.5.0-facsprod_legacy_dev.mips.dts

[single]

mrua_SMP8634_2.8.5.0-facsprod_legacy_dev.mips.dts


Where i can find this version @HighHD?

I only have:

mrua_SMP8634_2.8.5.1-celrun-08062009-2.6.15K_facsprod_legacy_dev.mips

:302:

Anyway you point me this, because?

(ARM vs MIPSEL) ???

[luky]

i am almost sure it is tango2 - saw it in some log
and there in no question about arm/mipsel - it's mips as you can se from cpuinfo

[single]

i am almost sure it is tango2 - saw it in some log
and there in no question about arm/mipsel - it's mips as you can se from cpuinfo


the arm/mipsel question is based on some boards is arm and others are mipsel, but if this one is tango 2 what config is used?




849/852/885??

# Hardware config file for SMP863x platform (xenv)
# Default for 885-E2 board (a.k.a BD reference)

# Hardware config file for SMP863x platform (xenv)
# Default for 849-E2 board (a.k.a Odyssey)

# Hardware config file for SMP863x platform (xenv)
# Default for 852-E2 board (a.k.a Envision)



:grouphug:

[HighHD]

Yes, single, i am also using that, and it is Tango 2.

Tango 3 is 8655

[luky]

I am experiencing another problem, which my be related to that. I can compile 2.8.5.1 sources to produce em8xxx.ko module. I can replace original one without problem, however I am getting segmentation fault when I try to rmmod this module in free_module/kfree
Did anybody experienced this? Is it because of some compiler flag or so some -D flag?
Can somebody post working MRUA.env?

[The_Ripper]

This one is used for Azbox receivers,

# Hardware config file for SMP863x platform (xenv)
# Default for 852-E2 board (a.k.a Envision)

[tx0]

This one is used for Azbox receivers,

# Hardware config file for SMP863x platform (xenv)
# Default for 852-E2 board (a.k.a Envision)


Mate, I was quite sorry to hear that you've run out of enthusiasm for developing azbox fw. You've mentioned
that MRUA need to be compiled against libc. Is that step
really important and there is no way to skip it? What are
the possible ways of future development if there will be
no other sigma leaked files? Just want to know your opinion.

[single]

Mate, I was quite sorry to hear that you've run out of enthusiasm for developing azbox fw. You've mentioned
that MRUA need to be compiled against libc. Is that step
really important and there is no way to skip it? What are
the possible ways of future development if there will be
no other sigma leaked files? Just want to know your opinion.

You can compile E2 with uclib, but you have to mod it all src, and looks all people don't like that.

Then moding crosscompiler can be a option to don't touch on E2.

To have a Idea you can take a look to VDR, how is write on uclib.

@The_Ripper

Using buildroot mode to mod it, or crosscompiler(ng)?

:cheers2:

[single]

Can someone with debie install make a strace log on azbox?

Thanks

[zfeet]

Where i can find this version @HighHD?

I only have:

mrua_SMP8634_2.8.5.1-celrun-08062009-2.6.15K_facsprod_legacy_dev.mips



Would you mind sharing this one, please?

[single]

Would you mind sharing this one, please?

Hi

This is the file:

mrua_SMP8634_2[1].8.5.1_facsprod_leg acy_dev.mips.dts.work.tar.bz2

I hope this can help you

:king-041:

This looks like the one used by opensat/celrun




export RMCFLAGS='-DEM86XX_CHIP=EM86XX_CHIPID_TANGO2 -DEM86XX_REVISION=6 -DWITH_FACSPROD=1 -DEM86XX_MODE=EM86XX_MODEID_STANDA LONE '
export COMPILKIND=release




Inside of Mrua you will find this:



source /DATA/Mountain/MtBaekDu/Target/target_td210.2850.gcc3.4/target.env
source /DATA/Mountain/MtBaekDu/Working/build/smp8634-2850.gcc3.dts.env
CURRENT_DIR=$PWD
TARGET_DIR=/DATA/Mountain/MtBaekDu/Target/target_td210/MMP/lib/
TARGET_USER_DIR=/DATA/Mountain/MtBaekDu/Target/target_td210/MMP/usr/lib/


############################ dcc ##############################
cd dcc/src/
make clean || exit 0
make || exit 0
cp -a ./libdcc.so /DATA/Yellow/Working/SVodLibrary280/SDecoderServer/libdcc.so.2850.gcc3
cp -a ./libdcc.so $RUA_DIR/lib/
cd $CURRENT_DIR




This dcc lib is very important because is the Decoding Chain Control API.


For example take a look to pmt.

With this you can understand how processor start demux, and how output is done.

Is a little crazy how they do this, but...

No standard means a lot more understanding :driving: by Parse Program Association Table you have link to drives The so call "EMhw...".

Interessting I just see reference to PMT and PAT, didn't find the others 2, CAT and NIT.

CU

[zfeet]

Inside of Mrua you will find this:



source /DATA/Mountain/MtBaekDu/Target/target_td210.2850.gcc3.4/target.env
source /DATA/Mountain/MtBaekDu/Working/build/smp8634-2850.gcc3.dts.env
CURRENT_DIR=$PWD
TARGET_DIR=/DATA/Mountain/MtBaekDu/Target/target_td210/MMP/lib/
TARGET_USER_DIR=/DATA/Mountain/MtBaekDu/Target/target_td210/MMP/usr/lib/


############################ dcc ##############################
cd dcc/src/
make clean || exit 0
make || exit 0
cp -a ./libdcc.so /DATA/Yellow/Working/SVodLibrary280/SDecoderServer/libdcc.so.2850.gcc3
cp -a ./libdcc.so $RUA_DIR/lib/
cd $CURRENT_DIR





I still haven't been able to find this exact mrua. Could you help me, please?

[wullieb25]

:respect-048:hi guys dont know if these files will be any use
hope they are


the files wont upload
pm me if you want them

DevAzbox_by_leandrpf
and
novosplugins

[satcamd]

Hi,

could someone download this file for me, please? hxxp://en.pudn.com/downloads156/sourcecode/unix_linux/detail693162_en.html

Many thanks, satcamd

[satcamd]

Hi,

does someone has an old mrua source contains rua.c ?
Please send me!

thank you!

[satcamd]

Hi,

mrua 2.8.8 released does anybody have it?
hxxp://liuye066.javaeye.com/blog/698513

regards,

[digihoe]

Kernel linux-2.6.32.tar.bz2 is now up on the sigma ftp.

[zfeet]

Hi,

mrua 2.8.8 released does anybody have it?
hxxp://liuye066.javaeye.com/blog/698513

regards,

Did you manage to find it?

[zfeet]

Hi,

could someone download this file for me, please? hxxp://en.pudn.com/downloads156/sourcecode/unix_linux/detail693162_en.html

Many thanks, satcamd


Here you are:

hxxp://www.mediafire.com/?juxcvimmhikjjrd

[zfeet]

Kernel linux-2.6.32.tar.bz2 is now up on the sigma ftp.

Is it unpatched version as always?

[digihoe]

Is it unpatched version as always?

I would think so yes. But I would think that Sigma Designs have made a patched version for one vendor or maybe for the "andriod OS", just hard to know what device is using this kernel, and hard to track it down.

Best regards!

[richp999]

Hi
I'm searching for the mrua_SMP8634 .
I had it a couple of years back, but it got deleted.
All the links on here are long since dead ; I don't suppose anyone still has it ?

Thanks,

Richard.

[ntv5]

Hi
I'm searching for the mrua_SMP8634 .
I had it a couple of years back, but it got deleted.
All the links on here are long since dead ; I don't suppose anyone still has it ?
Same problem. pudn has it, but the sendspace links are all dead. I'm guessing no response in the past 6 months isn't a good sign.

Anyone?

[tx0]

Pm

[arschloch111]

I would also add some files from here:


ftp://armutils:sigmadesigns((@))gw.sigm adesigns.com/smp86xx


it would be nice if somebody will post some how-to for newbies about building sigma work environment (I mean gcc, gdb, make and other stuff)

hey, registered here trying to find sigma smp86xx armutils from their ftp
if anyone still could share ?
cannot use pm(