Fortis 4th generation HD receivers: some info

[younesetre]

Thanks you are incredible

[Audioniek]

The project approach

The reason I started to try and bring Enigma2/Neutrino to the 4^th generation Fortis receivers is twofold:

• The duckbox-developers-git has an entry for the DP7000, so somebody (j00zek) already had provided a starting point;
• I owned a DP7001 at that point in time.

I first set out to explore the DP7000 stuff in the git mentioned, and soon found out that it probably contained some files directly originated from Fortis, but also that apart from some basic aspects, not much had been done with regard to receiver specific development. In addition, apart from the initial commit, the git has been stationary with regard to the DP7000 up to now.

Then I devised an approach of my own. The first step was to build a debug kernel that can be loaded and started with the stock bootloader already present in the receiver. Once the printk output can be seen on the serial port of the receiver, its config can be tuned and the required features can be added one by one. This has led to the .config I am using for about two months now, although it is not finished and/or optimized. The current kernel loads (with one error remaining) and starts the /etc/init.d/.rcS. Later on in the project I succeeded in retrieving the .config used by Fortis from the kernel in one of the their stock firmwares and used that info to further tune the .config I use. So far I have only built with patch level 215.

The next step is one I foresaw I could not finish on my own (and one of the reasons I started this thread): try and get/build all the drivers. Some are simply missing and not created yet in any git like the frontpanel driver, others do probably exist but are not available publicly or not found yet (like the FDMA firmware). I have tried to write the missing drivers on my own, and succeeded for some. The order of building is simply the order the rcS script uses to install them.

When the essential drivers are all ready, the next step would be to adapt Enigma2/Neutrino to the receiver(s), but that point has not been reached yet.

More to come, the kernel is in the next posting...

Regards,

Audioniek.

[Kodov]

Hello.
I have Xcruiser XDSR 420 Avant receiver.
I want to change channels via Up and Down buttons (they are on the top and bottom of the OK button). I mean that I want these buttons to do CH+/CH- functions.
But when I press Up or Down there is channel menu on the screen.
How to change that, because it is very uncomfortable?

[TopSat UltraVip]

enigma2 sur forever 9898

[harryhase]

enigma2 sur forever 9898

do you have a link for download?

[solala]

hi audioniek,
i use this one to display iboot logo, but i merged it to i-boot binary. maybe its worth a try to cat it to mtd3 so we would know if fortis uses the same coding
i-bootlogo7.gam.gz

[Audioniek]

Hello solala,

Thank you for your input, and you were spot on. File size and header info are exactly the same as the pictures used by Fortis. If I rename the unpacked .gam picture to duckbox.Booting.gam and gzip it, then add the .gz as user data (partition type 9) to the fup arguments, flash the .ird, then the Linux and Atemio logos (plus the text Titanit) are shown on power on. Can you enlighten me on how to create my own .gam pictures?

Meanwhile I have added support for the bootpicture to the flash environment: if X/cdk/root/bootscreen/bootscreen.gz is found, that file is used as the bootpicture file.

Regards,

Audioniek.

[zozman]

what's new

[Audioniek]

@zozman

At the moment I am, very busy solving problems on Spark7162, as many HDMU users are affected by them. So that takes precedence at the moment.

@Kodov
Assuming your are talking about the original Xcruiser firmware: all Fortis firmwares have this behaviour by design, and it cannot be changed as these firmwares are closed source. And why do you want to have functions on these keys that have their own keys quite nearby on the remote?

Regards,

Audioniek.

[Kodov]

@Kodov
Assuming your are talking about the original Xcruiser firmware: all Fortis firmwares have this behaviour by design, and it cannot be changed as these firmwares are closed source. And why do you want to have functions on these keys that have their own keys quite nearby on the remote?

Regards,

Audioniek.

I want to change this because I use to have functions on these keys.
But I solved the problem. You can use plugin SX key_redefine to change the keys.
Best regards, Kodov.