Announcement

Collapse
No announcement yet.

Disp linux

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Disp linux

    Hello,
    Do you have a script to save a config file (.h) on display that could be run on Linux ?
    If you don't, could you explain me the steps to upload a config file ?
    Thx,

  • #2


    The DISP file needs processing before it can be written to the display.

    DISP does produce a file that can be written to the display though. To use that you would need to write some serial commands.

    Easiest to get a windows computer to do it.

    Or maybe run Wine, or VMware
    Mark

    Comment


    • #3


      Yes but we are working on an industrial context.
      It's not easy to plug every uLCD on windows to update orientation.
      Can you tell me what kind of serial commands (SGC) to write to upload the config file on uLCD.

      Comment


      • #4


        DISP outputs three files the .h header file, .4DRom image which can be read by FAT Controller to âsimulateâ a display and the .4DPicasoROM which is only relevant or needed for Picaso Flash updating by SGC commands.



        For Goldelox displays the .4DRom file is in a suitable format for loading into the display as user flash.



        For Picaso displays this is not the case. The .4DPicasoROM file is used for Picaso.



        To load the Rom image onto the display âstandardâ SGC commands are used, changes to fonts take place immediately, whereas most other changes do not take effect until the display is reset. So it is a good thing to reset the display after updating the flash.



        First, the existing user flash needs to be erased, the following sequence is sent:-



        âXâ, 0x80, 0xAA



        The display responds ACK when the flash is erased.



        Then the new user flash needs to be loaded. For the purposes of loading the Rom onto the display it should be considered to be a series of 512 byte âblocksâ, each of which is sent separately using the following sequence:-



        âXâ, 0x40, block#, byte1, byte2, â.., byte512



        The display responds ACK after each block is written.



        The first block is block#0



        FAT Controller can demonstrate this using the âDISP Updateâ button on the âTestsâ tab.
        Mark

        Comment


        • #5


          Thank you, it works.

          Comment

          Working...
          X