• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 97 subscribers
  • Views 492 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Download image to NandFlash

michael lee68354
Prodigy 180 points
Other Parts Discussed in Thread: OMAP3530

Hi,all :

         I am a novice , this my first to use OMAP3530, but ran into difficulties.

         I have one development board based on OMAP3530 , board resources including:

                             CPU: OMAP3530

                       Memory: HYHOSQJOMF3P-5L60E-C, including 1Gb NAND Flash and 1Gb mDDR

                       Attention:  no SD/MMC card on board

                      In addition : boot from NandFlash

         There is some image files , including MLO , u-boot.bin , uImage and Angstrom(file system). Now , I want to download these image files into NAND flash. How can I do? Can use what software tools to download these image files?

         For example, In Samsung S3C2440(ARM9), i can use H-jtag and H-flasher software tools to download uboot to NandFlash of 0x0 address, reuse uboot download the kernel image and file system. In OMAP3530, what are the sofrware tool can be used? Hope you can download url and the tool instruction.

  • 0
    Mastermind 9310 points

    Hi,

    The binaries you mention need to be flashed at specific addresses matching partitions defined under your board-specific linux kernel code. Have a look under

    <kernel_src>/arch/arm/mach-omap2/<name_of_your_board>.c

    There should be a structure defining all your partitions in NAND such as follows (for the OMAP3530 EVM ref board):

     static struct mtd_partition omap3evm_nand_partitions[] = {
             /* All the partition sizes are listed in terms of NAND block size */
             {
                     .name           = "xloader-nand",
                     .offset         = 0,
                     .size           = 4*(SZ_128K),
                     .mask_flags     = MTD_WRITEABLE
             },
             {
                     .name           = "uboot-nand",
                     .offset         = MTDPART_OFS_APPEND,
                     .size           = 14*(SZ_128K),
                     .mask_flags     = MTD_WRITEABLE
             },
             {
                     .name           = "params-nand",
                     .offset         = MTDPART_OFS_APPEND,
                     .size           = 2*(SZ_128K)
             },
             {
                     .name           = "linux-nand",
                     .offset         = MTDPART_OFS_APPEND,
                     .size           = 40*(SZ_128K)
             },
             {
                     .name           = "jffs2-nand",
                     .size           = MTDPART_SIZ_FULL,
                     .offset         = MTDPART_OFS_APPEND,
             },
    };
    Starting from there, you know at which adress in NAND your are supposed to flash MLO (xloader-nand), u-boot.bin (uboot-nand), uImage (linux-nand) and the root filesystem (jffs2-nand).
    If you don't have an onboard SDCard connector and no bootloader is currently present on your board (connect a serial cable to your PC and open a terminal to figure out), then you will have to use TI's tools to flash your bootloaders (XLoader and U-BOOT) over USB or serial. Look up for similar threads in this forum for details. Remember that MLO needs to be flashed observing a specific ECC algorithm (detailed in the OMAP3530 datasheet) and U-BOOT with a different ECC algorithm (used by X-Loader).
    Once you get U-BOOT up and running, you can use commands to download uImage and your rootfs from TFTP and flash them into NAND.
  • 0 in reply to Adeneo Embedded support team
    TI__Expert 6735 points

    Michael:

    You should be able to flash x-loader, u-boot and kernel using Flash_v1.4 using USB peripheral boot mode.

    You may need to use the "Custom OMAP35xx" target configuration (configuration_custom_omap35xx.txt) and

    modify it as needed.    At the top of this file (at C:\Program Files\Texas Instruments\Flash v1.4\Targets\Configurations\)

    you find the memory specifications, for example.

    memory NAND    driver Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin parameters gpmc 0x6E000000 cs 0 address 0x28000000 bberase 0
    memory NANDINFO driver Targets\Flash-Drivers\nand_onfi_16bit_8bit.bin parameters gpmc 0x6E000000 cs 0 address 0x28000000 bberase 0 onfi 0 bpp 2048 sbpp 64 ppb 64 bpl 2048 l 1 acv 0x23 f 0x0019

    If your NAND device is ONFI-compliant, check the ONFI Compliant NAND checkbox in Flash Tool.  This would cause the NAND entry above to be used an

    geometry information will be automatically read from the NAND device.  If ONFI is not checked it will use the NANDINFO entry which specifies

    memory parameters explicitly:

    bpp 2048 = 2048 bytes per page

    sbpp 64 = 64 spare bytes per page

    ppb 64 = 64 pages per block

    bpl 2048 = 2048 blocks per logical unit (device)

    l 1 = 1 logical unit

    acv 0x23 =  Address cycle contains two column and three row values

     f 0x0019 = Supported Features code (Bit0 = 1 = 16-bit data bus)

    Modify these as needed to match your memory device.  There are also other entries that are used

    when other ECC modes are used (4-bit BCH, 8-bit BCH, etc.)

    Regards,

    Michael T

    PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

     

  • 0 in reply to Michael T
    Prodigy 180 points

           Thanks for your reply, but i seem to not understand.

           I have downloaded the Flash tool v1.4 from Ti official website , But I will not configure this software tool. Within the software interface, there are several configuration options. How do i configure??

           (1) Choose Target:    ????

           (2) Edit config file:      ???

           (3) Select target connection type:   ????

           (4) Choose the desired memory type:   ????

           (5) Select memory options:  ???

           (6) Choose operation parameters: ????

           (7) offset:  ???

          Resource of  my OMAP3530 development board including :

                 CPU: OMAP3530

               memory:  HYHOSQJOMF3P-5L6OE-C, including 1Gb NAND flash and 1Gb mDDR

           Eagerly look forward to your replay , thanks!!!