Enigma 2 by The_ripper - TEST -

Quote:

---

Originally Posted by jamesjay

Hi M8,

That would be impossible I cannot load anything with a USB stick, I have tried to load other versions of E2 but the USB ports are not responding on my box. I know how to use applications for FTP and Telneting but that was for only simple tasks with Opensat stuff, I have no real experience with Dreambox's and real coding.

If it was possible to override the E2 version I have by transfer another version of E2 via filezilla I would, but I don't know where to put the file, or for that matter what Telnet commands I would need to get it going. Having looked at a post that explained how to return to Opensat firmware by using Filezilla and Telnet, the Telnet commands looked very complicated for a novice, and I would probably do more harm than good.

................................. ....

---

@jamesjay

If you do not feel safe and do not know Linux very well, you can still try the @Telesat procedure ... that MickeySa showed in the first post:

BACK TO ORIGINAL FW ...

Quote:

---

If You have problem with E2 and want to go back to the original FW, as this is beta version :

Download file BACK TO ORIGINAL FW.rar , attached to this post.

First DELETE 2 pictures from the MMP directory !!! and than transfer this files !!!

Put file update in the /tmp directory and give CHMOD 755 .

Also , put the file backup_kernel in /MMP directory .

Connect to telnet, and run this command :

./update /MMP/backup_kernel

NOTE: Also You can put this files on usb and run them from it !!!

After, that flash AzBox with original fw, that is all.

---

Regards

Arci

Quote:

---

Originally Posted by Abdul1508

We have recently been very much spoiled by the team it's so quiet, so nice if we had something new for the weekend to test. with all due respect natural
with what they have given us so far.
with best regards:001_005:

---

M8,

In software development project, it is commonly known that 80% of work is done in 20% of time, the 20% of work left takes 80% of time.
So today, we could say that The_Ripper and his team have already developped most essential functionnalities of E2 for Azbox. So now it is time to stabilise E2 and this is the most difficult task.

VFD - OK
EMU - OK, trough blue panel
CC*am 2.1.4 - OK
ZAP - OK...
Clock - OK...
etc...

ScreanShot, what your words as the first - not that it is a small step - but .... Uhhhhhh

Pictures go without comment, and a picture speaks vishe of words I think that it is not necessary,
I emphasize that no one I had demolition E2, and I install of everything ...

http://lh5.ggpht.com/_HMyt1_tBnmA/TN...xE/DS_E2_1.jpg

http://lh6.ggpht.com/_HMyt1_tBnmA/TN...Oc/DS_E2_2.jpg

http://lh4.ggpht.com/_HMyt1_tBnmA/TN...9Q/DS_E2_3.jpg

http://lh3.ggpht.com/_HMyt1_tBnmA/TN...GE/DS_E2_4.jpg

http://lh3.ggpht.com/_HMyt1_tBnmA/TN...7g/DS_E2_5.jpg

http://lh4.ggpht.com/_HMyt1_tBnmA/TN...PM/DS_E2_6.jpg

Quote:

---

Originally Posted by **esp**

@jamesjay

Have you tried this... https://www.satpimps.co.uk/showthread.php?t=141544

I think you need Step. 7 onwards if you have read the tutorial, as you can already FTP/Telnet your box?

Step 7

Now let’s go to transfer the necessary files to the box using FTP
To do this, we connect with our favorite FTP client (I use filezilla). You have to enter the IP address we got on previous step. The user is root, and the password is azbox, as usual. Copy files (Files are in the Files folder of this tutorial):
backup_kernel : Copy it to /MMP on the box
update : Copy it to /tmp on the box


Step 8

Return to the putty windows, where it asks login and password.
The user is root, and the password azbox.
Type:
cd /tmp (We move to /tmp directory)
chmod a+x update (We give the file run permission)
./update /MMP/backup_kernel (start restoration)
The process will begin, and will show progress.
When the process completes, the decoder will reboot, and will come to life!
We have 100% operational box with the original firmware!
Now, we can flash the firmware we want. Don’t forget to make a “Format Application Area” to clean up remnants of previous firmware

---

Thanks **esp** your a star,

