Looks like tuners is not a problem, then go head.
Others chips are missing on this post's too, like scart (avs), ethernet, ic2 chips bla bla...
:king-041:
Printable View
Looks like tuners is not a problem, then go head.
Others chips are missing on this post's too, like scart (avs), ethernet, ic2 chips bla bla...
:king-041:
Well, if I can help decorificador Azboxhd elite motherboard information and tuners.
Motherboard: DRACO_M / B: Rev3.00
Tuners:
Draco_DVB-S-S2_REV 3.00
DNBU24512ICC LEAD FREE
080514 EAAATR
--------------------------------------------
SAMSUNG
TM10_DVB-C2_REV3.00
DNQS44CPP101A
Demodulation IC STV0297E
- - - - - - - - - - - - - -
090621 HAT.-LF
2009.04.02
I believe all the audio and video will be accessed through sigma audio video calls. Same goes for the demux, but dvbapi needs to made to work with this.
Ethernet is also provided by the kernel. I think main thing to build now is the dvbapi part, with the demux and sending the audio video through sigma chip.
Any progress on this the_ripper?
Any new Info on development?
when you have a second test version please release it, so i can test it.
Think about create silent az e2 team and donate function.
"Recovery procedure
__________________
* For all people which have a problem with fleshing Enigma 2 in AzBox , where installation stop ~58% and now have a BOOTING message on display.
You will need :
- Application Acronis True Image
- E2Backup.tib
- External HDD case with IDE controller ( or if You are working on PC, Motherboard which have IDE controller ) .
Take the DOM from AzBox and connect it with IDE connector from Your external usb case for HDD .
Connect the red wire from power cable ( 4-pin Molex connector ) from case ( +5V ) ( picture: Molex and pwrcom ) with right oriented pin on connector which is on DOM - pictures DOM1 and DOM2
Connect USB cable from the HDD case with Your PC.
Now, startup Acronis True Image application, and choose Recovery from the menu on right side - picture 1
Choose Disk Recovery on the top of the window and load file E2Backup.tib and press next - picture 2
Choose Recover whole disk and partition and press next - picture 3
Check-all whole Disk, so it means two partitions : Ex** and Linux Swap and press next - picture 4
Choose on which disk You will restore content, in our case DOM, and press next - picture 5
Commit with OK - picture 6
Choose Proceed - picture 7
Wait for few minutes that process complete - picture 8
When the restore of data and partitions finish, press Ok - picture 9
now You can exit from application, 'Safely' eject Your external USB HDD, in our case DOM.
Disconnect usb cable, and put back the DOM on AzBox, turn on AzBox and wait for 20 seconds that E2 boot.
Now you can take a look on enigma, and when You decide to go back on Official version of Firmware, that You can do with plugin from DDdamir.
Installation od DDamir plugin is described in another tutorial.
hxxp://rapidshare.com/files/407099608/Recovery.rar.html
rgs, "
Again " booting " ! what now ?
some more hardware-infos:
Network-chip:
Realtek RTL8201CP
_xxx.harerod.de/centipad/do***ents/RTL8201cp_121_.pdf
Boot flash:
Eon EN29LV640B-90TIP 64mbit(8MB)
_hxxp://pdf1.alldatasheet.co.kr/datasheet-pdf/view/207730/EON/EN29LV640B-90TIP.html
SATA-to-PATA bridge:
Marvel 88SA8052 (SATA 3 Gb/s to PATA 133)
Hdmi-Transmitter
-Silicon image SIL9030
_xxx.datasheet.in/datasheet-html//I/L/SIL9030_SiliconImage.pdf.html
-Silicon image SIL9134 (Premium+ only)
DDR-SDRAM 512mbit(64MB)
-Hynix HY5DU121622DTP-D43
_xxx.hynix.co.kr/datasheet/eng/consumer/details/consumer_02_HY5DU121622DTP.jsp?se archType=2&menuNo=1&m=2&s=2&RK=02 &RAM_NAME=
-Zentel a3s12d40etp (Premium+)
common interface controller
-STARCI V2.2
_xxx.inctech.co.kr/inctech2/product/StarCI_Brochure.pdf
-STARCI2WIN V1.1 (Premium+)
_xxx.megaupload.com/?d=9TTIBDDM
driver(sh4) for both,see here:
_hxxp://gitorious.org/open-duckbox-project-sh4/tdt/commit/4eac4a45bbac9eee336b320005b2ce3ba 7756f98
multiplexer bus-switch
IDT IDT74CBTLV16292
_xxx.datasheetdir.com/IDT74CBTLV16292+download
USB 2.0 Host Controller
Via VT6212L
_xxx.microdesignum.cz/_d/via-vt6212l.pdf
ISDB-T Frontend only brasil
Samsung DNVS22CXP241A Elite/Premium
90507XBG demod
About connexant demod-chips.
In the manual for a LG frontend,you can see a "little"more,
how the work.
_xxx.haluyatech.com/down/lgtunner/s2TDQR-C005F.pdf
VFD, IR and Ethernet are things which already working !!!
So why some of You mentioning ethernet drivers ?
It is working normally, and even it is faster in transfer of files, than on Official AzBox Firmware......
Thanks for your information, are You able to report the status of the project?
In last days we have heard many rumors from people who reported significant progress confided by coder or insider E2 project.
I'd like to ask You (if You can) to report the status of the project:
- What is already working (since the last alpha public release)
- What's not working, but people are working on.
- what's not working and nobody start to work on.
- The_ripper said:I think that team want to publish sources. Is true?Quote:
Many Python code is disabled in mytest.py , Harddisk.py is used from Sh4 build, etc ...
so guys who wants/know Python can start playing/repairing because it want work with default Python code for Dreambox ..
- If is true, when?
- Last important question: who are the components of the project, some of them we know, others have insights (maybe), but it is possible to know at present who are the people of this phase of the project?
Thanks for all
I think we have to give them some time. I also offered The_Ripper to use our git. We are ready for it, so let's wait. I'm working on some files to be adapted on OE to have a azbox specific files, like linux-azbox.bb. At the moment the build kernel is not booting via tftp - but I will get it to work.
It is very important that a lot of coders and Python specialist will have access to the toolchain to support the project.
Maybe I can offer today some stuff to start.
Yes You are right, my intention wasn't to increase the pressure(I didn't ask them about time to finish or time to next release, I know, they are approaching E2 as hobby althoght they are very good coders, so for this reason they can't work all time on the project), but only to clarify the situation, because someone make confusion.
At the moment only the four files of The_Ripper are available but we can put more in it.
git clone git://kf-repos.de/oe-azbox.git
( "git pull" to get updates if any available)
make -f Makefile-opendreambox-1.5
I will put the azbox specific stuff in it later. I will just modify the linux-dm800.bb and put the right path fot the kenerl source in it.
The original Makefile hast dm8000 acitivated - is there a reason for this?
Added a simple linux-azbox.bb
no you can use
bitbake -c compile - b ../openembedded/packages/linux/linux-azbox.bb
to build the kernel. No additional Patches at the moment (are there any missing yet?) and you first have to build the crosscompiler. It is possible to link an existing to build/tmp/cross/bin.
Hello ,
edit it from dm8000 to dm800 ;)
and for all other people, please consider the true news, only from the_ripper, telesat and me .
As You can see, there is no need that some persons spread rumors or news which are not true. We are on forums, like You guy's, and we are watching. So , as something new appear You will have information.
Also, thanks to all of You for supporting the ripper, as he is really doing amazing job, also thanks for support us ( telesat, me and other guy's involved in project ).
Thanx!
Well it is edited a while ago ;) just git pull.
We should also modify openembedded/conf/machine/dm800.conf to azbox.conf and put the wanted PREFERRED Versions. and kernel-modules. At the moment I have no idea which they are.
Hi, i follow the steps, with git, just fine but the make file gives me this error:
miguel@miguel-desktop:~/oe-azbox$ make -f Makefile-opendreambox-1.5
mkdir -p /home/miguel/oe-azbox/dm800/cache
mkdir -p sources
mkdir -p /home/miguel/oe-azbox/dm800/build
mkdir -p /home/miguel/oe-azbox/dm800/build/conf
mkdir -p /home/miguel/oe-azbox/dm800/build/tmp
git clone -n git://git.opendreambox.org/git/openembedded /home/miguel/oe-azbox/dm800/openembedded
fatal: destination path '/home/miguel/oe-azbox/dm800/openembedded' already exists and is not an empty directory.
make: ** [/home/miguel/oe-azbox/dm800/openembedded/.git] Erro 128
cd /home/miguel/oe-azbox/
mv dm800 _dm800
make -f Makefile-opendreambox-1.5
The problem is that git is not amused that there is a directory.
After OE is finished you can
cp -rd /home/miguel/oe-azbox/_dm800/openembedded/packages/linux/linux-azbox* /home/miguel/oe-azbox/dm800/openembedded/packages/linux/
To build the kernel alone (but you must have the crosscompiling stuff before)
cd ~/oe-azbox/dm800/build
bitbake -c compile -b ../openembedded/packages/linux/linux-azbox.bb
I'll fix this, that it is right in the git with _ .
EDIT: fix done
ok its working now, with your instructions
Thanks
But remember it is just a start. There must be some change made to get the stuff working like the one from The_Ripper. But it is a way to get it working.
you guys are the best :)
i'm really happy all good users/programmers are coming together.
i just can't wait for the "boom" that svn will bring :)
@moicas3004: I offered him but at the moment I'm nearly the only one. But I wanted a git server for other projects.
One of the advantages of git is that it can be cloned very easy - no problem for me if it will be on another server.
We'll see what happens in the next few days.
it would be good a word from the developers, givin us a feedback how the work is.
TONYBAM, do you recovery your box , and how ?
in progress I got nokia KU-42 with 3 wire only i connect to RX GND TX and with putty i connected and got
the following information
وxosPe0 serial#cf9f27d02f2f8cbe8fb8e5d313 c5b853 subid 0x50
xenv cs2 ok
�ـ�xosPe0 serial#cf9f27d02f2f8cbe8fb8e5d313 c5b853 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/0x000a7876).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a7676).
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:d1:83
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>
the problem i have i cannot write coomand in putty
for net initialization and IP for box i keeping try till I success
I wait telesat new file with old kernel and I will try again.
@The_Ripper
I sent you a link in pm with an interesting discussion
I hope it is useful
edit: I'm sorry but I did not realize that it had sufficient msgs to send pm
I sent PM on e2az
Help trouble with Enigma2...azbox keep booting
I installed Enigma2 yesterday & get stuck,wanted to go back to Azbox fw (tried old & new version) but the box don't recognize it ...
I connected trough Filezilla and I made the biggest mistake ever...I deleted some files thinking that was related to Enigma2 files...now the box doesn't respond it stuck at "BOOTING".
I've been looking everywhere how to reinstall fw but no luck...
-I unplugged power cable for few hours,tried differents fw,tried emergency flash...but nothing it keeps booting ...
indeed , big problem.
It as already sayd here, guys that dont have big know how in linux don't install this first image. ITS ON THE FIRTS POST.
Now you have to get a serial cable with RS232 to conect the box or folow the procedure that is on this post a few pages back, removing your DOM from the box and do as it says.
Dear friends, as we got many inquires on PM about that user hfmls spreading rumors about some release dates, and current progress on this project, We want to say that we are not speaking with him, and we dont know from which persons he is getting this informations, but absolutly NOT from us. Also we dont know what is the reason for that, like he is telling dates when something should be released, maybe to rise up his popularity or ?
Point of this post is not to insult anybody or to discredit anybody , just precaution that in future everybody of You know, that this guy is not representing our work, opinnion or any news, and as I mentioned before, all work will be published public, so nobody needs any kind of rumor.