Moderator Control Panel ]

Firmware V2.0

A release date? An update? Different versions? ... keep you informed.

Re: Firmware V2.0

Postby ahmedramze » Mon Dec 09, 2013 7:13 pm

Just there is issue on all ver,
problem its

when we do a search on tunner1 there is channels on
vertecal high and low and horizantal high and low
we access only on channels on same group VH or VL for example

need to use 2nd tunner to get the other channels

we did it but by doing two search on same Sat. but using two tunners
but now there is 2 channels one on tunnerA 2nd on tunnerB

Regards
ahmedramze
 
Posts: 20
Joined: Tue Dec 03, 2013 10:16 am

Re: Firmware V2.0

Postby im85288c » Sat Dec 14, 2013 3:44 am

SergioDanielG Wrote:
im85288c Wrote:Hello,

I am also not able to update using a R232 cable. I have followed all the steps, but like fantasticn I cannot see anywhere to input any lines in Tera Term. I even tried with a null modem cable just in case it was that but again that made no difference.

Any tips would be much appreciated or hopefully an alternative upgrade procedure?

Hi im85288c
This is my config in Putty (http://www.putty.org) to connect MOI.
ImageImage
I'd never used Tera Term, but maybe this is util for you.
Regards.

Thank you very much, following your guide I have finally succeeded in updating to the latest firmware :D

Now, I also have an issue of HOW to configure Vdr for a sky uk setup. I only have one dish and the diseq settings are confusing...
im85288c
 
Posts: 2
Joined: Mon Oct 28, 2013 5:19 pm

Re: Firmware V2.0

Postby SergioDanielG » Sat Dec 14, 2013 7:47 pm

im85288c Wrote:Thank you very much, following your guide I have finally succeeded in updating to the latest firmware :D

Now, I also have an issue of HOW to configure Vdr for a sky uk setup. I only have one dish and the diseq settings are confusing...

If you have only one dish with one lnb selec diseqc 1.0 and port 1, then scan.
Regards
SergioDanielG
 
Posts: 356
Joined: Tue May 31, 2011 3:53 am
Location: Tostado (SF) Argentina

Re: Firmware V2.0

Postby im85288b » Mon Dec 16, 2013 5:35 pm

SergioDanielG Wrote:
im85288c Wrote:Thank you very much, following your guide I have finally succeeded in updating to the latest firmware :D

Now, I also have an issue of HOW to configure Vdr for a sky uk setup. I only have one dish and the diseq settings are confusing...

If you have only one dish with one lnb selec diseqc 1.0 and port 1, then scan.
Regards


Thank you SergioDanielG, I followed your instructions and made some decent progress...however I think (and this is using v2.02) there is a bug with the scan function of VDR against the Eutelsat 28.2 satellite. After completing a scan of the satellite it only put about 20 channels into channels.conf and also they are being output into this file in a format that does not allow me to create/download someone else's channels.conf to use instead. I confirmed this by ssh into the moi box and running the scan command myself such as: scan -o vdr -v /usr/share/dvb/dvb-s/Eutelsat\ 28A,\ Astra\ 1N,2A,2F
> /etc/vdr/channels.conf which Does find all of the channels but the output is what I call standard and cannot be used by VDR on the MOI.

If you scan using the button "scan channels" the channels in channels.conf look like this:

Channel 4;BSkyB:12265:hC34M2O35S0:S28.2E:27500:2315:2316=eng,2317=NAR:2318:0:9211:2:2029:0
Channel 4;BSkyB:12265:hC34M2O35S0:S28.2E:27500:2327:2328=eng:2329:0:9212:2:2029:0

However when this is done by the scan command as above (which retrieves all my channels) the output is like:

Channel 4;BSkyB:12265:h:S28.2E:27500:2315:2316=eng,2317=NAR:2318:0:9211:2:2029:0

The part highlighted in bold is different and from what I have read it is not correct format for numbers to follow the polarisation...I would not really mind if it scanned all my channels...but something is really strange here.

I tried this on two separate MOI boxes and experienced the same problems.

It's a shame as VDR performance on XBMC seemed to be very good, any help is much appreciated
im85288b
 
Posts: 5
Joined: Sat Dec 14, 2013 11:30 pm

Re: Firmware V2.0

Postby im85288b » Sun Jan 12, 2014 3:37 am

Does anybody know how to get support on this product from TBS? I have posted the problems above both on this forum and directly to customer support. Surely it should not take well over a month to even respond?
im85288b
 
Posts: 5
Joined: Sat Dec 14, 2013 11:30 pm

stock on can't get kernel image!

Postby celevra » Fri Jan 24, 2014 3:02 am

Code: Select All Code
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:  3781MB
NAND:    256 MB


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

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

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

** Unable to read "MOI2900_k.bin" from mmc 0:1 **
Partition1: Start Address(0x2000), Size(0x760c00)
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 : 46200000
The input address don't need a virtual-to-physical translation : 462b8000

103532352 bytes read

NAND erase: device 0 offset 0x50c0000, size 0xaf40000
Skipping bad block at  0x05620000
Skipping bad block at  0x07760000
Skipping bad block at  0x09820000
Skipping bad block at  0x0b480000
Skipping bad block at  0x0ba20000
Erasing at 0xffe0000 -- 100% complete.
OK

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

Bad block at 0x5620000 in erase block from 0x5620000 will be skipped
Bad block at 0x7760000 in erase block from 0x7760000 will be skipped
Bad block at 0x9820000 in erase block from 0x9820000 will be skipped
Writing data at 0xb0de000 -- 100% complete.
 103532352 bytes written: OK

NAND read: device 0 offset 0x48c0000, size 0x400000
Main area read (32 blocks):
 4194304 bytes read: OK
get_format
-------- 0 --------
Wrong Image Format for bootm command
ERROR: can't get kernel image!
MOI2900 #



what can i do?
is there a way to flash the kernel separately?

/* EDIT */
flashing 2.0.1 and then 2.0.2 solved my problem
celevra
 
Posts: 3
Joined: Fri Jan 03, 2014 11:25 pm

Previous

Return to Announcements

Who is online

Users browsing this forum: No registered users and 2 guests