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.

sfh_OMAP-L138.exe stop at: Flashing application u-boot-ais.bin (192784 bytes)

Other Parts Discussed in Thread: OMAP-L138, OMAPL138

I cann't write u-boot-ais.bin to my board. 

The step is:

1 build u-boot

2 using AISgen_d800k008.exe and u-boot file to gernate BIN file:u-boot-ais.bin

3 flash to board, the command line is:

   sfh_OMAP-L138.exe -p COM6 -flashType NAND -flash_noubl u-boot-ais.bin

 stoped!!!

the log image is:

is it why? 

who can help me to solved it?

Thanks very much!

  • Hi Changcheng,

    Can you please answer the following questions to help you out.

    1) Is this OMAPL138 EVM board or custom?

    2) If it is custom board, Have you modified the "serial flasher utility" source code as per your custom board?

    http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138#Modifications_for_Custom_Boards

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

    3) Could you able to erase the NAND flash without any problems?

    Ex:

      sfh_OMAP-L138.exe -p COM6 -flashType NAND -erase

  • Hi Titusrathinaraj :

    Thanks very much!

    About your question ,mu answer is:

    1) Is this OMAPL138 EVM board or custom?

    ----->yes

    2) If it is custom board, Have you modified the "serial flasher utility" source code as per your custom board?

    ------>I had mocified all according those documents.

    and the parameter is:

                         DEVICE_PLL0Init(0, 15, 1, 1, 1, 3, 10);

                         DEVICE_PLL1Init(50, 4, 2, 2, 3);

                         DEVICE_ExternalMemInit(0x000000C6, 0x00134A32, 0x16922A09,0x3C0CC722, 0x000492, 0x00000000);

         is it right?

    3) Could you able to erase the NAND flash without any problems?

    ---->FAIL! STOP! the log is:

    What should I do?

    I really need your help! Thanks very much!

  • Hi Changsheng,

    ---->FAIL! STOP! the log is:

    Sorry, I could not see the errors properly from your screen shot.

    Whether it hangs at "Waiting for SFT" of some where else ?

    Can you please take full screen shot of that ?

    Q1) How about your CS signal which is connected to NAND ?

    Q2) What is NAND bus data width 8 bit or 16 bit ?

    Q3) Have you followed the below modifications for NAND in serial flasher source code mentioned by below TI wiki?

    NAND Settings

    • OMAP-L138/Common/include/device_async_mem.h: Modify the #define DEVICE_ASYNC_MEM_NANDBOOT_BUSWIDTH to match the bus width of your NAND

    http://processors.wiki.ti.com/index.php/Serial_Boot_and_Flash_Loading_Utility_for_OMAP-L138#Modifications_for_Custom_Boards

    Q4) What is your reference frequency used through crystal (OSCIN) ?

    Q5)What is your ARM operating frequency ?

    ------>I had modified all according those documents.

    and the parameter is:

                         DEVICE_PLL0Init(0, 15, 1, 1, 1, 3, 10);

                         DEVICE_PLL1Init(50, 4, 2, 2, 3);

                         DEVICE_ExternalMemInit(0x000000C6, 0x00134A32, 0x16922A09,0x3C0CC722, 0x000492, 0x00000000);

    I assume that reference frequency oscillator(OSCIN) is 24MHz.

    From this , I guess ARM is operating at 192MHz and EMIFA is 48MHz    {DEVICE_PLL0Init(0, 15, 1, 1, 1, 3, 10); 

    Is it right ?

  • Hi Changsheng,

    To confirm, you rebuilt the tool after you made the modifications to the source code, correct?

    Thanks,

    Clinton

  • Hi  ClintonRodgers:

    the result is wrong .

    is PPL0 or PPL1 wrong parameters?

     

  • Hi,

    To build SFH (serial flasher utility) source code under Linux as well Windows, Please refer the following TI wiki doc,

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

    Please run starter ware sample NAND code in your board through CCS to ensure/test the NAND functionality of your board (hw &  s/w)

    OMAPL138_StarterWare_1_10_03_03/examples/evmOMAPL138/nand/nandReadWrite.c

  • Hi Titusrathinaraj :

    Thanks very much!

    Q1) How about your CS signal which is connected to NAND ?

    CS3

    Q2) What is NAND bus data width 8 bit or 16 bit ?

    bus dta width is 8 bit

    Q3) Have you followed the below modifications for NAND in serial flasher source code mentioned by below TI wiki?

    yes

    Q4) What is your reference frequency used through crystal (OSCIN) ?

    24MHz

    Q5)What is your ARM operating frequency ?

    360MHz

    is PPL0 or PPL1 wrong?

    Thanks very much!

  • build in windows.

    I can run CCS to write ubl or uboot success.

    But after run through board, nothing can catch in SecureCRT.

    Why?

  • Hi,

    Q1) How about your CS signal which is connected to NAND ?

    CS3

    Q2) What is NAND bus data width 8 bit or 16 bit ?

    bus dta width is 8 bit


    Settings are seems good.

    Q5)What is your ARM operating frequency ?

    360MHz

    is PPL0 or PPL1 wrong?

    PLL0 settings seems wrong,

    PLL0 (phase locked loop)  controller for ARM frequency.

    PLL1 controller for setting mDDR/DDR2 frequency.

    device_PLL0(unsigned int CLKMODE, unsigned int PLLM, unsigned int POSTDIV,unsigned int PLLDIV1, unsigned int PLLDIV2, unsigned int PLLDIV3, unsigned int PLLDIV7 )

    Ex for 456MHz :

        device_PLL0(0,18,0,0,1,18,5); //PLLM = 18, POSTDIV=0 {24MHz * (18+1) / (1+0) = 456}

    To achieve 360MHz:

        device_PLL0(0,14,0,0,1,18,5); //PLLM = 14, POSTDIV=0 {24MHz * (14+1) / (1+0) = 360}

    or

        device_PLL0(0,29,1,0,1,18,5); //PLLM = 29, POSTDIV=1 {24MHz * (29+1) / (1+1) = 360}

    Otherwise use default gel file 300MHz settings for test case at ti/ccsv5/ccs_base/emulation/boards/evmomapl138/gel/EVMOMAPL138_ARM.gel

    After changing those settings , Probe the ARM o/p frequency through CRO and Please let me know the results.

    I can run CCS to write ubl or uboot success.

    In CCS setup, ARM frequency settings through default gel file which is 300MHz & EMIFA 25MHz.

  • Thanks all very much!

    I resolved the problem. It is caused by DDR2 parameters.