15 replies to this topic

[kleinerjunge]

Hi!

I have an et5000 here with new bootloader from 19.07.2011 and OpenPLI 2.1 running on it.

If I flash a new OpenPLI, the box boots normally for 1st time. I use the wizard to make some settings.

NOW THE PROBLEM:
If I want to reboot the receiver (not restaert enigma2, but full reboot), the box freezes at Xtrend Logo and doesn't boot anymore. If I turn off/on power switch, same problem, the box doesnt boot up. I have to reflash the box and it reboots, but again only for 1st time! I tried many PLI images and reflashed several times the bootloader, no chance. I also tried many other USB sticks!

BUT, if I flash other images, for example VIX or Egami, the Box reboots always if I make a restart!

I also have an older fullbackup of mine from early august, which I made from PLI 2.1 from those days. This image also reboots always. Only new images from PLI dont work at 2nd boot!

What could my problem be??

cu
KJ

[Sjaaky]

Could you post a serial log? That's probably the only way to find out what's wrong.

[kleinerjunge]

Yes, if you can tell me how to do this?

cu
KJ

[Sjaaky]

I couldn't find info on how to modify the kernelargs other then compile a new kernel. I hope others know.

[kleinerjunge]

Update:
The Fullbackup that I have made in the beginning of august also is based on OpenPLI 2.0, and not on 2.1 (as I thought before).

Therefore, it is obviuos that problems occur exclusively with OpenPLI 2.1 images!!

Is it possible to flash old bootloader and reflash all from the beginning with new bootloader and an OpenPLI 2.1 image?

cu
KJ

[MiLo]

Did you by any chance leave a USB stick or so plugged in? Remove 'm all, the bootloader sometimes hangs on them.

[kleinerjunge]

No, all sticks were removed!

Any other idea?

cu
KJ

[heli]

This is a very common problem for users with ET9000 as well (myself included).

The symptoms are: flashing OpenPli 2.1 based images works (including restart E2) until the machine is put in DeepStandby. After this the machine freezes with "Booting..." in the FP display, and with the OpenPli Bootlogo on the TV screen.

Reflashing either an OpenPli 2.0 image or backup based on OpenPli 2.0 then works consistently without problems.

Oddly enough there are also many users of ET9000 that report having absolutely no such problems with OpenPli 2.1.
There are also users that have had no problems with OpenPli 2.1 and then suddenly have this "Booting..." problem, for example after reflashing a 2.1-based backup.

There have been fixes suggested on the Clarke Tech site, most of which involve turning off the receiver immediately after flashing the bootloader, or at the start of the Setup Assistant of OpenPli 2.1 - with varying degrees of lasting success as far as I can tell.

ET-view had released a new bootloader on 19 July 2011. This bootloader supports both JFFS and UBIFS, and there is speculation that the problem is at the level of this bootloader, although this would not explain why some machines have no problem with OpenPli 2.1 while others do.
There is also speculation that there is a problem at the hardware level, that could explain why some machines have problems with OpenPli 2.1 while others do not.

In any case, it would be interesting to hear some comments from the OpenPli team regarding this problem, it's been over a month now and there has of yet been no official comment from Clarke Tech about this matter.

I myself am at the point of returning the receiver under warranty because I am unable to flash the latest "official Clarke Tech V2 Image" - that is based on OpenPli 2.1

Thanks very much in advance.

[kleinerjunge]

Hi!

Yesterday I was able to flash again my et5000 with actual OpenPLI 2.1! I dont know why it worked, but it did. I think the trick was that the box was in DeepStandBy for approx. 24h! I prepared the stick with fresh image from OpenPLI site, put it in front usb-socket and turned on the receiver (yes, i didnt boot the box once after those 24h!)

Today I made a backup of my new image flashed yesterday. And I reflashed to see if rebooting problem again exists, and yes, there it was again.

If I flash again a fresh PLI image, the reboot doesn't work again.

I will put the receiver again in DeepStandBy and reflash the box tomorrow.

A user called erdi1 has the same problem now on his et5000 on et-view.de. He made a SERIAL LOG with putty. Here is the output (i asked him to post it here):

-------
BCM74130011
012
K1
K2

