Page 2 of 3

Re: Firmware V2.0

PostPosted: Tue Dec 03, 2013 10:38 pm
by fantasticn
Hi SergioDanielG,

thanks for the hint and also the video. I bought the cable (and also the USB-to-COM-Adapter) just for the purpose of updating the MOI. The Cable was adverstised as a "Modem Cable". However, it looks like I have to try another one then.

However, I hope that TBS will find an easier way for updating this device in the future - and also a slightly better documentation of some tricky things, like the time-zone settings or including a network path for recording etc. Currently it seems like this device is only made for Linux-Nerds.

Once again thanks for your support. I will post if it worked after I have bought myself another RS232-Cable.

Brgds,

FantasticN

Re: Firmware V2.0

PostPosted: Wed Dec 04, 2013 12:44 am
by SergioDanielG
Hi FantasticN.

I don't know TBS plans, but MOI configuration web page have a page to update, nos usable in all cases yet (I think). And if you consider most dvb receiver have rs232 interface to upgrade firmware and others haven't got rs232 but have jtag (Jtag is more dificult)... well... we, better, can forget that.

I have other things maybe can help you, but only in spanish, I'm sorry.

This video about how to configure MOI and TVHeadend
https://www.youtube.com/watch?v=uy7aMbYi0Fo
And in FTATV forum, with a lot of images.
http://www.ftatv.org/foro/viewtopic.php ... 13&start=0

Regards.

Re: Firmware V2.0

PostPosted: Wed Dec 04, 2013 10:17 am
by ahmedramze
How to config oscam to read from PCMCIA CAMs, and is there is manual for it

files in /usr/local/etc/
oscam.config
oscam.server

were is the location of OSCAM.user

Ahmed

Re: Firmware V2.0

PostPosted: Wed Dec 04, 2013 3:17 pm
by fantasticn
Hi SergioDanielG,

you are right in saying that there are some other DVB-receivers with RS232-interface. However, those are standalone devices based on a very old-fashioned concept and the outdated idea of working totally autonomous. The MOI is supposed to be modern network device, since in most of the modern homes you will find a network consisting of several devices like PCs, Tablets, Smartphones etc. And the MOI is supposed to supply those devices with Satellite Television via network. So it should be able to update it same way - via network, or at least via its built-in USB- or SD-interface. Have a look at all the other modern network devices like Routers, NAS, FritzBox etc.: You can handle everything through the (mostly self-explaing) webinterface - even the update procedure - and you do not need any Linux experience for it.

Thanks for providing those videos and screenshots. Though I am already familiar with the TBS-webinterface and also the configuration with TVheadend I think it is very useful for other users. As I said, the MOI is constructed as a device for nerds. I do not think I could recommend buying one e.g. to my paraents or anybody else who is not really into PC technology. You even should be able to handle some Linux basics (which is my blind spot) otherwise you will not understand the answers you get in the support forum.

Sorry, I do not speak spanish (or at least not enough to have techniqual conversations). I could offer German instead :-)

Brgds,

FantasticN

Re: Firmware V2.0

PostPosted: Wed Dec 04, 2013 10:15 pm
by apol
Hi all
sorry for my english is not my first language;)

the problem what i have with MOI after upgrae to 2.0 or 2.0.1 :

i follow the instruction how to upgrade from 1.2.1
copied file to microSD card
conected RS

typed 2 setevn command then save and "re" after this i got: log

OK

U-Boot 1.3.4 (Mar 7 2013 - 16:38:41) for MOI2900


CPU: S5PV210@1000MHz(OK)
APLL = 1000MHz, HclkMsys = 200MHz, PclkMsys = 100MHz
MPLL = 667MHz, EPLL = 80MHz
HclkDsys = 166MHz, PclkDsys = 83MHz
HclkPsys = 133MHz, PclkPsys = 66MHz
SCLKA2M = 200MHz
Serial = CLKUART
Board: MOI2900
I2C: i2c1_init GPD1CON
ready
DRAM: 512 MB
Flash: 8 MB
SD/MMC: 7580MB
NAND: 256 MB


start normally!
MAC address: 00:22:ab:80:04:38
In: serial
Out: serial
Err: serial
checking mode for fastboot ...
Hit any key to stop autoboot: 0
MOI2900 # setenv loadmmcfs 'fatload mmc 0:1 40000000 MOI2900_fs.bin'
MOI2900 # setenv updatekfs 'nand erase 50c0000;nand write.yaffs 40000000 50c0000 ${filesize}'
MOI2900 # save
Saving Environment to SMDK bootable device...
Erasing Nand...
Writing to Nand...
Saved enviroment variables
MOI2900 # re
reset...

OK

U-Boot 1.3.4 (Mar 7 2013 - 16:38:41) for MOI2900


CPU: S5PV210@1000MHz(OK)
APLL = 1000MHz, HclkMsys = 200MHz, PclkMsys = 100MHz
MPLL = 667MHz, EPLL = 80MHz
HclkDsys = 166MHz, PclkDsys = 83MHz
HclkPsys = 133MHz, PclkPsys = 66MHz
SCLKA2M = 200MHz
Serial = CLKUART
Board: MOI2900
I2C: i2c1_init GPD1CON
ready
DRAM: 512 MB
Flash: 8 MB
SD/MMC: 7580MB
NAND: 256 MB


