CCS/MSP432P401R: Apparently misplaced file

Hello,

Tuatha De said:

Having loaded the ‘blinkled’ demo I can get it to load and run on the 432 Rev 2.1 launchpad but when I stop, reset the 432 and then single step through the program I only get to shutting down the watchdog timer:

Are you doing a CPU reset and then restart to get back to main, then single stepping? Can you describe exactly in details what action you did? I am trying to reproduce this using the same example and launchpad, but I am unable to reproduce.

Tuatha De said:

"Can't find a source file at "/run/shm/bazel-sandbox.50f2f2e12d21e0fb3bbe0ab1cf1c78eb/1214578678737256234/execroot/__main__/source/ti/devices/msp432p4xx/driverlib/wdt_a.c" 

Tuatha De said:

That requester has a ‘find file’ click-on and using it shows the file generally located in CCS but I do not see the specific file

That file (wdt_a.c) is part of the driverlib library that the example links in. The above path is the original location of that source file when the library was built. You should be able to browse to your copy in <simplelink dir>/source/ti/devices/msp432p4xx/driverlib to get source level debug in that source file.

Tuatha De said:

There is no clarity on what to do to correct this and CCS will not single-step forward without this correction.

Not finding the source file is a debugger visibility issue but it should not impact the execution of the application. There looks like some other issue here. If you terminate the debug session and start again, does it run ok?

Thanks

ki

Hi Ki:

wdt_a.c, the file described as not in the right path by CCS is at the bottom of the 'keil' folder in the 'driver lib' and wants to stay there. Is that where it should be?

Now a new one. after shutting off CCS and turning it back on I have a new requester that pops up when I hit the 'debug' bug, it says:

"An internal error has occurred.

The selected element org.eclipse.debug.ui.DebugView=org.eclipse.e4.ui.model.application.ui.advanced.impl.PlaceholderImpl@2db33feb (tags: [View, categoryTag:Debug], contributorURI: null) (widget: null, renderer: null, toBeRendered: false, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (closeable: true) must be visible in the UI presentation"

Then it tells me I have to shut down any program running on the launchpad, which I do not show the controls for in the line with the little hammer.

Hitting 'continue' to load the launchpad anyway results in the old program shutting down but no 'Start or Stop or Terminate' symbols appear and the new program does not seem to load or begin running.

Then if I shut CCS down the launchpad starts running the new timing I set in the program so the new program loaded I just had no symbols to run it from. I cannot tell if I can operate 'single-step' as there are no arrows for that in the bar either.

Thanks

Tuatha

Another couple of hints: The 'Console' has disappeared and does not tell me of a successful build or anything at all now, it disappears but seems to flash a couple of times during a build but then disappears and can be re-appeared by clicking on 'Console' in the top bar that has 'main.c' in it. If I slightly modify the pgm. and rebuild the console disappears again. Until the debug arrows and symbols disappeared 'console' worked normally.

In the 'debug' panel there is a pair of lines beneath the "Texas Instruments XDS110 USB Debug Probe......
Both lines have three blue bars to the left of them.

The first line says:

main() at main.c:59 0x0000019E

and the second line

_c_int00)_n_noint_noargs() at boot_cortex_m.c: 133 0x000001EA (_c_int00_noinit_noargs does not contain frame information)

For unknown reasons The 'Run, stop, terminate' and 'single step' arrows have reappeared when 'debug' is started and they seem to work normally after I go through the same set of warnings and problem requesters which have not changed.

If I breakpoint the CPU and stop it at the WDT instruction and press 'single-step' I get this requester again:

'Can't find a source file at "/run/shm/bazel-sandbox.50f2f2e12d21e0fb3bbe0ab1cf1c78eb/1214578678737256234/execroot/__main__/source/ti/devices/msp432p4xx/driverlib/wdt_a.c"
Locate the file or edit the source lookup path to include its location.'

If I continue to press 'single-step' I can see the CPU stepping forward in 'disassembly' and it does show the steps forward in 'main.c' but the requester just above remains as do the cautions about internal problems.

Not sure if that helps
Tuatha De

One more note:

I plugged my MSP430G2ET launchpad in place of the 432 and the '430 loads and runs its own 'blink' program without any problems or requesters turning up.

If I breakpoint it at WDT it single-steps normally after it stops but it does turn up this RED note:

'MSP430: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0xc000: Software breakpoint conflicts with one or more enabled hardware triggers'

Although I've only got the one WDT breakpoint set or active. With my breakpoint removed that red warning disappears.

Hitting 'console' in the top bar with 'main.c' in it causes no changes.

After re-programming the '430 several times this note turns up:

'MSP430: Warning: On-board LDO is now used to supply the target with power'

I have done no programming to cause that change in the LDO.

But everything else seems to be working normally on the MSP430 Launchpad

Tuatha De

Hi Ki:

So far I'm spending a lot of time:

Viewing videos that are referring to Windows based systems, I'm MAC. Their panels don't look like mine and various references don't match MACs.

Reading lots of 'helpful' material that refers to pre-CCS9 versions which don't seem to have even the same MAC panels or requesters to choose from.

I tried 'resetting the perspective,' that did not help.

I tried to use the '-clean' Argument but cannot find the 'ccstudio(.exe)' to tack' -clean' onto so it cannot be run, where in MACOS is this file? Or is this a Windows reference, it is not clear what works with windows and what works with MAC at each point. There are piles of files even in CCS, where is this one?

I tried to clean the workspace by using the '.metadata' removal but cannot find it.

I would try changing workspaces altogether but there is no 'File-SwitchWorkspace' on the CCS9 File panel that I can find or on any other panels I've seen.

I would like to do a clean re-install of CCS9 but everything I read cautions that uninstalling my present CCS9 may not work cleanly and I may have to remove extra files that I have no information on how to find or clearly remove.

I have seen the suggestion that I bring in CCS9 again and simply re-title it CCS900, is it that simple or does that just add to the problems of the system trying to locate related files?

My problem seems to be that CCS9 is relating to my MSP432 launchpad but does not show any of the 'debug' symbols after I click on the bug symbol. CCS9 seems to load my launchpad after telling me to stop the present running program, which I have no symbols to control with so I cannot stop it and have to tell CCS9 to continue anyway but I have no debug control symbols (Start, Stop, Terminate) to operate the launchpad with.

Then it hits me with the complaint you've apparently never seen before:

'An internal error has occurred.

The selected element org.eclipse.debug.ui.DebugView=org.eclipse.e4.ui.model.application.ui.advanced.impl.PlaceholderImpl@6424c975 (tags: [View, categoryTag:Debug], contributorURI: null) (widget: null, renderer: null, toBeRendered: false, onTop: false, visible: true, containerData: null, accessibilityPhrase: null) (closeable: true) must be visible in the UI presentation'

Any ideas or can anyone else there help with this? My user-name has no non-ascii symbols.

Tuatha

Part Number: MSP432P401R

Tool/software: Code Composer Studio

Hi Ki:

I followed all the leads you've supplied and it appears I was missing one or more files. I found a list of 6 software updates and while three said I had everything they had to offer three said I did not. So I downloaded those three, restarted CCS and Voila! All of the 432 Build and Debug functions now work fine and I do not get any requesters/panels complaining of anything and the debug launchpad control symbols all appear and work as expected.

I may be premature as I just got it going but things look excellent at this point. Thanks a ton for the help!

Tuatha De