• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 546 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.

flashburn problem

shimon akrish
Prodigy 110 points
Other Parts Discussed in Thread: TMS320DM6437

hello

I'm using the TMS320DM6437 EVM, and developing in CCS v3.3 + flashburn DSK v3.11

when I work in  CCS every thing works fine.

but when I'm trying to burnflash it, as writen in the instruction it just doesn't work

it seems every thing is fine, it is erasing and programing and I can see the memory but even a simple example like blinkingLed doesn't work when I burn it...

when I burn the dm6437_demo.hex it works fine

I am using the hexAIS to convert from .out -> .hex

one thing i have noticed that the demo "dm6437_demo.hex" is 4M when my program is much bigger and after the convert wights only 1M

I have investigated in forums and FAQ the flushburn to no success, maybe can some one help me here...

 thank you

  • 0
    Expert 1650 points

    Hi shimon

    I had a lot of problems with flashburn, but most case was the configuration of the DDR. Check the configuration in your code, the gel file and the .dll than build the hex file!

    Marcio

  • 0 in reply to Marcio
    Intellectual 645 points

    Hi Marico

    I am also havin the same problem like shimon, But i have check all the Configurations and memory but i have one more problem  , Shimon mentioned his dm6437_demo.hex is running properly, But i can able to flash the program using the flash burn utility but it is not working properly......

     

  • 0 in reply to shan54218
    Expert 1650 points

    Hi shan

    Are you using TMS320DM6437 EVM?
    If yes, check the SW2, SW1 and JP2!
    In the FlashBurn, can you read the values into the flash?

  • 0 in reply to Marcio
    Prodigy 110 points

    Hi Marcio


    can you please be more specific about what should be the DDR configiration and the Gel?

    i have the standard evmdm6437.gel v 1.03.

     thank you


  • 0 in reply to shimon akrish
    Expert 1650 points

    Hi shimon!

    We have the own board here, and we had a lot of problems of configuration to burn the program into the NOR/ NAND.
    The most of problem was the DDR configuration (the SDBCR register).
    The SDBCR register are into the evmdm6437_ddr.c file, .gel and the DM643X (configuration setting into the hexAIS folder).
    The another problem we had was memory map and PINMUX configuration.

    I hope these "tips" help you!

  • 0 in reply to Marcio
    Expert 1650 points

    Just a question, shimon, do you initialize the board in your code? Like EVMDM6437_init( ).
    Because if you debug your program without this initialization and with .gel, it works! But not work into the NOR.

  • 0 in reply to Marcio
    Prodigy 110 points

    yes I'm initializing the board:

    void main() {
    //initialize the board ,dip sitches
        EVMDM6437_init();
        EVMDM6437_DIP_init();
        printf("Video Preview Application\n");
        fflush(stdout);

        /* Workaround to BIOS/LOG issue: SDSCM00013785 */           
        TRC_disable(TRC_LOGCLK);

        /* VPSS PinMuxing */
        /* CI10SEL   - No CI[1:0]                       */
        /* CI32SEL   - No CI[3:2]                       */
        /* CI54SEL   - No CI[5:4]                       */
        /* CI76SEL   - No CI[7:6]                       */
        /* CFLDSEL   - No C_FIELD                       */
        /* CWENSEL   - No C_WEN                         */
        /* HDVSEL    - CCDC HD and VD enabled           */
        /* CCDCSEL   - CCDC PCLK, YI[7:0] enabled       */
        /* AEAW      - EMIFA full address mode          */
        /* VPBECKEN  - VPBECLK enabled                  */
        /* RGBSEL    - No digital outputs               */
        /* CS3SEL    - LCD_OE /EM_CS3 disabled           */
        /* CS4SEL    - CS4/VSYNC enabled                */
        /* CS5SEL    - CS5/HSYNC enabled                */
        /* VENCSEL   - VCLK,YOUT[7:0],COUT[7:0] enabled */
        /* AEM       - 8bEMIF + 8bCCDC + 8 to 16bVENC   */
        sysModuleRegs -> PINMUX0    &= (0x005482A3u);
        sysModuleRegs -> PINMUX0    |= (0x005482A3u);

        /* PCIEN    =   0: PINMUX1 - Bit 0 */
        sysModuleRegs -> PINMUX1 &= (0xFFFFFFFEu);
        sysModuleRegs -> VPSSCLKCTL = (0x18u);
        return;
    }

  • 0 in reply to shimon akrish
    Expert 1650 points

    Hi shimon!

    Do you know about a code to initialize  the program? Like boot.obj or bootstrap? This code initializes the program, there is one into the rts64plus.lib!

  • 0 in reply to Marcio
    Prodigy 110 points

    Marcio thank you very much

    I have manged to solve the problem by editing my initialization code of the pinmux

    from:

    sysModuleRegs -> PINMUX0    &= (0x005482A3u);
     sysModuleRegs -> PINMUX0    |= (0x005482A3u);
       
    sysModuleRegs -> PINMUX1 &= (0xFFFFFFFEu);

    to:

    sysModuleRegs -> PINMUX0 = 0x00548551;
    sysModuleRegs -> PINMUX1 = 0x02A00140;

     

    I have generated PINMUX0,1 by using DM643x  Pin Mux Utility.exe

    now it works fine

    thank you all for your help