Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09 May 2008 09:55 AM by  richard.laborde@logicpd.com
Is Lolo 2.4 really working ?
 7 Replies
Sort:
You are not authorized to post a reply.
Author Messages

olco



New Member


Posts:
New Member


--
02 May 2008 03:08 AM
    Hi,

    I'm using a imx31 SOM module ( P/N 1006581, silicon rev 1.2 ) with Lolo 2.3.5p

    I have not visible issue with it.

    I tried to use the new version 2.4 ( only to have sd/mmc fatfs access at boot-up ) and now I've got a lot of weird behavours at linux boot :

    - ethernet PMIC and sd/mmc do not initialized well ( randomly )
    - boot sequence lockup

    To summarize :
    - is the new lolo 2.4 compatible with my module ?
    - I buy it in feb 2008, is it normal that I received a pilot version ?
    - I downgrade to 2.3.5 to have a stable working module.


    What can I do to have this module working with the new Lolo 2.4

    Regards
    Olivier

    mikea@logicpd.com



    New Member


    Posts:
    New Member


    --
    02 May 2008 03:50 PM
    LogicLoader 2.4.0 is very stable and works well on our kits, we have done thorough testing and use it with Windows CE. I assume that you are using a patched Linux distribution that may not have been updated based on changes to LogicLoader. It could be that since LogicLoader now uses SD, something your code base is doing is not agreeing with what has been initialized. (SD works fine with WIndows CE, you can test the sample image if you are curious)

    I know of others who are using Linux with LoLo 2.4.0.

    olco



    New Member


    Posts:
    New Member


    --
    02 May 2008 07:29 PM
    Yes, I'm using a 2.6.19.2 patched linux.

    I'm pretty sure, I'm still facing issues without the SD inserted --> I will recheck

    About Linux, What shall I modify in it in order to be compatible with the new Lolo ?

    peter.barada@logicpd.com



    New Member


    Posts:72
    New Member


    --
    05 May 2008 08:46 AM
    What's the part number of the SOM and baseboard?

    I've suscessfully used LoLO 2.4.0 with linux-2.6.19.2 including SD/MMC and PMIC support quite successfully on a 1006581 Rev 1 module on a 1008549 Rev A baseboard.

    olco



    New Member


    Posts:
    New Member


    --
    05 May 2008 03:05 PM
    Hi,

    I'm using
    Module : P/N 1006581 Rev 2
    BaseBoard : 10070520 Rev1

    freem



    New Member


    Posts:
    New Member


    --
    05 May 2008 04:48 PM
    I too ran into a little SD card weirdness and gave up about 5 weeks ago. I was trying to mount a SD card from LOLO to try to boot WinCe.

    ecastelo



    New Member


    Posts:
    New Member


    --
    07 May 2008 11:32 AM
    I am still having issues with Linux booting with USB support. How can i verify that the "overdrive" function of the Lolo 2.4 works.

    I have a 2.0 SOM (model number MIMX31CSOMCR-A)
    Module: 1008130 Rev D
    Baseboard: 1008549 Rev B

    If i boot linux without USB support and then load USB as a module, i can get a usb mouse to work, but i cannot mount a usb drive.

    Any pointers where to look to solve this issue?
    Should i manually set "cpu_freq" or trust that Lolo 2.4 is doing it correctly?

    Thanks
    ecastelo

    richard.laborde@logicpd.com



    Basic Member


    Posts:247
    Basic Member


    --
    09 May 2008 09:55 AM
    escatelo -

    Try using

    w /w 0x53FD0004 0x00010100

    before loading linux with USB enabled. There was a change in the board that was released with the Rev 2.0 silicon. See PCN 377.
    This will switch the default state of those two pins from Inputs to Outputs, and when doing this, the default state of the output is a ‘0’, thus driving ‘low’. This will work and is essentially what we do in the USB driver.

    Thanks
    Richard
    You are not authorized to post a reply.