53 replies to this topic

[javier3034]

Is mi first post and I send at all members hello and thank your for this forum, for mi the open Pli images are the best,
Have a Vu+-Duo and two usb-dtt, works perfect, thank your.

I need your help for a box Gigablue HD-800 Solo, it is not a clone, is a legal box.

The Red Team develop e2 for this box and he images is based on nemesis code, he is a good persons but is impossible collaborate whit they, don't send mi nothing and don't ask a different questions, like recovery if bat flash, support of usb-dtt...

Is for this if is possible whit your help, try a compile a image open Pli for this box.

This box is same at VU+ Solo, micro Broadcom 7325, single tuner dvbs2 bcm-7325.

Don't have a extern rs232, in a motherboard have a rs232 but don't say a pins to connect for console and what is the correct connexion.

For install the image E2 of Red Team, need two steps:

1- In a root of usb-pen in fat32 two files, one "burn.bat" and other "cfe.dmt"
the burn.bat is for install only the first and one time the file cfe.dmt (293Kb), the burn.bat:

flash -noheader usbdisk0:cfe.dmt flash0.cfe

Turn on the box whit the usb-pen in a usb connector of the box, in 5-7 seconds is finish, turn off the box and extract the usb-pen,

2- In the same or another usb-pen, delete the first two files I describe and copy another two files "burn.bat" and "ker_e2.img",
inside of this .img file have one only "vmlinux" file of 127Mb. The time for install this is 20-30 minutes, the burn.bat for this is:

flash -noheader usbdisk0:ker_e2.img flash1.user
setenv -p STARTUP "boot -z -elf flash0.kernel: 'rootfstype=jffs2 root=/dev/mtdblock6 rw mem=150m '"

Turn on the box whit this two files in a root of usb-pen connected in a box, it finish when in display say "done", the box start and configure the wizard like all e2 images.

The step 1 is only one or first time, when have a new image only repeat the 2 step (20-30 minutes).

Like I say, this box don't have a extern rs232, but if your look, the command in a .bat files is the same for a pc console connected at rs232 box.

I take a pli image of VU-solo, rename the image .nfi a "ker_e2.img", copy the .bat file and the pli image renamed in usb-pen and the box erase a flash and copy the pli image, because in the display look the same like a e2 red team image, but when say in display "done" the box don't start, he stay in "boot" on display,

Is possible that the problem for not start is in the .bat file the line "setenv...... "root=/dev/mtdblock6...?, It's possible whit another number of mtdblock he start?

For not crash the flash, your know whats I test start the box whit VU-solo pli image in a usb-pen, modifying the line in the file .bat, without the first line "flash......", and in the second line for example: "boot -z -elf usbdisck0:kernel-of-vu-solo: 'rootfstype=jffs2 root=usbdisck0/.....???"

I say "usbdisck0", because when the box start, first of all active the usb connector and the box recognize this usb connector like "usbdisc0",

The box have a net connector rj45, but first active the usb connector.

Sorry for this extended post, is for explain whats I think work this box and if is possible whit your help start the box whit vu-solo pli image, first in a usb-pen and if he work good try at install the image in flash.

Thank your in advance for your help

Best regards

[javier3034]

Hello friends,

Don't have a developer or another person help my whit this, plis?

Have a person for compile my only a kernel of VU-solo of a openPli image plis? or whats I compile the VU-solo pli image whit usb-dtt drivers?

If I compile all pli Vu-solo image, in the compilation have a only kernel for test that I say in the first post, or I need compile only a kernel?

If I need a especial compilation for only a kernel, whats execute this?

Thank your, help my plis,

Regards

[dAF2000]

Welcome on this forum.

I'm not an E2 developer, so I can't give you an answer. What I can tell: we never tested our image on a Gigablue HD-800 Solo which may make it difficult for us to give a solution. I can image there's always a bit of "trail and error" involved

If one of our developers has a solution, they will let you know in this thread. For now, I can't do much more.

[javier3034]

Ok Dear dAF2000,

Thank Your for your answer,

I hope that some developer can help me.

To try if I boot the pli Vu-solo in this box, first only need a kernel of the Pli image.

I wait

Thank Your and regards

Edited by javier3034, 12 October 2011 - 19:26.

[pieterg]

did you setup an openembedded build environment?
As you probably know, openpli is 100% opensource, so you can build your own image (or kernel to start with), and modify it to your needs

