PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Admin Tool - Bootargs



morly
29.03.2013, 11:23
Hi Zusammen,
musste feststellen, dass bei einigen Boxen die Bootargs nicht ausgelesen werden.
Ich bitte euch mir kurz zu sagen - bei welcher Box (bitte auch das gebootete Image angeben) die Bootargs mit dem SH4 STB Admin Tool ausgelesen werden, und bei welcher nicht (UFS913 natürlich ausgenommen)

Wenn keine Bootargs angezeigt werden bitte das Tool mit der Box verbinden und im Telnet Tab folgendes ausführen:


cd /tmp/SH4_MORLY
./fw_printenv


Das Ergebnis posten.

Danke, morly

morly
29.03.2013, 11:23
Hier fasse ich dann eure Ergebnisse zusammen um dann Fehler beheben zu können!:



Boxtyp
Image
Bootargs ja/nein
Bemerkungen


UFS910
HDMU
OK

Test by morly, ReWard


SPARK
HDMU
OK
Test by hult


GM990Spark
???
OK
Test by hix


IPBox9000
HDMU und Cuberevo
OK
Test by santa


UFS912
HDMU
NOT - OK
Test by Anskar


Atemio 7500
HDMU
NOT - OK
Test by Surfacedj

ReWard
29.03.2013, 11:37
UFS 910, Bootargs werden angezeigt, Image HDMU.

hult
29.03.2013, 12:55
spark bootargs ok

Nachtrag: HDMU Image

hix
29.03.2013, 13:13
GM990Spark bootargs ok!

santa
29.03.2013, 13:21
IPBox9000 mit HDMU und Cuberevo OK:D

Anskar
29.03.2013, 14:13
Hallo Morly!

Kathrein UFS 912, HDMU im Flash:cool:, es werden im Tool keine Bootargs angezeigt.

Telnetausgabe:


... WELCOME to Morly's box telnet! ...





