• State
  • Locked Locked
  • Replies 7 replies
  • Subscribers 99 subscribers
  • Views 560 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.

flashing uboot without ccs

shp ma
Prodigy 245 points

Please help me:
now,we can Flashing U-Boot using CCS, but without CCS failed!
We would like to know  whether there is a similar DM6467 tools(sfh_DM646x.exe by UART) to erase u-boot?
Another method,Flashing U-Boot without CCS,we must involves booting from SD card or EMA,
But in previous tests,There is an error(Bad block) when erase nand flash.
Thanks again!
  • 0
    TI__Expert 7765 points

    Are you facing this issue on EVM or DVR or any custom board of DM8168? These is nand_flash_writer utility that can be used to erase and flash nand. Let me know your plaform, we would be able give you that utility and gel file.

     

  • 0 in reply to Yogesh Marathe
    Prodigy 245 points

    Dear Yogesh Marathe,Thank you very much!

    our use EVM of DM8168,i know the tool "nand-flash-writer.out" used by ccs,

    You said tools that nand_flash_writer utility is separate windows program?
    Thanks again!
  • 0 in reply to shp ma
    TI__Expert 7765 points

    No. I'm talking about the same, the one used from CCS.

    If you want to flash nand without CCS you can do so by first booting through SD or UART boot mode. Both of these modes will need uboot images built for that particular boot mode.

     

  • 0 in reply to Yogesh Marathe
    Prodigy 245 points
    Thanks for your quick reply!
    We tried to boot form the SD first,then flash nand uboot. But when erase nand flash at adress 0x0, bad block message display.
    How to solve?
    UART boot must use a hub?why?
  • 0 in reply to shp ma
    TI__Expert 7765 points

    Hi,

    Can you please boot from SD boot mode and execute "nand info" command from console?

    I could not get your question about UART boot mode. You dont need to use any hub there. Just need to transfer images to target using "Xmodem" and "Kermit" with right switch settings and right UART images. Let me know if you dont have steps to boot using UART. Please provide RDK/PSP version you are using.

  • 0 in reply to Yogesh Marathe
    Prodigy 245 points

    hi:

    here is the display information:

    TI8168_EVM#nand info

    Device 0: nand0, sector size 128 KiB
    TI8168_EVM#nand erase 0x0 0x1c0000

    NAND erase: device 0 offset 0x0, size 0x1c0000
    Skipping bad block at  0x00000000
    Skipping bad block at  0x00020000
    Skipping bad block at  0x00040000
    Skipping bad block at  0x00060000
    Skipping bad block at  0x00080000
    Skipping bad block at  0x000a0000
    Skipping bad block at  0x000c0000
    Skipping bad block at  0x000e0000
    Erasing at 0x1a0000 -- 100% complete.
    OK
    TI8168_EVM#

    also ,when write u-boot to nand flash shows error. Similar situation appeared?

    sorry,I made a mistake.I would like to ask that EMac boot need to use a hub there.
    psp-dvr: linux-psp-dvr-04.04.00.01 ,its uboot is work when boot from emac
    uboot version:u-boot-2010.06-psp04.00.01.13.patch1 Provided by ezsdk is Ok.
    Thanks again!
  • 0 in reply to shp ma
    TI__Prodigy 540 points

    Hi,

    -------------------------------

    Flash Bad Blocks

    -------------------------------

    Bad blocks on Flash can be seen due to variety of reasons like:

    (1) Factory Programmed: Bad blocks occurring during manufacturing of Flash device. Such bad-blocks are identified by Flash device manufacturer, and are marked in the flash before shipping the device.

    (2) Wear & Tear:  These bad-blocks occur due to wear and tear of device. Such bad-blocks are usually managed, checked and marked by file-system (like UBIFS) running over the NAND Flash device.

    (3) Multiple read/write errors: Sometime due to improper timing configurations, file-system sees repeated failures occurring on particular blocks. It therefore mistakenly marks them as bad-blocks, so that next time a read/write/erase operation just skips such blocks.

    You can see the bad-blocks already present in NAND using command at UBOOT prompt (with NAND enabled)

    UBOOT>  nand bad

    You can also forcefully delete these bad-block markings (except for factory programmed bad-blocks), using following command. This is particularly useful in case where bad-blocks occurred due to some incorrect configuration (3).

    UBOOT>  nand scrub

    Otherwise, Flash File-System (like UBIFS) will again identify these bad-blocks in next device erase, and mark them again. This way you can know, that bad-blocks are permanent ones, if they re-occur.

    I'm assuming that your NAND Flash device is relatively new, and it might have not worn-out by now.. So you can try above command.

    For you another query, please refer to following links..

    -------------------------------------------

    EMAC Boot (Booting from Network)

    -------------------------------------------

    http://processors.wiki.ti.com/index.php/TI81XX_PSP_UBOOT_User_Guide#EMAC_Boot

    http://processors.wiki.ti.com/index.php/TI81XX_PSP_EMAC_Boot

    http://processors.wiki.ti.com/index.php/TI81XX_PSP_User_Guide#Boot_over_Network_.28Ethernet.29

    with regards, pekon