Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Page 2 of 2 FirstFirst 12
Results 16 to 18 of 18

Thread: Identifying Bootloaders

  1. #16
    Rob van der Does's Avatar
    Title
    ViX Beta Tester
    Join Date
    Apr 2010
    Location
    The Netherlands & France
    Posts
    36,262
    Thanks
    1,720
    Thanked 9,461 Times in 6,675 Posts
    Quote Originally Posted by abu baniaz View Post
    I'd like to disagree with the comments made so far about being unable to display details.
    Reason being is that the text that appears before flashing an image has changed several times. It should therefore be possible to add some text during the boot stage. A simple version description is that is required. Such as "Boot v 2.56"
    All that happens at that stage is done by the bootloader. So if you have any specific wishes, you should ask the box manufacturer.

    Not sure however what the benefit of that would be: you know that you updated the bootloader, and when a new one comes out uou update again; so it provides no real info at all.

    Help asked via PM will be ignored.
    The forum is there for help and all will benefit from your questions.
    NO CARD SHARING TALK WILL BE TOLERATED, LAN OR WAN, IN OPEN FORUM OR PM !

    English is not my native tongue.
    I apologise for all my grammar, spelling and idiom errors.

  2. #17
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,365
    Thanks
    6,445
    Thanked 9,160 Times in 6,235 Posts
    Many thanks. No problem. The success of the Twin is mainly because of the Vix team getting things done. Left to the manufacturer, it would not be where it is now.

    It's not about me, but about the community and other users in general. One person recently said "which suggests I still had {an} old bootloader". Having details displayed would mean that there is no ambiguity. As said before, when in doubt, flash the latest bootloader.

  3. #18
    abu baniaz's Avatar
    Title
    Moderator
    Join Date
    Sep 2010
    Location
    East London
    Posts
    23,365
    Thanks
    6,445
    Thanked 9,160 Times in 6,235 Posts
    Sorrry to drag an old thread....

    Could someone with a few minutes to spare compare the rs232 bootlogs using the bootloader on the Vix site (checksum of cfe.bin 28b962603b47d629cf4fa15d51fd63d0 with the one that 4D (checksum of cfe.bin 77ac0c49036968768e0392dc0432d246) use. I would really appreciate knowing if it is just my receiver that responds differntly.

    I submitted a request to TM to make sure that there is only one bootloader in circulation. I suggested to them that the one that their coders are using is different to the ones that the VIX team and the few other teams are using. This is because the cfe.bin files have different checksums. They said that the reason for the differnt checksums was because of the names in the bin files.

    I also said that there are a few differences, but they said this is not the case.

    I found the following differences on my Twin, (not that I know if there are any implifications). This is a genuine query to see if only my receiver responds differently.

    IQON/4D
    Code:
    Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
    VIX ONE
    Code:
    Detected MIPS clock frequency: 404 MHz (202.499 MHz counter)
    IQON/4D
    Code:
    MEMC-00000001 RW=0000000E WW=00000045 G=00000001 R=00000008 W=00000006 #$
    VIX ONE
    Code:
    MEMC-00000001 RW=0000000F WW=00000041 G=00000001 R=00000008 W=00000006 #$

Page 2 of 2 FirstFirst 12

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.