[javier3034]

Thank your dear pieterg,

I read in a old post that openpli don't support Vu-solo,

In this moment, is the same situation?

In a Makefile of openpli not have a possibility for select VU-solo for compile, but in download nightly images have the openpli images for VU-solo, whats I compile this images?

Is other makefile or in makefile 2.1 select vusolo?

Thank your

Edited by javier3034, 13 October 2011 - 11:56.

[pieterg]

you can change the MACHINE in the makefile, to any of the machines found in conf/machine/*.conf

[javier3034]

Ok dear pieterg.

I compile a openpli image for VU-solo, uufffff, many links for sources don't work, but in your help posts I read a solutions and finali compile a complete image,

Whats compiling only a kernel?

Is for try a start the Pli image in the usb-pen in a Gigablue 800 hd, like I say in the first post.

Whit your help in this steps, I try if is possible star a OpenPli Vu-solo image in this box,

Thank Your very much

Regards

[pieterg]

to (re-)compile only the kernel:

bitbake -f -c compile virtual/kernel

and you'll find the kernel image in tmp/work/<machine>/linux-xyz/<srcdir>/vmlinux

[javier3034]

Ok pieterg, I try this,

Thanks for your kelp

Regards

[javier3034]

Hello dear pieterg I have a litle time for try if is possible start this box (gigablue HD-800) whit a openPli image of VU-solo, (have the same procesor bcm-7325),

Like your say my, I compile a Vu-solo openPli image in a pc, and compile only the kernel,

I read tutos very olds for boot the box of linux PC, for try if boot this box whit the VU-solo image, withou install in flash for not crash the box.

when start the box connected whit rs232, I pres Ctrl+c may times and don't stop the boot,

all at first start is the same at firs start of the box VU-solo:

BCM73250010
012
K1
K2

K3

K4

K5

Shmoo Version=3.7
DDR Freq=0x0000014D
%00000001%
RC1=00000002
WC1=FFFFFFE8
RC2=00000018
WC2=0000003B
RC3=0000000D
WC3=FFFFFFE9
RC4=0000000D
WC4=0000003B
NWC=00000012
RC5=00000003
WC5=00000012
RC6=00000018
WC6=00000012
NRC=0000000D
RW=00000016
WW=00000053
G=00000000 R=0000000D W=00000012
BL=00000000
RC1=00000002
RC2=0000001F

BL=00000001
RC1=00000002
RC2=0000001A

BL=00000002
RC1=00000000
RC2=00000019

BL=00000003
RC1=00000000
RC2=00000018
ESoooooooooooooR3
COPY CODE
COMPARE CODE
4567
CP16=80040483,BEA3519F,80000167


BCM97325B0 CFE v2.28, CFE core v2.9, Endian Mode: Little
Build Date: Wed Mar 16 18:15:08 2011 (JJS@JJS-LAPTOP)
Copyright © Broadcom Corporation.


fprobe.flash_phys = 1200000f
DDR Freq: 333MHz
CPU speed: 333MHz
Memory Config: 32-bit UMA
Device Tech: 1Gb
Total memory: 256MB
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

As I don't know how to stop the boot of box in the console, I can not configure the boot of the box to boot via tftp and ethernet.

What I do is copy the kernel from the VU at the root of the pen and the file that understands the boot of the box , and in this file (burn.bat), I wite the root of the kernel (usbdisk0:vmlinux) and the root of the PC in I have the all folders and files of openPli image, like this:

file "burn.bat":

setenv -p STARTUP "boot usbdisk0:vmlinux root=192.168.1.3:/dreamboxfs rw ip=dhcp"

Start the box and say this:

BCM73250010
012
K1
K2

K3

K4

K5

Shmoo Version=3.7
DDR Freq=0x0000014D
%00000001%
RC1=00000002
WC1=FFFFFFED
RC2=00000018
WC2=00000032
RC3=0000000D
WC3=FFFFFFEC
RC4=0000000D
WC4=0000003B
NWC=00000013
RC5=00000003
WC5=00000013
RC6=00000017
WC6=00000013
NRC=0000000D
RW=00000015
WW=00000050
G=00000000 R=0000000D W=00000013
BL=00000000
RC1=00000003
RC2=0000001B

BL=00000001
RC1=00000002
RC2=00000019

BL=00000002
RC1=00000000
RC2=00000019

BL=00000003
RC1=00000000
RC2=00000018
ESoooooooooooooR3
COPY CODE
COMPARE CODE
4567
CP16=80040483,BEA3519F,80000167


BCM97325B0 CFE v2.28, CFE core v2.9, Endian Mode: Little
Build Date: Wed Mar 16 18:15:08 2011 (JJS@JJS-LAPTOP)
Copyright © Broadcom Corporation.


fprobe.flash_phys = 1200000f
DDR Freq: 333MHz
CPU speed: 333MHz
Memory Config: 32-bit UMA
Device Tech: 1Gb
Total memory: 256MB
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.
USB: New device connected to bus 0 hub 1 port 1
USB: Resetting device on bus 0 port 1
USB: Locating Class 08 Vendor 0C76 Product 0005: Mass-Storage Device
USBMASS: Unit 0 connected
FAT| PART:1, START:1, SYSTEM: FAT32 "NO NAME "
BA[0]:setenv -p STARTUP "boot usbdisk0:vmlinux root=192.168.1.3:/dreamboxfs rw ip=dhcp"
ERASE AMD PGM: ADDR[ 17CA0000 ], IDX[ 2 ], PROGRESS[ 0 ]
FLASH AMD PGM: ADDR[ 17CA0000 ], IDX[ 3 ], PROGRESS[ 0 ]

Loader:raw Filesys:fat Dev:usbdisk0 File:vmlinux Options:root=192.168.1.3:/dreamboxfs
Loading: ........... 262144 bytes read
Entry address is 0x80010000
Starting program at 0x80010000

**Exception 32: EPC=80010000, Cause=1000002C, VAddr=9731D0C0
RA=8900907C, PRID=0101954C

0 ($00) = 00000000 AT ($01) = A0000000
v0 ($02) = 00020000 v1 ($03) = 00000080
a0 ($04) = 89051020 a1 ($05) = 00000000
a2 ($06) = 890090F0 a3 ($07) = 43464531
t0 ($08) = 80010000 t1 ($09) = 00020000
t2 ($10) = FFFFFF80 t3 ($11) = 89091CD8
t4 ($12) = 00000001 t5 ($13) = 0000000D
t6 ($14) = 89009458 t7 ($15) = 80000167
s0 ($16) = 8900907C s1 ($17) = 890697C0
s2 ($18) = 00000000 s3 ($19) = 890697C0
s4 ($20) = 8916B598 s5 ($21) = 89091728
s6 ($22) = 8916B540 s7 ($23) = 8901343C
t8 ($24) = B7698628 t9 ($25) = 45C43483
k0 ($26) = 0D4A5B1B k1 ($27) = 00000000
gp ($28) = 89051020 sp ($29) = 8916B3F8
fp ($30) = 89030184 ra ($31) = 8900907C


*** Waiting for system reset ***

and stop of boot the box.

I don't know if this is correct for try to start this box.

I have a VU-duo, but not an VU-solo, I know the start of VU-solo and this box is the same because I read the start of Vu-solo in Internet.

When start the box, only understand a pen in fat32 not in ext3 or another linux format, in case at start the boot box understanding the linux format I try to copy all file system and kernel in the pen and try if he boot of the pen, modifying the file "burn.bat", but is not possible for that I say.

If it helps to understand, when install a image e2 of the red-team (is the only e2 image for this box), I copy in a root of pen in fat32 the image (ker_e2.img) aprx. 128Mb and the file I say "burn.bat", and in to the file this is:

flash -noheader usbdisk0:ker_e2.img flash1.user
setenv -p STARTUP "boot -z -elf flash0.kernel: 'rootfstype=jffs2 bmem=106M@150M root=/dev/mtdblock6 rw '"

When copy the image (20 Min aprox.), automatic start de image and box,

loock the second line in the burn.bat file, setenv -p ........, this line is for start the box.

This is the bloks in the flash:

[javier3034]

This is the block of flash:

[ 0.267000] GigaBox NOR flash device: 0x08000000 @ 0x17c00000
[ 0.273000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00227e
[ 0.284000] Amd/Fujitsu Extended Query Table at 0x0040
[ 0.289000] Amd/Fujitsu Extended Query version 1.3.
[ 0.294000] number of CFI chips: 1
[ 0.297000] Creating 10 MTD partitions on "physmap-flash.0":
[ 0.303000] 0x000000000000-0x000000080000 : "cfe"
[ 0.311000] 0x000000080000-0x0000000a0000 : "macadr"
[ 0.319000] 0x0000000a0000-0x0000000c0000 : "nvram"
[ 0.326000] 0x0000000c0000-0x000000100000 : "reserved"
[ 0.334000] 0x000000100000-0x000000400000 : "data"
[ 0.342000] 0x000000400000-0x000000800000 : "kernel"
[ 0.350000] 0x000000800000-0x000008000000 : "rootfs"
[ 0.358000] 0x000000000000-0x000000400000 : "system"
[ 0.366000] 0x000000400000-0x000008000000 : "user"
[ 0.374000] 0x000000000000-0x000008000000 : "all"
[ 0.382000] bcmemac: Broadcom STB 10/100 EMAC driver v3.0
[ 0.391000] bcmemac: registered interface #0 at 0x10080000 as 'eth0' (ac:db:

This is a good start of box whit a red-team image, only the first lines (if your need all complet start y atach the archive:

BCM73250010
012
K1
K2
K3
K4
K5
Shmoo Version=3.7
DDR Freq=0x0000014D
%00000001%
RC1=00000003
WC1=FFFFFFE8
RC2=00000017
WC2=0000003B
RC3=0000000D
WC3=FFFFFFEA
RC4=0000000D
WC4=0000003B
NWC=00000012
RC5=00000003
WC5=00000012
RC6=00000017
WC6=00000012
NRC=0000000D
RW=00000015
WW=00000052
G=00000000 R=0000000D W=00000012
BL=00000000
RC1=00000003
RC2=0000001B
BL=00000001
RC1=00000002
RC2=00000019
BL=00000002
RC1=00000000
RC2=00000019
BL=00000003
RC1=00000000
RC2=00000017
ESoooooooooooooooooR3
COPY CODE
COMPARE CODE
4567
CP16=80040483,BEA3519F,80000167

BCM97325B0 CFE v2.28, CFE core v2.9, Endian Mode: Little
Build Date: Wed Mar 16 18:15:08 2011 (JJS@JJS-LAPTOP)
Copyright © Broadcom Corporation.

fprobe.flash_phys = 1200000f
DDR Freq: 333MHz
CPU speed: 333MHz
Memory Config: 32-bit UMA
Device Tech: 1Gb
Total memory: 256MB
Total flash: 128MB
Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
CFE initialized.
USB: Device disconnected from bus 0 hub 1 port 1

USB: New device connected to bus 0 hub 1 port 1

USB: Resetting device on bus 0 port 1
USB: Locating Class FF Vendor 07CA Product 850A: Not found.
Executing STARTUP...
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 bmem=106M@150M root=/dev/mtdblock6 rw
Loading: 0x80001000/4232704 0x8040a600/124736 Entry address is 0x80005170
Starting program at 0x80005170
[ 0.000000] Linux version 2.6.36 (kajgan@teamRed) (gcc version 4.4.3 (GCC) ) #48 Wed Oct 19 21:26:02 UTC 2011
[ 0.000000] Fetching vars from bootloader... found 5 vars.
[ 0.000000] Early serial console at MMIO32 0x10400b00 (options '115200n8')
[ 0.000000] bootconsole [uart0] enabled
[ 0.000000] Options: sata=0 enet=1 emac_1=0 no_mdio=0 docsis=0 pci=1 smp=0 moca=0 usb=1
[ 0.000000] Using 256 MB RAM (from straps)
[ 0.000000] Linux version 2.6.36 (kajgan@teamRed) (gcc version 4.4.3 (GCC) ) #48 Wed Oct 19 21:26:02 UTC 2011
[ 0.000000] Fetching vars from bootloader... found 5 vars.
[ 0.000000] Early serial console at MMIO32 0x10400b00 (options '115200n8')
[ 0.000000] bootconsole [uart0] enabled
[ 0.000000] Options: sata=0 enet=1 emac_1=0 no_mdio=0 docsis=0 pci=1 smp=0 moca=0 usb=1
[ 0.000000] Using 256 MB RAM (from straps)
[ 0.000000] bootconsole [early0] enabled
[ 0.000000] CPU revision is: 0101954c (Brcm4380)
[ 0.000000] FPU revision is: 01739300
[ 0.000000] Determined physical RAM map:
[ 0.000000] memory: 10000000 @ 00000000 (usable)
[ 0.000000] bmem: adding 106 MB RESERVED region at 150 MB (0x06a00000@0x09600000)
[ 0.000000] Initrd not found or empty - disabling initrd
[ 0.000000] Zone PFN ranges:
[ 0.000000] Normal 0x00000000 -> 0x00010000
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[1] active PFN ranges
[ 0.000000] 0: 0x00000000 -> 0x00010000
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: rootfstype=jffs2 bmem=106M@150M root=/dev/mtdblock6 rw
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Primary instruction cache 32kB, VIPT, 4-way, linesize 32 bytes.
[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[ 0.000000] MIPS secondary cache 128kB, 8-way, linesize 128 bytes.
[ 0.000000] Writing ErrCtl register=00800001
[ 0.000000] Readback ErrCtl register=00800001
[ 0.000000] L2 cache parity protection enabled
[ 0.000000] Memory: 147088k/262144k available (3132k kernel code, 115056k reserved, 808k data, 192k init, 0k highmem)
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU-based detection of stalled CPUs is disabled.
[ 0.000000] Verbose stalled-CPUs detection is disabled.
[ 0.000000] NR_IRQS:128
[ 0.000000] Detected MIPS clock frequency: 332 MHz (166.499 MHz counter)
[ 0.000000] Calibrating delay loop... 221.18 BogoMIPS (lpj=110592)
[ 0.021000] pid_max: default: 32768 minimum: 301
[ 0.022000] Mount-cache hash table entries: 512
[ 0.024000] devtmpfs: initialized
[ 0.027000] NET: Registered protocol family 16
[ 0.031000] PCI2.3->SDRAM window: 512 MB
[ 0.032000] bcm-gpio: registered 64 GPIOs
[ 0.054000] bio: create slab <bio-0> at 0
[ 0.056000] vgaarb: loaded
[ 0.058000] SCSI subsystem initialized
[ 0.059000] usbcore: registered new interface driver usbfs
[ 0.060000] usbcore: registered new interface driver hub
[ 0.061000] usbcore: registered new device driver usb
[ 0.063000] Advanced Linux Sound Architecture Driver Version 1.0.23.
[ 0.065000] Switching to clocksource upg
[ 0.071000] NET: Registered protocol family 2
[ 0.076000] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.084000] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.092000] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.099000] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.105000] TCP reno registered
[ 0.108000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.114000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.121000] NET: Registered protocol family 1
[ 0.126000] RPC: Registered udp transport module.
[ 0.131000] RPC: Registered tcp transport module.
[ 0.136000] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.146000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.153000] JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
[ 0.160000] msgmni has been set to 287
[ 0.164000] io scheduler noop registered
[ 0.169000] io scheduler cfq registered (default)
[ 0.174000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 0.204000] serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
[ 0.211000] console [ttyS0] enabled, bootconsole disabled
[ 0.211000] console [ttyS0] enabled, bootconsole disabled
[ 0.244000] serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
[ 0.261000] loop: module loaded
[ 0.267000] GigaBox NOR flash device: 0x08000000 @ 0x17c00000
[ 0.273000] physmap-flash.0: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000089 Chip ID 0x00227e
[ 0.283000] Amd/Fujitsu Extended Query Table at 0x0040
[ 0.289000] Amd/Fujitsu Extended Query version 1.3.
[ 0.294000] number of CFI chips: 1
[ 0.297000] Creating 10 MTD partitions on "physmap-flash.0":
[ 0.303000] 0x000000000000-0x000000080000 : "cfe"
[ 0.310000] 0x000000080000-0x0000000a0000 : "macadr"
[ 0.318000] 0x0000000a0000-0x0000000c0000 : "nvram"
[ 0.326000] 0x0000000c0000-0x000000100000 : "reserved"
[ 0.334000] 0x000000100000-0x000000400000 : "data"
[ 0.342000] 0x000000400000-0x000000800000 : "kernel"
[ 0.350000] 0x000000800000-0x000008000000 : "rootfs"
[ 0.358000] 0x000000000000-0x000000400000 : "system"
[ 0.366000] 0x000000400000-0x000008000000 : "user"
[ 0.374000] 0x000000000000-0x000008000000 : "all"
[ 0.382000] bcmemac: Broadcom STB 10/100 EMAC driver v3.0

Sorrry for this very long post,

The team red image is good, but don't work good the usb-dtt,s, in spanish and in italy we need work good the usb-dtt drivers, and other bugs, is for this that I try if is posible whit your help, start and boot this box whit the openpli image (VU-solo).

You see something to I test with the data I posted, you need something more?

Thank your very much

[pieterg]

if their kernel boots and ours doesn't if you just replace the kernel image, I guess you have to compare their kernelsources+config with ours. There must be a difference there.

[javier3034]

the problem is that I don`t have their kernel and kernel-sources,

they do not deliver anything, do not explain how to connect the box to the PC via RS232,
rs232 is not extern, is on the motherboard and do not want to explain to anyone where he was on the motherboard rs232,I had to find myself doing many tests and connections on the motherboard

With the problem of drivers for usb-dtt not answer anything,
the drivers for usb-dtt are sifteam and their image is based in nemesis,

the problem in their image, I think is, they use linux ver. 2.6.36 and have rewrite more code and, etc..
It's also impossible to deliver the makefile, which could be compiled and / or get some kind of information

Is possible to get the kernel from flash or their image?

Thanks for answering dear pieterg, if you or another developer know anything else, I can try this.

I try boot the box with their kernel installed in the flash and try to load the openpli operating system from pc, but I don`t think like this if the box boot, I post this test.

I should know to change or modify the kernel of openpli to boot openpli image of VU-duo in this box.

Regards

[javier3034]

Hello,

In which kernel file (source) are configured the blocks for boot and install flash?

I think this is the problem of boot image openpli

Look at the block of the flash when booting good with the kernel of their:

Executing STARTUP...
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 bmem=106M@150M root=/dev/mtdblock6 rw
Loading: 0x80001000/4232704 0x8040a600/124736 Entry address is 0x80005170
Starting program at 0x80005170
[ 0.000000] Linux version 2.6.36 (kajgan@teamRed) (gcc version 4.4.3 (GCC) ) #48 Wed Oct 19 21:26:02 UTC 2011

And now look at the block want to boot the kernel image openpli when fails and will not start:

Loading: ........... 262144 bytes read
Entry address is 0x80010000
Starting program at 0x80010000

**Exception 32: EPC=80010000, Cause=1000002C, VAddr=9731D0C0
RA=8900907C, PRID=0101954C

I read in internet about this error but for others devices (linux routers), and say that this problem is solved changing in a file of kernel the configuration of start a blocks in the flash,

Your know which file is?

Thank your for your help

[pieterg]

you're not up to that point yet, the kernel doesn't need the mtd partition table untill it tries to mount the rootfs.
And since you seem to be trying to mount an nfs rootfs, the kernel doesn't need to know about the flash at all.

[kajgan]

@pieterg u are right i have compiled kernel for gigablue, i think he ist sure what he is doing. @javier3034 try to load with tftp and dont forget gigablue is simulare to vusolo but not indentical, and keep in mind what kernel is.

[DrData]

IMPORTANT:

There exist an offer that the PLi Team get two Gigablue Boxes to develop a PLi Image for it.

Here is the Link:

http://www.gigablue-...D=6907#post6907


I think it a good idea. I bought a Gigablue 800 solo last week for 155 Euro. It´s a good box for this price. Nice to use it as client-box.
Similar to VU+ Solo.

In german:

Es besteht ein Angebot das das PLi Team zwei Gigablue Boxen bekommen könnte um ein PLi Image
dafür zu entwickeln.
Ich habe mir letzte Woche selbe eine Gigablue 800 solo für 155 Euro gekauft. Für den Preis eine gute Client- bzw. Zweitbox.
Ähnlich der VU+ solo.


Greets
DrData

[MiLo]

It doesn't work that way... We expect the manufacturer (or distributor, or even a bunch of hobbyists) to provide the kernel configuration and patches and drivers, so we can integrate it into the build environment. Just dumping another box on the doormat and ringing the doorbell isn't enough...

It works like that for VU, CT and even DMM. "They" do the legwork of making the system capable of running enigma2. We can help, and will (as you can read), but we do expect some commitment from the supplier.

[DrData]

@Milo

Thanks for your Statement. I 100% agree with that what you say.
My target was to build a little bridge.
The need of kernel config, patches and drivers are absolutely essential.
I wrote a Mail to impex-sat , who is the owner of gigablue.de domain.
Now it is their part to contact the PLi Team, I think.
Lets wait and see.