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.

TMS320C28344: TMS320C28344

Part Number: TMS320C28344
Other Parts Discussed in Thread: CONTROLSUITE, TMS320C28346

Routines found on controlSUITE (controlSUITE\device_support\c2834x\v112\DSP2834x_examples_ccsv4), using CCS 9.3 + complier v18.12.4.LTS and CCS 10 + complier v20.2.2.LTS, there is an error when download to the chip, and the error message is "C28xx: Error initializing flash programming: Interface returned from dll, but flash is not available on this device"

The same routine, using CCS 7.4.0 + complier v16.9.6. LTS, can be downloaded to the chip and run normally。

Is it related to the compiler version? Or is it related to the configurations? What should I do? Thank you in advance!

  • The SME assigned to this is out of the office till 17th March. Please expect a response by 18th of March.

  • I can repeat the error using:

    • A TMS320C320C28346 connected to a XDS100v2
    • A program built with compiler v20.12.0
    • CCS 10.2.0.00009 

    In that get the the following error in the Console when start a debug session:

    C28xx: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.

    However, the downloaded program does reach main and can step in the debugger:

    I suspect the issue is in CCS.

    When you get the error on starting a debug session, does the program reach main and allow you to debug?

  • And loadti.sh also reports the same error but does set the program running, as shown the printf output:

    $ ~/ti/ccs1020/ccs/ccs_base/scripting/examples/loadti/loadti.sh -c workspace_v10/TMS320C28346_hello/targetConfigs/TMS320C28346.ccxml workspace_v10/TMS320C28346_hello/Debug/TMS320C28346_hello.out
    
    ***** DSS Generic Loader *****
    
    START: 22:53:46 GMT-0000 (GMT)
    
    Configuring Debug Server for specified target...
    Done
    TARGET: Texas Instruments XDS100v2 USB Debug Probe
    Connecting to target...
    SEVERE: C28xx: Error initializing flash programming: Interface returned from dll, but flash is not available on this device.
    
    testEnv.outFiles: workspace_v10/TMS320C28346_hello/Debug/TMS320C28346_hello.out
    Loading workspace_v10/TMS320C28346_hello/Debug/TMS320C28346_hello.out
    Done
    Target running...
    Interrupt to abort . . .
    test=5.000000
    

  • What is it mean? Is it related to the version of debug server?

  • Is it related to the version of debug server?

    That is my guess. I hope someone from TI will be able to clarify.

    I could also try different CCS versions to try and find in which version the problem was introduced.

  • What is the use of debug server?

  • Chester,

    If you connect to the device with CCSv10, can you manually load the .out that was build from the older CCSv7 or does it still give this error?

    I'm trying to see if this is tied to the project settings or a function of CCS.  As you said, this device has no flash, so CCS shouldn't be trying to init this DLL anyway.

    Best,

    Matthew

  • If you connect to the device with CCSv10, can you manually load the .out that was build from the older CCSv7 or does it still give this error?

    I went the other way and tried older CCS versions to see at what point the error went away. Attempting to load a simple hello world program into a TMS320C28346 with a XDS100v2:

    • CCS 8.2.0.00007 with Debug Server 8.2.0.1409 and TI C2000 Device Support 4.2.7.0 there is no error.
    • CCS 8.3.0.00009 with Debug Server 8.2.0.201810301800 and TI C2000 Device Support 5.0.0.0 results in the "C28xx: Error initializing flash programming: Interface returned from dll, but flash is not available on this device." error. When manually launching a debug session it is the act of connecting to the target which generates the error, not the loading of the .out file.

    With CCS 10.2.0.00009 confirm that is the act of connecting to the target which generates the error, not the loading of the .out file.

  • Thanks for the detailed debug Chester.  I'm going to pull in the CCS team directly, as they should be able to determine when the change was made and the corrective actions. 

    Best,
    Matthew

  • I filed a bug for this issue. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10267

    Thanks

    ki