• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 83 subscribers
  • Views 861 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.

CCS/TMS320F28335: F28335 problem loading up the program to chip and connectivity issues

Jose alvarez
Prodigy 230 points
Part Number: TMS320F28335

Tool/software: Code Composer Studio

Hello,

I have two problems,

problem 1: I don't understand what this means because this example is from TI (HPVM sensorless example for the F28335) and it is giving me the following error,

Compilation failure

makefile:150: recipe for target 'HVPM_Sensorless_2833x.out' failed

"../F28335_RAM_HVPM_Sensorless.CMD", line 88: error: BEGIN memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 88: error: BEGIN memory range

   overlaps existing memory range BEGIN

"../F28335_RAM_HVPM_Sensorless.CMD", line 90: error: RAMM0 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 90: error: RAMM0 memory range

   overlaps existing memory range RAMM0

"../F28335_RAM_HVPM_Sensorless.CMD", line 92: error: RAML0 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 92: error: RAML0 memory range

   overlaps existing memory range RAML0

"../F28335_RAM_HVPM_Sensorless.CMD", line 93: error: RAML1 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 93: error: RAML1 memory range

   overlaps existing memory range RAML1

"../F28335_RAM_HVPM_Sensorless.CMD", line 93: error: RAML1 memory range

   overlaps existing memory range RAML2

"../F28335_RAM_HVPM_Sensorless.CMD", line 94: error: RAML2 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 94: error: RAML2 memory range

   overlaps existing memory range RAML3

"../F28335_RAM_HVPM_Sensorless.CMD", line 95: error: RAML3 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 96: error: ZONE7A memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 96: error: ZONE7A memory range

   overlaps existing memory range ZONE7A

"../F28335_RAM_HVPM_Sensorless.CMD", line 97: error: CSM_RSVD memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 97: error: CSM_RSVD memory range

   overlaps existing memory range CSM_RSVD

"../F28335_RAM_HVPM_Sensorless.CMD", line 98: error: CSM_PWL memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 98: error: CSM_PWL memory range

   overlaps existing memory range CSM_PWL

"../F28335_RAM_HVPM_Sensorless.CMD", line 99: error: ADC_CAL memory range has

already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 99: error: ADC_CAL memory range

   overlaps existing memory range ADC_CAL

"../F28335_RAM_HVPM_Sensorless.CMD", line 100: error: RESET memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 100: error: RESET memory range

   overlaps existing memory range RESET

"../F28335_RAM_HVPM_Sensorless.CMD", line 101: error: IQTABLES memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 101: error: IQTABLES memory range

   overlaps existing memory range IQTABLES

"../F28335_RAM_HVPM_Sensorless.CMD", line 102: error: IQTABLES2 memory range

   has already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 102: error: IQTABLES2 memory range

   overlaps existing memory range IQTABLES2

"../F28335_RAM_HVPM_Sensorless.CMD", line 103: error: FPUTABLES memory range

   has already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 103: error: FPUTABLES memory range

   overlaps existing memory range FPUTABLES

"../F28335_RAM_HVPM_Sensorless.CMD", line 104: error: BOOTROM memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 104: error: BOOTROM memory range

   overlaps existing memory range BOOTROM

"../F28335_RAM_HVPM_Sensorless.CMD", line 108: error: RAMM1 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 108: error: RAMM1 memory range

   overlaps existing memory range RAMM1

"../F28335_RAM_HVPM_Sensorless.CMD", line 109: error: RAML4 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 109: error: RAML4 memory range

   overlaps existing memory range RAML4

"../F28335_RAM_HVPM_Sensorless.CMD", line 110: error: RAML5 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 110: error: RAML5 memory range

   overlaps existing memory range RAML5

"../F28335_RAM_HVPM_Sensorless.CMD", line 111: error: RAML6 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 111: error: RAML6 memory range

   overlaps existing memory range RAML6

"../F28335_RAM_HVPM_Sensorless.CMD", line 112: error: RAML7 memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 112: error: RAML7 memory range

   overlaps existing memory range RAML7

"../F28335_RAM_HVPM_Sensorless.CMD", line 113: error: ZONE7B memory range has

   already been specified

"../F28335_RAM_HVPM_Sensorless.CMD", line 113: error: ZONE7B memory range

   overlaps existing memory range ZONE7B

error: errors encountered during linking; "HVPM_Sensorless_2833x.out" not

   built

gmake: *** [HVPM_Sensorless_2833x.out] Error 1

gmake: Target 'all' not remade because of errors.

how can I fix this?

Problem two : when verifying the connectivity of the F28335 with the TI development board, it doesn't connect. I have gone to the website (referenced in CCSv6 website) but it continues to give me this issue

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

-----[Print the board config pathname(s)]------------------------------------

C:\Users\alvarezj\AppData\Local\TEXASI~1\

    CCS\ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.

This utility will load the adapter 'jioserdesusb.dll'.

An error occurred while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-151' (0xffffff69).

The title is 'SC_ERR_FTDI_OPEN'.

The explanation is:

One of the FTDI driver functions used during the connect

returned bad status or an error. The cause may be one or

more of: no XDS100 is plugged in, invalid XDS100 serial number,

blank XDS100 EEPROM, missing FTDI drivers, faulty USB cable.

Use the xds100serial command-line utility in the 'common/uscif'

