CCS/MSP430FR2355: How to Detect or Manually Set Target?

Hi Bryce,

Bryce Nesbitt said:

But how do I set the target type?  In the project properties I've manually entered my part type (MSP430FR2355 on an MSP-EXP430FR2355 ) but literally nothing happens:

For MSP430 devices, the connection type should default to "TI MSP430 USB1". The when you try to debug the project, It should automatically try to launch the debugger for that target and connect to it. But that does not seem to be happening in your case. How are you trying to launch the debugger?

Thanks

ki

Clicking on a project, then properties, gets me to an "Identify" button.
That's how I'm trying to set this up.

If CCS Cloud is running, it errors out.
If CCS Cloud is not running, it times out.
After fresh reboot, no change.

See screenshot:

Bryce Nesbitt said:

If CCS Cloud is running, it errors out.

I would expect this since both CCS Cloud and CCS IDE cannot communicate to the target at the same time

Bryce Nesbitt said:

If CCS Cloud is not running, it times out.

This is also expected. But before it does, it should flash some LEDs on the target. Did you see any LEDs flash?

Thanks

ki

No LED's flash.

I mention CCS Cloud only because it proves the hardware connection is present.

Hi Bryce,

The screenshot you shared of the 'Identify Connection' windows seems normal. However, it is odd that the LEDs do not flash.

Bryce Nesbitt said:

In the project properties I've manually entered my part type (MSP430FR2355 on an MSP-EXP430FR2355 ) but literally nothing happens:

Thanks,

Ghislain

I think this installation may just be horribly broken.  It worked for a while, but won't compile anything now.

The issue with the target seemed to be that CCS was not detecting the target, and everything followed from there.

Now I can't even compile any demo that involves linking.
The Hello World example compiles, but nothing more complicated.

The problem may be installation of MSPWare in ""E:\Program Files\Texas Instruments\ccs\tools", as it seems to choke and try to find "E:\Program " instead.

---------------

**** Build of configuration Debug for project MSP430 TI OutOfBox Demo ****

"E:\\Program Files\\Texas Instruments\\ccs\\utils\\bin\\gmake" -k -j 12 all -O

Building target: "MSP430 TI OutOfBox Demo.out"
Invoking: MSP430 Linker
"E:/Program Files/Texas Instruments/ccs/tools/compiler/ti-cgt-msp430_20.2.1.LTS/bin/cl430" -vmspx --code_model=large --data_model=large --use_hw_mpy=F5 --advice:power="all" --advice:hw_config=all --define=__MSP430FR2355__ --define=_FRWP_ENABLE --define=_INFO_FRWP_ENABLE -g --printf_support=minimal --diag_warning=225 --diag_wrap=off --display_error_number --silicon_errata=CPU21 --silicon_errata=CPU22 --silicon_errata=CPU40 -z -m"MSP430 TI OutOfBox Demo.map" --heap_size=160 --stack_size=160 --cinit_hold_wdt=on -i"E:/Program Files/Texas Instruments/ccs/ccs_base/msp430/include" -i"E:/Program Files/Texas Instruments/ccs/ccs_base/msp430/lib/FR2xx" -i"E:/Program Files/Texas Instruments/ccs/tools/compiler/ti-cgt-msp430_20.2.1.LTS/lib" -i"E:/Program Files/Texas Instruments/ccs/ccs_base/msp430/lib/5xx_6xx_FRxx" -i"E:/Program Files/Texas Instruments/ccs/tools/compiler/ti-cgt-msp430_20.2.1.LTS/include" --priority --reread_libs --define=_FRWP_ENABLE --define=_INFO_FRWP_ENABLE --diag_wrap=off --display_error_number --warn_sections --xml_link_info="MSP430 TI OutOfBox Demo_linkInfo.xml" --use_hw_mpy=F5 --rom_model -o "MSP430 TI OutOfBox Demo.out" "./functiongenerator.obj" "./lightsensor.obj" "./main.obj"

"./driverlib/MSP430FR2xx_4xx/adc.obj" "./driverlib/MSP430FR2xx_4xx/crc.obj" "./driverlib/MSP430FR2xx_4xx/cs.obj" "./driverlib/MSP430FR2xx_4xx/ecomp.obj" "./driverlib/MSP430FR2xx_4xx/eusci_a_spi.obj" "./driverlib/MSP430FR2xx_4xx/eusci_a_uart.obj" "./driverlib/MSP430FR2xx_4xx/eusci_b_i2c.obj" "./driverlib/MSP430FR2xx_4xx/eusci_b_spi.obj" "./driverlib/MSP430FR2xx_4xx/framctl.obj" "./driverlib/MSP430FR2xx_4xx/gpio.obj" "./driverlib/MSP430FR2xx_4xx/icc.obj" "./driverlib/MSP430FR2xx_4xx/lcd_e.obj" "./driverlib/MSP430FR2xx_4xx/mpy32.obj" "./driverlib/MSP430FR2xx_4xx/pmm.obj" "./driverlib/MSP430FR2xx_4xx/rtc.obj" "./driverlib/MSP430FR2xx_4xx/sac.obj" "./driverlib/MSP430FR2xx_4xx/sfr.obj" "./driverlib/MSP430FR2xx_4xx/sysctl.obj" "./driverlib/MSP430FR2xx_4xx/tia.obj" "./driverlib/MSP430FR2xx_4xx/timer_a.obj" "./driverlib/MSP430FR2xx_4xx/timer_b.obj" "./driverlib/MSP430FR2xx_4xx/tlv.obj" "./driverlib/MSP430FR2xx_4xx/wdt_a.obj" "./jsmn/jsmn.obj" "../lnk_msp430fr2355.cmd" -lfrwp_init.a -llibmath.a -llibc.a