I will give that a go later when I have more time on the lappy it's been taken over by one of my daughters, step 8 looks slightly different that what I have tried so far.

Best wishes and thanks again,

James.

Quote:

---

Originally Posted by arcibald

@jamesjay

If you do not feel safe and do not know Linux very well, you can still try the @Telesat procedure ... that MickeySa showed in the first post:

BACK TO ORIGINAL FW ...


Regards

Arci

---

Thanks again Arci for trying to help me, I have been trying that but the wheels come off at : ./update /MMP/backup_kernel

I get something like "no update found" or words to that effect.

Cheers M8

James.

Quote:

---

Originally Posted by jamesjay

Thanks again Arci for trying to help me, I have been trying that but the wheels come off at : ./update /MMP/backup_kernel

I get something like "no update found" or words to that effect.

Cheers M8

James.

---

Copy update to /tmp folder

Copy backup_kernel to /MMP folder

After login in telnet mode.

Type:

cd /tmp

chmod a+x update

./update /MMP/backup_kernel

Quote:

---

Originally Posted by jamesjay

Thanks **esp** your a star,

I will give that a go later when I have more time on the lappy it's been taken over by one of my daughters, step 8 looks slightly different that what I have tried so far.

Best wishes and thanks again,

James.

---

@ **Esp** you really are a STAR :respect-023:

I cannot thank you enough M8...I was missing this bit:

cd /tmp (We move to /tmp directory)
chmod a+x update (We give the file run permission)

As soon has I followed those instructions the box accepted the update, and it got me back to the Opensat upgrade page, from there I was able to load 0.9.4219 and I have now updated to 0.9.5020 so back to the firmware I had before testing E2.

A BIG THANK YOU to everyone that tried to help me over the last couple of days I was beginning to think my box was dead forever...just at a time when E2 was making it into a box worth having.

Many Thanks and Kind Regards.

James.

James,

Your experience was tricky for you, but one lesson we all learn out of this is that lots of things are repairable even when we think there not.
I followed this threat whit curiosity because this can happen to me to.
Now there is a good work around to restore the system.
Thanks all involved.

Quote:

---

Originally Posted by Sjaak66

James,

Your experience was tricky for you, but one lesson we all learn out of this is that lots of things are repairable even when we think there not.
I followed this threat whit curiosity because this can happen to me to.
Now there is a good work around to restore the system.
Thanks all involved.

---

Well said, I agree with you 100%...but I am not sure if I restored the box and reverted to opensat firmware how it was intended.

I think running this: "cd /tmp chmod" then "a+x update" caused the E2 firmware to crash and forced the box back to the opensat upgrade page.

I am just grateful to the members that helped me even when they were suggesting something I had already attempted.

Cheers,
James.

Good to hear you got your box working jamesjay :)

At least we know that method does work and should help a lot of people.

If you are going to try E2 again, then I would opt for v1.0.30 as that's the version I am running in my P+

Make sure you don't remove the USB stick until after the box has rebooted, and then you may have to put the USB back in again if E2 does not run, then reboot Azbox with the USB stick in which should put it in Rescue mode showing the IP if you have router attached, and then use Azup to install the E2 again with your box IP.

Jamesjay, I'm glad you got your box working again. I completely understand the relief that you must have felt when it came back to life!

I've been struggling to find a solution to my problems for nearly two weeks, now and I've tried different fixes without finding a solution. In fact, I have now made things worse because I cannot even connect with telnet or filezilla now. I think things have got worse through a combination of my inexperience with linux and my own stupidity.

I started out as described in post #1673 https://www.satpimps.co.uk/showpost....postcount=1673 and was quite rightly told by leao6 to go and read more. At that point the display showed the box’s IP Address and I could connect via telnet, filezilla and serial cable.

I have read every post several times now and tried these fixes without success:

When I tried the fix in
https://www.satpimps.co.uk/showthrea...166#post761166
I connected with the serial cable and followed the process through and it all seemed to go smoothly until I could not connect through tftp no matter how many times I repeated the process and tried various changes in the program settings. After this the display changed to show Booting, Gecko IP and the box’s IP address.

