st71xx is a very different platform so is not an even compare.
On the other way developers on azbox E2 have the up2date tools to make it work better than st71xx.
The only problem we are facing guys is the low level driver that need to be written from scrutch, but we are getting there
IMOH though e2 is going to be slower than vu+ as platform has 2 do with solid cpu power and 300mhz is what we have to work from.
Last edited by demetris; 24-03-2010 at 08:53 PM.
what has the_ripper to do with this subject? yes he is trying to do this, but he isn't the only one working on it Carp95, a lot of more users/teams are working on it (enigma 2)
YES dvbapi is done! jesus..
Last edited by hfmls; 24-03-2010 at 09:00 PM.
Sorry m8 to misty for me.Originally Posted by hfmls
I know how it should be done, only the recources aren't there to do it.
So far all the people on this topic wich have replayed couldn, t confince me.
If the release is there within this month, even if it isn't stable ( including april) I will open a new topic and make a official apology to you.
So far I'am shure I don't need to open a new topic
i think there should be 2 threads anyway for e2 on azbox. all the negitive people and flamers. and one for people that actualy want updates . the thread on nabilos site is looking promissing. fingures crossed.:respect-059:
Carp95, mate i don't care about that, apology or not. Simple fact is, enigma 2 is coming, really really soon. There are now many many users with same sources as me, that can provide proof.
What do u want, screen shots, videos? There aren't any. Because from what i understand, the "testers" are the coders. We are all in the same boat, we all want good stuff for this box.
All i can say there's a cvs already and many coders/teams/groups,are working on it.
The rest i can't say because it was info given from some admin in FISCPT.NET and asked not to post outside the forum. But there is a lot more, and regarding Opensat method to operate around this subject.GOOD method.
Sigma Designs 863X platform requires the kernel image to be
> signed so
> that the bootloader boots it. I foresee this conflict of GPLv3
> and
> signed kernel. I think I could not disclose the key for
> signing a kernel
> to end users so that they can build their kernel. I may need
> to build a
> signed 2nd stage bootloader to boot unsigned kernel image. It
> will slow
> down the boot process in turn.
>
> I also afraid that I breaks the license agreement with Sigma
> Designs and
> with Microsoft, for WMV DRM, if I let users run their own
> kernel on the
> product.
So the team must stay hidden if they dont want to face the consequences
this was probably expected.
should be a lot more problems. dts licenses, etc etc etc
i dont mind to not know who is doing itas long as they provide a paypal link and releases
Well yeah i'm quite aware of that, hence me stating my hope for good performance
its all about license issue.
thats the reason Opensat not can made the source open to the public.
because if opensat made the source open to the public they are in conflict with sigma design and microsoft and the drm license dts ect ect
so they knew this receiver never will be open source.
and about the signed kernel image.
this news is already more than a year old.
and about the second signed bootloader is also more than a year old.
there is also one chinese team that have spoken about a modchip to load unsigned kernel to the sigma chip.
Sigma Designs 863X platform requires the kernel image to be
> signed so
> that the bootloader boots it. I foresee this conflict of GPLv3
> and
> signed kernel. I think I could not disclose the key for
> signing a kernel
> to end users so that they can build their kernel. I may need
> to build a
> signed 2nd stage bootloader to boot unsigned kernel image. It
> will slow
> down the boot process in turn.
>
> I also afraid that I breaks the license agreement with Sigma
> Designs and
> with Microsoft, for WMV DRM, if I let users run their own
> kernel on the
> product.
So the team must stay hidden if they dont want to face the consequences
Note:
E2 have a license too.
@alcomys
I wouldn't mix all things in one. Sigma have some packages which are not GPL but released under thier terms. For example MRUA kit. I think opensat can release some part of its own code but they just don't want to. I have not seen any source code from opensat. do they have?
UPD: forgotten tv_sdk..
@demetrisI think I could not disclose the key for signing a kernel to end users so that they can build their kernel.
It was said about the loader source code? by whom? image is signed with no private key exposed.
Last edited by tx0; 25-03-2010 at 01:29 AM.
Ok here is it :
beta test - 25
official - - 28
---------------------------------------------------------------------------------------------------
Unsupported features and known problems
---------------------------------------
- CAM slots are not supported yet.
- Timeshift does not work yet.
- Rewind does not work properly. Enigma2 sometimes freezes when rewinding.
"Jump back" can be used instead (see playback).
- Samsung LCD TVs will probably have problems with the default resolution
576i.
This is an alpha image. That is some functions may not be available or be
buggy (causing crashes / freezes or loss of data).
The installation of the Enigma2 image formats (ext2) the internal harddrive.
ALL FILES ON THE HARDDRIVE WILL BE LOST.
Installation instructions
You will need either a USB stick or a USB harddrive with FA**2 filesystem.
- Copy the files Enigma_Installer.tfd, uImage and rootfs.tar.gz to the USB device.
- Attach the drive to the USB slot.
- Open the firmware update menu and select the image file Enigma_Installer.tfd on the USB drive.
- Start the firmware update from USB.
- After about 6-7 minutes the installation should be finished.
DO NOT REMOVE THE USB DEVICE UNTIL the installation has finished.
During the installation the VFD shows the current installation step and error messages (if any):
"9 USB Stck" mouting USB stick
"PART 8 HDD" HDD partitioning
"7 HDD FMT" formatting HDD (root fs)
"6 HDD FMT" formatting HDD (FS date)
"5 HDD SWAP" Creating swap
"ROOT FS 4" Installing root file system
"3 LOADER" flashing U-Boot settings
"2 kernel" kernel flashing
"1 fsck" checking file system
"0 REBOOT" rebooting within 2 seconds
It is recommended to attach a cable to the serial port and log the output in a
terminal program (eg TeraTerm) during the installation and the first start.
The USB should be writable filesystem to prevent infinite loop installation.
(The uImage file is renamed to avoid the infinite loop.)
The first play usually takes approximately 3 minutes due to creation of
device nodes.
First start
-----------
On the first start the Enigma2 interactively configures the video output to be
used. The following options are available:
- Component
- HDMI
- Scart
- HDMI-PC
Each connection type is switched on for 30 seconds. The VFD displays the
connection type which is currently active. You can either wait until the
connection type you want is displayed and your TV shows a picture or you
can select the connection type with Up and Down buttons on the remote control.
Confirm the desired connection type with the OK button. After that you can
proceed with the configuration supported by the configuration ******.
The image contains a default channel table. If you want to replace it you can
perform a channel scan later.
Network configuration
---------------------
The U-Boot settings contain the following configuration by default:
MAC address 00:3 e: 9e: 11:22:33
IP address 192,168,178,100
That is after booting the image you can login via telnet if your computer is in
the same subnet.
These values are set up by the U-Boot. You can temporarily change the values
Enigma2 in the menu "Settings / System / Network... / Adapter Settings" or change the
U-Boot parameters.
Default U-Boot bootargs:
BA1 = console = ttyAS0, 115200 root = / dev/sda1 rw init = / bin / devinit
ip = 192.168.178.100:192.168.178.10:19 2.168.178.10:255. 255.255.0: tf7700: eth0:
off nwhwconf = device: eth0, HWaddr: 00:3 e: 9e: 11:22:33
mem = 128M bigphysarea = 4000 coprocessor_mem = 4m @ 0x10000000, 4m @ 0x10400000
To change the IP addresses interrupt the U-Boot and execute the countdown
following command replaced with IP addresses:
TF7700> set BA1 'console = ttyAS0, 115200 root = / dev/sda1 rw
init = / bin / devinit ip = <own IP>: <server IP>: <DNS
IP>: 255.255.255.0: tf7700: eth0: off
nwhwconf = device: eth0, HWaddr: 00:3 e: 9e: 11:22:33
mem = 128M bigphysarea = 4000 coprocessor_mem = 4m @ 0x10000000, 4m @ 0x10400000 '
Please note that the setting has to be split in two lines to bypass the
limitation of the U-Boot. The second line must start with a
white space. The
string is enclosed in single quotes. Any change is temporary unless the
settings are saved to flash using the command "saveenv". Before saving
settings to flash you should test whether the kernel boots with your settings.
Enter "boot" at the U-Boot prompt to start the kernel. (After testing the
settings without saving them you will have to enter your changes again.)
Full map can be found in the file / usr/local/share/
Where's the image?
Are you beta-tester ? you aren't
So wait until 28 and prepare your apologyze topic...
No problem I'll be away untill 31-3-2010 then I'll post that topic if release is there
I saw this text very long time ago on some forum. It is not for Enigma 2 on azbox.
I found it, its for TF7700HDPVR.
Yes -> http://www.sat-television.com/showth...he-TF7700HDPVR
It´s not the same, but very similar...
Last edited by linarense; 25-03-2010 at 09:21 AM.
that is totally different to what was posted here
hey this is the beta for azbox????
After being 16 months on beta firmware, you guys are willing to go back to a rumoured alpha E2 release and you call this a step forward?
Too bad my other topic, which was asking your view on how long should it take for a professional team to release a non-beta firmware working as advertised, somehow "vanished". I posted it a few months back and i remember goran saying he would give them infinite time. This is going in the Guinness world records book, the box which is on beta firmware for more than 16months + a couple of months of internal company tests and still going.
Posting Permissions
Reply With Quote
Bookmarks