Posts by joeuser

  • sti7111 based unknown clone

    I did not have time to look at the files, but a quick look a the duckbox developers source code showed there are some well known boxes with NOR.

    https://github.com/Duckbox-Dev…cripts/flash_part_w_fw.sh


    I did not look through all the maps, but maybe one matches, or is close to your box?


    You can either build your own image, or you can try a build from one of the groups. For sure HDMU has some builds for these boxes:

    http://www.hdmedia-universe.co…ges.php?pageid=1&tabid=33

  • sti7111 based unknown clone

    It is common to the /var folder to be separated from the rest of the file system because it can contain user files and logs which can grow and fill up the disk - so separating is a way of protecting the root file system.


    Using the current kernel, you would also need the current file system because it contains the modules (drivers) which were built specifically for that kernel.


    oscam has some spesific things for enigma2, but it also works also with Spark and if you do not recognize the current application as enigma2, it probably is Spark.


    It may be possible to add enigma2 to the existing file system, but there may be space issues. You would probably need a combination of the NOR and a USB flash drive.


    You should look at the root file system and look at things like the /etc/inittab and /etc/fstab to see what it mounts and runs after boot.


    If you upload the bin files someplace, I could take a look at them.


    the oscam is:

  • sti7111 based unknown clone

    It looks like it recognizes it, but maybe the problem is the partition map is different than what it is expecting???


    I found this: https://www.denx.de/wiki/DULG/…figurationOfMTDPartitions

    but checking the kernel for my spark7162, I see it is not enabled.


    Attached is a script you can run to extract the kernel config from an uImage file. (if enabled)


    You may have to build your own kernel. There are 2 main development environments to choose from.

    One is the duckbox developers: https://github.com/Duckbox-Developers/

    The other is from open embedded alliance: https://github.com/oe-alliance

    Taapat has a custom build environment for the spark7111 from oe-alliance: https://github.com/Taapat/vuplus-fulan-openpli-oe-core


    Each has its pluses and minuses...



    These links may also be helpful in setting up a kernel:

    http://processors.wiki.ti.com/…Filesystem_in_NOR_or_NAND

    http://how-to.wikia.com/wiki/H…_Technology_Devices_(MTD)

  • sti7111 based unknown clone

    First, here is a link for uboot commands in case you do not have: https://www.denx.de/wiki/U-Bootdoc/BasicCommandSet


    The root needs to be the extracted img, or for many images, they have a USB option which is a tar.gz file containing all the files. The partition on the USB probably needs to be ext2.


    Attached script can be used to extract the files from an e2jffs2.img


    basic manual steps would be to make two partitions on a flash drive - first a small fat partiton for the uImage file and the second a ext2 partition to put the enigma2 files.


    commands would then be something like:


    fatload usb 0:1 80000000 uImage 

    setenv bootargs console=ttyAS0,115200 root=/dev/sda2 rootfstype=ext2 rw coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 printk.time=1 nwhwconf=device:eth0,hwaddr:00:80:E1:12:40:69 bigphysarea=6000 stmmaceth=msglvl:0,phyaddr:2,watchdog:5000 panic=10 rootwait usb_storage.delay_use=0 

    bootm 80000000

  • PowerVU working on vu+ vuplus Solo 4k Without stream relay.

    Yes, I use:

  • PowerVU working on vu+ vuplus Solo 4k Without stream relay.

    oscam-emu ignores the groupid when searching for keys. It will try all keys which match the SID. The goupid allows for two things, first to separate keys for channels with the same SID and second to know which keys should be updated when a new key is found. (As opposed to only being able to update the key for the current channel.)


    Note: when reading keys from the file, if a line with an already used groupd+sid is found, it will replace the previous key - so each groupid+sid must be unique.

  • sti7111 based unknown clone

    What is installed on it now?


    It is hard to tell without more info about the uboot.


    Possibly you could re-partiton the mtd, but it seems there is only 128MB, which would be limiting.


    From my spark7162:

    Code
    SPARK7162:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00100000 00020000 "uboot"
mtd1: 00a00000 00020000 "Spark kernel"
mtd2: 00700000 00020000 "Reserve0"
mtd3: 00200000 00020000 "Reserve1"
mtd4: 16c00000 00020000 "Spark Userfs"
mtd5: 00800000 00020000 "E2 kernel"
mtd6: 07700000 00020000 "E2 Userfs"


    Possibly you could boot from USB or NFS, but again depends on uboot.

  • PowerVU working on vu+ vuplus Solo 4k Without stream relay.

    Quote from linuxyoung

    Sorry, but I'm asking this again:


    If the two channels on different TP have the same SID, only one of them opens. Is this a solution?

    Look here for proper key file format:

    OSCam 1.20 rev 11209 emu with auto update for multiple PowerVu channels

    (read about groupid)


    Also, after editing the SoftCam.Key file, you do not need to restart all of oscam, it is enough to use the webif to restart the emu reader.


    EDIT: sorry, not restart emu reader, you can use the "refresh" button to "Refresh Entitlement" under "actions"...

  • Tvheadend with extended_cw functionality (powervu)

    The official Tvheadend added code for powervu to the release version a few months ago. Newer builds should contain the code.


    I did a few ARM builds awhile ago, but I used someone else's complete build environment and only replaced the links for downloading the official Tvheadend code with links for my code.


    So, if you know of some build environments for your box, first I would check if they are using the latest Tvheadend.


    Tvheadend's latest stable release is 4.2 and unstable builds are 4.3. But beware because some builds reported they were using version 4.2, but were actually using 4.1. Best way to verify is via the Tvheadend webif (About).