When I tried the fix in
https://www.satpimps.co.uk/showpost....&postcount=117
it all seemed to be going smoothly but got stuck in rebooting. I switched the box off and on again. Since then I now have the display showing Err:NO_DISK, Connect AS. I can no longer connect through telnet or filezilla and the IP Address is no longer showing.

I am sorry to bother you guys when my problems seem partly down to my own stupidity, but I am unable to work this out myself. Can anyone help me with this? It’s driving me crazy!

Quote:

---

Originally Posted by NodiSa

VFD - OK
EMU - OK, trough blue panel
CC*am 2.1.4 - OK
ZAP - OK...
Clock - OK...
etc...

ScreanShot, what your words as the first - not that it is a small step - but .... Uhhhhhh

Pictures go without comment, and a picture speaks vishe of words I think that it is not necessary,
I emphasize that no one I had demolition E2, and I install of everything ...

---

Is this from the DS image?

Yes it is.
It's a good image but still needs all the finishes from the AzboxE2 team for fixes.

Hi,

i've installed CCcam and NewCS in EII 1.0.30 but the internal cardreader seems not working. Is it possible to read the smartcard in the internal reader or in Smargo or is it necessary to share the card in another Box?
I tried S.G.C and Glass UnivCam-Manager to install CCcam and NewCS but both without results.

Internal Reader does not work because there is no /dev/sci0
Smargo does not work because there is no FTDI-Driver installed.
Does anybody have a source for this driver?


Best regards
Ralf

I can still connect with the serial cable. This is what comes up in Putty when I reboot the box:

xosPe0 serial#c795d7a7b13a488198f565e834 f44f62 subid 0x50
xenv cs2 ok
xosPe0 serial#c795d7a7b13a488198f565e834 f44f62 subid 0x50
xenv cs2 ok
power supply: ok
dram0 ok (8)
dram1 ok (9)
zboot (0) ok
>
********************************* *****
* SMP863x zboot start ...
* Version: 2.4.0-2.8.0.1
* Started at 0x91000000.
* Configurations (chip revision: 6):
* Use 8KB DRAM as stack.
* Support XLoad format.
* Enabled BIST mode.
* Enabled memory test mode.
* Use internal memory for stage0/1.
********************************* *****
Boot from flash (0x48000000) mapped to 0x8c000000.
Found XENV block at 0x8c000000.
CPU clock frequency: 347.62MHz.
System clock frequency: 231.75MHz.
DRAM0 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a5555).
DRAM1 dunit_cfg/delay0_ctrl (0xf34111ba/0x000a6565).
Using UART port 0 as console.
Board ID.: "852-E2"
Chip Revision: 0x8634:0x86 .. Matched.
Setting up H/W from XENV block at 0x8c000000.
Setting <SYSCLK avclk_mux> to 0x00000000.
Setting <SYSCLK hostclk_mux> to 0x00000100.
Setting <IRQ rise edge trigger lo> to 0xff28ca00.
Setting <IRQ fall edge trigger lo> to 0x0000c000.
Setting <IRQ rise edge trigger hi> to 0x0000009f.
Setting <IRQ fall edge trigger hi> to 0x00000000.
Setting <IRQ GPIO map> to 0x20090820.
Setting <PB default timing> to 0x10101010.
Setting <PB timing0> to 0x10101010.
Setting <PB Use timing0> to 0x000003f4.
Setting <PB timing1> to 0x00110101.
Setting <PB Use timing1> to 0x000003f3.
Setting <PB timing2> to 0x105f1010.
Setting <PB Use timing2> to 0x000003f8.
PB cs config: 0x000e0040 (use 0x000e0040)
Enabled Devices: 0x00021ace
BM/IDE PCIHost Ethernet I2CM I2CS USB PCIDev2 PCIDev3 SCARD
MAC: 00:02:14:15:4e:79
PCI IRQ routing:
IDSEL 2: INTA(#14) INTB(#14) INTC(#14) INTD(#14)
IDSEL 3: INTA(#15) INTB(#15) INTC(#15) INTD(#15)
Smartcard pin assignments:
OFF pin = 0
5V pin = 1
CMD pin = 2
Setting up Clean Divider 2 to 96000000Hz.
Setting up Clean Divider 4 to 33333333Hz.
Setting up Clean Divider 5 to 25000000Hz.
Setting up Clean Divider 6 to 20000000Hz.
Setting up Clean Divider 7 to 20000000Hz.
GPIO dir/data = 0x76000038/0x76000000
UART0 GPIO mode/dir/data = 0x6e/0x00/0x00
UART1 GPIO mode/dir/data = 0x6e/0x00/0x00
XENV block processing completed.
Found existing memcfg: DRAM0(0x08000000), DRAM1(0x08000000)
Heap/Temp/Temp1/Dest start at 0x14000000/0x16000000/0x15000000/0x12000000.
Default boot index: 0
Scanning ROMFS image at 0x8c040000 (0x48040000) .. Found.
ROMFS found at 0x8c040000, Volume name = YAMON_XRPC
Found 1 file(s) to be processed in ROMFS.
Processing xrpc_xload_yamon_ES4_prod.bin (start: 0x8c040090, size: 0x0002fe84)
Checking zboot file signature .. Not found.
Trying xrpc_xload format .. OK
Checking zboot file signature at 0x13000000 .. OK
Decompressing to 0x91200000 .. OK (453328/0x6ead0).
Load time total 151/222 msec.
Execute final at 0x91200000 ..



********************************* *
* YAMON ROM Monitor
* Revision 02.06-SIGMADESIGNS-01-2.8.0.1
********************************* *
Memory: code: 0x11000000-0x11040000, 0x11200000-0x11204000
reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000
Environment variable 'start' exists. After 1 seconds
it will be interpreted as a YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

xrpc succeeded
Stopped due to Ctrl-C
YAMON>

I have just noticed that the display is now showing 'Booting'

Thanks for any help anyone can suggest.

Stephen

Quote:

---

Originally Posted by SPF

Jamesjay, I'm glad you got your box working again. I completely understand the relief that you must have felt when it came back to life!

I've been struggling to find a solution to my problems for nearly two weeks, now and I've tried different fixes without finding a solution. In fact, I have now made things worse because I cannot even connect with telnet or filezilla now. I think things have got worse through a combination of my inexperience with linux and my own stupidity.

I started out as described in post #1673 https://www.satpimps.co.uk/showpost....postcount=1673 and was quite rightly told by leao6 to go and read more. At that point the display showed the box’s IP Address and I could connect via telnet, filezilla and serial cable.

I have read every post several times now and tried these fixes without success:

When I tried the fix in
https://www.satpimps.co.uk/showthrea...166#post761166
I connected with the serial cable and followed the process through and it all seemed to go smoothly until I could not connect through tftp no matter how many times I repeated the process and tried various changes in the program settings. After this the display changed to show Booting, Gecko IP and the box’s IP address.

When I tried the fix in
https://www.satpimps.co.uk/showpost....&postcount=117
it all seemed to be going smoothly but got stuck in rebooting. I switched the box off and on again. Since then I now have the display showing Err:NO_DISK, Connect AS. I can no longer connect through telnet or filezilla and the IP Address is no longer showing.

I am sorry to bother you guys when my problems seem partly down to my own stupidity, but I am unable to work this out myself. Can anyone help me with this? It’s driving me crazy!

---

Hi SPF,

As I am a novice and because I was in so much of a mess myself it is quite difficult to help you.

The first thing you need to do is get Filezilla and Putty connecting with your box again. I had times when my box wouldn't connect to my PC with those applications and I was told to turn the box off unplug it from the mains for a while and even to disconnect the box from the router (if your using one), are you using a crossover cable when connecting your PC to your box? I went into the routers webpage and checked the attached devices to make sure the box's IP address had not changed, you can also do this with Dreambox Control Centre or DCC.

I turned my router off for 10 minutes or so to try and force the box to connect when I turned it on again, and although I am not advising you to do this I even turned the AZbox off and on quickly using the power switch at the back to force it to connect.

By the way I tried the fixes you have tried...but the advice that **ESP** gave me a few pages or so back is the one that helped most...but remember what caused my box to fail is not necessarily the same as your box's failure

Good luck
James.

@ spf
i had booting too, mine is fixed
Now we are on Yamon console. It shows a command interpreter YAMON>
First is to initialize the network interface.
Introduce the following, pressing Enter after each line

setenv bootserver 192.168.1.64 (IP address of your computer)
setenv gateway 192.168.1.254 (router address)
setenv ipaddr 192.168.1.55 (IP address you want for AZBox)
setenv subnetmask 255.255.255.0 (network mask)
net init (initializes network)
net up (gets up network interface)

Well, we already have network connection in the box (although it does not have telnet, ftp, or anything else)

Step 4
Download and install TFTPd32

link https://www.satpimps.co.uk/showthread.php?t=141544

Thanks, James

I'll try your suggestions next.
I have afeeling that ESP's suggestion might have solved my problem last night. It looks like the difference from what I tried was the "a+x update" part.

I am searching for links to info about putting the flash drive into a portable USB HDD caddy. This might help but I won't know until I read up about it.

Thanks for your feedback

Stephen

Quote:

---

Originally Posted by SPF

I can still connect with the serial cable. This is what comes up in Putty when I reboot the box:
.......
********************************* *
* YAMON ROM Monitor
* Revision 02.06-SIGMADESIGNS-01-2.8.0.1
********************************* *
Memory: code: 0x11000000-0x11040000, 0x11200000-0x11204000
reserved data: 0x11240000-0x12440000, PCI memory: 0x12440000-0x12840000
Environment variable 'start' exists. After 1 seconds
it will be interpreted as a YAMON command and executed.
Press Ctrl-C (or do BREAK) to bypass this.

xrpc succeeded
Stopped due to Ctrl-C
YAMON>

I have just noticed that the display is now showing 'Booting'

......

Stephen

---

That's mean that your four or fifth partition of thr NOR flash is damaged.
To find out who you have to let the box showing the next steps till it stopped by himself (don't interrumpt Ctrl-C the Yamon loader).
When it's stop, will show us the error and we can find then the exact problem the box have.
For the forth partition problem you (linux kernel) you have to load a linux kernel via tftp server and mount a usb device with the kernel and flash it.

For the 5 partition is more simple, you can flash a dump file of that partition (i or anybody can make a dump and let you have it) or just mount that dump file on a directory (you can do it because your kernel is working in that case) and copy recursively (cp -R) all the files on DISK1 (this is the mount point of the 5 partition of the NOR flash) like following:
$ mount|grep mtd
/dev/mtdblock5 on /DISK1 type jffs2 (rw,noatime)

But first lets us know where is your problem posting the entire log of the serial connection.

Thanks, Simon30000

I have entered those commands and tried the next step too. Here is the result:

xrpc succeeded
Stopped due to Ctrl-C
YAMON> setenv bootserver 192.168.0.100
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setenv gateway 192.168.0.1
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setenv ipaddr 192.168.0.103
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> setenv subnetmask 255.255.255.0
Updating XENV block at 0x48000000.
.
XENV verification OK.
YAMON> net init
Ethernet driver for EM86XX (v1.0)
(MAC 00:02:14:15:4e:79, tx_desc/rx_desc = 16/32)

em86xx_eth::open(em86xx_eth) - Full-duplex mode
em86xx_eth::open(em86xx_eth) - 100 Mbit/s
em86xx_eth ethernet start
ipaddr: 192.168.0.103
subnetmask: 255.255.255.0
gateway: 192.168.0.1
YAMON> net up
em86xx_eth ethernet start
YAMON> load -b tftp://192.168.0.100/vmlinux.bin 0x90020000
About to load tftp://192.168.0.100/vmlinux.bin
Press Ctrl-C to break

Error : TFTP READ-REQ timeout ERROR
Hint : Check TFTP-server is up and running, or try command "net down"/"net up"
YAMON>

I got to this stage before but could not connect through TFTPd32. Do you know what the settings should be for this program. I am unsure if it is a change in settings that is required here but I have tried everything I can think of.

Thanks