K3

K4

K5

Shmoo Version=3.8
DDR Freq=0x0000018C
%00000001%
RC1=00000006
WC1=FFFFFFEE
RC2=00000019
WC2=00000024
RC3=0000000F
WC3=FFFFFFEE
RC4=0000000F
WC4=00000037
NWC=00000012
RC5=00000006
WC5=00000012
RC6=00000019
WC6=00000012
NRC=0000000F
RW=00000014
WW=0000004A
G=00000000 R=0000000F W=00000012
BL=00000000
RC1=00000004
RC2=00000018

BL=00000001
RC1=00000008
RC2=0000001B

BL=00000002
RC1=00000006
RC2=00000015

BL=00000003
RC1=00000009
RC2=00000015

BL=00000004
RC1=00000005
RC2=00000017

BL=00000005
RC1=00000006
RC2=00000019

BL=00000006
RC1=00000003
RC2=0000001A

BL=00000007
RC1=00000006
RC2=0000001F
SCfC3
COPY CODE
COMPARE CODE
4567

BCM97413B1 CFE v2.26, CFE core v2.12, Endian Mode: Little
Build Date: Mon Jul 18 21:07:33 WEDT 2011 (Administrator@buildserver)
Copyright © Broadcom Corporation.

start cfe init device
sec-0 nblks=8 blksiz=8192
sec-1 nblks=63 blksiz=65536
Enabling NAND flash at CS1, NOR flash at CS0
NAND Flash size = 128MB
CPU speed: 405MHz
Memory Config: 64-bit UMA
Device Tech: 512Mb
Total memory: 256MB
Boot Device: NOR
Total flash: 4MB

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

CFE initialized.
Set default GPIO...
USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 09 Vendor 1A40 Product 0101: USB Hub
USB: New device connected to bus 1 hub 2 port 2
USB: Resetting device on bus 1 port 2
USB: Locating Class 02 Vendor DEAD Product BEEF: Ethernet Device
USB: [Transfer error: 4]
USB CDC Device (00:00:00:00:00:00)
Starting splash screen.
***************************************************
Found splash image - Width = 720 Height = 576
bmp ptr : 0x8fa00000 , surface ptr : 0xafc00000
***************************************************

Loader:elf Filesys:raw Dev:nandflash0.kernel File: Optionshttp://www.et-view.de/wcf/images/smilies/sad.png" alt="" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial;null)
Loading: !!!!! UNC read error occurred, while reading from NAND flash -1
0x80001000/6497856 !!!!! UNC read error occurred, while reading from NAND flash
-1
0x80633640/142432 Entry address is 0x80005470
TP1 Entry Address at 0x80000ffc = 80005470
Starting program at 0x80005470

**Exception 32: EPC=8061CAC4, Cause=A000802C, VAddr=00000000
RA=8000548C, PRID=0002A044

