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.

Flash over SCI ok, but then processor wont startup

Other Parts Discussed in Thread: TMS320F28032, UNIFLASH

Hi alls,

i used c2Prog from codeskin to flash my device(TMS320f28032) via SCI, the status of the flashing procedure says:  programming...ok

But when i set the Boot Setup pins back to boot from flash and power up the device nothing happens ? (i should see on our custom board some Led's blinking, when i flash over Jtag everything works fine)

What could i have missed ?

thx in advance

  • Hi Stefan,

    When you flash from JTAG, the 'out' file  is same right? After flashing it from JTAG did you do multiple resets? Every time LEDs blink?

    Also, just go through this guide: 7711.0728.C2Prog.pdf

    Regards,

    Gautam

  • I used the .hex file generated in CCS via post-build-steps 

    command line looks like this :

    "${CG_TOOL_HEX}" -i "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.hex" -order MS -romwidth 16

     for jtag flashing i use CCS because i think my Jtag-adapter is not supported by c2prog.

  • Dear Mr. Fischer,

    Generating the .hex file via the post-build steps should work fine.  However, can you try using the hex2000 utility with the parameters mentioned in chapter 2.2 of the guide that Gautam linked? 
    (I'm wondering if some of your post-link parameters need to be adjusted).

    If that doesn't work, can you let me understand how you are programming via JTAG with CCS?  Are you programming via CCS, halting the debug session, and then power cycling the baseboard while in boot-to-flash mode? 
    (or are you programming and then running directly from CCS?)


    Thank you,
    Brett

  • Hi Brett and others,

     I programm and run from ccs.

    after further investigation i checked to program an ti example( flash example from tidcs) to our board via c2Prog and this works fine i see GPIO34 toggling after reset.

    The question now is why does our custom software not run when programmed over SCI?

    I suspect that it has something to do with our "special" .cmd file. 

       

  • Hi, 

    im investigating further on because we need a working system for production line.

    My next attempt was to use the Uniflash Tool from Ti. Now when i flash the generated .hex file via jtag i have the same issue, processor wont startup. 

    But when i use the .out  file to flash the Device via Uniflash it works fine. 

    So where is the difference between my .out file and the generated .hex file ?

    (for now our workarround will be to buy some xds100rets  and flash the .out files in production line with Uniflash)  

    Although It would be nice to solve this issue 

  • I found the Solution :) 

    So here we go, we use the ability to copy compiler sections from flash to RAM in our Software (http://www.ti.com/lit/an/spraau8/spraau8.pdf) therefore we have another code entry point thus we need to set this new entry Point for Hexfile generation.

    the new pre-Compile-Step command line looks like :

    "${CG_TOOL_HEX}" -i "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.hex" -order MS -romwidth 16

    -e codestart

    with -e you can set the name of your entry point which is used in CodeStartBranch.asm.

    Now i can flash my .hex file with c2Prog and also Uniflash. Thanks and have a nice Day   

  • Thats Great!

    Goodluck & Regards,

    Gautam