Create Account
Search
You are here: TDG Forum  >>  Freescale / NXP SOMs and Development Kits  >>  i.MX31 LITEKIT Development Kit  >>   CE Driver issues and LOLO docs

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 26 Mar 2008 12:44 PM by  freem
CE Driver issues and LOLO docs
 6 Replies
Sort:
You are not authorized to post a reply.
Author Messages
freem
New Member
New Member
Posts:


--
25 Mar 2008 10:03 AM
    To Logic

    I need the LOLO 2.4.0 user manual and/or update.

    Question, if I upgrade form LOLO 2.3.5 to 2.4.0 do I need to format the nand, if I am using version 1.4.5 of the yaffs driver and the module is new out of box?

    Issue1:
    I have upgraded to version 2.4.0 and the new drivers(3/18 updates) that are on logic website and all hell has broke out. Windows crashes if I load it from the yaffs partition. If I load it from bootme it works most of the time, still unstable. I have tried this with 4 modules all are doing the same thing. I am still sorting what is happening. When I get more info I will post later.

    Issue2:
    We are loading a bitmap in lolo's config file. This has work just fine. When we upgraded to the IPU driver 1.0.0, and before 3/18 updates, when windows comes up it trashes the bitmap for a couple of seconds.
    freem
    New Member
    New Member
    Posts:


    --
    25 Mar 2008 03:40 PM
    More details on Issue 1

    This is what I have done to the new module
    1) Upgraded lolo to 2.4.0 from 2.3.5
    2) Reset the module
    3) Erase the nand erase /dev/nand0 B0 B4096
    4) Reset the module
    5) Start the network
    6) Run bootme, load the NK.BIN
    7) Run the image, all works
    8) Thru Activesync I load the NK.BIN onto the yaffs drive, all works
    9) Reset module
    10) Create config file
    11) Make config file for autostart
    echo "VOLO add-yaffs ccc nand B0 B4096; mount yaffs /ccc; w /w 0x43fac008 0x0000000c; load bin /ccc/NK.BIN; exec rtc:rtc_imx31_pmic:dbg_serial:IMX31_UART:share_eth:1: \n" /dev/config
    12) Reset module, module crashes just after windows starts

    If I never mount the yaffs drive from LOLO windows will start every time.
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    25 Mar 2008 05:55 PM
    Michael,
    The YAFFS driver's default partition size is from B1 to B4095 (thus 4095 blocks total), not B0 through B4095. Are you building your NK.bin using B0 to B4095 or B1 to B4095?

    If you haven't chnaged the default, try changing your boot script to VOLO add-yaffs ccc nand B1 B4095; mount yaffs /ccc;.... and retry the steps below (do an erase of all first).

    It could be that the partition confusion is causing a crash.

    This was true (default YAFFS blocks) with previous versions of YAFFS, but it could be that some of the updates and fixes made are just enough to make this crash when used incorrectly.

    Thanks,
    -Mike
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    26 Mar 2008 09:17 AM
    Michael,
    Why are you using this (w /w 0x43fac008 0x0000000c;) in your script? This will make the OS fail, the USBF driver will not load correctly and will lock up the system.

    LogicLoader 2.4.0 changes the GPR register (0x43fac008) to 0x00000000, which is important for our hardware set-up.

    Can you let me know if your setting of this register to 0x0000000c is required for what you are doing?

    Thanks,
    -Mike
    freem
    New Member
    New Member
    Posts:


    --
    26 Mar 2008 09:25 AM
    We are using all of the serial ports in our design. Serial2 had a problem, this is the support email I got:

    [Ticket #10619] FW: Serial2 on imx31 SOM does not work
    Quote:
    Mike,
    We recently found that problem as well. It turns out that LOLO is
    improperly initializing the IOMUX register within the IMX31 due to an
    undocumented dependancy in the MX31 reference manual. You can fix this
    by executing this command in LOLO before starting your image:

    w /w 0x43fac008 0x0000000c

    Let me know if this works for you.



    Do I need this now???
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    26 Mar 2008 09:59 AM
    Michael,
    Using 'w /w 0x43fac008 0x0000000c' was to set bit 0 to '0', to fix the UART issue. LogicLoader 2.3.x set this register to 0x0000000d.

    So, moving forward, you can take this out of your script altogether, since LoLo 2.4.0 sets this register to all '0's.

    Bit '2' of this register needs to be set to '0' for USB Function to properly work, which is why your image is locking up.

    We have a PCN that will describe this issue in more detail released very soon to the website.

    I hope this works for you and thanks for your patience.

    Thanks,
    -Mike
    freem
    New Member
    New Member
    Posts:


    --
    26 Mar 2008 12:44 PM
    Thanks Mike for your quick reponse to my problems. I got one module up, so far so good. Will post more on the other 3 if any problems occur. I could use some documentation on the new lolo.
    You are not authorized to post a reply.

    Forums Freescale / NXP SOMs and Development Kits i.MX31 LITEKIT Development Kit