<Linking>
warning #10366-D: automatic library build: using library "E:\Program Files\Texas Instruments\ccs\tools\compiler\ti-cgt-msp430_20.2.1.LTS\lib\rts430x_lc_ld_eabi.lib" for the first time, so it must be built. This may take a few minutes.

'e:/program' is not recognized as an internal or external command, operable program or batch file.

>> ERROR: mklib: gmake error during rts430x_lc_ld_eabi.lib build

warning #10207-D: automatic RTS selection: resolving index library "libc.a" to "rts430x_lc_ld_eabi.lib", but "rts430x_lc_ld_eabi.lib" was not found
"../lnk_msp430fr2355.cmd", line 224: warning #10374-D: Interrupt vector "UNMI" does not have an interrupt handler routine.
"../lnk_msp430fr2355.cmd", line 225: warning #10374-D: Interrupt vector "SYSNMI" does not have an interrupt handler routine.
warning #10062-D: entry-point symbol "_c_int00" undefined

undefined first referenced
symbol in file
--------- ----------------
__TI_decompress_lzss
__TI_decompress_none
__TI_int23
__TI_int25
__TI_int27
__TI_int28
__TI_int30
__TI_int31
__TI_int33
__TI_int34
__TI_int35
__TI_int36
__TI_int37
__TI_int38
__TI_int39
__TI_int40
__TI_int41
__TI_int42
__TI_int44
__TI_int45
__TI_zero_init
__mspabi_addf ./functiongenerator.obj
__mspabi_cvtdf ./functiongenerator.obj
__mspabi_divd ./functiongenerator.obj
__mspabi_divf ./functiongenerator.obj
__mspabi_divi ./functiongenerator.obj
__mspabi_divli ./functiongenerator.obj
__mspabi_fixfi ./functiongenerator.obj
__mspabi_fltid ./functiongenerator.obj
__mspabi_fltif ./functiongenerator.obj
__mspabi_fltuf ./functiongenerator.obj
__mspabi_mpyd ./functiongenerator.obj
__mspabi_mpyf ./functiongenerator.obj
__mspabi_slll_3 E:\Program Files\Texas Instruments\ccs\ccs_base\msp430\lib\5xx_6xx_FRxx\MSPMATHLIB_CCS_msp430_5xx_6xx_FRxx_large_code_large_data.lib<msp430_cos_sin.o>
__mspabi_subf ./functiongenerator.obj
memcpy ./functiongenerator.obj
strlen ./main.obj
strncmp ./main.obj
strtol ./main.obj
remark #10372-D: (ULP 4.1) Detected uninitialized Port 2 in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.

remark #10372-D: (ULP 4.1) Detected uninitialized Port 5 in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.
....
remark #10372-D: (ULP 4.1) Detected uninitialized Port E in this project. Recommend initializing all unused ports to eliminate wasted current consumption on unused pins.

>> Compilation failure
makefile:173: recipe for target 'MSP430 TI OutOfBox Demo.out' failed
error #10234-D: unresolved symbols remain
warning #10202-D: no suitable entry-point found; setting to 0
error #10010: errors encountered during linking; "MSP430 TI OutOfBox Demo.out" not built
gmake[1]: *** [MSP430 TI OutOfBox Demo.out] Error 1
gmake[1]: Target 'secondary-outputs' not remade because of errors.
gmake: *** [all] Error 2
makefile:169: recipe for target 'all' failed

**** Build Finished ****

Bryce Nesbitt said:

The problem may be installation of MSPWare in ""E:\Program Files\Texas Instruments\ccs\tools", as it seems to choke and try to find "E:\Program " instead.

Yes, this is likely the problem. CCS is installed in a path with whitespaces. This usually causes issues with building:

https://e2e.ti.com/support/tools/ccs/f/81/t/740719?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

Thanks

ki

Ki said:

Yes, this is likely the problem. CCS is installed in a path with whitespaces. This usually causes issues with building:
https://e2e.ti.com/support/tools/ccs/f/81/t/740719?tisearch=e2e-sitesearch&keymatch=faq%3Atrue

Is in on the schedule to be fixed?
or at the very least to not allow installation into a directory name that can't be supported?

There are no current plans to address the limitation, though I believe there is a plan to warn the user (I actually thought this is already in current versions of CCS already)

Ki said:

There are no current plans to address the limitation, though I believe there is a plan to warn the user (I actually thought this is already in current versions of CCS already

I did not see a warning under the current version.

My user name on Windows has a space in it, so this affects both CCS and the Workspace.

Really: It's not that hard to fix, especially for spaces.  The other special characters like #/\* are potentially harder because TI is incorporating some open source tools that were developed on Unix/Linux first.  But spaces?  That's just a matter of a few small escapes and quotes when shelling out to the build tools.

While CCS/Eclipse itself can handle the whitespaces, it is some of the underlying tools that comes with CCS that has issues with it. I can file bugs against these underlying tools.

I file one against the compiler to handle whitespaces when building the rts lib:

https://sir.ext.ti.com/jira/browse/EXT_EP-10055

Thanks

ki