Actions
Forum Thread Details
  • Replies 3 replies
  • Subscribers 6 subscribers
  • Views 660 views
  • Users 0 members are here
Related

Sabre Lite Yocto Image & LCD8000-97C

Former Member

Hello,

i am really new to embedded linux so hopefully anybody can give me a hint how to succeed with my problem...

 

I bought the sabre lite board and the  LCD8000-97CLCD8000-97C Since i can´t achive CAN communication with the original demo Image i switch to Yocto core-image-base where i add the CAN stuff

 

Now i have problems to get the  LCD8000-97CLCD8000-97C working I tried to add the uBoot environment vars as descriped in the manual but i think the 6xbootscript override this variables and so i can´t get any output to the lcd display

Is it possible to adopt the bootscript with the Yocto build environment?

 

Or any other suggestions how to get the  LCD8000-97CLCD8000-97C working

 

Many Thanks

Wolfgang 

Parents

  • Jumping in the deep end is very courageous. Embedded Linux is different from what you would expect to find on a normal installation. Most of the "tools" you are used to using either would need to be added, or simply would not be available. Things like sed/awk, and grep for starters. Also it is good to understand the principles of a multi-threaded OS.  I would suggest tracking down a copy of "Running Linux" from O'Reilly.  It has a good description of lots of the innards of the OS and covers many of the connector mechanisms of the OS components.

     

    It might also be a good idea to kind of divorce your thinking from the specific hardware (other than the connections) and consider the programming from the OS level only.  Only deal with actual hardware when you need to manage critical timing and routing of signals to specific channels or registers.  The last is choosing the programming language to use.  I like to do my embedded work in C and not so much C++, because I am an old Assembler hack and it translates better. The key programming element is

     

    #define REG(a)    *((volatile {data type}* const) (a))

     

    where {data type} is whatever data structure you need to include, giving access to the physical memory mapped location of the structure.

     

    Hope this proves helpful,

    Jack

  • in reply to jack.chaney56

    Hi,

    you are right! Embedded Linux is not plug and play image

     

    The good thing is, that the Display works now after modifying and recompiling the 6x_bootscript with Boundary Devices: ARM Single Board Computers - Power over Ethernet Technology

    Now I need to get the tochscreen working, hopefully i can use the patch provided by element 14.....

     

    I also like to programming in C, but sadly I am not familiar with doing this Linux things and I really need to get this running for my job.

     

    Thanks

    Wolfgang

Reply Children
  • in reply to Former Member

    Wolfgang,

    Great to hear you have the screen working, Usually the bugger task, unless you are lucky to find a pre-built driver that doesn't inflict too many rabbit holes to generate your graphics.

     

    For a hint, which you probably already know, "Linux is the same as UNIX". So any books or techniques you may have used under UNIX will work the same on Linux.  Forking to get multiple tasks running, using inter task messaging and semaphores during operations to keep things in sync, and treating everything like a port, either serial or block form.  The biggest differences are the additions to the file manager for logging and data protection.

     

    Jack