sure your bootarg environment is OK?AMIKO ALIEN 2 + (HDMU 10797)
The bootargs environment variables are not read ... in the shell returns only the label definition!
P.S. This afternoon ... i can try with telnet command !
Ciao ...Code:host135 login: root Password: ('-. .-. _ .-') _ _ .-') ( OO ) /( ( OO) )( '.( OO )_ ,--. ,--. \ .'_ ,--. ,--.),--. ,--. | | | | ,`'--..._)| `.' | | | | | | .| | | | \ '| | | | | .-') | | | | ' || |'.'| | | |_|( OO ) | .-. | | | / :| | | | | | | `-' / | | | | | '--' /| | | |(' '-'(_.-' `--' `--' `-------' `--' `--' `-----' -----====== HDMU 10797 enigma2 Git 5400 ======----- BusyBox v1.21.0 (2013-03-28 16:46:31 CET) built-in shell (ash) Enter 'help' for a list of built-in commands. host135:~# cd /tmp/SH4_MORLY host135:/tmp/SH4_MORLY# ./fw_printenv Warning: Bad CRC, using default environment bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm bootdelay=5 baudrate=115200 host135:/tmp/SH4_MORLY#
there seems to be a problem: Bad CRC, ...
could you check it again?
"Every Setback is a Set Up for a Comeback"
hello
can be formatted to create partitions and full backup with sh4 stb admintool
thank you in advance
@morly
Amiko Alien 2+ ... Enigma2 bootargs is OK ...
I think that your fw_env.config (Spark7162.tool) u.boot linked not good with this type of receiver !Code:Starting kernel console=ttyAS1,115200 rw root=/dev/mtdblock6 rootfstype=jffs2 init=/bin/devinit coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 ip=172.100.100.249:172.100.100.174:172.100.100.174:255.255.0.0:Enigma2:eth0:off stmmaceth=msglvl:0,phyaddr:2,watchdog:5000 bigphysarea=6000 nwhwconf=device:eth0,hwaddr:30:00:0A:00:xx:xx Manufacture=Spark-Project STB_ID=0C:00:0A:00:00:xx:xx - 0x00000000 - 0 ...
considers that ... / dev/mtd0 ... is empty (FF) and u-boot not linked!Code:# Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundand # environment sector is assumed present. # MTD device name Device offset Env. size Flash sector size /dev/mtd0 0x00060000 0x00020000 0x20000
only if start i2s.ko module ... u-boot is linked to /dev/mdt7Code:host135:~# 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"
Let me know if you want to other test ... or correct offset that I should try, because fw_printenv display the bootargs environment!Code:host135:~# 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" mtd7: 00100000 00010000 "uboot"
Ciao ...
in spark7162 uboot env can be read only from mtd7 = after insmod i2s.ko@morly
Amiko Alien 2+ ... Enigma2 bootargs is OK ...
I think that your fw_env.config (Spark7162.tool) u.boot linked not good with this type of receiver !Code:Starting kernel console=ttyAS1,115200 rw root=/dev/mtdblock6 rootfstype=jffs2 init=/bin/devinit coprocessor_mem=4m@0x40000000,4m@0x40400000 printk=1 ip=172.100.100.249:172.100.100.174:172.100.100.174:255.255.0.0:Enigma2:eth0:off stmmaceth=msglvl:0,phyaddr:2,watchdog:5000 bigphysarea=6000 nwhwconf=device:eth0,hwaddr:30:00:0A:00:xx:xx Manufacture=Spark-Project STB_ID=0C:00:0A:00:00:xx:xx - 0x00000000 - 0 ...
considers that ... / dev/mtd0 ... is empty (FF) and u-boot not linked!Code:# Configuration file for fw_(printenv/saveenv) utility. # Up to two entries are valid, in this case the redundand # environment sector is assumed present. # MTD device name Device offset Env. size Flash sector size /dev/mtd0 0x00060000 0x00020000 0x20000
only if start i2s.ko module ... u-boot is linked to /dev/mdt7Code:host135:~# 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"
Let me know if you want to other test ... or correct offset that I should try, because fw_printenv display the bootargs environment!Code:host135:~# 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" mtd7: 00100000 00010000 "uboot"
Ciao ...
what would be the workaround to read the args without opening mtd7 wiht insmod i2s.ko ?
you said there is a working binary in the image - can you provide it to create a tools packages for the admin tool?
thanks, morly
"Every Setback is a Set Up for a Comeback"
Yes ... and I found a correct /dev/mtd7 param offset for all env: Thanks zdzislaw
Code:http://dev.duckbox.info/cgi-bin/cgit.cgi/tdt/commit/?id=4198111557fefb3f05aa1ae03d7d2f6db8ab1690SH4 STB Admin Tool.jpgCode:/dev/mtd7 0x000A0000 0x00020000 0x20000
Now it's up to you ... experts !
Ciao ...
Geändert von arci (02.04.2013 um 21:20 Uhr)