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.

TMS320F28030: Help with porting ControlSuite sample code (using F2833x) to Piccolo F2803x

Part Number: TMS320F28030
Other Parts Discussed in Thread: CONTROLSUITE

Hi Team,

My customer have a question. Please see details below.
"I am trying to port the TI's ControlSuite's sample code for a single phase grid tied inverter (developed for a TI F2837x controller) to another TI controller (Piccolo F2803x). I tried to include the library files for DSP2803x in my project under Target configurations. However, the code seems to not be downloaded to the target F2803x controller.

My target controller F2803x is connected and shows a successful connection from the 'Test connection' option in the 'Target configurations' window as shown in the attached screenshot labelled 'test_connection.png'.

However, as I try to debug the code CCS gives me the error as follows.

----------------------------------------------------------------------
Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 9.3.0.00042)
-----------------------------------------------------------------------

Can you please help me with how to fix this issue?"



I hope you can help.

Thank you so much.

Gerald

  • Hi Matthew,

    Thank you so much for your help.
    I got a feedback from my customer. He said:
    "I followed the debug manual suggested by MatthewPete.
    I found that the JTAG works fine when I try to load sample codes meant specifically for my desired target microcontroller (TMSF28035).

    It seems like the Target configurations (.ccxml) file from the sample code (for TI F2837x controller) needs to be updated as per F28035 controller.
    Is there any online resource where I can seek guidance from in order to be able to update this .ccxml file?"

    I hope to received your response.

    Thank you and keep safe.

    Gerald

  • Gerald,

    This page shows how to create a new .ccxml file.  Once the customer has created a new .ccxml for the F28035 they can add it to the project.  They will also need to right click on the existing .ccxml that supports the F2837x and "exclude from project".  This should allow the customer to debug launch the project.

    If the above does not work(the exclude/launch), the customer can manually launch the new .ccxml by right clicking on it and "launching target config".  From there they can connect to the target(by right clicking on the C28x core and "connecting") and then manually load the .out from the project under Run->Load Program.

    The above avoids the use of the "debug" hot button which combines several actions into one.  Technically the project does not need to include a .ccxml for compilation; it is just used to auto connect and load.

    Best,

    Matthew

  • Hi Matthew,

    Good day and thank you for response.

    My customer tried the suggestion to create a custom .ccxml file and tried building the code. However, He get the following warnings:
    warning #10373-D: library "../device/driverlib/ccs/Debug/driverlib_coff.lib" contains TI-COFF object files which are incompatible with the ELF output file. Ensure you are using the proper library.
    warning #10373-D: library "../device/driverlib/ccs/Release/driverlib_coff.lib" contains TI-COFF object files which are incompatible with the ELF output file. Ensure you are using the proper library.
    warning #10373-D: library "../device/driverlib/ccs/Debug/driverlib_coff.lib" contains TI-COFF object files which are incompatible with the ELF output file. Ensure you are using the proper library.
    warning #10373-D: library "../device/driverlib/ccs/Release/driverlib_coff.

    After this, he hit debug and CCS crashed. He tried to open CCS again but it won't respond until he restart his computer.

    Can you kindly help?

    Thank you so much.

    Gerald

  • Gerald,

    I'm not sure how changing the .ccxml file triggered this error/warning.  This seems to be related to the recent change we made for newer devices to switch from COFF ABI to EABI format.  This is controlled in the project properties(right click on the project, select properties, then on the general tab and then output format = Legacy COFF or EABI ), but again I'm not sure why the ccxml would have modified this at all.

    F2803x is COFF based only, while F2837x could be either COFF or EABI.

    I would recommend removing the .ccxml file altogether from the project and re-rebuild.  We can use the "target configurations" file to manually connect to the F28035 and then load the .out file.

    If customer has created a new project that is EABI based and he is migrating to the F2803x device he will need to change this setting to Legacy COFF as all the libs for F2803x are built in legacy COFF

    Best,
    Matthew