Create Account
Search
You are here: TDG Forum  >>  Texas Instruments SOMs and Development Kits  >>  OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit  >>  Linux/DM3730: NAND rootfs image update over OMAPFlashtool v4.2 doesn't work

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 13 Jul 2018 08:54 AM by  Sergey Brandis
Linux/DM3730: NAND rootfs image update over OMAPFlashtool v4.2 doesn't work
 4 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Sergey Brandis
New Member
New Member
Posts:79


--
14 Jun 2018 09:09 AM

    Good afternoon.
    I'm expereiencing some troubles updating bootloaders and rootfs on DM3730.
    First of all - I had to install Windows XP x86 (THIS IS IMPORTANT!) on separate PC for being able just properly connect to my DM3730. It turned out, OMAP Flashtool (v 4.2) works only with WinXP x86.
    But the main issue is that after full chip erase and downloading:

    • MLO (offset 0x0, ECC 1-bit x-loader/u-boot),
    • u-boot.bin (offset 0x8000, NAND ECC),
    • uImage (offset 0x280000, NAND ECC)
    • rootfs.yaffs2 (I was trying different offsets: 0x780000, 0x1b80000 and 1400000, NAND ECC).

    So after thouse manipulations I reboted, set some environments (diff my bootargs with bootargs, generated after run makeyaffsboot command):

    OMAP Logic # setenv kernel_location nand-part
    OMAP Logic # setenv rootfs_location /dev
    OMAP Logic # setenv rootfs_type yaffs
    OMAP Logic # setenv partition nand0,0
    OMAP Logic # setenv mtddevname x-loader
    OMAP Logic # setenv mtddevnum 0
    OMAP Logic # setenv filesize 8E9BCC0
    OMAP Logic # setenv yaffsimage rootfs.yaffs2
    OMAP Logic # saveenv

    After reboot x-loader starts successfully, u-boot starts successfully, Linux kernel starts successfully, but then I got:

    [ 6.520996] devtmpfs: error mounting -2
    [ 6.525268] Freeing init memory: 244K
    [ 6.529571] Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.

    So what's going on? I tried erase each region instead of entire chip, but it gives me error about wrong ECC in debug terminal at u-boot loading stage.
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    13 Jul 2018 07:19 AM
    Sergey,

    I am not familiar with the OMAP Flash tool, so I am not sure I can be all that helpful, but I'll ask for some advice on that.

    If you're seeing ECC Errors, my recommendation would be to erase the chip, then reload U-Boot. The ECC of the X-loader partition is different than the ECC of the rest of the partitions. If you're running makeyaffsboot, you should not make environmental variable changes after that, because the ECC has changed to burn X-Loader, and when you save the environmental variables, the ECC will be wrong. If you need to make changes, reboot to u-boot first, then make the changes and save the variables because the ECC will be correct.

    If you've used LTIB to build the rootfs, I would not expect you to need to make any environment at all, because makeyaffsboot should burn the yaffs partitition and the kernel then set the variables to boot from the yaffs partition it just burned.

    I don't see a full log, it's hard for me to determine of the yaffs partition mounted correctly, but I am guessing it didn't, and it could be because the environment has been corrupted due to ECC issues.

    My recomendation is this,
    From U-Boot:

    nand erase.chip
    reboot
    run makeyaffsboot
    Sergey Brandis
    New Member
    New Member
    Posts:79


    --
    13 Jul 2018 08:19 AM

    Sorry, I forgot to mention that I'm uploading bootloaders and rootfs via USB. I thought it's obvious because of OMAP Flash tool (it's PC software).
    So the problem is that our device is without SD Card (that is the reason why we use OMAP Flash tool), but we still need ability to update.
    So again, my question is: "Is this possible too burn filesystem (rootfs.yaffs2 file) via USB (via OMAP Flash tool) same way as we did it with bootloaders?"
    Adam Ford
    Advanced Member
    Advanced Member
    Posts:794


    --
    13 Jul 2018 08:43 AM
    I will reach out to others to see if they are aware of anything over USB.

    If your board has Ethernet available, you could download the image via Ethernet then burn the image to NAND.

    Depending on your volume, we can create a custom SOM with your images pre-programmed, so you wouldn't need to load them yourselves. I believe there are minimum volume requirements and possibly some NRE, but if you're interested, I can put you in contact with someone.

    adam
    Sergey Brandis
    New Member
    New Member
    Posts:79


    --
    13 Jul 2018 08:54 AM

    Our device have no SD Card neither Ethernet. The only available interface to user is USB. So updates (including filesystem updates) should be done only over USB.
    Okay, thank you, I will try to ask Texas Instruments directly.
    You are not authorized to post a reply.

    Forums Texas Instruments SOMs and Development Kits OMAP35x, DM3730, AM3703 Torpedo SOM Development Kit