do you use just an ordinary 2.6.22 kernel or some special one? 2.6.22 seems to me like the one from WDLiveIt would help if you can post kernel config file as well so we can try to build own kernel?
Did you get any improvement on network speed with the new kernel?
Thank you,Originally Posted by The_Ripper
Ok guys, as I promise,here is the links
hxxp://www.megaupload.com/?d=S9GC4UQR (vmlinux.bin)
hxxp://www.megaupload.com/?d=KZBRMLEK (files and modules)
hxxp://www.megaupload.com/?d=R88HACTT (MMP uclibc)
Ok first I use tftpd32 server for Windows,link to download hxxp://tftpd32.jounin.net/.
I put vmlinux.bin(from first link) file where is main tftp exe file is, and after start of the program just change "Current Directory" to point
there if allready not and change "Server interface" to your PC IP Address(mine is 192.168.1.3) and let it stay running.
Thats all to setup tftp on Windows.
Next, boot up receiver and transfer all files from second link in
/MMP/modules/2.6.22/ (make 2.6.22 folder)
chmod 755 all files
Pls make shure you have this files on DISK1 because I am using this files.
/DISK1/.passwd
/DISK1/.shadow
Next, download MMP uClibc tmp folder from third link.You must unpack it on receiver because of soft symlinks.
After extract you should have /MMP/tmp folder with uClibc based librarys files.We need uCLibc because of setting up video signal out with
small MRUA app.
SO, after this go into telnet console and write this command (ELITE MODEL tested!!!!!)
setxenv -f /dev/mtdblock0
it should list all XENV settings in flash. Our main interest for now is in 4 settings,
y.ipaddr,y.subnetmask,y.gateway and y.start,
unfortunaly YAMON boot loader doesnt have dhcp so you must manualy add all IP based datas.Pls be cerful with this, if you are wrong with this settings you will not be able to boot and no other way to repair
it, then to make your self rs232 cable like "telesat" user explain here.
So before you change pls write down default values for this 4 settings but main value y.start IS MUST so you can change it back after you want to load standard FW!!!!
Here is my values for IP datas. My router always give my Azbox receiver this IP address 192.168.1.5, Subnet mask for this range is 255.255.255.0 and my router gateway is 192.168.1.1.
So this is way I will change this values for mine IP settings
(It takes few seconds to change value)
setxenv -f /dev/mtdblock0 -k y.ipaddr -v "192.168.1.5"
setxenv -f /dev/mtdblock0 -k y.subnetmask -v "255.255.255.0"
setxenv -f /dev/mtdblock0 -k y.gateway -v "192.168.1.1"
-------------------------------
Next is to change boot up command for Yamon, default value on my receiver is
y.start on my receiver is "xrpc 0xac080090; load zbf 0xb3000000; go"
so pls write it down somewhere.
So, next step is to change startup boot command (y.start).
PLEASE CHANGE IP ADDRESS FOR YOUR TFTP SERVER, MINE TFTP SERVER PROGRAM IS ON PC(WINDOWS) WITH 192.168.1.3 IP ADDRESS!!!!!!!!!!!!!!!!!!!!!!!!!!
setxenv -f /dev/mtdblock0 -k y.start -v "net init; net initpci; net up; load -b tftp://192.168.1.3/vmlinux.bin 0***020000; go"
hmm 0x 9 0 0 2 0 0 0 0 ,just put it together instead of 0***020000 and without spaces!!!
after you change all just in case ./setxenv -f /dev/mtdblock0 check again if your values are okey,plus y.XXXX commands maybe some letter is missing while you type it!!!!!
It's just left to boot it, so type reboot in console and hope it will boot
to go back after boot to standard firmware, go to /MMP/modules/2.6.22 , where setxenv program is and put back OLD y.start command value and just reboot it
./setxenv -f /dev/mtdblock0 -k y.start -v "xrpc 0xac080090; load zbf 0xb3000000; go"
-----------------------------------------------------------
If all goes well you should be able to telnet/ftp to Azbox receiver.If NO, sorry I dont have solution, you will need rs232 cable to fix it,
But if all okey, telnet and go to /MMP/modules/2.6.22 folder and use set_outport prog to activate video out signal, I just tested analog out
./set_outport -analog -f PAL_BG
for digital maybe this way
./set_outports -digital -f HDMI_1080i59 -dvi_hdmi siI9030 -hdmi2c 2
If anyone managed to come till here I will explain how to load FB driver, it's still in working process and it has fixed screen resolution 720x576, and maybe
letter upload E2 files but it needs alot of patching and fixing plus writing next driver(s).
I will try it on my bedroom elite this weekend. I was wondering which driver would you suggest should be written first? What do you need first to progress?
@luky
Yes, I used 2.6.22 from WDLive, but you need many more things to compile vmlinux for Azbox, it goes beyond simple explanation, sorry.
No , no speed improvment on network speed, 3 MB , 3.3 MB max, and main CPU is on full load.So maybe overclocking few Mhz up like acceleration option in Azbox FW will help.
I'll try it with the Premium but the first file is not available.
Last edited by 4@@@@; 03-06-2010 at 07:20 PM.
Now first link works ?
www.megaupload.com/?d=S9GC4UQR
No: it tells that the file is not available - but it knows that the file name is vmlinux.rar.
Strange ?
EDIT: Well I changed the language to english and now it works.
hmm, not good news. I can get with current kernel and nfs udp up to 7MB but it requires killing almost all other processes. So those 3MB are on current level :(
One thing which I notice with current kernel is high number of interrupts (thousands) which decrease after killing some processes (sdecoder etc). I hoped for better results with new kernel.
My tv can transfer 10MB and asus o!play 11MB no problem. What a lame piece of hw
Yes , current CPU cant handle more data traffic.
On new Sigma CPUs version(s) they put seperate CPU just for USB/Lan and other peripherals
Just to explain a little bit more to the other users the connection to azbox and recovery if the things go bad.
The normal RS232 connection doesn't work directly, so we need a TTL logical level to RS232 converter (like a max232 converter or any other converter like a simple CA-42 nokia data cable). The nokia cable is a good one because we have TTL to usb directly (com emulation).Here you get more information about it.
And for the recovery, if the things go bad, we can recover the box only if the first 3 partition of the NOR flash are ok, in other words we must have Yamon bootloader working (partition 3). So we can recover partition 4 and 5.
If one of the first 3 partition is damaged then it's nothing to do.
To recover this boxes it needs jtag enabling and using and specific software or removing the NOR flash, writing and soldering back as on the Sigma do***entation smp8634_do***entation_2.8.5.0 is explained
Here you got passage from Board Bring-up How To section of sigma do***entation:
Bringing Up the SMP8634 Board
Currently, there are two kinds of faulty SMP863x boards. The first ones are the prototype boards (from the first batch of boards) that have hardware problems due to bad soldering, bad layout, faulty components, etc. The second ones are existing working boards that were booting, but are not booting currently due to hardware (e.g., bad DRAM chip or bad flash memory) or software issues. This do***ent focuses on the second category of boards with software issues. The goal is to recover the boards and make them bootable.
Typical Problems with Non-Booting Boards
1. Corrupted xenv block: The xenv block and its mirror blocks are corrupted. xos displays the messages xenv cs2 failed and xenv cs3 failed, followed by the zboot failed message.
2. Corrupted first level boot: The first level boot (typically the zboot) is corrupted. xos displays the zboot failed message. This can arise from the wrong image being flashed (i.e., from flashing a development image to production chip or production image to a development chip).
3. Faulty settings in xenv: For example, the DRAM parameters are set incorrectly in xenv. As a result, the DRAM is not in a good condition, causing the decryption of the first level boot to fail.
4. Corrupted secondary boot: The secondary boot (typically Yamon) is corrupted. As a result, zboot boots to the Linux kernel (if installed) instead.
Solutions for Non-Booting Boards
In all the cases, recovery can be made by removing the flash memory, reprogramming it with the image and soldering it back. This approach is beyond the scope of this do***ent and tends to be more intrusive than most users want.
A non-intrusive way to deal with a corrupted xenv block, first level boot or faulty xenv settings (cases 1, 2, 3, or even 4) is by using emulators, such as MAJIC from EPI tools (Mentor Graphics).
Before connecting the emulator to the JTAG port on the board, ensure that JTAG is enabled on the board. For Sigma reference boards, typically there is one jumper to enable the JTAG connection. This jumper has to be set. Next, get the software ready by building a special version of Yamon by modifying Yamon's Makefile, WITH_RESET=y and WITH_XENV=n before rebuilding Yamon. Finally, get the image to be flashed onto the board ready by getting the replacement xenv block ready, making sure that the first level boot is signed with the right certificate, etc.
After Yamon is rebuilt, two images are later loaded via the JTAG onto the board (if using an older version of Yamon, then the version number is 02.06).
reset-02.11-SIGMADESIGNS-01.elf
yamon-02.11-SIGMADESIGNS-01_el.elf
So people, please be careful on what you are doing or the box will be gone forever.
Just to be clear we are not flashing anything.
What @shklifo posted is true if we where flashing like for normal new Azbox FW, erasing all datas in FLASH partitions and puting new one. We dont do that.
The_Ripper just out of curiosity, if we/you guys manage to make something good, how would it be in mediaplayer/mediacenter situation?
Just like normal enigma2 in dm800 for example using plugins , but with support for all codecs? (dm800 doesn't support xvid etc)
Or would it be possible to have enigma2 + azbox original mediacenter?
Either way, what's your thought on that? Just curious
@hfmls
If someone has Azbox mediacenter source code and recompile it, then yes np at all to use it or with plugins. Sigma chip support full media decoding, how you will coded it , it's up to you ...
oh ok.
i have no clue if someone has it. if so, can that person tell us?
Here I show you the research I did in his day on the console Yamón and mapping of the FLASH if it helps you.
ttp://www.azboxhd.es/foro/showthread.php/6984-Puerto-RS232-y-Consola-YAMON-y-la-FLASH-del-Azbox?p=66272#post66272
Because of time let standing project for months, seeing the post of The Ripper I hope you can be helpful to work with the console Yamón.
It is important that when they are made instead of recording evidence in the FLASH. Doing it in the SDRAM in real time it never hurts FLASH and allows you to load the kernel for example.
A KGDTeam greeting.
NOTE:
Many photos show the network connection Tx and Rx in an incorrect position.
The photos of the manual are tested with various TTL converters and are all OK.
The files you uploaded The Ripper I could not test for lack of time, I hope it encourages people to try and finally go things interesting for our azbox
Last edited by milix; 04-06-2010 at 04:26 PM.
Traslate manual here:
https://www.satpimps.co.uk/showthrea...389#post728389
Salu2
Here's how the kernel etc. are replaced during the firmware upgrade. I am wondering if the cpu keys package could be used to flash a proper signed kernel for the Azbox using the dummy private keys included in the cpu keys archive. Someone with JTAG/RS-232 access might test it.
Cpu keys:
hxxp://www.megaupload.com/?d=3CEJY6NY
#!/bin/sh
DISK2_HOME=`if [ -f /tmp/.disk2 ]; then /bin/cat /tmp/.disk2; else /bin/echo "/DISK2"; fi`
. $DISK2_HOME/include.sh
PATCHDIR=/DATA/swpatch/patch
FLASHTOOL=$PATCHDIR/bin/flashcp
FLASHOK=/tmp/flash_write_ok
IMG_ZBOOT=$PATCHDIR/zboot.bin
IMG_YAMON=$PATCHDIR/yamon.bin
IMG_LINUX=$PATCHDIR/linux.bin
FLASH_ORG=/DISK2/flash.org
FLASH_NEW=/DISK2/flash.txt
FLASH_ROM=/root/DISK2/flash.txt
[ -f $FLASH_ROM ] && FLASH_ORG=$FLASH_ROM
VER_O_ZBOOT=`cat $FLASH_ORG | grep 'zboot ' | awk '{print $2}'`
VER_O_YAMON=`cat $FLASH_ORG | grep 'yamon ' | awk '{print $2}'`
VER_O_LINUX=`cat $FLASH_ORG | grep 'linux ' | awk '{print $2}'`
VER_N_ZBOOT=`cat $FLASH_NEW | grep 'zboot ' | awk '{print $2}'`
VER_N_YAMON=`cat $FLASH_NEW | grep 'yamon ' | awk '{print $2}'`
VER_N_LINUX=`cat $FLASH_NEW | grep 'linux ' | awk '{print $2}'`
[ -z "$VER_N_ZBOOT" ] && VER_N_ZBOOT="00000000"
[ -z "$VER_N_YAMON" ] && VER_N_YAMON="00000000"
[ -z "$VER_N_LINUX" ] && VER_N_LINUX="00000000"
mtd_block6=`cat /proc/partitions | grep mtdblock6 | wc -l`
if [ $mtd_block6 = 1 ]; then
sync
sync
sleep 6
umount /dev/mtdblock5
sleep 1
umount /dev/mtdblock5
sleep 1
/DATA/swpatch/patch/bin/flash_eraseall /dev/mtd6
dd if=/dev/mtd5 of=/dev/mtd6 bs=1024 seek=1024 count=1024
mount -t jffs2 /dev/mtdblock5 /DISK2
fi
if [ -e "$IMG_ZBOOT" ] && [ "$VER_N_ZBOOT" != "$VER_O_ZBOOT" ]; then
echo "Start put bootloader"
$FLASHTOOL -v $IMG_ZBOOT /dev/mtd0
rm $FLASHOK
fi
if [ -e "$IMG_YAMON" ] && [ "$VER_N_YAMON" != "$VER_O_YAMON" ]; then
echo "Start put yamon image"
$FLASHTOOL -v $IMG_YAMON /dev/mtd3
rm $FLASHOK
fi
if [ -e "$IMG_LINUX" ] && [ "$VER_N_LINUX" != "$VER_O_LINUX" ]; then
echo "Start put linux image"
$FLASHTOOL -v $IMG_LINUX /dev/mtd4
rm $FLASHOK
fi
echo "Done"
That's right.
I wanted to give more details on the serial connection on how it works and warn the other users to be more responsible using it. When you got the serial connection working, you can do a lot of things.
Just a dd to the wrong direction or pflash commands and the box go ...
AZBox Premium
It only used dhcp to set my ip.Connected to noname.
Escape character is '^]'.
Powered by The Ripper and telesat
Linux/mips 2.6.22.19-19-the_ripper
AZBOX login: root
Password:
AZBOX[~]$
AZBOX[2.6.22]$ lsmod
em8xxx 2515264 0 - Live 0xc8b2d000 (PF)
llad 124320 1 em8xxx, Live 0xc8896000 (P)
AZBOX[2.6.22]$ ./set_outports -analog -f PAL_BG
Segmentation fault
AZBOX[2.6.22]$ ./set_outports -digital -f HDMI_1080i59 -dvi_hdmi siI9030 -hdmi2c 2
Segmentation fault
AZBOX[2.6.22]$
Hmmm, strange about Segmentation fault,
Can you pls go to MMP/tmp and type
ls -l
Thx
That's the output
AZBox[tmp]$ ls -l
-rwxr-xr-x 1 root root 22364 Jan 1 2000 ld-uClibc-0.9.27.so*
lrwxrwxrwx 1 root root 19 Jan 1 2000 ld-uClibc.so.0 -> ld-uClibc-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libblkid.so -> libblkid.so.1.0*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libblkid.so.1 -> libblkid.so.1.0*
-rwxr-xr-x 1 root root 33636 Jan 1 2000 libblkid.so.1.0*
lrwxrwxrwx 1 root root 9 Jan 1 2000 libc.so -> libc.so.0*
lrwxrwxrwx 1 root root 19 Jan 1 2000 libc.so.0 -> libuClibc-0.9.27.so*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libcom_err.so -> libcom_err.so.2.1*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libcom_err.so.2 -> libcom_err.so.2.1*
-rwxr-xr-x 1 root root 7596 Jan 1 2000 libcom_err.so.2.1*
-rwxr-xr-x 1 root root 11720 Jan 1 2000 libcrypt-0.9.27.so*
lrwxrwxrwx 1 root root 18 Jan 1 2000 libcrypt.so -> libcrypt-0.9.27.so*
lrwxrwxrwx 1 root root 18 Jan 1 2000 libcrypt.so.0 -> libcrypt-0.9.27.so*
-rwxr-xr-x 1 root root 7704 Jan 1 2000 libdl-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libdl.so -> libdl-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libdl.so.0 -> libdl-0.9.27.so*
lrwxrwxrwx 1 root root 13 Jan 1 2000 libe2p.so -> libe2p.so.2.3*
lrwxrwxrwx 1 root root 13 Jan 1 2000 libe2p.so.2 -> libe2p.so.2.3*
-rwxr-xr-x 1 root root 23500 Jan 1 2000 libe2p.so.2.3*
lrwxrwxrwx 1 root root 16 Jan 1 2000 libext2fs.so -> libext2fs.so.2.4*
lrwxrwxrwx 1 root root 16 Jan 1 2000 libext2fs.so.2 -> libext2fs.so.2.4*
-rwxr-xr-x 1 root root 133572 Jan 1 2000 libext2fs.so.2.4*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libform.so -> libform.so.5.2*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libform.so.5 -> libform.so.5.2*
-rwxr-xr-x 1 root root 64764 Jan 1 2000 libform.so.5.2*
lrwxrwxrwx 1 root root 13 Jan 1 2000 libgcc_s.so -> libgcc_s.so.1*
-rwxr-xr-x 1 root root 54240 Jan 1 2000 libgcc_s.so.1*
-rwxr-xr-x 1 root root 109448 Jan 1 2000 libm-0.9.27.so*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libm.so.0 -> libm-0.9.27.so*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libm.so.6 -> libm-0.9.27.so*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libmenu.so -> libmenu.so.5.2*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libmenu.so.5 -> libmenu.so.5.2*
-rwxr-xr-x 1 root root 31212 Jan 1 2000 libmenu.so.5.2*
-rwxr-xr-x 1 root root 539666 Apr 24 2008 libncurses.a*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libncurses.so -> libncurses.so.5.2*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libncurses.so.5 -> libncurses.so.5.2*
-rwxr-xr-x 1 root root 322508 Jan 1 2000 libncurses.so.5.2*
-rwxr-xr-x 1 root root 1988 Jan 1 2000 libnsl-0.9.27.so*
lrwxrwxrwx 1 root root 16 Jan 1 2000 libnsl.so -> libnsl-0.9.27.so*
lrwxrwxrwx 1 root root 16 Jan 1 2000 libnsl.so.0 -> libnsl-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libpanel.so -> libpanel.so.5.2*
lrwxrwxrwx 1 root root 15 Jan 1 2000 libpanel.so.5 -> libpanel.so.5.2*
-rwxr-xr-x 1 root root 14584 Jan 1 2000 libpanel.so.5.2*
-rwxr-xr-x 1 root root 79316 Jan 1 2000 libpthread-0.9.27.so*
lrwxrwxrwx 1 root root 20 Jan 1 2000 libpthread.so -> libpthread-0.9.27.so*
lrwxrwxrwx 1 root root 20 Jan 1 2000 libpthread.so.0 -> libpthread-0.9.27.so*
-rwxr-xr-x 1 root root 1988 Jan 1 2000 libresolv-0.9.27.so*
lrwxrwxrwx 1 root root 19 Jan 1 2000 libresolv.so -> libresolv-0.9.27.so*
lrwxrwxrwx 1 root root 19 Jan 1 2000 libresolv.so.0 -> libresolv-0.9.27.so*
-rwxr-xr-x 1 root root 5160 Jan 1 2000 librt-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 librt.so -> librt-0.9.27.so*
lrwxrwxrwx 1 root root 15 Jan 1 2000 librt.so.0 -> librt-0.9.27.so*
lrwxrwxrwx 1 root root 18 Jan 1 2000 libstdc++.so -> libstdc++.so.6.0.2*
lrwxrwxrwx 1 root root 18 Jan 1 2000 libstdc++.so.6 -> libstdc++.so.6.0.2*
-rwxr-xr-x 1 root root 688484 Jan 1 2000 libstdc++.so.6.0.2*
-rwxr-xr-x 1 root root 14112 Jan 1 2000 libthread_db-0.9.27.so*
lrwxrwxrwx 1 root root 22 Jan 1 2000 libthread_db.so -> libthread_db-0.9.27.so*
lrwxrwxrwx 1 root root 22 Jan 1 2000 libthread_db.so.1 -> libthread_db-0.9.27.so*
-rwxr-xr-x 1 root root 433756 Jan 1 2000 libuClibc-0.9.27.so*
-rwxr-xr-x 1 root root 5064 Jan 1 2000 libutil-0.9.27.so*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libutil.so -> libutil-0.9.27.so*
lrwxrwxrwx 1 root root 17 Jan 1 2000 libutil.so.0 -> libutil-0.9.27.so*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libuuid.so -> libuuid.so.1.2*
lrwxrwxrwx 1 root root 14 Jan 1 2000 libuuid.so.1 -> libuuid.so.1.2*
-rwxr-xr-x 1 root root 13452 Jan 1 2000 libuuid.so.1.2*
lrwxrwxrwx 1 root root 13 Jan 1 2000 libz.so -> libz.so.1.2.1*
lrwxrwxrwx 1 root root 13 Jan 1 2000 libz.so.1 -> libz.so.1.2.1*
-rwxr-xr-x 1 root root 71268 Jan 1 2000 libz.so.1.2.1*
Posting Permissions
Reply With Quote
Bookmarks