start normally!
MAC address: 00:22:ab:80:04:38
In: serial
Out: serial
Err: serial
checking mode for fastboot ...
Hit any key to stop autoboot: 0
Partition1: Start Address(0x2000), Size(0xecc000)
reading MOI2900_k_bk.bin

** Unable to read "MOI2900_k_bk.bin" from mmc 0:1 **
Partition1: Start Address(0x2000), Size(0xecc000)
reading MOI2900_fs_bk.bin

** Unable to read "MOI2900_fs_bk.bin" from mmc 0:1 **
Partition1: Start Address(0x2000), Size(0xecc000)
reading MOI2900_k.bin

** Unable to read "MOI2900_k.bin" from mmc 0:1 **
Partition1: Start Address(0x2000), Size(0xecc000)
reading MOI2900_fs.bin
The input address don't need a virtual-to-physical translation : 40000000
The input address don't need a virtual-to-physical translation : 41fffe00
The input address don't need a virtual-to-physical translation : 43fffc00
The input address don't need a virtual-to-physical translation : 45fffa00
The input address don't need a virtual-to-physical translation : 46170000

102199680 bytes read

NAND erase: device 0 offset 0x50c0000, size 0xaf40000
Skipping bad block at 0x06440000
Skipping bad block at 0x06d40000
Skipping bad block at 0x08c20000
Skipping bad block at 0x08f20000
Skipping bad block at 0x09200000
Skipping bad block at 0x0c680000
Skipping bad block at 0x0c860000
Skipping bad block at 0x0f640000
Erasing at 0xffe0000 -- 100% complete.
OK

NAND write: device 0 offset 0x50c0000, size 0x6177180

Bad block at 0x6440000 in erase block from 0x6440000 will be skipped
Bad block at 0x6d40000 in erase block from 0x6d40000 will be skipped
Bad block at 0x8c20000 in erase block from 0x8c20000 will be skipped
Bad block at 0x8f20000 in erase block from 0x8f20000 will be skipped
Bad block at 0x9200000 in erase block from 0x9200000 will be skipped
Writing data at 0xafe2800 -- 100% complete.
102199680 bytes written: OK

NAND read: device 0 offset 0x48c0000, size 0x400000
Main area read (32 blocks):
4194304 bytes read: OK
Boot with zImage

Starting kernel ...

Uncompressing Linux... done, booting the kernel.



Welcome to Moi
Moi login:



after this MOI boot ok can connect to WEBinterface but only at 192.168.1.188 service like VDR or VDRadmin not running tvheadend not running

canot connect to 192.168.1.188:8001 nothing happens timed out

on WEBinterface i see still version 1.2.1 what is this? and how to do proper update

Have try to connecting thru XBMC to MOI without success ( vdr not running)

dmesg log http://pastebin.com/VsYVWNV2

Re: Firmware V2.0

PostPosted: Thu Dec 05, 2013 1:15 am
by SergioDanielG
apol Wrote:Hi all
sorry for my english is not my first language;)

the problem what i have with MOI after upgrae to 2.0 or 2.0.1 :

i follow the instruction how to upgrade from 1.2.1
copied file to microSD card
conected RS

typed 2 setevn command then save and "re" after this i got: log

...
after this MOI boot ok can connect to WEBinterface but only at 192.168.1.188 service like VDR or VDRadmin not running tvheadend not running

canot connect to 192.168.1.188:8001 nothing happens timed out

on WEBinterface i see still version 1.2.1 what is this? and how to do proper update

Have try to connecting thru XBMC to MOI without success ( vdr not running)

dmesg log http://pastebin.com/VsYVWNV2


Hi apol.
Please verify all. If web interface say version 1.2.1, your MOI is not updated to 2.0.x
Try again using an empty SD card and copy again all files to upgrade.

Regards

Re: Firmware V2.0

PostPosted: Thu Dec 05, 2013 5:38 am
by ahmedramze
Hello

after upgrade you need to select whcih service to start , TVHeadend or VDR the defulat setting its off for both , login using MOI ip for ex http://192.168.1.188 with out any port

then go to MOI setting then select the main service and reboot it , like picture below

MOI.PNG
MOI



after that you can login using http://192.168.1.188:9981/

Re: Firmware V2.0

PostPosted: Thu Dec 05, 2013 5:39 am
by ahmedramze
on issue in upgrade , need to Delete files from memory card , if not , each start-up will do upgrade and reset config.

Re: Firmware V2.0

PostPosted: Sat Dec 07, 2013 8:27 am
by apol
after try 10micro sd card old one 1gb sandisk worked out;)
now with 2.0.1 thx

ok
now maybe any detailed workflow howto setup scan with vdr channels then setup oscam or other cam

Re: Firmware V2.0

PostPosted: Mon Dec 09, 2013 3:06 pm
by fantasticn
Hi SergioDanielK,

just wanted to give you a brief feedback: With a new cable and setting the serial speed to 115200 the updated went well. Thanks for the hint.

Now I am a little puzzled as to configuring the VDR-Section (no manual for that). I tried Astra and activated VDR-client on one of my XBMC-machines, but I did not get anything. Also it seems that VDR can target not more than one Satellite per DVB-S-receiver, while I am targeting Astra and Hotbird. So it seems I am staying with TVheadend not sure what the update gained me then.

However, now I am on 2.0.1 and hoping that future updates can be done easier and TBS will introduce new features/functions with a little bit more explanation.

Best reagrds,

FantasticN