Admin Tool - Bootargs

[zdzislaw22]

@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]

Mit dem GM Triplex schauts gut aus

[morly]

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]

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

SH4 STB Admin Tool.jpg

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

Ciao ...

[morly]

@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]

@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

Reboot for clean and change packet tools:

SH4 STB Admin Tool_new.jpg
Morly_MTD7.jpg


Thanks ... Ciao

[morly]

... not so bad
Thanks for testing!

[arci]

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

Have a good Evening ! ... Ciao

[zdzislaw22]

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]

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