Admin Tool - Bootargs

[morly]

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]

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]

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]

hello
can be formatted to create partitions and full backup with sh4 stb admintool


thank you in advance

[morly]

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]

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]

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]

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]

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]

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