('-. .-. _ .-') _ _ .-')
( OO ) /( ( OO) )( '.( OO )_
,--. ,--. \ .'_ ,--. ,--.),--. ,--.
| | | | ,`'--..._)| `.' | | | | |
| .| | | | \ '| | | | | .-')
| | | | ' || |'.'| | | |_|( OO )
| .-. | | | / :| | | | | | | `-' /
| | | | | '--' /| | | |(' '-'(_.-'
`--' `--' `-------' `--' `--' `-----'



-----====== HDMU 10790 enigma2 Git 5400 ======-----




BusyBox v1.21.0 (2013-03-23 02:10:16 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

UFS912:~# cd /tmp/SH4_MORLY
UFS912:/tmp/SH4_MORLY# ./fw_printenv
seek error on /dev/i2c-1: Illegal seek
UFS912:/tmp/SH4_MORLY#

MfG

arci
29.03.2013, 14:35
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 !



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#


Ciao ...

Surfacedj
29.03.2013, 16:07
Atemio AM 7500 HDMU 10790

keine Bootargs
-----====== HDMU 10790 enigma2 Git 5400 ======-----




BusyBox v1.21.0 (2013-03-23 04:52:13 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

AT7500:~# cd /tmp/SH4_MORLY
AT7500:/tmp/SH4_MORLY# ./fw_printenv
Can't open /dev/mtd6: No such device

ReWard
30.03.2013, 18:11
Mal noch als Ergänzung zu oben:


Requesting bootargs via LAN...
Bootargs: memory allocate error
Requesting bootargs via LAN...
Bootargs received via LAN

morly
02.04.2013, 12:34
Mal noch als Ergänzung zu oben:


Requesting bootargs via LAN...
Bootargs: memory allocate error
Requesting bootargs via LAN...
Bootargs received via LAN

Hi ReWard,
das ist die Fehlermeldung von der Box - wird hier nur wiedergegeben.
Neustart hilft - dann wieder mehr Saft vorhanden. Du kannst auch e2 beenden bevor du viele Bootargs schreiben möchtest...

morly
02.04.2013, 12:34
Atemio AM 7500 HDMU 10790

keine Bootargs
-----====== HDMU 10790 enigma2 Git 5400 ======-----




BusyBox v1.21.0 (2013-03-23 04:52:13 CET) built-in shell (ash)
Enter 'help' for a list of built-in commands.

AT7500:~# cd /tmp/SH4_MORLY
AT7500:/tmp/SH4_MORLY# ./fw_printenv
Can't open /dev/mtd6: No such device

Thanks - the problem is known - we are currently working on it...

morly
02.04.2013, 12:39
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 !



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#


Ciao ...

sure your bootarg environment is OK?
there seems to be a problem: Bad CRC, ...
could you check it again?

samiherz
02.04.2013, 13:37
hello
can be formatted to create partitions and full backup with sh4 stb admintool


thank you in advance

morly
02.04.2013, 13:42
yes - you can create your partitions,
go to the HDD/Images - Tab and switch to "Manage Partitions" - there you'll find everything you need

regarding full backup: currently not...

samiherz
02.04.2013, 15:52
yes - you can create your partitions,
go to the HDD/Images - Tab and switch to "Manage Partitions" - there you'll find everything you need

regarding full backup: currently not...

Morley thank you for your help


how to format

morly
02.04.2013, 16:00
Manage partitions - there you first have to choose the device (flashdrive, hdd, ...) choose your device

Then you can change the number of partitions - or just use the pre-defined partition table,
double klick on the entries (e.g. filesystem, label, ...) and the changes get indicated properly.
If you are happy with your new layout just press the apply button (green tick) and the tool will do the rest for you...

morly
02.04.2013, 16:01
maybe you understand German better than you can write it - in this case please visit the FAQ's (tbf in my signature) - there santa described everything very well...

solala
02.04.2013, 16:25
hi morly,
bei AV700/7000/7500 und baugleichen kannst das knicken. die haben noch nie bootargs im flash abgelegt und nutzen ausschließlich embedded.
lediglich beim 7500 und baugleichen kann man die embedded bootargs durch einen "saveenv" in der uboot konsole ins flash kopieren und CRCgültig machen.
die im flash befindlichen bootargs haben ab dem zeitpunkt dann vorrang vor den embedded args

arci
02.04.2013, 19:25
sure your bootarg environment is OK?
there seems to be a problem: Bad CRC, ...
could you check it again?

@morly

Amiko Alien 2+ ... Enigma2 bootargs is OK ...



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 ...


I think that your fw_env.config (Spark7162.tool) u.boot linked not good with this type of receiver !


# 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


considers that ... / dev/mtd0 ... is empty (FF) and u-boot not linked!



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"


only if start i2s.ko module ... u-boot is linked to /dev/mdt7



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"


Let me know if you want to other test ... or correct offset that I should try, because fw_printenv display the bootargs environment!

Ciao ...

zdzislaw22
02.04.2013, 20:29
@morly

Amiko Alien 2+ ... Enigma2 bootargs is OK ...



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 ...


I think that your fw_env.config (Spark7162.tool) u.boot linked not good with this type of receiver !


# 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


considers that ... / dev/mtd0 ... is empty (FF) and u-boot not linked!



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"


only if start i2s.ko module ... u-boot is linked to /dev/mdt7



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"


Let me know if you want to other test ... or correct offset that I should try, because fw_printenv display the bootargs environment!

Ciao ...

in spark7162 uboot env can be read only from mtd7 = after insmod i2s.ko ;)

svox
02.04.2013, 20:33
Mit dem GM Triplex schauts gut aus

morly
02.04.2013, 20:40
in spark7162 uboot env can be read only from mtd7 = after insmod i2s.ko ;)

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

arci
02.04.2013, 20:50
Yes ... and I found a correct /dev/mtd7 param offset for all env: Thanks zdzislaw ;)



http://dev.duckbox.info/cgi-bin/cgit.cgi/tdt/commit/?id=4198111557fefb3f05aa1ae03d7d2f6db8ab1690




/dev/mtd7 0x000A0000 0x00020000 0x20000


3775

Now it's up to you ... experts ! :cool:

Ciao ...

morly
02.04.2013, 21:04
@arci: could you please try the new tools archive (just replace the existing one from the Tools folder)
before testing please reboot the box (just in case...) :)

arci
02.04.2013, 21:48
@arci: could you please try the new tools archive (just replace the existing one from the Tools folder)
before testing please reboot the box (just in case...) :)

Like a charm ... @morly :cool:

Reboot for clean and change packet tools:

3783
3784


Thanks ... Ciao

morly
02.04.2013, 21:50
... not so bad ;)
Thanks for testing!

arci
02.04.2013, 22:33
@ morly

If Zdzislaw helps you ... you may make a small script (dd) or better a object code module for u-boot backup (bin format) that would be useful in case of need (TFTP)!

The choice is yours! ...Think about it ... :cool:

Have a good Evening ! ... Ciao

zdzislaw22
02.04.2013, 23:45
Guys,

I strongly advice you to NOT insmod i2s.ko during initial connection to the spark7162 box. Usage of it brakes normal operations and reboot is needed. I would propose to add it when user selects bootargs menu and only after confirmation.

morly
03.04.2013, 13:23
I would propose to add it when user selects bootargs menu and only after confirmation.

yes - this is exactly how it is implemented in 1.2
I stopped loading bootargs by default (user can still activate this option) - and I added a "confirmation dialog" for the spark7162

arci
06.05.2013, 14:38
Hi ... good morning !

Just to know ...

@zdzislaw

Any news on the multiboot management for spark7162?

@ morly

I saw that you added to the confirmation message for reading the bootargs, but you left the old offset of the mtd partition ... in the Spark7162 file tool!

Another thing ... before I try (in safe) ...
I did not understand if ... I can use the write images Enigma 2 function in flash /mtd6 ... with folder /movie support on the USB stick or HDD partition !

thanks

Ciao ...

morly
06.05.2013, 15:02
I saw that you added to the confirmation message for reading the bootargs, but you left the old offset of the mtd partition ... in the Spark7162 file tool!

ups - correct - happened after re-syncing,
the new package can be found in the tool thread...



Another thing ... before I try (in safe) ...
I did not understand if ... I can use the write images Enigma 2 function in flash /mtd6 ... with folder /movie support on the USB stick or HDD partition !

if you want to flash the box there is not enough space in the /tmp file to store the image files.
Therefore I need additional space - so I am using the HDD partition (labeled with: RECORD and containing a movie folder). This partition gets mounted automatically (/etc/fstab) - doesn't matter where the partition (on which device) it is located...

Greetings,
morly

mohamadh
21.10.2013, 23:02
5527

What is this?
my win is 7.
please...

morly
22.10.2013, 06:37
dll's missing,
you have to download the dll pack (also listed in the first post) and place the content of this archive (all dll's) directly in the tools' folder - where the .exe is located

by the way - so less time to say at least hello??!!?? very short for the first post ;)

lct
29.10.2013, 08:36
hi morly,
beim tf7700hdpvr funktioniert das auslesen der bootargs problemlos. Image HDMU 11607
lg