folder to verify the XDS100 can be located.

[End]

I have also tried different cables, ti development boards (TMDSDOCK28335-TMS320F28335), and f28335 chips, is there a special set of sequential steps I need to do to properly upload the ti example code onto the chip via the ti development board so that I can then put the chip into the inverter/motor kit. any ideas on how at least have the ti example connect with the board so I can try out the HVPM kit inverter and motor?

I have uploaded the blinking example for the f28335 and it work well before, so I think this ti example has a bug...any insight on this would be greatly appreacited?

v/r

Jose

  • 0
    Expert 1180 points
    Hi Jose,

    To eliminate first problem double check if there are more than one command linker files active for current debug configuration.
    If so, exclude all but one from the the build.
    The command linker file is one with .cmd extension.

    For the second one it may be that you selected wrong debug device. Are you using standalone XDS100 debugger, or TI development board with integrated debugger? You can select debuggers in target configuration file.

    Going to windows device manager and checking what is the name of the debugger when you connect it to PC might give you an idea if the correct option is selected.

    Hope this gets you started on solving the mentioned issues,

    Ugnius
  • 0 in reply to Ugnius Subacius
    Prodigy 230 points

    Hi Ugnius,

    thanks for your feedback,

    Problem 1:

    Feedback:To eliminate first problem double check if there are more than one command linker files active for current debug configuration.
    If so, exclude all but one from the the build. The command linker file is one with .cmd extension.

    Question: in the files, "F28335_FLASH_HVPM_Sensorless.cmd" & "F28335_RAM_HVPM_Sensorless.cmd.cmd" ,

    In addition to this memory linker command file, add the header linker command file directly to the project. The header linker command file is required to link the

    peripheral structures to the proper locations within the memory map. The header linker files are found in <base>\DSP2833x_Headers\cmd

    For BIOS applications add: DSP2833x_Headers_BIOS.cmd & For nonBIOS applications add: DSP2833x_Headers_nonBIOS.cmd

    using this CCS V6, how do I enable these two files? and how would enabling this files would  clear the error of memory range? what are the steps I need to follow?

    Problem 2:

    Feedback: For the second one it may be that you selected wrong debug device. Are you using standalone XDS100 debugger, or TI development board with integrated debugger? You can select debuggers in target configuration file. Going to windows device manager and checking what is the name of the debugger when you connect it to PC might give you an idea if the correct option is selected.

     Question: yes, I am using the XDS 100 debugger through CCS v6. I verified this by check through the windows device manager (FTDI, on TI XDS 100 Channel B); however, thought properties under general & clicking on the "Verify" button, I get the following

    [Start]Execute the command:

    %ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

    [Result]-----[Print the board config pathname(s)]------------------------------------

    C:\Users\alvarezj\AppData\Local\TEXASI~1\
        CCS\ti\0\0\BrdDat\testBoard.dat

    -----[Print the reset-command software log-file]-----------------------------

    This utility has selected a 100- or 510-class product.
    This utility will load the adapter 'jioserdesusb.dll'.
    The library build date was 'Jul 27 2016'.
    The library build time was '18:31:37'.
    The library package version is '6.0.407.3'.
    The library component version is '35.35.0.0'.
    The controller does not use a programmable FPGA.
    The controller has a version number of '4' (0x00000004).
    The controller has an insertion length of '0' (0x00000000).
    This utility will attempt to reset the controller.
    This utility has successfully reset the controller.

    -----[Print the reset-command hardware log-file]-----------------------------

    The scan-path will be reset by toggling the JTAG TRST signal.
    The controller is the FTDI FT2232 with USB interface.
    The link from controller to target is direct (without cable).
    The software is configured for FTDI FT2232 features.
    The controller cannot monitor the value on the EMU[0] pin.
    The controller cannot monitor the value on the EMU[1] pin.
    The controller cannot control the timing on output pins.
    The controller cannot control the timing on input pins.
    The scan-path link-delay has been set to exactly '0' (0x0000).

    An error occurred while hard opening the controller.

    -----[An error has occurred and this utility has aborted]--------------------

    This error is generated by TI's USCIF driver or utilities.

    The value is '-150' (0xffffff6a).
    The title is 'SC_ERR_FTDI_FAIL'.

    The explanation is:
    One of the FTDI driver functions used during
    configuration returned a invalid status or an error.

    [End]

    I think that the FTDI driver has been installed correctly, right? how should I interpret this error? I think there is a selection in CCS v6 that I need to check, what do u think? any thoughts?

  • 0 in reply to Jose alvarez
    Expert 1180 points
    1. The error is saying that the same memory is linked to system resources multiple times. Meaning that multiple command linker files are present.
    If you have copied in the Bios or nonBios, or selected it through properties, you should exclude others from build. In code composer if any command linker file is present inside the project workspace it will be used in a build. To exclude it you right click it and select exclude from build. Then the icon greys out and has a crossed out symbol. Make sure there is only one command linker file in project workspace that is active for the debug configuration.

    2. It looks like the software successfully communicates to the programmer. However there is a problem communicating with the actual controller.

    *Are you using a development kit from TI or is it a custom built board?
    *Are you powering the controller board you are trying to connect to?
    *When you select the debugger in the target configuration. There should be a list of processors. Is the correct processor selected?

    regards
    Ugnius