0 ($00) = 00000000 AT ($01) = 80630000
v0 ($02) = 00010000 v1 ($03) = 00000040
a0 ($04) = 87055000 a1 ($05) = 00000000
a2 ($06) = 8700C32C a3 ($07) = 43464531
t0 ($0http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 80005470 t1 ($09) = 8000FFC0
t2 ($10) = FFFFFFC0 t3 ($11) = 870972B4
t4 ($12) = 00000001 t5 ($13) = 8709FA4C
t6 ($14) = 00000001 t7 ($15) = 3EA95587
s0 ($16) = 8700C2B8 s1 ($17) = 87010000
s2 ($1http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 00000000 s3 ($19) = 8704D620
s4 ($20) = 8714F588 s5 ($21) = 870976C8
s6 ($22) = 8714F530 s7 ($23) = 870167BC
t8 ($24) = 000009F3 t9 ($25) = 8709730C
k0 ($26) = 87099728 k1 ($27) = 00000000
gp ($2http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 87055000 sp ($29) = 8714F3E8
fp ($30) = 87031F08 ra ($31) = 8000548C
-------

Soemone knows what is happening?

cu
KJ

[kleinerjunge]

I think i have a solution for this problem (tested on et5000):

1. Flash Egami 1.1 image on et5000 (not 1.0 or 1.2).
2. After booting, go in DeepStandBy.
3. Switch off receiver on back.
4. Prepare usb-stick with PLI2.1 based image (can also be a fullbackup).
5. Put stick in front usb-slot.
6. switch receiver on from back
7. start flashing.
8. When you see that box is rebooting, pull usb-stick out of slot.
9. Box reboots. Reboot from menu when box is up and running.
10. If box reboots without problems, you can flash directly any PLI2.1 based image without the need to flash egami 1.1 again.

Hope it helps.

cu
KJ

PS: A network cable was always plugged off! Dont know if that is really needed...

[heli]

This is a very common problem for users with ET9000 as well (myself included).

The symptoms are: flashing OpenPli 2.1 based images works (including restart E2) until the machine is put in DeepStandby. After this the machine freezes with "Booting..." in the FP display, and with the OpenPli Bootlogo on the TV screen.

Reflashing either an OpenPli 2.0 image or backup based on OpenPli 2.0 then works consistently without problems.

Oddly enough there are also many users of ET9000 that report having absolutely no such problems with OpenPli 2.1.
There are also users that have had no problems with OpenPli 2.1 and then suddenly have this "Booting..." problem, for example after reflashing a 2.1-based backup.

There have been fixes suggested on the Clarke Tech site, most of which involve turning off the receiver immediately after flashing the bootloader, or at the start of the Setup Assistant of OpenPli 2.1 - with varying degrees of lasting success as far as I can tell.

ET-view had released a new bootloader on 19 July 2011. This bootloader supports both JFFS and UBIFS, and there is speculation that the problem is at the level of this bootloader, although this would not explain why some machines have no problem with OpenPli 2.1 while others do.
There is also speculation that there is a problem at the hardware level, that could explain why some machines have problems with OpenPli 2.1 while others do not.

In any case, it would be interesting to hear some comments from the OpenPli team regarding this problem, it's been over a month now and there has of yet been no official comment from Clarke Tech about this matter.

I myself am at the point of returning the receiver under warranty because I am unable to flash the latest "official Clarke Tech V2 Image" - that is based on OpenPli 2.1

Thanks very much in advance.

[kleinerjunge]

Hi!

Yesterday I was able to flash again my et5000 with actual OpenPLI 2.1! I dont know why it worked, but it did. I think the trick was that the box was in DeepStandBy for approx. 24h! I prepared the stick with fresh image from OpenPLI site, put it in front usb-socket and turned on the receiver (yes, i didnt boot the box once after those 24h!)

Today I made a backup of my new image flashed yesterday. And I reflashed to see if rebooting problem again exists, and yes, there it was again.

If I flash again a fresh PLI image, the reboot doesn't work again.

I will put the receiver again in DeepStandBy and reflash the box tomorrow.

A user called erdi1 has the same problem now on his et5000 on et-view.de. He made a SERIAL LOG with putty. Here is the output (i asked him to post it here):

-------
BCM74130011
012
K1
K2

K3

K4

K5

Shmoo Version=3.8
DDR Freq=0x0000018C
%00000001%
RC1=00000006
WC1=FFFFFFEE
RC2=00000019
WC2=00000024
RC3=0000000F
WC3=FFFFFFEE
RC4=0000000F
WC4=00000037
NWC=00000012
RC5=00000006
WC5=00000012
RC6=00000019
WC6=00000012
NRC=0000000F
RW=00000014
WW=0000004A
G=00000000 R=0000000F W=00000012
BL=00000000
RC1=00000004
RC2=00000018

BL=00000001
RC1=00000008
RC2=0000001B

BL=00000002
RC1=00000006
RC2=00000015

BL=00000003
RC1=00000009
RC2=00000015

BL=00000004
RC1=00000005
RC2=00000017

BL=00000005
RC1=00000006
RC2=00000019

BL=00000006
RC1=00000003
RC2=0000001A

BL=00000007
RC1=00000006
RC2=0000001F
SCfC3
COPY CODE
COMPARE CODE
4567

BCM97413B1 CFE v2.26, CFE core v2.12, Endian Mode: Little
Build Date: Mon Jul 18 21:07:33 WEDT 2011 (Administrator@buildserver)
Copyright © Broadcom Corporation.

start cfe init device
sec-0 nblks=8 blksiz=8192
sec-1 nblks=63 blksiz=65536
Enabling NAND flash at CS1, NOR flash at CS0
NAND Flash size = 128MB
CPU speed: 405MHz
Memory Config: 64-bit UMA
Device Tech: 512Mb
Total memory: 256MB
Boot Device: NOR
Total flash: 4MB

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

CFE initialized.
Set default GPIO...
USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 09 Vendor 1A40 Product 0101: USB Hub
USB: New device connected to bus 1 hub 2 port 2
USB: Resetting device on bus 1 port 2
USB: Locating Class 02 Vendor DEAD Product BEEF: Ethernet Device
USB: [Transfer error: 4]
USB CDC Device (00:00:00:00:00:00)
Starting splash screen.
***************************************************
Found splash image - Width = 720 Height = 576
bmp ptr : 0x8fa00000 , surface ptr : 0xafc00000
***************************************************

Loader:elf Filesys:raw Dev:nandflash0.kernel File: Optionshttp://www.et-view.de/wcf/images/smilies/sad.png" alt="" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial;null)
Loading: !!!!! UNC read error occurred, while reading from NAND flash -1
0x80001000/6497856 !!!!! UNC read error occurred, while reading from NAND flash
-1
0x80633640/142432 Entry address is 0x80005470
TP1 Entry Address at 0x80000ffc = 80005470
Starting program at 0x80005470

**Exception 32: EPC=8061CAC4, Cause=A000802C, VAddr=00000000
RA=8000548C, PRID=0002A044

0 ($00) = 00000000 AT ($01) = 80630000
v0 ($02) = 00010000 v1 ($03) = 00000040
a0 ($04) = 87055000 a1 ($05) = 00000000
a2 ($06) = 8700C32C a3 ($07) = 43464531
t0 ($0http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 80005470 t1 ($09) = 8000FFC0
t2 ($10) = FFFFFFC0 t3 ($11) = 870972B4
t4 ($12) = 00000001 t5 ($13) = 8709FA4C
t6 ($14) = 00000001 t7 ($15) = 3EA95587
s0 ($16) = 8700C2B8 s1 ($17) = 87010000
s2 ($1http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 00000000 s3 ($19) = 8704D620
s4 ($20) = 8714F588 s5 ($21) = 870976C8
s6 ($22) = 8714F530 s7 ($23) = 870167BC
t8 ($24) = 000009F3 t9 ($25) = 8709730C
k0 ($26) = 87099728 k1 ($27) = 00000000
gp ($2http://www.et-view.de/wcf/images/smilies/cool.png" alt="8)" style="unicode-bidi: embed; text-overflow: ellipsis; vertical-align: middle; border-top-width: 0px; border-right-width: 0px; border-bottom-width: 0px; border-left-width: 0px; border-style: initial; border-color: initial; = 87055000 sp ($29) = 8714F3E8
fp ($30) = 87031F08 ra ($31) = 8000548C
-------

Soemone knows what is happening?

cu
KJ

[kleinerjunge]

I think i have a solution for this problem (tested on et5000):

1. Flash Egami 1.1 image on et5000 (not 1.0 or 1.2).
2. After booting, go in DeepStandBy.
3. Switch off receiver on back.
4. Prepare usb-stick with PLI2.1 based image (can also be a fullbackup).
5. Put stick in front usb-slot.
6. switch receiver on from back
7. start flashing.
8. When you see that box is rebooting, pull usb-stick out of slot.
9. Box reboots. Reboot from menu when box is up and running.
10. If box reboots without problems, you can flash directly any PLI2.1 based image without the need to flash egami 1.1 again.

Hope it helps.

cu
KJ

PS: A network cable was always plugged off! Dont know if that is really needed...

[vboris]

Hi!

Yesterday I was able to flash again my et5000 with actual OpenPLI 2.1! I dont know why it worked, but it did. I think the trick was that the box was in DeepStandBy for approx. 24h! I prepared the stick with fresh image from OpenPLI site, put it in front usb-socket and turned on the receiver (yes, i didnt boot the box once after those 24h!)

Today I made a backup of my new image flashed yesterday. And I reflashed to see if rebooting problem again exists, and yes, there it was again.

If I flash again a fresh PLI image, the reboot doesn't work again.

I have exactly the same problems and experiences!
But I have СT9100(ET9000)

[vboris]

Hi!


A user called erdi1 has the same problem now on his et5000 on et-view.de. He made a SERIAL LOG with putty. Here is the output (i asked him to post it here):

-------


start cfe init device
sec-0 nblks=8 blksiz=8192
sec-1 nblks=63 blksiz=65536
Enabling NAND flash at CS1, NOR flash at CS0
NAND Flash size = 128MB
CPU speed: 405MHz
Memory Config: 64-bit UMA
Device Tech: 512Mb
Total memory: 256MB
Boot Device: NOR
Total flash: 4MB

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

CFE initialized.
Set default GPIO...
USB: New device connected to bus 1 hub 1 port 1
USB: Resetting device on bus 1 port 1
USB: Locating Class 09 Vendor 1A40 Product 0101: USB Hub
USB: New device connected to bus 1 hub 2 port 2
USB: Resetting device on bus 1 port 2
USB: Locating Class 02 Vendor DEAD Product BEEF: Ethernet Device
USB: Transfer error: 4
USB CDC Device (00:00:00:00:00:00)
Starting splash screen.
***************************************************
Found splash image - Width = 720 Height = 576
bmp ptr : 0x8fa00000 , surface ptr : 0xafc00000
***************************************************

Loader:elf Filesys:raw Dev:nandflash0.kernel File: Options null)
Loading: !!!!! UNC read error occurred, while reading from NAND flash -1
0x80001000/6497856
!!!!! UNC read error occurred, while reading from NAND flash-1
0x80633640/142432 Entry address is 0x80005470
TP1 Entry Address at 0x80000ffc = 80005470
Starting program at 0x80005470

**Exception 32: EPC=8061CAC4, Cause=A000802C, VAddr=00000000
RA=8000548C, PRID=0002A044

0 ($00) = 00000000 AT ($01) = 80630000
v0 ($02) = 00010000 v1 ($03) = 00000040
a0 ($04) = 87055000 a1 ($05) = 00000000
a2 ($06) = 8700C32C a3 ($07) = 43464531
t0 ($0 = 80005470 t1 ($09) = 8000FFC0
t2 ($10) = FFFFFFC0 t3 ($11) = 870972B4
t4 ($12) = 00000001 t5 ($13) = 8709FA4C
t6 ($14) = 00000001 t7 ($15) = 3EA95587
s0 ($16) = 8700C2B8 s1 ($17) = 87010000
s2 ($1 = 00000000 s3 ($19) = 8704D620
s4 ($20) = 8714F588 s5 ($21) = 870976C8
s6 ($22) = 8714F530 s7 ($23) = 870167BC
t8 ($24) = 000009F3 t9 ($25) = 8709730C
k0 ($26) = 87099728 k1 ($27) = 00000000
gp ($2 = 87055000 sp ($29) = 8714F3E8
fp ($30) = 87031F08 ra ($31) = 8000548C
-------

Soemone knows what is happening?

cu
KJ

I think that the problem of incorrect operationUSB device
This may be an explanation for all the problems with loading a new image


Regards

[kleinerjunge]

Impossible! See my post above. Here quoted:

I think i have a solution for this problem (tested on et5000):

1. Flash Egami 1.1 image on et5000 (not 1.0 or 1.2).
2. After booting, go in DeepStandBy.
3. Switch off receiver on back.
4. Prepare usb-stick with PLI2.1 based image (can also be a fullbackup).
5. Put stick in front usb-slot.
6. switch receiver on from back
7. start flashing.
8. When you see that box is rebooting, pull usb-stick out of slot.
9. Box reboots. Reboot from menu when box is up and running.
10. If box reboots without problems, you can flash directly any PLI2.1 based image without the need to flash egami 1.1 again.

Hope it helps.

cu
KJ

PS: A network cable was always plugged off! Dont know if that is really needed...

No matter what USB-Stick I use. It works...
cu
KJ